# Referral content review: numbers and definitions | SourceX

Canonical: https://refer.sourcex.si/guides/a-referral-content-review-that-checks-numbers-and-definitions
Last updated: 2026-11-05

A factual review of referral content checks more than whether a figure appears somewhere in SourceX's documents. For each number it asks what the figure counts, which definition keeps it true, which sentence it rests on, what scope and date that sentence covers, and whether you may repeat it. Most errors in partner copy are right numbers with their definitions stripped off: 50 employees without "full-time, at peak", 60 days without its trigger, 90 days without the event that starts the count. Restore the definition, cite the sentence, or delete the number.

This sheet is for whoever signs off a partner firm's referral copy, from web pages and slides to the paragraph an agency drafted. It sits beside two narrower reviews. Lines about money go through the [payout claim checklist](/guides/the-partner-marketing-checklist-before-publishing-a-payout-claim), and the job of keeping each program sentence on the current terms version is covered in [aligning partner pages with the current terms](/guides/how-to-keep-partner-pages-aligned-with-current-program-terms). This review takes every other figure, and every word that SourceX defines more narrowly than everyday English does.

## Why the number is rarely what goes wrong

SourceX's documents give one figure several jobs. Sixty days appears twice. On SourceX's process page it is the company's payment term, due after a valid invoice that follows Closing unless different terms are signed. In section 5 of the program terms it is the partner's reward deadline, counted from a different event entirely. Section 8 keeps the two apart: "a supplier's payment timetable, including any Net 60 clause, never determines when referral rewards are paid."

Thirty days is busier still: the process page uses it for the initial assessment, the acceptance review and deleting data that never closed, and section 9 of the terms uses it for notice to end the partner agreement. A post that says "SourceX works in 30-day cycles" is built from real numbers and is still false.

The pattern holds for words. "Relationship" in section 3 of the terms is far wider than its everyday sense: "A relationship includes any earlier lead, account or email correspondence between SourceX and the company, however it began." A partner page that promises credit "if the company has never worked with SourceX" uses the everyday sense and misstates the rule.

## The claim, its readers and your stake in it

Three groups read your figures differently. A CEO reads a number as a condition or a promise about the company. A professional weighing whether to join your referral effort reads it as an expectation. Your colleagues copy it into decks, where it loses whatever qualifier it had.

Your own interest is the reason accuracy is owed. Whoever signed the Channel Partner Agreement may be paid if a company it introduces completes a qualifying transaction, so a figure in your content is never neutral. The FTC's Guides on endorsements say in section 255.1: "Endorsements must reflect the honest opinions, findings, beliefs, or experience of the endorser." The same paragraph, in our paraphrase of the eCFR text, bars an endorsement from conveying a claim that would be deceptive if the advertiser made it directly. Whether the Guides reach your content is a question for your own counsel. As a working test it is useful anyway: publish no number SourceX could not stand behind in the same words.

Figures in partner copy come from five places: SourceX's program documents, its process page, third-party publishers, your own records and the companies you write about. Each needs its own source, and the sheet below gives every one a row.

## The number-definition-source QA sheet

Fill one row for every figure and every defined word in the draft. A row passes only when the published copy carries the definition in the same sentence, or links straight to the sentence that does.

| Figure as drafted | What it counts | Definition it needs to stay true | Rests on | Fix when the definition is missing |
|---|---|---|---|---|
| "50 employees" | Full-time employees at the company's peak | Full-time only, at peak, contractors left out; a staffing firm counts its own staff, never workers placed with clients | Terms section 1; who-qualifies | "50 or more full-time employees at peak, contractors excluded" |
| "90 days" | The attribution window | From the recorded introduction to the company's verified application; it does not stretch while contact protection runs | Terms section 2; Schedule A paragraph 2 | Name both ends of the window |
| "60 days" for your reward | The reward payment deadline | Starts at whichever comes later, the Acquisition Partner's final written acceptance or completed handoff; an open condition defers payment with no fresh period | Terms section 5 | Name the trigger, or link section 5 |
| "60 days" for the company | The company's payment term | After Closing and a valid invoice, unless the company signed different terms | SourceX process page | Never set beside the reward deadline as one clock |
| "6 months" | Contact protection after the agreement ends | Covers contacts introduced during the term; credit is a separate clock | Terms section 9; sample agreement 3.2 | Never present it as a credit window |
| "70%" | Share of the company's data in English | Applies only to the listed countries outside the U.S., Canada and the EU | Who-qualifies | Paste the geography sentence whole |
| "7 to 14 days" | Commercial feedback at step 6 | A target at one step, after the Confirmation is signed, not a promise and not the whole process | SourceX process page | Quote "target, not a promise" with the step, or drop it |
| "One partner" | Partners credited per company | The first valid introduction, decided from dated records; a link click alone decides nothing | Terms section 2 | Keep "first valid" and "dated records" |
| the greater of $50,000 plus 5% and 15% and "no cap" | The reward formula and the once-per-company floor | the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; the USD 50,000 floor applies once per referred company, to its first qualifying transaction, and repeats within the 12-month Repeat Window pay 15% with no floor | Terms section 4; offer block | Use the offer block and the payout checklist |
| "New company" | A company SourceX did not already know | Any earlier lead, account or email correspondence makes a duplicate | Terms section 3 | Replace "never worked with SourceX" |
| A market estimate | Whatever its publisher defined | The publisher's own scope words, year and method | The publisher's page | Quote scope and date, or drop it; never link it to any payout |
| "Companies we have introduced" | Whatever you define | Your definition in the same sentence | Your own dated records | Define it, or drop it |

The geography row has one acceptable text, copied from the who-qualifies page: 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.

**Method note.** The rows come from SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), its who-qualifies, process and trust pages, the unsigned sample Channel Partner Agreement, and section 255.1 of the FTC's Endorsement Guides, all read on 2026-10-28. We chose the twelve figures because each one carries a definition that is easy to drop. The sheet has not been tested against how readers interpret partner copy, and no such data has been published.

## Evidence, scope, time base and permission: four tests for every row

**Evidence.** The sentence exists on its publisher's page, and you read it on a date you recorded. A paraphrase of someone else's paraphrase fails, even when it happens to be right.

**Scope.** Ask what population, step or document the sentence covers. The who-qualifies page says "SourceX applies the criteria of the specific program, not one universal minimum", and that some programs set higher thresholds. A size figure is therefore a published floor, not a pass mark, and copy that implies "50 or more means you are in" overstates it. When two SourceX pages phrase a figure differently, cite the terms for what an introduction requires and link who-qualifies for screening detail.

**Time base.** Every figure is true as of a date. Record the version line of the terms and the update date of each SourceX page you used, and treat a change in either as a reason to re-run the affected rows.

**Permission.** A figure about a named company is that company's information and appears only with its CEO's agreement. Figures a fund knows from board packs never appear at all; the who-qualifies page puts it plainly: "The fund's knowledge is a reason to ask the CEO, never material to pass along." Status you receive from SourceX stays private too: section 4.6 of the sample agreement says partner updates come as generic stages or reference codes. Security figures fail on evidence: SourceX's trust center lists its three security certification and audit-report initiatives as in progress, with none yet issued, so no partner copy may describe SourceX as certified.

## One real sentence, three partner drafts (Illustrative drafts)

The source sentence is real, from step 6 of SourceX's process page: "Commercial feedback usually takes 7–14 days; that is a target, not a promise, and positive interest is not yet a purchase." The three drafts that reuse it are invented for this guide.

| Test | Draft A: "SourceX gets back to companies within two weeks" | Draft B: "Expect commercial feedback in 7 to 14 days" | Draft C: "SourceX's process page gives a target of 7 to 14 days for commercial feedback once a company has signed its Dataset Deal Confirmation, and calls it a target, not a promise" |
|---|---|---|---|
| Evidence | Fails: rounded, no source | Passes: the figure matches | Passes: quoted, linkable |
| Scope | Fails: reads as the first reply to an application | Fails: no step named | Passes: step and stage named |
| Time base | Fails: a target turned into a commitment | Fails: "expect" implies a promise | Passes: "target" kept |
| Permission | Passes: public page | Passes: public page | Passes: public page |
| Verdict | Rewrite or delete | Rewrite | Publish with the link |

Draft A is the one most firms publish, because it is short and sounds helpful, and it is the one a CEO will quote back when a reply takes longer. Draft C is longer, and it is the only one a reviewer can defend line by line.

## Release with a disclosure, or correct the figure

A draft is ready when every row passes. Publish it with your interest stated near the content, in plain words: "SourceX may pay us a reward if a company we introduce licenses data to it, and the company is paid the same either way." The last clause rests on section 4 of the terms: "The referral reward is paid separately by SourceX and is never deducted from the supplier's agreed compensation." File the completed sheet with the published version.

When a published figure fails, fix it where it lives, add a dated correction note and look for the copies in decks, PDFs and templates. A wrong number inside an image needs its own handling, set out in [correcting a shared referral graphic](/guides/how-to-correct-a-shared-referral-graphic-with-wrong-economics). A wrong message that has already been forwarded is handled in [correcting an overenthusiastic message](/guides/how-to-correct-an-overenthusiastic-message-before-it-spreads). Growth figures about your own program need the cohort file described in the [rapid-growth evidence guide](/guides/the-evidence-behind-a-claim-of-rapid-partner-growth), and [the line between an interesting angle and an unsupported claim](/guides/the-difference-between-an-interesting-angle-and-an-unsupported-claim) helps with the framing around a number.

## What the sheet cannot catch

- **Sums of true figures.** Adding SourceX's step targets into a total timeline produces a number nobody published, and a guess.
- **Design.** A correct figure in display type above its definition in a footnote still misleads. Review the rendered page on a phone.
- **Translations.** A translated page needs its own pass in the language it is published in.
- **Questions the terms leave open.** Where they are silent, for example on credit when someone else introduced a sister company, write that SourceX decides.
- **Your professional rules.** Whether you may accept a reward at all is for your own counsel or ethics adviser.

More partner questions 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.

Run your next draft through the twelve rows before it goes out, [register as a partner](/register) if you have not signed yet, send readers to [who qualifies](/who-qualifies) rather than restating fit in your own numbers, and cite the [program terms](/terms) by section wherever a figure rests on them.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/how-it-works
- https://sourcex.si/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://sourcex.si/trust
- https://www.ecfr.gov/current/title-16/chapter-I/subchapter-B/part-255/section-255.1
