Partners write two kinds of comparison. Some compare referral programs for other introducers; others compare ways a company can license its records, for founders and finance teams. Both are interested content the moment a link in them can pay, and both fail the same way: the table looks neutral and is not.
Why your link changes how the table reads
A reader assumes a comparison was built to inform them. A reward for one of the options is a connection they would not expect, and that is the situation the FTC's Endorsement Guides address. Section 255.5, in our paraphrase of the search excerpt we read, says a connection between endorser and seller that could affect the weight a reader gives the endorsement, and that readers would not reasonably expect, should be disclosed clearly and conspicuously, in terms that convey what the connection is. The FTC's FAQ on the Guides speaks to links inside reviews: "In some instances – like when the affiliate link is embedded in your product review – a single disclosure may be adequate." The same FAQ notes that "A disclosure in the comments to a post is easily avoidable and thus not clear and conspicuous."
Comparisons carry one more layer. The FTC's policy statement on comparative advertising, 16 CFR 14.15, in our paraphrase, encourages truthful comparisons, judges them by the same test as other advertising (whether they tend to deceive) and favors comparisons whose bases are clearly identified. Whether either text applies to your article, and how, is a question for your own counsel. As an editing standard, they explain the checklist below: say who could be paid, say what you compared, and make every cell true.
Who could be paid depends on who signed. The sample Channel Partner Agreement names the Partner as "[an individual, or entity type and jurisdiction]", so the disclosure names you or your firm accordingly. Partners sign that agreement before submitting introductions, and SourceX's terms add no marketing rules of their own.
What the agreement says about naming SourceX in a comparison
Three lines in SourceX's published documents bear directly on a comparison article.
- Section 4.5 of the sample agreement: "No data license, trademark license or right to train models is granted. Neither Party may publicly identify the other as a partner or disclose non-public deal details without written authorization, except as legally required." A column headed "our partner" or a SourceX logo plainly falls under it and waits for SourceX's written OK. For a plain factual mention of SourceX as one option, the documents say nothing further, so any doubt goes to SourceX.
- Section 7.1: "Partner is not an agent of SourceX and may not commit SourceX to prices, licenses, payouts or other obligations." A table cell that promises an outcome SourceX has not promised is a commitment you cannot make.
- Section 2 of the terms: credit is decided from dated records, and "an earlier link click alone does not decide credit." Lines such as "use my link so I get credit" misstate how credit works.
Where a question is not covered by those lines, such as whether a comparison may quote SourceX's page layout, the published documents do not settle it and SourceX decides.
The comparison disclosure and evidence checklist
Run every line on the article as it will render, on a phone as well as a desktop.
| # | Check | Passes when | Fails when |
|---|---|---|---|
| 1 | Disclosure placement | A plain line sits directly above the table and beside each paid link | It lives only in a footer, sidebar or about page |
| 2 | Disclosure wording | It says who could be paid, by whom and for what | "Affiliate links may be present" |
| 3 | Criteria first | The criteria are written above the table before any score or verdict | Criteria appear after the verdict, or change per option |
| 4 | Same yardstick | Every option is judged on every criterion | SourceX gets rows the others do not, or the reverse |
| 5 | Dated facts | Each program fact links that program's own page and carries the date checked | A fact comes from a forum, a reseller or memory |
| 6 | Missing figures | A figure a program does not publish reads "not published" | A blank, a zero or a guessed range |
| 7 | No pay ranking | No "best", "#1" or pay superlative that your reward could have shaped | A winner badge over the paying option |
| 8 | Comparable terms | Base, cap, trigger, eligibility and written terms sit side by side | Headline caps alone are compared |
| 9 | SourceX as published | SourceX's reward appears as its offer block, whole, and its other facts as SourceX words them | A paraphrased rate with the conditions dropped |
| 10 | Link language | The link text says what it is, without claims about credit | "Use my link so I get credit" |
| 11 | Name and logo | No "our partner SourceX" and no logo without written authorization | A partner badge copied from somewhere else |
| 12 | Owner and re-check | A named owner and a re-check date sit with the article's record | Nobody rereads it after a program changes its terms |
Method note. The twelve lines were written for this guide from SourceX's terms (version 2026-10-22.2, since replaced by version 2026-11-04), sections 4.5 and 7.1 of the sample Channel Partner Agreement, the FTC's FAQ on its Endorsement Guides, 16 CFR 255.5 and 16 CFR 14.15, read on 28 October 2026. They have not been tested on reader behavior, and no data on how readers respond to comparison disclosures has been published.
Line 8 matters most for referral comparisons. A higher advertised cap does not establish higher expected earnings, because programs differ on what the percentage is taken from, when anything becomes payable and which companies count. The ten-line rubric that keeps the headline number out of the score covers the reader's side of that decision; this checklist covers the writer's.
One real row, audited against its source
The table below is Illustrative in its layout and in Option B; the SourceX cells are checked against SourceX's terms as published on 4 November 2026 (version 2026-11-04).
| Row | Draft SourceX cell | Source | Approved SourceX cell |
|---|---|---|---|
| Base | "A share of the deal value" | Terms section 4: Actual Supplier Payout excludes "SourceX's fees and the Acquisition Partner's full transaction price"; "The reward is not calculated on SourceX's fees or revenue." | the greater of $50,000 plus 5% and 15% of what SourceX actually pays the company, never a share of SourceX's fees |
| Floor and cap | "Capped per company" | Terms section 4: no cap per transaction, per company or in total; the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and repeats first agreed within 12 months pay 15% | No cap. The USD 50,000 floor applies once per company, on its first qualifying transaction; repeats within the 12-month Repeat Window pay 15% of Actual Supplier Payout |
| Trigger | "Paid within 60 days" | Terms section 5 counts 60 calendar days from whichever comes later, final written acceptance by the Acquisition Partner or completed handoff, once every payment condition is met | Payable only after SourceX pays the company and the conditions in section 5 are met |
| Company's payment | "Free for the company" | Terms section 4: the reward "is never deducted from the supplier's agreed compensation" | SourceX pays the reward separately; the company's payment is unchanged |
| Estimates | "Typical reward" | Terms section 5: "Estimates shown in the portal or calculator are projections, not promises." | Not published |
Option B, the Illustrative other program, gets the same five rows from its own published terms, with "not published" where it states nothing. The disclosure above the finished table reads: "We may be paid by SourceX if a company we introduce licenses data to it. We are not paid by Option A or Option B." If you are paid by more than one option, the line names each.
The company-payment row deserves care because it is often overstated. The terms sentence supports exactly this: the company is paid the same amount whether or not a partner introduced it, because SourceX pays the reward separately, from its own share. It does not support "free", which implies the company spends nothing at all, including its own time.
Scope, timing and permission for the whole article
Scope. A comparison written for introducers answers "which program should I join?"; one written for companies answers "how could we license our records?". Do not reuse a table across the two. A founder reading a referral-economics row learns nothing useful and may read it as a sales pitch. For the company-facing version, point readers to who qualifies rather than summarizing fit, and leave every price question to the company's own conversation with SourceX.
Timing. Programs change their terms. SourceX's section 11 says it may publish new versions, and it published five between 12 and 22 October 2026. Print the date checked under the table and reread every row when any compared program changes its terms.
Permission. A column headed "our partner", a logo or any non-public detail needs SourceX's written authorization under section 4.5. Whether a bare factual mention needs anything is not settled by the published documents; ask SourceX if you are unsure. File SourceX's written authorization, if you get it, with the article's evidence packet.
Publish with the disclosure, or correct the comparison
Publish only when all twelve lines pass. For disclosure wording in other formats, the FTC disclosure examples for referral posts offer plain lines you can adapt; when the comparison sits inside advice to a client, read disclosing an incentive without implying independent advice and check when a referral relationship must be disclosed in writing.
When a row turns out wrong, or a program changes its terms:
- Correct the cell and add a dated correction note under the table.
- Update the checked-on date for every row you reread, not only the one that changed.
- Fix copies of the table in decks, newsletters and PDFs.
- Log the change, with the old and new wording, in the article's record.
More guides for partners who publish sit in the guides hub.
What a disclosed comparison still cannot do
- It does not make an interested comparison neutral. Disclosure tells readers about your stake; it does not remove it. If a fair comparison is impossible for you, publish a disclosed recommendation instead and call it that.
- It cannot verify another program's terms for you. Each row is only as good as the page you checked and the date you checked it.
- Professional rules may add duties. Whether you may accept a referral reward at all, and what you must tell clients, depends on your profession and your clients' contracts; ask your counsel or ethics adviser.
- FTC texts are guidance and policy statements. Their reach over your article is a legal question for your counsel.
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.
Run the twelve lines before your comparison goes live, register as a partner before the article carries a link that could pay you, send company readers to who qualifies and cite the program terms by version in every SourceX row.