A strategy vote is not a yes to licensing
The 2023 G20/OECD Principles of Corporate Governance list, first among a board's key functions, reviewing and guiding corporate strategy, major plans and budgets, setting performance objectives and monitoring how management carries them out (our paraphrase). Approving a strategy is that function at work: it sets a direction for management. It does not open a conversation with an outside licensing counterparty, and in SourceX's program it never stands in for the CEO.
SourceX's screening page answers the question directly. Asked whether a board seat lets a fund partner approve a licensing discussion, it says no: "That decision, and the signature that follows it, belong to the CEO." It also notes that "anything the fund learned through board materials or information rights usually stays confidential, so the right move is to raise the idea with the CEO."
Two working rules follow. The deck, the minutes and the vote never appear in a follow-up, never go to SourceX and are never mentioned to another company; what you learned as a director may prompt a single question to this company's own CEO and travels nowhere else. And enthusiasm is not sponsorship: "the board would love this" only adds pressure the CEO then has to manage, which is why keeping board pressure out of a voluntary introduction matters here too.
Three follow-ups a strategy vote can set off
Where the referral stood before the vote decides what, if anything, you may do after it.
| Where the referral stood | What the vote may have changed | What you may do | Who updates SourceX |
|---|---|---|---|
| The CEO said "after the strategy review" | The condition the CEO named may now be met | Ask the CEO once whether that moment has come | Nobody yet; the company applies itself if the CEO wants to |
| The company had applied or was talking to SourceX | The records, the entity or the team in scope | Answer the CEO's questions if asked; relay nothing | The company, directly |
| Licensing had never come up | A strategy that touches records, such as a retired product line | Wait until the CEO has spoken about the change outside the boardroom, then at most one question | Nobody; the company applies itself if it wants to |
| The CEO had declined | Nothing a vote can reopen | Wait for the CEO to raise it | No one |
The second row is where engagement leads overreach. Section 2 of the terms says "SourceX may communicate directly with a referred company without affecting valid attribution," so no follow-up keeps an introduction alive; dated records settle credit, never a click on your link. The fourth row belongs to reconnecting after a company declined.
What an approved strategy can move in the records, and what it cannot
A strategy is a bundle of decisions. A few move records; most move calendars; none makes a company fit, which only SourceX's review decides.
| Approved move | What it can change in scope | What it leaves exactly as it was |
|---|---|---|
| Retire a product or service line | That line's records stop growing; the people who know them disperse; a system may be switched off on a date | Peak full-time headcount; whose records they are |
| Consolidate onto one ERP or service platform | Old systems freeze or migrate, and history can be trimmed on the way | The rights picture; who decides |
| Sell or carve out a division | Records may leave with the division; once the sale closes, the buyer's CEO decides for what was sold | One reward cap per corporate group, whichever group holds the records |
| Build AI tools in-house | Records may be used internally | An AI-training license granted earlier would put those records out, as SourceX's process page shows |
| Cut costs or headcount | Less room for any new project | The size test reads the peak, not today |
Read the table one way: from a move to a question for the CEO, never to a verdict that the company fits. Location rarely moves with strategy, and the published rule stays as it was: 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 strategy-to-scope update brief
One page per company, filled in from what the CEO has told you or said publicly. Nothing on it comes from board packs, minutes, management accounts or a data room.
| Line | What you write | Where it may come from | Never from |
|---|---|---|---|
| 1. The approved move, in the CEO's words | "We are closing the managed-services desk by June" | A one-to-one with the CEO, or a public announcement | The board deck or minutes |
| 2. The records it touches | System names and the years each covers | The CEO, or someone the CEO names | Logins, exports or screenshots |
| 3. The entity that will hold them | The same company, a new subsidiary or a buyer | The CEO; public filings | Draft deal documents |
| 4. When the change settles | The date the CEO expects it to be done | The CEO | Your own estimate |
| 5. Who runs the affected work now | Names and roles; the CEO still decides | The CEO | An organization chart from board materials |
| 6. Room for one more project | The CEO's read of the team's workload | The CEO | Your reading of the plan |
| 7. Inputs that did not move | Peak full-time headcount, own records, rights, location and record language | Earlier notes, rechecked with the CEO | Assumption |
| 8. Earlier contact with SourceX | An application, account, correspondence or none | The CEO | Records you never see |
| 9. The one question | Drafted before anything is sent | You | Any wording that cites the board |
| 10. The answer and the next step | Date, answer and who owns the next move | The CEO | A colleague's summary |
It ends in one question now, a wait until the date on line 4, or the row closed again; never in "now fits".
Before and after the vote at one portfolio company (Illustrative)
Illustrative. One invented software company, made-up figures and no result implied.
| Before the vote | After the vote | |
|---|---|---|
| Strategy | Software plus a managed-services desk | Software only; the desk closes in June |
| Desk records | Tickets from 2013 onward in one help desk, still growing | The same history, frozen in June; the help desk retires in the autumn |
| Who knows them | A 40-person desk team | Fewer people, some moving to product support |
| Full-time headcount | 260 at peak | 260 at peak, 230 today |
| Who decides | The founder-CEO | The founder-CEO |
| What the CEO said about licensing | "After the strategy review" | Nothing yet; staff hear about the desk next week |
The badly timed follow-up. The morning after the board meeting, the engagement lead emails the CEO, copying the CFO: the board has signed off on closing the desk, so license the archive before the help desk goes. It quotes the board, arrives before the staff announcement, treats a vote as consent, copies someone the CEO did not choose and turns the company's own switch-off date into pressure.
The well-timed one. Three weeks later, in a one-to-one, the CEO mentions that the desk archive is "a question for after June." The engagement lead fills lines 1 to 8 from that conversation, waits until the desk has closed and asks one question in July. Whatever the CEO answers goes on line 10.
A company already in SourceX's process. A 180-person logistics company applied after the fund's introduction; months later its board approves selling a division. The engagement lead sends SourceX nothing and, when the CEO asks, suggests raising it with SourceX directly. After a signed Dataset Deal Confirmation, SourceX's process page says a material change "needs a signed amendment", and what leaves with the division is the buyer's CEO's to decide once the sale closes.
Who runs the changed work, and who has a spare week
Strategy changes reshuffle people: a transformation lead appears, a division head leaves, systems move under a new COO. They may hold the records or run the systems, and they can describe both; none of them authorizes.
Capacity needs its own question. SourceX's first published step asks the company to list its systems, years of history and what can be exported, then completes the inventory with the company and runs the rights check. In a migration or a wind-down, the people who would answer have no spare week. Ask the CEO who would answer and whether they have room this quarter; "after the migration" is a date for line 4. The fundraising-window rubric applies the same capacity logic to a round.
The follow-up note, built on what changed
Send it to the CEO alone, in your own words:
When we last spoke, you said the records question could wait until [the condition the CEO named]. Since then you've told me [the change, in the CEO's words]. Would you like an introduction to SourceX, or would you rather look at its process yourself first? It may not be a fit, and SourceX decides that in its review. If the company went ahead and completed a paid deal, SourceX might pay me a reward, separately and never out of the company's payout. I'm glad to leave it here if the timing is wrong.
The disclosure rests on section 4 of the terms: the reward "is paid separately by SourceX and is never deducted from the supplier's agreed compensation." After a yes, you sign the SourceX Channel Partner Agreement if you have not, and the company applies itself. A no closes the row; a "later" gets the CEO's date, not yours.
A strategy that is really a new business model fits the changed-model review better; a sale that splits records from the people who decide fits the divestiture sponsor map; and what a director may ask inside board business is set out in the corporate director's question set.
Where a strategy-led follow-up goes wrong
- Strategies reverse. A board can revisit a decision within a quarter; date every line of the brief.
- Boardroom leakage. The easiest mistake is citing something only the board knows; a follow-up that leans on board material has already failed.
- Demand moves too. Whether a current program wants the affected records is a review question. "A company that does not fit one program may fit another later," the screening page says, and the reverse can happen.
- Earlier contact. If the company approached SourceX during its strategy work, section 3 of the terms treats it as a duplicate that no later partner is credited for.
- No published base rates. Nobody has published how often companies take on licensing work in the middle of a strategy change. Count your own: briefs started, questions asked, yeses.
Method note. The moves table, the ten-line brief and the cases apply SourceX's terms (Version 2026-10-22.2, since replaced by version 2026-11-04), screening page and process page, read on 2026-10-27, plus the OECD's board principles. They are this page's design, not SourceX rules; no SourceX outcome data was used.
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 brief shows a settled change and the CEO has asked to hear more, register as a partner, recheck the company against who qualifies and reread the program terms before anything is sent; more timing guides sit in the guides hub.
Following up a portfolio referral and deciding whether SourceX merits an investment are separate decisions; for the second, the SourceX investor overview offers materials on request.
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.