How can an introducer check whether an operational workflow has a complete evidence trail?
Ask for a continuity count, not a sample. The company picks a handful of finished cases, follows each from start to finish in its own systems, and tells you which links held. You learn the shape of the trail without handling data.
Why this matters: buyers in this market describe their target as workflow data, meaning records of how work moved, not isolated documents. Mercor, for example, says it licenses, packages and pays for business workflow data. A pile of tickets with no link to the engineering fix, or invoices with no link to the approval, describes moments of work rather than a workflow. The workflow data explainer covers the general idea; this page gives you a test.
The five-hop trace: a field-level linkage sample
Illustrative. A fictional 350-person B2B software company traces one support case from first contact to confirmed fix. All IDs and dates are invented.
| Hop | From record | To record | Linking key | Where the key lives | Linked by ID? |
|---|---|---|---|---|---|
| 1 | Support ticket 48211 opened | Escalation to tier 2 | Same ticket ID; assignee and group change | Ticket change history | Yes |
| 2 | Tier 2 escalation | Engineering bug ENG-3307 | Ticket ID stored on the bug; bug key stored on the ticket | Both records | Yes |
| 3 | Bug ENG-3307 | Code change merged | Bug key in the change description | Source control | Yes |
| 4 | Code change | Release 7.4.2 | None; release notes describe the fix in words | Release notes document | No: matched by date and wording |
| 5 | Release 7.4.2 | Ticket 48211 solved | Bug key in the closing note; ticket not reopened in 30 days | Ticket change history | Yes |
Result: four of five hops linked by ID, one inferred. That is a strong but not perfect trail, and the weak hop is a common one: engineering and release management often keep separate records.
The keys in this table are ordinary system features, not special projects. Helpdesks typically keep a change history; Zendesk, for instance, records each ticket update as an audit containing events that show the field changed, its new value and its previous value. Engineering trackers support explicit links between items; Jira's link types include blocks, duplicates and relates to, and admins can add their own. Whether a given company used those features consistently is exactly what the trace reveals.
How to run the count without touching data
Give the company's operations or support lead this script. It takes an hour, and all of it happens inside the company.
- Pick twenty cases closed at least three months ago, chosen at random rather than hand-picked.
- For each, name the first record (the request) and the last (the confirmed resolution).
- Follow each hop and note whether the next record is reached by a stored ID, by date and wording, or not at all.
- Report three numbers: cases traced end to end by ID, cases traced with at least one inferred hop, and cases that broke.
- Name the hop that breaks most often, and the systems on either side of it.
Ask for the counts and the weak hop, nothing else. Do not ask for ticket numbers, screenshots or exports. SourceX publishes no benchmark for what a "good" count is; the point is to give SourceX an honest starting picture, not to pass a threshold.
| What you hear | What it suggests | Next move |
|---|---|---|
| Most cases trace end to end by ID | A continuous trail across systems | Introduce the decision-maker |
| Most trace with one inferred hop | Strong core, one weak seam | Introduce, and mention the weak hop |
| Most break at the same hop | Two separate archives | Introduce if each side is deep; scope may narrow |
| The team cannot find closed cases from three years ago | Retention or migration gap | Ask what was migrated, and when |
Large companies with several overlapping tools need extra care at step 3; the guide on assessing companies with fragmented business systems covers that case. For support specifically, identifying tickets with useful resolution context and the ITSM ticket history page describe what a rich ticket looks like, and the software workflow example pack shows sample chains in other software functions.
Company qualification questions
Beyond the trace, the usual qualification questions apply, all at metadata level.
| Ask | Strong answer | Why it matters |
|---|---|---|
| Which systems sit on each side of the weak hop? | Named tools with dates in use | Shows where linking might be reconstructed |
| Were any systems migrated, and was history carried over? | Yes, with full history | Migrations are the most common cause of breaks |
| How many years does the trail cover? | Five or more | Depth |
| Do customer contracts restrict use of support records? | Not known yet, or a short list | A rights question SourceX reviews |
| Who can authorize a licensing discussion? | CEO, or the owner in an owner-run company | The sponsor to introduce |
The introduced company needs 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records and an authorized contact. 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.
What stays unknown until SourceX reviews it: buyer interest in this workflow, redaction of customer and employee details, the rights review result and any offer.
Limits and unanswered questions
A continuity count measures linkage, not value. A perfectly linked workflow can still be one buyers do not currently want, and a trail with a weak hop can still be useful. This page makes no claim about what any trail is worth, and SourceX has not published continuity benchmarks.
Company compensation and referral rewards are separate. The company is paid under its own agreement with SourceX. The partner's reward is calculated on what SourceX actually pays the company, is funded separately and never reduces that payment. Illustrative only: on a USD 800,000 first qualifying transaction, the reward would be USD 120,000, since 15% of the payout exceeds USD 50,000 plus 5%; there is no cap, and the USD 50,000 floor applies once per company. See how rewards work.
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's trace shows most cases reaching resolution by ID, register as a partner, check the company against who qualifies and read the program terms before introducing its decision-maker. More evidence-trail topics are in the guides hub.