# Founder referral readiness questions: 12 to answer | SourceX

Canonical: https://refer.sourcex.si/guides/the-questions-a-founder-should-answer-before-being-introduced
Last updated: 2026-11-05

Give the founder twelve questions to answer privately before you introduce anyone, and say which answers matter. Only two answers stop an introduction: "I don't want this conversation" and "I'm not the CEO, and the CEO hasn't agreed." Everything else, from peak headcount to rights in customer contracts, can be answered roughly or with "I don't know", because SourceX's review settles those facts. Funding stage settles none of them. The founder then decides which answers travel with the introduction.

That framing changes the conversation. A checklist that reads like diligence makes a founder defensive and invites optimistic guesses. A checklist that says "an honest unknown is fine" gets accurate answers, and accurate answers are what keep an introduction from wasting the CEO's time or SourceX's.

## The decision in front of the founder

The founder's question is simple: "Do I want SourceX to look at whether our records could be licensed, and am I the person who can say so?" The next step you are requesting is equally specific: a permissioned introduction that leads, if the company chooses, to its own application. SourceX describes that application as a few questions and no files, in which the company lists its systems, years of history and what can be exported. No records are shared at that stage.

So the founder is not being asked to prepare a dataset, open a data room or commit to a license. The twelve questions exist to make the introduction accurate, not to pre-empt the review.

## Readiness is the founder's call; eligibility is SourceX's

| Question | Founder readiness | Company eligibility |
|---|---|---|
| Who decides | The founder, and the CEO for the company | SourceX, in review |
| When | Before any introduction | After the company applies |
| What it rests on | Willingness, authority and rough facts | Peak headcount, history, rights, the CEO's authorization and fit with a current program |
| What an unknown means | A note in the handoff | A question SourceX answers with the company |
| What funding changes | Nothing | Nothing |

The last row is worth saying out loud to a portfolio founder. SourceX's own screening guidance says none of the checks it screens on mentions funding. A celebrated round proves nothing about records, and a company that never raised outside money can pass every check. For the fund-side screen that comes before you even raise the topic, use the [portfolio referral screen](/guides/the-portfolio-referral-screen-before-a-founder-email).

## The pre-introduction founder checklist

Twelve questions in four groups. The founder answers alone, in about fifteen minutes, and nobody grades the answers. The last column is the founder's choice.

| # | Question | Who can answer | Answer that keeps going | Answer that pauses or stops | Travels with the introduction? |
|---|---|---|---|---|---|
| A1 | Do I want this conversation at all? | The founder | Yes, or "curious" | No: stop | Only that the CEO agreed |
| A2 | Would a no, from me now or from SourceX later, cost me anything I care about? | The founder | No | Yes: pause and name the worry | No |
| A3 | Do I have a personal stake that differs from the company's? | The founder | No, or yes and disclosed to the board | Undisclosed: pause | No |
| B4 | Am I the CEO? If not, does the CEO know and agree? | The founder | I am, or the CEO agreed | Not CEO and CEO not asked: stop for now | Yes: the CEO's name and agreement |
| B5 | Does anyone besides the CEO have to agree? | The CEO, with counsel | No, or yes and named | Unknown: note it | Yes, as a flag |
| B6 | Who would carry the work day to day? | The CEO | A named person | Nobody yet: fine | Yes: name and role |
| C7 | How many full-time employees did we have at our peak, contractors excluded? | The founder or HR | A number at or above 50 | A lower peak: say so plainly | Yes: a band |
| C8 | How many years of our own records survive, and from when? | The founder or operations | Several years | Mostly deleted: pause | Yes: a range of years |
| C9 | Which systems hold them, and what can be exported? | The founder or IT | A list of named systems | One system: still worth asking | Yes: system names |
| D10 | Do any of these records belong to our clients rather than to us? | The founder, then counsel | Ours, or mixed and unknown | Mostly clients': usually not a fit | Yes: ours, mixed or unknown |
| D11 | Has any of it been licensed for AI training before, or created or altered with AI for a sale? | The founder | No | Yes: say so before anything else | Yes |
| D12 | Was personal data in these records collected lawfully, and do notices or contracts limit reuse? | Counsel | "I don't know" is acceptable | A known restriction: flag it | Only whether counsel is involved |

How to read the groups:

- **A, the founder as a person.** Only the founder can answer these, and no one else should see the answers. A1 is one of the two stops. A2 and A3 exist because an investor is asking: the founder should know what a no would cost them before saying yes.
- **B, authority.** B4 is the other stop. The program gives the CEO the authority to approve a licensing discussion and sign for the company; the [authority question](/questions/who-needs-authority-to-approve-a-company-data-partnership) has more. B5 catches the unusual cases, such as owners holding equal stakes or a lender whose consent a credit agreement requires.
- **C, records.** These map directly onto SourceX's application, which asks for systems, years of history and what can be exported, and notes that qualifying companies list at least five systems. A company that runs mostly on one platform can still be a candidate when that platform holds years of connected records, as the page on [whether one system is enough](/questions/one-system-company-data-enough-for-licensing) explains.
- **D, rights.** D11 and D12 come straight from what SourceX asks suppliers to confirm: rights to license the data, personal data collected lawfully, no earlier licensing for AI training and no creation or alteration with AI for the sale. A founder who says "I don't know" to D12 has given a correct answer; [what happens when a founder says they own the data](/guides/a-founder-says-they-own-the-data-what-happens-next) shows how such claims get tested.

**Counting C7 without guessing.** The program counts full-time employees at peak and excludes contractors. Use the classification payroll or HR already applies rather than reclassifying anyone for this purpose. The IRS describes its general rule as treating a worker as an independent contractor when the payer controls only the result of the work, not what is done and how; a founder who is unsure which side of that line a team sits on should say so. For a staffing firm, only the firm's own full-time employees count, not placed workers on assignment at clients. Give both numbers and introduce the firm anyway when its records are strong.

## Three founders, three outcomes (Illustrative)

Illustrative: the companies and people are invented, and no outcome beyond the introduction is implied.

| Founder | Where the checklist lands | What happens next |
|---|---|---|
| A co-founder and CTO of a 300-person logistics software company, which hired an outside CEO two years ago | A1 yes and keen; B4 "not the CEO, the CEO hasn't heard of it" | Founder interest only. Nothing is submitted. The co-founder decides whether to raise it with the CEO, who answers the checklist from group B onward |
| The founder-CEO of a staffing firm with 70 full-time employees of its own and about 900 workers placed at clients | A and B clear; C7 answered with both numbers; D12 "don't know" | Authorized sponsorship. The CEO names the head of operations as day-to-day contact, and the introduction carries the band, the years, nine system names and the D12 flag |
| The founder-CEO of a 120-person medical billing company | A1: "Not now; we're in the middle of a refinancing" | A voluntary decline. No reason is asked for, nothing is passed on and the investor raises it again only if the CEO does |

The second row shows what readiness looks like in practice: not every answer known, but the two stopping questions cleared and every unknown labeled. The first row shows the most common mistake, treating a founder's enthusiasm as the company's decision.

## A founder's stake is not the company's decision

"Founder" describes history, not an office. A founder may be the CEO, a board member, a minority shareholder after several rounds or an employee who no longer runs the company. Each of those people can be interested. Only the CEO decides for the company under the program.

Personal interests deserve their own line on the checklist because they shape answers. A founder planning to sell shares may want the company to look as attractive as possible; a founder close to the investor may find it hard to say no. A3 asks the founder to name any such stake, and the answer stays with the founder. The investor's own interests, a possible referral reward and the fund's shareholding, belong in the investor's request, not in the founder's homework.

## Document what was approved and hand off only that

The final column of the checklist is the handoff. Whatever the founder did not mark stays with the founder. A typical introduction note, built only from marked answers, looks like this (Illustrative):

| Field | What the note says |
|---|---|
| Company | Legal entity name and web domain |
| Authorization | The CEO agreed on a stated date, in writing |
| Contact | The CEO, and the named day-to-day person |
| Size | "70 full-time staff; about 900 placed workers, not counted" |
| History and systems | "Records from 2013; nine named systems" |
| Flags | "D12 unknown; counsel not yet involved" |

Nothing else goes in: no files, samples, screenshots, client names or figures. The Channel Partner Agreement gives a partner no authority to share a supplier's inventory, records, raw data or personal information, so the investor never holds more than the founder chose to say. Write the date and the CEO's words in your own file. Credit is settled by timing: it goes to whoever made the first valid introduction inside the 90-day attribution window, once the company files a verified application, and a company with any earlier relationship with SourceX is a duplicate however well prepared.

## Where this checklist misleads

- **Self-reported numbers drift upward.** Founders remember peak headcount generously and assume records survived migrations that dropped them. Ask for bands and ranges, not precision.
- **Unknowns can scare founders off.** A founder who reads twelve questions as a test may decline rather than admit gaps. Say at the start that "I don't know" is an acceptable answer to most of them.
- **Readiness does not predict demand.** SourceX checks relevance to its current data needs in review, and its process page says qualifying does not guarantee an offer. A perfectly answered checklist can still end in a decline.
- **It can feel like diligence.** Keep it to fifteen minutes and private. If a founder wants help with the discovery call itself, [preparing a founder for the first discovery call](/guides/how-to-help-a-founder-prepare-for-the-first-discovery-call) covers that stage.
- **No founder data has been published.** Nobody has measured which of these questions founders skip or get wrong. To find out, log which questions each founder left blank across your next twenty uses, and compare that with what the founders later choose to tell you about their review.

**Method note.** The twelve questions apply the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), SourceX's screening profile and process page, the Channel Partner Agreement sample and the IRS worker-classification rule, all checked on 26 October 2026. They do not measure founder behavior, demand for any company's records or outcomes.

## 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 founder has cleared both stopping questions and marked what may travel, [register for a partner link](/register), compare the marked answers with [who qualifies](/who-qualifies) and keep the [program terms](/terms) version with your note. More founder conversation guides are in the [guides library](/guides).

Preparing a founder for an introduction is referral work. Weighing SourceX as a possible investment is a different decision, and the [SourceX investor overview](https://sourcex.si/investors) is where to ask for investor materials.

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.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-defined
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/investors
