# Professional management referral readiness | SourceX

Canonical: https://refer.sourcex.si/guides/when-a-company-moves-from-founder-led-to-professional-management
Last updated: 2026-11-05

When a founder-led company builds a professional management layer, more people can tell you about workload, systems and timing, but the person who decides on a licensing conversation stays the same: the CEO. New operating chiefs and department heads are useful contacts once the CEO brings them in; none of them becomes the authorizer, however much of the company they now run. Map what moved, wait for the new structure to settle, then ask the CEO once, naming what changed.

This playbook is for VC portfolio engagement leads watching a portfolio company hire its first COO, vice presidents and functional heads while the founder stays CEO. If the founder is handing over the CEO title itself, [the founder succession handoff checklist](/guides/a-founder-succession-can-reset-the-introduction-path) applies instead. A first CFO hire has [its own timing guide](/guides/the-data-partnership-conversation-after-a-founder-hires-a-cfo). Funding stage and management headcount play no part in eligibility.

## What a management layer takes off the founder's desk

Larger companies outgrow the founder doing everything. Larry Greiner's classic Harvard Business Review article describes growth as a run of phases with different dominant themes (creativity, direction, delegation, coordination and collaboration) in which each stretch of steady growth ends in a period of turmoil, and a fix that worked in one phase becomes the problem of the next (our paraphrase of HBR's summary). Hiring professional managers is one of those fixes, and the months around it are rarely calm.

What usually moves to the new managers:

- day-to-day operating calls, scheduling and process ownership;
- hiring within agreed plans, and budgets within limits;
- vendor selection and the running of internal systems;
- the regular reporting the board now expects.

What does not move:

- **The licensing decision.** Under the program the CEO authorizes a licensing discussion and signs for the company. An internal approval matrix that lets a COO sign supplier contracts below some threshold does not change who decides this question.
- **The published checks.** SourceX's screening page says none of its checks mentions funding, and nothing on its list concerns an org chart: size at peak, years of records the company created, rights to license them, an authorizing CEO and fit with a current program.
- **Earlier contact with SourceX.** Section 3 of the terms makes a company with any earlier application, lead, account or email correspondence a duplicate, whoever now runs operations.
- **Board knowledge.** If you heard about the hires through a board seat, that may prompt one question to this company's CEO, and it never travels anywhere else.

## The management-transition authority review

For each question a licensing conversation raises, the review records who answered it in the founder-led company, who answers it now, whether you may ask that person, and who decides. Fill one row per question, dated.

| Question the conversation raises | Founder-led: who answered | Professionally managed: who answers | May you ask them? | Who decides |
|---|---|---|---|---|
| Whether to discuss licensing the company's records | The founder-CEO | The CEO | Yes, and only the CEO | The CEO |
| Who signs for the company | The founder-CEO | The CEO | No need to ask | The CEO |
| Which systems hold which years | The founder, from memory | Function heads and the systems administrator | Only once the CEO names them, and only what, how many years and which system | Not a decision |
| Who would carry an application | The founder, alone | Usually an operating chief | Through the CEO | The CEO names the person |
| Whether this quarter has room | The founder's own calendar | The management team's plan | Ask the CEO, who may consult the team | The CEO |
| Customer contracts and other limits on rights | The founder and outside counsel | General counsel or outside counsel | No; SourceX's rights review and the company's counsel handle it | SourceX's review, with the company's counsel |
| Value, payment and accounting | The founder and the accountant | The finance chief | No; SourceX and the company's advisers answer | The company, on SourceX's offer |
| Whether staff hear about it | The founder | The CEO | No | The CEO |

The trap sits in rows 3 and 4. A new operating chief often knows the systems better than the founder ever did, and may well be the person who would carry the work. That makes them an excellent contact after the CEO says yes and the wrong first contact before it. Nothing in the review ever needs a file, an export or a screen share from anyone; it records names, roles and dates.

## Signals that the new structure has settled

A reorganization is a reason to wait, then a reason to ask. These signals mark the turn:

1. The new reporting lines are announced and in effect, not "from next quarter".
2. At least one full operating review or management meeting cycle has run under the new structure.
3. Senior operating roles are filled, with no interim head of operations covering a vacancy.
4. No restructuring, layoff or further leadership change is announced or rumored.
5. The CEO talks about the new team in settled terms, for instance "now that operations runs without me".

Treat these as reasons to hold: a professionalization pushed by the board against the founder's wishes, an open search for a COO, a financing or a sale in progress, or a founder who is visibly stretched. In a sale, the target's CEO decides until closing and the acquirer's CEO after it.

## A good ask and a premature one at a 260-person firm (Illustrative)

Illustrative. An invented company, team and calendar; read no outcome into it.

A 260-person commercial cleaning and facilities company has been run by its founder-CEO for fifteen years. In January it hires a COO, a sales vice president and a head of people; finance stays with the controller.

| Item | Last year, founder-led | Spring, new team in place |
|---|---|---|
| Who decides on a licensing conversation | The founder-CEO | The founder-CEO, unchanged |
| Who knows where job and inspection records sit | The founder, roughly | The COO and the systems administrator |
| Who would carry an application | Nobody had room | The COO, if the CEO chooses |
| Room in the calendar | None; the founder ran operations | Some, after the COO's first quarterly review |
| Published fit checks | Peak headcount, years of job records, the company's own records | Unchanged by the hires |

**The good ask.** The engagement lead says nothing about SourceX through the winter. In April, after the COO's first quarterly operating review, the CEO mentions that she finally has afternoons back. The engagement lead asks her one question, naming that change. She says yes and names the COO as the person who will describe the systems. The engagement lead, already signed up under the SourceX Channel Partner Agreement, submits the introduction with her written yes; the company applies itself.

**The badly timed ask.** In February a fund colleague meets the new COO at a portfolio event, calls licensing "an easy win for your first year" and asks the COO to sign off on it and list the company's systems. The COO, keen to impress, agrees, and the colleague submits an introduction naming the COO as the contact. The CEO first hears of it from SourceX. SourceX's screening page warns that introductions the decision maker did not know about usually fail, and this one also asked a manager for the kind of systems list a partner should never collect.

| What differed | The good ask | The badly timed ask |
|---|---|---|
| Who was asked | The CEO | The new COO |
| When | After the first operating review | Week six of the new job |
| What was asked for | Whether the CEO wanted a conversation | A sign-off and a list of systems |
| Who knew first | The CEO | The COO; the CEO heard last |
| What it cost | Nothing | An apology to the CEO and a withdrawn introduction |

The repair is plain: apologize to the CEO, withdraw the request to the COO, and write a dated line that nobody raises it again unless the CEO does.

## Rechecking authority and capacity with the CEO

Authority first. Confirm that the founder still holds the CEO title, and whether a handover is planned within the year; if it is, the answer you get now may not last, and the succession checklist linked above sets out who to ask after it. A new operating chief who is about to become CEO decides only from the day the title passes.

Then capacity, asked of the CEO rather than of the managers. SourceX's FAQ sets the first step low: "Describing your data takes about 10 minutes." It also notes that "Preparing a delivery may need someone who can export files from your systems," which is company staff's work after an agreement, never a partner's. And "Applying and the fit check create no obligation," so the CEO can look without committing the new team. Ask who would carry it, whether the new team has room this quarter, and when the CEO would rather hear more. If the CEO is keen and the finance chief is cautious, [the founder-and-CFO worksheet](/guides/the-founder-is-interested-but-the-cfo-is-not-ready) sorts each worry by who can answer it.

## One question that names the new team

Name the change the CEO already lives with, and nothing you inferred:

> Now that [the COO] has a quarter behind them, would you like to hear about SourceX? It licenses business records directly from the companies that created them, for AI training and evaluation. Whether to talk to them is your decision, and SourceX decides fit after its own review. If your company licensed, SourceX might pay me a referral reward, separately from what it pays you. No one needs to send me anything.

The last two sentences follow section 4 of the terms, which states that the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." Record the date, the CEO's answer in her own words and the person she names, if any. A "not yet" becomes a condition, handled as in [when a founder says the timing is wrong](/guides/when-a-founder-says-the-timing-is-wrong); a no closes the row unless the CEO reopens it. Credit, if any, follows dated records: the first valid introduction of a company new to SourceX, once it files a verified application within the 90-day attribution window.

## Where the professionalization reading misleads

- **Titles without delegation.** Some founders hire vice presidents and keep every decision. Capacity has not changed; judge by what the CEO says, not by the org chart.
- **A prelude to something bigger.** A management layer is sometimes built ahead of a sale or a CEO change. Then authority may move at closing or at the handover.
- **An eager manager.** A new leader who wants to champion the idea is welcome as a contact and never a route around the CEO.
- **Models are not timetables.** Greiner's phases describe how growing companies change; they do not say when any company is ready for a licensing question.
- **Location and fit still apply.** 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. Full-time headcount must also have peaked at 50 or more, contractors excluded.
- **No outcome data.** SourceX has published nothing on how introductions fare after a management transition. To build your own, count transitions in the portfolio, the date each settled, and the CEOs who asked for an introduction. An operations leader's archive review raises separate questions, covered in [the archive review guide](/guides/a-new-operations-leader-reviews-the-company-s-archives).

**Methods note.** The authority review and the settling signals rest on SourceX's referral terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening page and its FAQ, each read on 2026-10-27, with HBR's summary of Greiner's growth phases as background. They are a reasoned procedure, not measured results; demand for a company's records, record quality and any payout are left out because only SourceX's review can assess them. Related timing playbooks sit in the [guides hub](/guides).

## 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 the new structure has settled and the CEO asks for the conversation, [join as a partner](/register), run the company past [who qualifies](/who-qualifies) again and keep the [program terms](/terms) open while you write the introduction.

Watching a portfolio company professionalize is referral work. Judging SourceX as a possible investment is a different exercise, and investor materials can be requested through the [SourceX investor overview](https://sourcex.si/investors).

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://hbr.org/1998/05/evolution-and-revolution-as-organizations-grow
- https://sourcex.si/faq
- https://sourcex.si/investors
