The draft might be a fund's quarterly letter, a platform-team newsletter, a conference write-up, a thought-leadership post an agency wrote for you, or a journalist's story that lands in your inbox for comment. The question is the same each time: whose information does each line carry, and who can release it? This workflow is for the general counsel's office, or whoever acts as its liaison to the platform and marketing teams.
Whose information is in the sentence?
A single sentence naming a company can carry five kinds of information, each with a different owner.
- The company's identity and facts: its name, size, systems, history and plans. The company owns them, and its CEO decides; once a company is acquired, the acquirer's CEO decides, and in a formal process such as a bankruptcy case, SourceX's who-qualifies page says the CEO may not be enough, because someone else may control the assets.
- The company's interest in licensing its data. That interest is commercially sensitive before the company has decided anything, and afterwards SourceX's published deal terms add a constraint between the company and SourceX: "Neither side publicizes the deal." A willing CEO still checks the company's own signed terms. You do not interpret them for it.
- Your relationship with SourceX. Section 4.5 of the sample agreement says: "Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." The same section grants no trademark license.
- What SourceX told you. Section 3.4 limits a partner to information reasonably needed to understand its own referral and reward, and section 4.6 says updates come as generic stages or reference codes. Section 1.6 counts introduced contact identities and introduction records among the information the agreement treats as confidential.
- What your fund learned in confidence. Board packs, diligence files and information-rights reports come with duties the fund already owes. The who-qualifies page puts it in one line: "The fund's knowledge is a reason to ask the CEO, never material to pass along."
Approval follows ownership. Nobody can release information that belongs to someone else, however senior they are, and a CEO's enthusiasm for a story does not authorize SourceX's name in it.
What is the article for, and who will read it?
Start with purpose, because it decides how much of the company the article needs. Many pieces work just as well with "a 300-person claims administrator" as with a name. If the point survives the description, use it and run the identifiability checks in publishing network research without exposing companies; a description plus a city, a founding year and a photo can name a company as surely as its logo.
A restricted audience is still an audience. An LP letter, a members-only newsletter and a slide shown at a portfolio summit all leave the room, get forwarded and get quoted. Apply the same approvals as for a public post.
Some drafts are not yours. When a journalist, an event organizer or a research firm sends a draft that names a company and asks you to confirm it, you can approve nothing on the company's behalf. Decline to comment on companies, point the writer to the company and tell the CEO the question came in. A draft an agency writes for you is the opposite case: it is your draft, and the workflow applies in full.
The publication consent workflow
Match every line in the draft to a row. A line that matches two rows needs every approval either row requires.
| Line in the draft | Whose information | Who must approve, in writing | Default without that approval |
|---|---|---|---|
| Company name or logo in a list of firms you work with, no mention of SourceX | The company | The CEO | Leave out |
| Company name next to data licensing, with SourceX unnamed | The company | The CEO | Leave out |
| Company name next to SourceX | The company and SourceX | The CEO, and SourceX under section 4.5 | Leave out |
| "We introduced this company to SourceX" | The company, and your relationship with SourceX | The CEO and SourceX | Leave out |
| Where the company stands: applied, in review, signed, delivered | SourceX and the company | Both; partner updates exist for tracking your own referral | Leave out |
| A company that declined or paused | The company | Not cleared by this workflow | Never |
| Any amount: an offer, a payout, your reward | The company's signed terms and SourceX's | Not cleared by this workflow | Never |
| A fact from board packs, diligence or information rights | The company, through your fund's duties | Your fund counsel first, then the CEO | Leave out |
| A quote from the CEO or an employee | The speaker and the company | The speaker, plus the CEO for an employee | Leave out |
| A description no reader could trace to the company | Nobody's, once it is truly untraceable | Your own identifiability review | Publish after the review |
Method note. The rows apply section 4.5 and sections 1.6, 3.4 and 4.6 of the unsigned sample Channel Partner Agreement, SourceX's published deal terms, its who-qualifies page and the program terms (version 2026-10-22.2, since replaced by version 2026-11-04), all read on 2026-10-28. The "never" rows reflect two facts: SourceX need not reveal prices to partners under section 4.6, and a company's payout is fixed only in its own signed Dataset Deal Confirmation. The workflow is our design; it has not been reviewed by any regulator, and it does not replace your counsel's reading of your fund's own obligations.
Running the workflow on one draft
- Mark every line that touches a company, including captions, alt text, file names, speaker bios and the footnote that says where a chart came from.
- Give each line its row and its owner.
- Cut first. Delete what the article does not need, and replace names with descriptions wherever the point survives. Each line you cut is one approval you no longer need.
- Ask each owner in writing, separately from any referral conversation. Send the exact sentences, the channel, the publication date and how long the piece stays online. A CEO should be able to say yes to an introduction and no to the article, or the reverse, without either answer costing anything.
- Record the answer with the sentence, channel, period, approver and date. An approval of version two does not cover version three.
- Recheck on the day you publish. Has the company been acquired? Before closing, the target's CEO decides; afterwards, the acquirer's CEO does. Has a formal process begun? Has anyone withdrawn?
- Keep a way out. If the CEO withdraws approval after publication, take the line down promptly, note the change where readers will see it and keep the record.
Escalation, withdrawal and a line that is already out
Escalate to counsel whenever a line rests on something your fund learned in confidence, or when a CEO asks you what the company's agreement with SourceX allows it to say. The second question belongs to the company's own counsel and to SourceX. You can point the CEO there; you cannot answer it.
Withdrawal needs no reason. Treat a CEO's "please take it out" as complete, and do not ask SourceX or anyone else to persuade the company otherwise.
If a line went out without the approvals it needed, remove or correct it where it lives, tell the CEO what was published and for how long, and, if it named SourceX, tell your SourceX contact as well. A founder who wants to name the eventual buyer in public is a different case, handled in what to do when a founder wants a public buyer name.
Two drafts through the workflow (Illustrative)
Illustrative: invented funds and companies, no outcome implied.
A quarterly LP letter. The platform lead drafts: "Portfolio company [name], a 410-person freight broker, was introduced to SourceX by our platform team and is now in review; its board deck shows 14 years of dispatch records." Four rows apply: name next to SourceX, the introduction, a status (in review) and a figure the fund knows only from board reporting. The status row and the board row default to out. The CEO is willing to be named, but the company's deal is undecided and SourceX has given no written authorization. The published version reads: "Our platform team now explains direct data licensing to portfolio CEOs who ask, and each company decides for itself whether to talk to anyone." No company, no status, no SourceX name, and nothing for anyone to approve.
A reporter's question. A trade reporter writing about AI training data emails a fund partner: "Can you confirm [company] is working with SourceX?" The partner replies that the fund does not comment on companies and suggests the reporter ask the company directly, then forwards the question to the CEO with no advice attached. Nobody at the fund confirms or denies anything.
Where this workflow can fail
- Identification by combination. A description, a date and a photo can name a company with no name in the text. Test the whole page, not single lines.
- Approvals that drift. A yes given in an email thread to an earlier draft gets treated as covering the final one. Tie every approval to an exact version.
- What you cannot see. SourceX's published deal terms summarize the company's agreement; they are not the agreement. The company's own signed terms may say more, which is why the CEO, not you, checks them.
- Other rules on fund communications. Whether a fund publication falls under other obligations is for fund counsel; this workflow covers only the referral and confidentiality questions.
- Gaps in the published documents. Where the terms and sample agreement are silent, for example on quoting SourceX's own public statements next to your firm's name, SourceX decides. Ask it in writing rather than inferring a permission.
For the step before any article, putting a question to SourceX without naming a company is covered in asking a SourceX question anonymously, and confidentiality terms owed to other parties are sorted in when a referral includes third-party confidentiality terms. Other publishing and confidentiality questions are gathered in the guides hub.
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.
Keep the article and the introduction as separate decisions: register as a partner before you submit anything, let the CEO read who qualifies for the company's side, and check the program terms and section 4.5 of the sample agreement before any line names SourceX.
Approving a line in an article is a confidentiality question about your fund's work; deciding whether SourceX itself merits an investment is a different exercise, and materials for it are requested through the SourceX investor overview.
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.