The vertical is what makes this workable. When every customer does the same kind of work, one honest judgment about whose records a segment keeps covers hundreds of firms, and your team already speaks the industry's language. The same concentration makes trust fragile: a clumsy message reaches the whole network at once.
Why one vertical makes the relevance question easier and the trust question harder
A horizontal tool serves companies whose records have little in common, so relevance has to be judged customer by customer. A vertical platform serves firms whose work orders, dispatch notes, project files or service histories look alike. That lets you reason about a segment's records from the workflow alone, without looking at any customer's content. The vertical AI training data guide maps which industries hold which kinds of records.
Trust runs the other way. Customers in one industry talk to each other, attend the same events and compare vendors. If one firm hears "your vendor wants to sell your data", the whole network hears it. Many customers already wonder what their vendors do with their records, which is why whether a SaaS vendor is training AI on customer data is a question in its own right. The conversation below is designed so that nobody can mistake it for that.
Your own company's records are a different matter. Whether a vertical SaaS business should license its own operating history is covered in the SaaS data partner guide, and the strategic question of where AI leaves vertical software is analyzed on sourcex.si in what private software owners should do. This page is only about introducing customers.
The benefit has to be the customer's, and so does the decision
The genuine benefit is simple to state. A customer firm with years of its own operating records may license them directly to SourceX for AI training and evaluation and be paid by SourceX under its own agreement. The vendor is not a party, does not handle records and has no say in terms. What the vendor gains is a useful conversation with a customer that has nothing to do with renewal, and possibly a referral reward that it discloses.
The sponsor inside a customer firm is usually whoever runs operations and knows where the history lives: an operations director at a contractor, a head of service at a maintenance firm. The decision to discuss licensing, and the signature, belong to the CEO. Your account team's ask is therefore to the operations sponsor, to raise the idea with the CEO, or directly to an owner-CEO your team already knows.
The vertical customer relevance guide
Score each segment, not each customer, on five tests. Every answer comes from your knowledge of the industry's workflow or from what customers say publicly or tell you, never from what your product can see.
| Test | 2: strong | 1: check | 0: fails | Where the answer comes from |
|---|---|---|---|---|
| Size | Most firms had 50+ full-time employees at peak | Sizes are mixed | Most firms are under 50 | Public company facts or what customers tell you, never seat counts |
| Whose records | The firms' own operating records: work orders, dispatch notes, project files, quality checks | Own records mixed with personal data of the firms' customers, tenants or patients | Mostly material that belongs to, or is controlled by, the firms' clients | How the workflow runs, not any customer's content |
| History | Several years of records still held | Records split by a migration or archive purge | Only recent records survive | What customers say about their own archives |
| CEO path | Owner-CEOs your team already knows | Reachable through an executive sponsor | Only a tool-admin relationship | Your account plan |
| Place | Firms are in the U.S., Canada or the EU | Firms elsewhere on the eligible list, English share unknown | Firms outside the eligible list | Where the firms say they operate |
Decision rule. A 0 on size or on whose records leaves the segment out, whatever the total. Otherwise, 8 to 10 points means invite the segment by opt-in; 5 to 7 means individual conversations only, through an executive sponsor; 4 or less means leave it out for now. The thresholds are a working method, not measured results.
The place test follows the published rule. 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 "whose records" test follows SourceX's published screening, which lists personal consumer data, data the company does not control and material belonging to clients as usually not a fit. A 1 on that test is not a rejection: mixed records go to SourceX's rights review, which decides what, if anything, a license could cover.
One field-service network scored (Illustrative)
Illustrative. A generic field-service management platform with invented segments and scores; no real companies or outcomes.
| Segment | Size | Whose records | History | CEO path | Place | Total | Decision |
|---|---|---|---|---|---|---|---|
| Multi-branch commercial mechanical contractors | 2 | 2 | 2 | 1 | 2 | 9 | Invite by opt-in |
| Multi-site property maintenance firms | 2 | 1 | 2 | 1 | 2 | 8 | Invite by opt-in; tenant data flagged for review |
| Franchise brands and their franchisees | 1 | 1 | 1 | 1 | 2 | 6 | One by one, through a sponsor |
| Facilities outsourcers working inside their clients' accounts | 2 | 0 | 2 | 1 | 2 | 7 | Leave out: the records are their clients' |
| Owner-operated residential trades firms | 0 | 2 | 1 | 2 | 2 | 7 | Leave out: under 50 full-time employees |
Two rows show why the zero rule exists. The facilities outsourcers are large and well documented, but they work inside accounts their clients own on your platform, so the client controls those records; a high total does not rescue them. The residential trades firms have excellent records and warm owner relationships, and they still fail the size test. Franchise systems sit in the middle because the franchise agreement decides who owns which records, as the franchise data ownership page explains.
What a vertical vendor holds, and what it may do with it
A vertical platform often hosts the most sensitive records in its industry, and regulation in many verticals makes the vendor's position explicit. Under Article 28 of the EU's General Data Protection Regulation, a processor must process personal data only on documented instructions from the controller. In U.S. healthcare, HHS's sample business associate provisions limit a business associate to using or disclosing protected health information only as its contract permits or the law requires. A referral program is not among the instructions your customers gave you, which is why the relevance guide never reads customer content.
The same logic covers usage analytics: telemetry tells you how customers use your product, not whether they want a licensing conversation. The rules for keeping it out are set out in keeping usage analytics out of customer referrals.
Be explicit about your role category. Even Microsoft's co-sell documentation, which describes co-selling as collaborative engagement that includes building demand, sales planning and sharing sales leads, separates deals worked with Microsoft sales teams from partner-to-partner deals and private deals shared only for reporting. Your category with SourceX is narrower than any of those: introduction only, with no joint sale, no records handled and no say in terms. Write that sentence into every invitation.
The conversation, line by line
Five lines, in this order, given by whoever owns the relationship with the operations sponsor or the owner-CEO.
- Why you are raising it. "SourceX licenses business records directly from established companies for AI training and evaluation, and some firms in our industry keep the kind of operating history it reviews."
- What it is not. "This is between your company and SourceX. We see none of your records for it and have no part in any deal."
- Who decides. "Your CEO decides whether to talk. If they want to, we make an introduction, and SourceX reviews fit, rights and its current needs."
- The disclosure. "We may receive a referral reward from SourceX. It is paid separately and never comes out of your payout."
- The exit. "If it is not for you, nothing changes in our relationship or in your product."
Leave out anything that sounds like knowledge of the customer's data ("we noticed you have years of jobs in the system"), any figure for what a firm might earn, any claim that other customers are licensing, and any deadline.
Customers who ask how rewards work deserve a straight answer from the published terms. As Illustrative arithmetic only, if SourceX's Actual Supplier Payout to a firm on its first qualifying transaction were USD 100,000, the default reward to the introducing partner would be USD 55,000 (the greater of USD 50,000 plus 5% and 15%), paid by SourceX on top of, not out of, the firm's payout.
Start with one segment and a stop rule
Pick the highest-scoring segment and invite it through a channel its members already chose, such as a session at your user conference or your customer advisory board. Count each stage separately: invitations, opt-ins, sponsors who raise it with their CEO, CEOs who want a conversation, and trust concerns raised. Decide in advance that a single complaint about data handling pauses the pilot. No results from vertical networks running this kind of pilot have been published, so your own stage counts are the evidence. The opt-in customer cohort pilot sets out a fuller design.
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.
Once a segment scores 8 or more and a customer's CEO wants the conversation, register for a partner link, check the firm against who qualifies and read the program terms; the partner signs the SourceX Channel Partner Agreement before submitting. The software and SaaS industry page and the guides hub cover neighboring cases.