This page covers the founder who left and comes back to run the company. A founder who returns as chair while someone else stays CEO has a role-and-authority guide of their own, and a founder handing the CEO role to a successor is covered by the succession handoff checklist.
What a return restores, and what it leaves out of date
A return restores authority. Under the program the CEO opens a licensing discussion and signs for the company, and from the date the appointment is confirmed, that person is the founder again. A return does not restore current knowledge. While the founder was away, an interim or successor CEO may have replaced systems, signed customer and vendor agreements with new data terms, shrunk or grown the team, sold a unit, or taken a call from a data buyer. The founder may still describe "eleven years of tickets in one system" when the system was retired last spring.
So treat the return as a change of leader and nothing more. It moves who decides; it moves none of the published fit checks. A celebrated founder coming home does not make the company a better fit, and an awkward absence does not make it a worse one.
Three published rules matter more than usual after a return:
- Size uses the peak. SourceX's screening page counts 50 or more full-time employees at peak, contractors excluded, so a peak reached before or during the absence still counts if headcount has since fallen.
- Earlier contact is permanent. Section 3 of the terms treats any earlier application, lead, account or email correspondence between SourceX and the company, "however it began", as making it a duplicate. An interim leader's inquiry counts.
- Earlier licenses end the question for that data. SourceX's how-it-works page lists, among the supplier's confirmations, that the data has not been licensed for AI training before. A deal signed during the absence takes that data out.
The company before the absence, during it, and after the return
| What you look at | Founder's first tenure | While the founder was away | First months back | Once the return settles |
|---|---|---|---|---|
| Who decides on licensing | The founder, as CEO | The interim or successor CEO | The founder, from the confirmed date | The founder |
| What the founder knows firsthand | What they ran | Little | Mostly the old company | The current company, after a few cycles |
| Systems holding records | As the founder built them | Possibly migrated, merged or retired | Being relearned | Known again |
| Contracts touching records | Signed by the founder | Signed by others, perhaps with new data terms | Not yet read by the founder | Read |
| Contact with SourceX | None known | Unknown | Asked in the interview | Recorded with a date |
| Full-time headcount at peak | On record | May have peaked, or fallen | Peak still counts | Same |
| Room for an outside idea | Varied | Not your question | Usually none | Ask the founder |
| Published fit checks | Unchanged | Unchanged | Unchanged | Unchanged |
The last row is the point of the table. Everything above it changes with the return; the checks themselves never do.
The returning-founder context interview
Twelve questions in four groups. Ask them in a scheduled conversation the founder has agreed to, never in the week the return is announced. Record each answer with its date and its source, and record nothing the founder reads aloud from a file.
| # | Question | Why it matters | Never ask instead |
|---|---|---|---|
| 1 | What is your title now, and since when? | The CEO decides; a role still being agreed is not yet the decider | "Can you get the board to approve this?" |
| 2 | Did ownership change while you were away? | After a sale the acquirer's CEO decides; before closing, the target's CEO does | "Who really runs things now?" |
| 3 | Whom do you want involved in conversations about operations? | The CEO names any internal sponsor | "Can I go straight to your COO?" |
| 4 | Which systems were replaced, merged or retired while you were away? | The founder's map of the records may be stale | "Can you export the system list for me?" |
| 5 | Did the company sign customer or vendor agreements with new data terms? | Rights rest on the company's own contracts, read by its counsel and SourceX's review | "Can I see the contracts?" |
| 6 | Was any company data licensed to an AI developer during your absence? | Data already licensed for AI training does not qualify | "How much were they paid?" |
| 7 | Has anyone at the company already spoken with SourceX? | Earlier contact makes the company a duplicate | "Forward me anything SourceX sent." |
| 8 | What did full-time headcount peak at, and when? | The size check reads the peak, contractors excluded | "Send me the payroll report." |
| 9 | What has to be true before you take on anything new? | Attention after a return is scarce | "Surely you can spare an hour?" |
| 10 | Who would carry the company's share of a licensing process? | Interest without an owner stalls | "Could your team pull a sample?" |
| 11 | Would you like to hear an idea involving the company's records, now or later? | The CEO decides whether and when | "You'll want to hear this today." |
| 12 | If later, which event should prompt me to ask again? | A dated trigger replaces chasing | "I'll check in every month." |
Questions 4 to 8 rest on the founder's own knowledge and what colleagues tell them, never on documents passed to you. SourceX's first step asks the company itself to list its systems, years of history and what can be exported, with no records shared at that stage, so nothing the interview learns needs to travel further than your notes.
Rechecking authority and capacity after the return
Two groups of answers decide whether question 11 is asked at all.
Authority, from questions 1 to 3. If the founder holds a title other than CEO, or the company now sits inside an acquirer, stop and find out who decides. If the company went through a wind-down, receivership or bankruptcy during the absence, the CEO may not be enough: whoever controls the estate decides. And whatever the fund learned through board papers or information rights stays where it was; it can prompt one question to this company's CEO and nothing else.
Capacity, from questions 9 and 10. A founder brought back to fix something usually has no room for months, and a founder with interest but no one to carry the work is not ready either. Record "not now" with the trigger from question 12, and leave it there. The workload-first worksheet helps when interest arrives before capacity, and the exploration decision map helps when the founder wants to look without committing.
Week one versus month four at a freight-audit business (Illustrative)
Illustrative, with a generic company and invented facts.
Badly timed. The week a 310-person freight-audit business announces that its founder is back as CEO, the fund's engagement lead emails her: "Welcome back! You know where all the old claims files live, and SourceX pays for that kind of thing." The note treats her memory as current, calls the records hers, skips whether anyone already contacted SourceX, and lands in her busiest week. It is also wrong on the facts: the interim CEO migrated the claims system a year earlier and signed a hosting agreement she has not read. The repair is a short apology and silence until the return settles.
Better. At the fund's review four months later, the founder mentions that the migration she inherited is finished. The engagement lead asks whether she would spend thirty minutes on how the company's operations changed while she was away, and she agrees. Questions 1 to 10 take the half hour. Nobody opens a file. The founder knows of no contact with SourceX and names a colleague who would carry any work. At question 11 she says after quarter-end; at question 12 she names the January board meeting.
The permission question, built on what changed
Once questions 1 to 10 are answered and the trigger arrives, ask once, and build the question on the facts the interview produced (Illustrative wording):
"Now that the migration is behind you, there's an idea I'd like to put to you as CEO. SourceX licenses operating records directly from companies for AI training. Whether it fits is entirely your call, and SourceX decides after its own review. If you wanted the conversation, I would make the introduction and SourceX could pay me a reward; your company would receive the same amount either way. Would you like to hear more?"
The last clause rests on section 4 of the terms, which says the reward is paid separately and never deducted from the company's agreed compensation. If the fund rather than you would act as the partner, say so: SourceX's sample Channel Partner Agreement names the partner as "an individual, or entity type and jurisdiction". Whoever submits signs that agreement first.
Risks and limits of a context interview
- Self-report. Every answer is the founder's recollection or a colleague's. Only SourceX's review examines records, rights and relevance.
- Rights may have moved. Agreements signed during the absence can change what the company may license. The interview flags them; it clears nothing, much as SourceX's own matrix says it "cannot clear a customer contract".
- Duplicates. An interim leader's inquiry to SourceX leaves the company credited to no later partner, however warm your tie to the founder.
- Programs move. Criteria follow each SourceX program, and a company that misses one may fit another later; an interview is valid on the date it was held.
- Relationship cost. A founder in a turnaround may resent operational questions from an investor. Ask permission for the interview itself, and accept a no.
- No outcome data. Nobody has published how returning-founder companies respond to licensing introductions. A fund that wants its own evidence can follow its introducers over time with a cohort report.
Methods note. The interview, the timeline table and both examples were built on 2026-10-28 from SourceX's program terms, its screening page, its how-it-works page and the sample Channel Partner Agreement. They describe which questions to ask and when, not measured results. Demand for a company's records, their quality and any payout are left out, because only SourceX's review can assess them.
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 returning founder has answered the interview, named a trigger and, at that trigger, asked for the conversation, register, set the company beside the who qualifies checks a final time and reread section 3 of the program terms on earlier contact; other timing guides sit in the guides hub.
Interviewing a portfolio founder is referral work. Sizing up SourceX as a company to back is its own exercise, and the SourceX investor overview takes requests 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.