Volume headlines play no part in fit. The published screening asks for 50 or more full-time employees at peak, years of original documentation the company created itself, rights to license it, an authorized sponsor and relevance to a current program, and it lists personal consumer data and material that belongs to clients as usually not a fit. A transaction business can pass all of that. It rarely passes on the strength of the transactions themselves, which is why the growth-versus-suitability plot never lets volume stand in for the score.
Name the metric before you read the surge
"Transaction growth" covers several different counts, and each describes somebody's activity in a different way.
| Metric as announced | What it counts | Whose activity it mostly describes |
|---|---|---|
| Transactions processed | Payments or messages handled for clients | The clients' own customers |
| Gross volume, such as GMV or TPV | Money moving through the platform | Buyers and sellers, valued in their money |
| Orders or order lines | Sales the company itself made | The company and its business customers |
| Claims, tickets or cases handled | Work items the company resolved | The company's staff, and the people they served |
Record every surge with its metric, period, source and date. Two figures with different metrics are not a trend. A gross-volume figure says least of all about records, because it measures other parties' money rather than the company's work. An orders figure says the most, because each order is a sale the company made and handled.
The volume-versus-rights question matrix
Take any transaction the company handles and separate it into five layers. Ask the same four questions of each.
| Layer | Grows one-for-one with volume? | Who usually decides how it is used | Usual fit on the screening profile | Metadata question for the CEO |
|---|---|---|---|---|
| 1. The transaction record: amount, time, parties, status | Yes | The client whose sale it is, when the company processes on its behalf; the company itself when the sale is its own | Client-owned material is usually not a fit; the company's own sales records can be | Are these your sales, or sales you process for clients? |
| 2. Personal data of consumers or cardholders | Yes | The client, as controller | Personal consumer data is usually not a fit; card data also falls under PCI DSS | Which systems hold consumer identities, and can they be kept apart? |
| 3. Client business data handled for them, such as catalogs or invoices | Roughly | The client | Usually not a fit | Which records do your client agreements say are theirs? |
| 4. The company's handling work: exceptions, disputes, fraud reviews, routing decisions, support tickets | No; it grows with problems, not with count | The company, subject to client contracts and privacy | Can fit: original documentation of the company's own work | How many years of exception and dispute notes, in which system? |
| 5. The company's procedures: SOPs, QA reviews, policy changes, training material | No | The company | Strong candidate, if the company wrote it | Who maintains the procedures, and since when? |
Layers 1 to 3 grow with every transaction, and they are where most volume headlines live. In the EU framework, the client that decides why and how its customers' personal data is processed is the controller; a company handling that data on the client's behalf is a processor. The European Commission adds that a processor which uses the data for its own purposes becomes a controller for that use. Licensing client transaction data for AI training would be such a purpose, so client contracts and privacy law decide whether it is possible at all. Card payments carry a standard of their own: PCI DSS applies to entities that store, process or transmit cardholder data, including merchants, processors, acquirers, issuers and service providers. A payments surge widens that compliance scope. It does not widen what the company may license.
Layers 4 and 5 are the company's own work. They grow when transactions go wrong, when rules change and when the company teaches new staff how it decides, which is exactly the documented judgment the screening profile describes. For the general test of what makes records licensable, see what makes a dataset licensable.
Method note. Layers and questions were built on 2026-10-26 from the published screening profile, the program terms, the European Commission's controller and processor guidance and the PCI Security Standards Council's description of PCI DSS scope. The matrix sorts records by who controls them. It does not measure buyer demand, record quality or what any license would pay; SourceX's rights review and relevance check settle those.
A payments surge and an order surge under the same questions (Illustrative)
Illustrative. Two generic companies with invented details; no outcome is implied.
A 450-person payment processor for independent restaurants says its processed transactions tripled between 2023 and 2025. A 260-person industrial fasteners distributor founded in 1987 says its order lines rose 40% after it opened a B2B web store in 2024. Most screens would put the processor first. The matrix reads them differently.
| Question | Payment processor, transactions tripled | Fasteners distributor, order lines up 40% |
|---|---|---|
| Size at peak | 450 full-time employees | 260 full-time employees |
| Layers 1 to 3 | Nearly all of the surge is restaurants' sales and cardholder data, processed for clients | Orders are sales the distributor made; buyers are business contacts |
| Layers 4 and 5 | Chargeback dispute notes since 2016, merchant risk reviews and support tickets | Quote revisions, returns and supplier lead-time corrections in its ERP since 2009; written procedures for pricing exceptions |
| Rights questions | Merchant agreements, consumer personal data, PCI DSS scope | Confidentiality clauses in customer contracts and supplier price lists |
| Authorized path | Founder-CEO, reachable through a board member | Owner-CEO, reachable through an LP |
| What the matrix says | A narrow candidate: layers 4 and 5 only, if the company controls them | A broader candidate: its own sales plus its handling work |
The processor's number is the more impressive one, and almost none of it is the processor's to license. The distributor's number is modest, and most of what sits behind it is its own. Neither row is accepted or declined by this table; it tells you which question to ask first.
How much history sits behind the surge?
A surge compresses activity into the most recent periods, so test it with three questions before you count it as history.
- When did the company start handling this kind of transaction? A process with fifteen years behind it is different from a product line launched last year.
- Did the process exist before the surge? The distributor's web store is new, but its ERP order history runs back to 2009, so the surge adds a channel on top of fifteen years. A company whose entire volume arrived with a new product holds months of history, however large the count.
- Did the surge come with a new system? Records before a cutover may sit in an old platform. A documented retirement date for that platform is the one real deadline in this picture, because retired systems can take their history with them.
Rank the shortlist by controlled share, ownership and operating load
Order candidates on these keys, in this order:
- Controlled share. How much of the record base sits in layers 4 and 5, or in sales the company made itself, by the CEO's own rough estimate.
- Process history. Years the company has handled this work, not years since the surge.
- Ownership. A pending sale moves the decision to the buyer's CEO; a parent and its subsidiaries count as one company for the reward cap.
- Operating load. A team in the middle of a surge, a peak season or a platform migration has little time for a licensing review; record a date and ask after it.
| Rank | Company (Illustrative) | Controlled share | Process history | Ownership | Operating load |
|---|---|---|---|---|---|
| 1 | Fasteners distributor | High | 39 years | Owner-run, settled | Normal |
| 2 | 180-person freight claims administrator | High in layers 4 and 5 | 14 years | Settled | Peak season ends in January |
| 3 | Payment processor | Low, layers 4 and 5 only | 10 years | Settled | Migration under way |
| 4 | 90-person marketplace launched in 2024 | Low | 2 years | Sale announced, not closed | Integration ahead |
For the portfolio side of the program, see the overview for venture platform teams, and test single companies with the company fit checker.
Where volume-first screening, and this matrix, can fail
- Contracts can cut both ways. Some client agreements grant broad rights to use processed data, which would open layers 1 to 3; others restrict even layer 4. Only SourceX's rights review reads them.
- Volume is not value. The matrix sorts by control, not by worth. Whether a company's handling records match a current program is checked in review.
- Personal data runs through every layer. Dispute notes and support tickets name people too. A layer marked "company" still goes through privacy review.
- Metrics are defined by the company. "Transactions" in one announcement and another may not count the same thing, and gross volume can rise with prices while activity is flat.
- Substitutes may narrow demand. If AI developers find synthetic or public stand-ins for some record types, the handling layers that look strongest here could matter less.
A measurable next step. Take ten companies in your network whose growth story is transactional and fill the matrix for each from what their CEOs or relationship owners already know. Count how many have a layer 4 or 5 with at least five years of history. After a quarter, compare conversation outcomes between the high and low controlled-share groups. SourceX has not published conversion data by business model, so that comparison would be yours alone.
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.
When a company's matrix shows years of handling work it controls and its CEO wants a conversation, register for a partner link, confirm the basics on who qualifies and read the program terms before you submit.
Screening transaction businesses is referral work; if the question on your desk is SourceX as an investment, treat it on its own and ask for materials through the SourceX investor overview.
This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.