The discipline matters because "we own it" compresses several different statements into three words. A founder can be sincere about all of them and right about only some, and the partner who repeats the claim as fact has lent it credibility nobody checked.
Five meanings hiding inside "we own the data"
Most ownership claims are one of five statements, or a mix. Each can be true while the others are false, so the handoff note keeps them apart.
| When the founder says | It may mean | What can make it untrue | What goes in the note |
|---|---|---|---|
| "We created all of it." | Employees produced the records as part of their jobs | Contractors, agencies or clients wrote part of it | Who wrote the records: staff, contractors, agencies or clients |
| "It's our system." | The company runs the software that holds the records | The content describes customers' work and belongs to them | Whose activity the records describe: the company's own operations or its clients' |
| "I own the company." | The founder holds shares, perhaps a majority | A sale, recapitalization or investor rights moved control | Who controls the company today and since when, as the founder states it |
| "Nobody else has a claim." | The founder knows of no dispute | Confidentiality terms, privacy promises, a former partner or an earlier license | Any contract, dispute or earlier license the founder mentions, without asking for the document |
| "I have the files." | The founder personally holds archives | They were created at another company or a previous employer | Which entity created them; they travel separately or not at all |
The first row is where sincere founders most often overreach. The U.S. Copyright Office explains that a work an employee creates within the scope of employment is a work made for hire, with the employer treated as its author and owner, and that hiring or paying someone to create a work does not by itself make them an employee. Records produced by outside contractors or an agency can therefore sit on a different footing from those written by staff. Whether they do is for SourceX's rights review and the company's counsel; the partner only writes down who did the work.
The second row is the most common reason a confident claim fails. A company that hosts or processes records for its clients controls the system but often not the content, and SourceX's published screening criteria list material that belongs to clients, and data the company does not control, as usually not a fit. For software companies the question of customer data in a SaaS product shows how that line usually falls.
Place the claim on an entity, a controller and a CEO
A claim needs three anchors before it means anything. The operating entity: the company that employs the people and keeps the records, not a holding company and not the founder personally. The controller: who holds a majority or otherwise controls that entity today, with the month and year the founder gives. The CEO: the person who authorizes a licensing discussion and signs for the company.
If the founder is the CEO, the founder authorizes. If the founder has become chair, a minority holder or an adviser after a sale, the CEO authorizes and the founder's enthusiasm is sponsorship. Where two founders each hold half, or a trustee or court controls the company, the CEO alone may not be enough; note it. The intake in asking about ownership without a diligence project collects these anchors in one call. This page starts where that intake ends: the founder has already made the claim, and the question is what to do with it.
The ownership assertion-to-review handoff
Five stations, each with one thing the partner does, one thing the partner never does and one output. The handoff ends when SourceX's review takes over.
| Station | The partner does | The partner never does | Output |
|---|---|---|---|
| 1. Hear | Writes the founder's words verbatim, with the date and the speaker's role | Paraphrases them into "ownership confirmed" | One quoted sentence |
| 2. Place | Names the operating entity, the controller with a date, and the CEO | Asks for a cap table or share agreements | Three anchors |
| 3. Decode | Marks each of the five meanings as stated, unknown or contradicted | Decides which records are licensable | A five-line decoder |
| 4. Describe | Notes record types, systems, years, rough volume and who created them | Requests samples, exports, screenshots or logins | A metadata summary |
| 5. Hand off | Sends the note with an introduction the CEO wants, or the company applies itself | Promises acceptance or puts a figure on the records | Introduction made; the partner steps back |
An annotated handoff note (Illustrative). A generic 190-person freight company; invented facts.
| Field | Entry | Why it is written this way |
|---|---|---|
| Assertion | "Every dispatch record is ours; we built that system ourselves." Founder and CEO, video call, 21 October 2026 | Quoted, dated and attributed, so nobody later mistakes it for a finding |
| Entity | The operating company that employs the dispatchers, not the founder's holding company | Ownership attaches to an entity |
| Controller | Founder 70%, a family office 30%, per the founder on 21 October 2026 | Stated, not proven, and dated |
| Authorizer | The CEO, who is the founder | Names the person who can say yes |
| Who created the records | Company dispatchers and service staff; carrier rate sheets come from outside brokers | Separates staff work from outside material |
| Whose content | Company operations, plus shipping documents uploaded by customers | Flags a client-content question for review |
| Contracts or disputes mentioned | Shipper agreements with confidentiality terms; no dispute known | Mentioned, not read |
| Status | Ready for SourceX review, two open questions noted | Never "qualified" or "approved" |
The note is short on purpose. Everything a reviewer needs to ask the right questions is there; nothing in it pretends to answer them.
Three checks a confident founder still has to pass
Ownership is one gate. The claim says nothing about the others.
- The program. SourceX's current data needs differ in company size, operating history, geography, language and data category, and SourceX applies the criteria of the specific program rather than one universal minimum. Relevance is checked in review. Falling short of one program's criteria does not close the door on another program later.
- Size and place. 50+ full-time employees at peak, contractors excluded. 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 English share is measured on the records actually offered, not on the founder's description of them.
- History across an ownership change. If control changed in the last few years, records created before the change may sit with a former owner or may not have transferred. Put the change date beside the span of years; the guide to assessing a company that recently changed ownership covers what to look for.
One handoff that proceeds, one that is refused (Illustrative)
Illustrative. Generic companies, invented facts, no outcomes implied.
A. Proceeds with a flag. A 140-person building inspection firm, founder-led. The founder says: "Twenty years of inspection reports, and they are all ours." Staff inspectors write the reports, but some client contracts assign report ownership to the client; the firm's defect logs, quality reviews and procedures are its own. Decoder: row 1 stated (staff), row 2 mixed (client-assigned reports), row 4 contracts mentioned. The note goes to review with the client-assigned reports flagged, and the founder-CEO applies.
B. Refused. An 85-person payroll bureau. The founder says: "We own all of it; it's all in our system." The records are client companies' payroll runs and their employees' personal details. Row 2 contradicts the claim outright: the material belongs to clients and is personal data, both listed as usually not a fit. Decision: do not introduce on these records, and tell the founder why in one sentence. If the bureau later wants to discuss its own internal procedures and support history, that is a new row that has to pass every check on its own.
After the handoff: three replies a partner can give
Every claim ends in one of three replies. None of them implies acceptance.
| Outcome | What you say to the founder | What you record |
|---|---|---|
| Ready for review | "I've passed on your description as you gave it. SourceX's review decides fit and rights, not me." | Date sent and the open questions |
| Parked | "Before I introduce you, one thing needs an answer from your side: who wrote the older project files?" | The single question and who owns it |
| Not a fit | "Under SourceX's published criteria, records that belong to your clients usually aren't a fit, so I won't introduce these." | The failing fact, in one line |
Two further points keep the founder's trust. A disputed or doubtful set does not sink the rest: SourceX's rights review can carve it out while the company qualifies on records it clearly owns, as the ownership dispute page explains. And if you may receive a referral reward, say so: it is paid separately by SourceX and never deducted from the company's payout. The company keeps ownership of anything it licenses, which the guide to keeping ownership sets out.
How a sincere ownership claim still goes wrong
- Outside authors. Contractor and agency work may not belong to the company by default, as the Copyright Office's work-made-for-hire guidance implies. Founders rarely think of this unprompted.
- Client content. A company's own system can be full of other companies' records. SourceX's published criteria treat that material as usually not a fit.
- Control moved. After a sale or recapitalization the founder may still say "my company" about a business someone else controls.
- Demand. Even a clean claim meets a program-specific review, and relevance to current data needs can change.
- Partner credibility. Repeating an unchecked claim to SourceX, an LP or a co-investor spends your reputation. How often founder ownership claims hold up in review has not been measured, and no such figures are published.
Methods note. The decoder and handoff were built on 26 October 2026 from SourceX's published screening criteria and program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), the owner's decision that the CEO authorizes, and the U.S. Copyright Office's Circular 30. They do not measure demand, record quality or payout. To measure how claims fare, log every assertion with its five-line decoder and the eventual review disposition, then report the share of each meaning that held, failed or was carved out. A blank portfolio company screening workbook is a convenient place to keep the log.
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 founder's claim is written up as a dated handoff note and the CEO wants the conversation, take three steps: register to receive a partner link, hold the company up against who qualifies, and read the program terms; the partner signs the SourceX Channel Partner Agreement before submitting. More introduction guides are in the guides hub.
Readers weighing SourceX as an investment face a separate decision from any referral: the SourceX investor overview is where to request investor materials and the company and commercial metrics SourceX shares with investors directly.
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.