That last point is the one consultants most often get wrong. The brief is the company's description of its own system. You can help it ask the questions, and if you built the system you will know many answers, but the page stays with the company and never travels with your introduction.
When a homegrown system turns into a referral conversation
Custom systems rarely come up on their own. They come up when someone has to explain them, and those moments are worth noticing:
- A replacement is planned. The company is moving the work onto a commercial platform and has to decide what history comes across.
- The builder is leaving. The developer who wrote it, inside or outside the company, is retiring, changing jobs or ending a support contract.
- A documentation or rebuild project starts. Someone is finally writing down what the tables mean.
- The hosting changes. An old server moves to the cloud and somebody asks what is actually on it.
The natural sponsor is whoever commissioned the system and still owns the process it runs, often a COO, head of operations or CTO. That person can carry the idea to the CEO. The builder, whether an in-house engineer or you as the outside consultant, is the custodian: the one who knows how it works and who could export from it, with no say over licensing.
One published fact frames the conversation. SourceX's process page says that at the first step a company lists its systems, years of history and what can be exported, and that "qualifying companies list at least 5 systems, and no records are shared at this stage." A custom system is one line on that list, usually an important one. The brief makes that line intelligible.
The custom-system context brief
Google's Data Cards Playbook describes Data Cards as "structured summaries of essential facts about various aspects of ML datasets needed by stakeholders across a project's lifecycle for responsible AI development." The brief borrows that idea one step earlier, before any dataset exists, and stops at facts the company is willing to say aloud. (The Playbook itself notes it dates from 2022.)
| Question | What to write | Who answers | Leave out |
|---|---|---|---|
| 1. Purpose | The business process the system runs, in one plain sentence, such as "dispatch and job closeout for field crews" | The system's day-to-day owner | Screenshots, customer names on screens |
| 2. Lineage | The first year it held live records, each rebuild or rewrite since, and whether older records were carried across | The builder | Dates read off database logs for this purpose |
| 3. Builder and maintainer | In-house team, outside developer or both, who maintains it today and whether the original builder can still be reached | The CEO or owner | Contract terms and rates |
| 4. Record families | The kinds of records it holds, such as work orders, approvals, notes, change history, and the mix of coded fields, free text and attachments | The day-to-day owner | Sample records, field lists, table names |
| 5. History kept or overwritten | Whether the system keeps a trail of changes or overwrites a status when it moves on | The builder | Audit log extracts |
| 6. Volume band | Order of magnitude per record family, from a report the company already runs, marked as an estimate | The day-to-day owner | Counts you queried yourself |
| 7. Documentation | Whether a schema, data dictionary or runbook exists, and roughly when it was last updated | The builder | The documents themselves |
| 8. Whose content | Roughly how much the company's own staff created and how much came from clients or the public | The CEO, with counsel if unsure | Any statement that rights are clear |
| 9. Export path | How an export could be made, as the builder describes it: a report, a database dump, an interface | The builder | Credentials, connection strings, hostnames |
Two of these matter more for custom software than for a commercial product.
Question 5 decides whether the history is a history. A commercial helpdesk usually records every reply and status change. A system written in-house to run a process may keep only the latest state of each job, and then fourteen years in operation can mean fourteen years of final answers with none of the steps that led to them. Only the builder knows.
Question 9 replaces the vendor's export guide. Nobody can look up how to get data out of a system that exists in one company. The builder's plain description is enough at this stage; actually making an export waits until the company has signed with SourceX and SourceX has set the processing route.
The no-upload approach behind the brief is the one SourceX describes for its own first assessment: eligibility, record families, history and volume bands, linkage and the content mix can be settled from settings, reports, counts and documents, while quality, the exact de-identification effort and value need a reviewed sample later, under agreed terms.
Builder, owner and reviewer each hold a different piece
A custom system blurs roles that a commercial product keeps apart, because the person who wrote the code may also run the servers and know the data better than anyone. Keep three jobs distinct.
The builder or maintainer knows the tables, holds database access and works under a development or support agreement. That knowledge makes them the best person to answer questions 2, 5, 7 and 9, and it gives them no authority over licensing. If the builder is you and you are also the referring partner, section 4.2 of SourceX's sample partner agreement is plain: the referral gives a partner "no authority to share a supplier's inventory, records, raw data or personal information, or to access extraction systems."
The company owns the records, subject to SourceX's rights review, and decides. The CEO authorizes a licensing discussion; the operations owner prepares answers. SourceX's screening page asks for documentation the company created itself, such as SOPs, project histories, QA records and support workflows, and treats material that belongs to its clients as usually not a fit. Question 8 exists for that reason.
SourceX checks fit, completes the inventory with the company, runs the rights check and sets the processing route, and its process page says the records stay with the company while it aligns the deal. Whether the system's code or engineering history could ever be in scope is a question the company can raise with SourceX; who owns code written by an outside developer is a question for the company's own counsel. Neither belongs in a partner's introduction.
Introducing the CEO without an export or a number you measured
Your introduction carries three things: the company's name, the CEO's name and the fact that the CEO asked to be introduced. If the CEO agrees, add one plain sentence, such as "a 180-person freight audit firm whose main system is custom-built". That is all.
Leave out every figure you know as the custodian. Row counts, database sizes and the date of the oldest record are the client's information even when you are sure of them, and an estimate you measured yourself carries more authority than it deserves. The company states its own bands when it applies.
Before you send anything, ask one question: has anyone at the company already contacted SourceX? Under section 3 of the terms an earlier lead, account or email exchange makes the company a duplicate, and then it simply continues directly. If the company has changed core systems several times, the timeline method for repeated migrations pairs well with question 2.
Fit facts to ask about before the brief
The brief is wasted effort if the company fails a basic check. Ask the CEO first: did full-time headcount reach 50 or more at its peak, leaving contractors out? Does the company have several years of records from its own operations? Can it license them without breaching client confidentiality or other contracts? 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. Records ever licensed for AI training are excluded. For a first, non-binding screen, the CEO can try the company fit checker alone.
A freight audit firm and its fourteen-year-old platform (Illustrative)
Illustrative. The firm and its people are fictional, and no outcome is implied.
A 180-person freight audit firm runs claims and invoice disputes on a platform an outside developer built in 2011. The developer, now retiring, has maintained it under a support agreement ever since. During the handover planning the COO asks what the platform "is worth", and the developer suggests the COO raise data licensing with the CEO instead of guessing.
The CEO wants to hear more. The COO answers questions 1, 4 and 6: dispute handling from claim to settlement, case records with adjuster notes and attachments, "hundreds of thousands" of cases. The developer answers 2, 5, 7 and 9 inside the COO's document: live since 2011 with one rewrite in 2017 that carried everything across, a full change trail on each case, a data dictionary last updated in 2019, and exports by database dump. The CEO answers 3 and 8 and flags that some attachments are carrier documents, a question for review. The firm keeps the page.
The developer, already registered as a SourceX partner, sends a two-line introduction. The firm applies and lists the platform alongside its accounting, document, email and phone systems. If a license later closed and SourceX paid the firm USD 100,000 under its agreement, the developer's reward on that first qualifying transaction would be USD 55,000 (the greater of USD 50,000 plus 5% and 15% of the Actual Supplier Payout), paid by SourceX on its own account and not drawn from the firm's compensation.
Where the brief falls short
- It is only as good as the builder's memory. If the original developer is gone, questions 2, 5 and 9 may stay unknown. Write "unknown" rather than guess.
- It cannot judge quality or value. Those need records, reviewed later under agreed terms, and SourceX does not publish how it prices offers.
- It cannot settle rights. Question 8 flags where rights questions sit; counsel and SourceX's review answer them.
- Self-referral is different. If you are the company's own CTO, the company can simply apply; whether an insider can be a referring partner is covered in can a business owner refer their own company.
- No outcome data exists. Nobody has published how custom systems fare in licensing reviews. To learn it, record for each brief how many questions were answered, unknown or refused, and whether the company applied.
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 the CEO has read the company's brief and asked to talk to SourceX, set up your partner account, check the company once more against who qualifies and go through the program terms before you send a two-line introduction. Other technology-partner playbooks are collected in the guides library, and the program overview for IT service firms is on the managed service providers page.