Does a client's permission-aware agents data qualify? A 12-point approval-records scorecard for introducers

Short answer

Run three yes-or-no gates, then score six criteria from 0 to 2. The gates: 50 or more full-time employees, a named CEO who can authorize a licensing talk, and a location the program covers (outside the U.S., Canada and the EU, that also means at least 70% English records). The criteria: monthly volume of second-approver changes, system-enforced separation of requester and approver, retention beyond the tool's default window, request-to-action linkage, recorded outcomes, and rights clarity. Ten or more of 12 is a strong fit.

Visual briefFull-size diagram
A semicircular gauge with weak, borderline and strong bands; as six approval-record criteria are ticked beside it, the needle settles at 10 of 12 in the strong band for a fictional engineering firm.
Illustrative score for a fictional 380-person engineering firm. The scorecard is a conversation aid, not SourceX's review.

This scorecard is part of the guide to permission-aware agents and the second approver, which traces one account change minute by minute. That guide explains the concept. This page turns it into a scoring exercise for a call with an IT director, head of security or controller, using answers only, never files.

Three gates before any scoring

A gate is pass or fail. If one fails, stop: the approval records may be excellent, but the company cannot be introduced yet.

GatePasses whenQuestion that settles it
Size50 or more full-time employees at peak, contractors excluded"What was your full-time headcount at its highest?"
AuthorityThe CEO is named and could authorize a discussion about licensing IT and approval records"Who would sign off on anything involving your identity or ticketing data?"
Location and English shareThe company is in a covered country; outside the U.S., Canada and the EU, at least 70% of tickets, justifications and notes are in English"Where is the company based, and are request reasons and ticket notes written in English?"

Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English. The company also needs documented operating history and rights to license, which criteria 3 and 6 test in more detail.

Six criteria, each scored 0, 1 or 2

Ask in this order. Criteria 1 and 2 establish that permission-gated work happens and is enforced; 3 and 4 establish that its trail survives and connects; 5 and 6 establish that it can be judged and licensed.

Criterion2 points: strong1 point: borderline0 points: weak
1. Volume of gated changesAdmin role use, payment releases, credit limit or price overrides need a second approver hundreds of times a yearDozens a year, or only in one departmentRare, or approvals happen verbally
2. Enforced separationThe system blocks self-approval and records blocked attemptsSeparation is policy only, checked in auditsRequester and approver are often the same person
3. Retention beyond defaultApproval and audit records archived outside the tool for several yearsArchived for a year or two, or only some systemsOnly what the tool keeps by default
4. Request-to-action linkageA ticket or change ID ties request, approval and action, and is validatedThe ID is typed by hand and mostly rightNothing connects the approval to the ticket or action
5. Recorded outcomeTicket closure, user confirmation or reversal is logged against the changeClosure is logged without the resultThe change is made and nothing records whether it worked
6. Rights clarityThe company owns its IT and approval records; no known provider term limits useAn MSP or outsourcer's contract has not been checkedA parent company, client or outsourcer controls the records

Two sources explain why criteria 2 to 4 carry weight. Microsoft's documentation for Entra Privileged Identity Management says approvers can't approve their own activation requests, which is what system-enforced separation looks like. The same documentation says ticket information entered at activation is informational and not checked against any ticketing system, so linkage often depends on someone typing the right number. And Entra keeps audit logs seven days on the Free tier and 30 days on P1 and P2 unless they are routed to longer-term storage; expired data that was not archived cannot be recovered. A company scoring 0 on criterion 3 may hold years of tickets but almost no approvals.

Strong, borderline and weak fits

Add the six scores. The bands are a guide to the next action, not a verdict.

TotalBandWhat it usually looks likeNext action
10 to 12StrongEnforced approvals, archived logs, ticket links and outcomes across several yearsIntroduce the CIO, COO or CEO
6 to 9BorderlineApprovals exist, but retention is short or linkage is manualAsk whether audit logs were ever exported or archived, then decide
0 to 5WeakApprovals are informal, unlinked or goneNote the company for later; do not introduce yet

A borderline score often turns on one fact the IT director can find in a day, such as the date audit-log archiving began. That is worth asking for before the introduction, not after.

A worked score (Illustrative)

Illustrative and fictional. A 380-person civil engineering firm in Canada gives these answers on a discovery call with its IT director:

CriterionAnswer givenScore
1. VolumeAbout 90 admin role activations and 40 payment releases need a second approver each month2
2. SeparationIdentity tool blocks self-approval; payment release is enforced in the ERP2
3. RetentionAudit logs streamed to an archive since 20212
4. LinkageChange number required on activation, but typed by hand and not validated1
5. OutcomeTicket closure notes record the result; reversals are linked2
6. RightsRecords are the firm's own; the managed service provider contract has not been reviewed1
Total10 of 12, strong

The two single points are honest borderline answers, not disqualifiers. Hand-typed change numbers mean some approvals will not link to their ticket. The MSP contract may or may not limit use; SourceX's rights review, not the introducer, settles it. The firm is worth introducing, with both points noted.

Questions that move a borderline score

Five follow-ups, asked in plain language, settle most borderline answers. None needs the phrase "permission-aware agents".

  1. "Which changes need a second person to approve, and roughly how many a month?" (criterion 1)
  2. "Can someone approve their own request, or does the system stop it?" (criterion 2)
  3. "How far back can you see who approved an admin change, and is that kept outside the tool?" (criterion 3)
  4. "When someone approves access, how do you tie it to the ticket and to what was actually changed?" (criterion 4)
  5. "Who owns these records, and is any of it held by an outside provider?" (criterion 6)

Keep the call at metadata level: which systems, how many changes, how many years, who owns them. Partners never ask for logs, screenshots or tickets. If you need a warm route to the IT director, the guide to introducing two people on LinkedIn covers it. The company qualification checklist and the introducer guide to operational data licensing cover the wider basics. Authority inside a task is not the same as the company's right to license; that distinction is in de-identification versus permission to license.

After a strong or borderline score, the evidence gaps analysis shows what is likely to be missing, and the review packet contents list shows what the company would assemble later. Other record families are in data types.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If a client clears all three gates and scores 10 or more, or a borderline score you can explain, register as a partner, confirm the details on who qualifies, and read the program terms before you introduce the decision-maker.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Does a score of 10 mean SourceX will accept the company?

No. The scorecard helps an introducer decide whether a conversation is worth having. SourceX's review decides what is usable, and SourceX's current data needs, rights and de-identification are all assessed there.

Who at the client can answer these questions?

Usually the IT director or head of security for system access changes, and the controller for payment releases or credit limit changes. Twenty minutes with one of them is normally enough, and nobody needs to open a log.

What if the company uses an identity tool other than Microsoft Entra?

The scorecard does not depend on the product. What matters is whether requests, approvals, actions and outcomes are recorded with a person and a time, and kept long enough to matter.

Sources

  1. learn.microsoft.com/en-us/entra/id-governance/privileged-identit…
  2. learn.microsoft.com/en-us/entra/id-governance/privileged-identit…
  3. learn.microsoft.com/en-us/entra/identity/monitoring-health/refer…
  4. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment