# Customer onboarding history referral: what to say | SourceX

Canonical: https://refer.sourcex.si/guides/customer-onboarding-histories-what-can-a-partner-say-publicly
Last updated: 2026-11-04

In public, talk about onboarding records as a category and about how the referral program works, and stop there. Anything that names or could identify a client, says its records exist or are available, describes its customers or its onboarding method, or hints at a deal stays private, and reaches anyone only in wording the client's CEO has approved in writing. SourceX's own deal terms say neither side publicizes a deal. A partner who is not even a party to it has less reason still.

Specialist advisors and operators see onboarding histories up close: the implementation consultant who rebuilt a client's kickoff process, the customer success advisor who audited a year of setup tickets, the fractional COO who sat in on go-live reviews. That access is exactly why their public words carry weight, and why a careless post can do more damage than a stranger's.

## What an onboarding history holds, and whose words are in it

SourceX's own guide to [customer onboarding records](https://sourcex.si/data/customer-onboarding) describes them as the record of how new customers are set up: steps, questions, delays and fixes. It lists onboarding checklists, kickoff notes, setup tickets and time-to-value milestones, usually kept in tools such as Salesforce, HubSpot, Gainsight or Jira, and its preparation checklist removes customer names and contacts and leaves contract terms out. That page is the technical guide for suppliers; this one is about what you say.

Inside any one onboarding history sit three kinds of author:

- **The company's own work.** Checklists, playbooks, internal kickoff notes, its staff's replies on setup tickets, milestone tracking.
- **Customer content.** Data files sent for migration, org charts, requirement documents, contract terms, the customer's own emails.
- **Third parties.** An outside implementation firm's project notes, a software vendor's setup guides pasted into tickets.

Only the first layer is plausibly the company's to license. SourceX looks for material a company created itself and can license without breaching client confidentiality, employee privacy or third-party contracts; material that belongs to its clients is usually not a fit. The [onboarding and training data page](/data-types/onboarding-and-training) and the guide to [assessing original onboarding materials](/guides/how-to-assess-original-onboarding-materials) cover the record type itself.

## Three rooms, and what belongs in each

Every statement a partner makes lands in one of three rooms.

- **Public:** posts, talks, panels, newsletters, closed groups with more than a handful of people. Here you talk about the category, the program, your role and your possible reward.
- **Private, with the client:** the relationship owner first, then the CEO. Here you ask the bounded questions further down.
- **Inside SourceX's process:** once the company applies, it describes its records to SourceX directly, and SourceX says those summaries stay private between the company and SourceX. You are not in this room.

## The public-summary boundary examples

Ten sentences a partner might be tempted to write. Each is Illustrative, and each is placed by what it reveals, not by how it is phrased.

| Sample sentence (Illustrative) | Where it belongs | Why |
|---|---|---|
| "Onboarding checklists, kickoff notes and setup tickets are one kind of operating record AI developers study." | Post it | A category, with no client in it |
| "I introduce companies to SourceX and may earn a referral reward if a deal completes." | Post it | Discloses your interest before anyone has to ask |
| "As the company said in its own case study, it rebuilt onboarding in 2024." | Post it, exactly as the company said it | Repeats what the company chose to publish; never tie it to data or licensing |
| "One of my clients, a 300-person payroll software firm, has nine years of onboarding records." | CEO-approved wording only | No name, but size, sector and years can identify a client in a small market |
| "We helped a client organize its onboarding history for a licensing review." | CEO-approved wording only | Reveals that the client is weighing a license |
| "[A named company] has nine years of onboarding records and is talking to SourceX." | Never public | Names the company and a possible deal |
| "Their playbook gets new customers live in 14 days, and here is how." | Never public | The company's method, which may be worth more because it is not public |
| "Their onboarding files include customers' org charts and data exports." | Never public | Describes customer content, which belongs to the customers |
| "Most of their customers are regional banks." | Never public | Identifies the company's customers |
| "An outside firm ran their onboarding and kept the notes in its own tool." | Never public; ask it privately | Ownership is uncertain, and only the company and SourceX's rights review can settle it |

Three reasons sit behind the "never" rows. First, SourceX's process page says neither side publicizes a deal, so a partner announcing one gets ahead of both parties. Second, the signed Channel Partner Agreement governs confidentiality, and the program terms say its confidentiality obligations last three years, longer for trade secrets while they remain protected. Third, a company's onboarding method can be the kind of information federal law protects: under 18 U.S.C. § 1839(3), something counts as a trade secret only if its owner has taken reasonable measures to keep it secret and it gets value from not being generally known. A partner who posts a client's method works against both conditions.

"CEO-approved wording only" means the CEO approves the exact words, in writing, for a named audience and a single use. A general "sure, mention us" does not cover a post written later.

## Original work, mixed content and an uncertain owner (Illustrative)

Illustrative. Three generic companies with invented facts; no outcome implied.

| What we compared | Original work | Mixed content | Uncertain owner |
|---|---|---|---|
| Company | 180-person HR software company | 240-person benefits administrator | 95-person logistics software company |
| What the history holds | Eight years of checklists, kickoff notes and setup tickets written by its own implementation team | Its staff's notes, mixed with employers' census files and plan documents attached to tickets | Summary milestones only; a reseller ran five years of onboarding in its own project system |
| What you may say publicly | Category talk only | Category talk only | Category talk only, and nothing about the reseller |
| What you ask privately | Whether the CEO wants a conversation | What share of the history is the company's own notes | Who holds the reseller's project notes, and under what agreement |
| Likely outcome of the screen | A conversation, if the CEO wants one | A conversation about the company's own layer, with customer files left out | Rights review settles it; you do not guess |

The public column is identical in all three. That is the point: what a partner may say in public does not improve as the records get better.

## Find the owner of the history and where each part came from

The person who knows an onboarding history best is usually the head of customer success, the onboarding or implementation lead, or whoever administers the customer success or ticketing tool. None of them decides on licensing; the CEO agrees to a licensing discussion and signs for the company. Your relationship may run through any of them, and an introduction made without the CEO's knowledge is usually not a fit.

Trace origin layer by layer before any introduction: who wrote it (employees, customers, an outside firm), whose account holds it now, and whether any contract with a customer or implementation partner says something about reuse. The last question is for the company and its counsel; the [confidentiality clause guide](/guides/confidentiality-clause-use-restriction) explains why use restrictions matter. The related [implementation project records page](/data-types/customer-implementation-project-records) covers the delivery records that often sit beside onboarding.

## Bounded questions that need no files

Ask these privately, through the person who owns the relationship. None needs a file, a screenshot, a customer name or a login.

1. Which systems hold onboarding checklists, kickoff notes, setup tickets and milestones, and from which year?
2. Roughly how many customers are onboarded in a year, and over how many years does that history run?
3. Who wrote most of it: your own team, your customers or an outside firm?
4. Do setup tickets carry customer files, and roughly what share of them?
5. Did a reseller or implementation partner run any onboarding in its own tools?
6. Has any of this been licensed for AI training before? Data already licensed for that purpose is out.
7. Would the CEO want a conversation, and may I give the company's name to SourceX?

SourceX's own first step is a few questions with no files attached, so nothing above asks for more than SourceX would. When the CEO says yes, the [six-turn private conversation](/guides/a-linkedin-conversation-that-leads-to-an-authorized-introduction) shows how to keep the exchange off public channels.

## Where the boundary needs more than a table

- **Your own contract comes first.** An NDA or services agreement with the client can be stricter than anything here, and it governs.
- **Regulated onboarding.** Where onboarding includes identity checks, the records hold personal details such as government IDs, which SourceX's preparation removes before anything is shared. Never describe them at all.
- **Small markets.** Anonymity fails fastest where few companies do the same work. If a reader could guess the client, treat the sentence as identifying.
- **Closed groups are public.** A private community of 2,000 members is an audience, not a conversation.
- **Approval expires.** Approved wording covers the use it was approved for. Ask again for the next one.

The figures behind these boundaries, such as how often public posts lead to complaints or introductions, have not been published. If you want to know for your own practice, log each public mention, the client's reaction and whether an introduction followed.

## 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 public talk to the category and your own role, and when a client's CEO wants a private conversation about its onboarding history, [register for a partner link](/register), check the company against [who qualifies](/who-qualifies) and read the [program terms](/terms). How to [raise your reward with a business contact](/guides/how-to-discuss-referral-rewards-transparently-with-a-business-contact) is covered separately, and more partner guides are in the [guides hub](/guides).

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/data/customer-onboarding
- https://sourcex.si/how-it-works
- https://www.law.cornell.edu/uscode/text/18/1839
