The risk with a customer webinar is that it becomes a pitch wearing a teaching costume. The format below is built the other way round: five of its six segments would be worth running if the referral program did not exist, and the sixth takes three minutes.
Who the session serves, and who has to sign off
Start with the customer's benefit, because it is the only reason to take an hour of their time. Most companies have never listed their own operating history: the procedures, project files, QA records, approvals and support workflows their people wrote while running the business. Knowing what exists, where it lives and who owns it is useful for audits, system migrations and sale preparation, whether or not they ever license a record. SourceX licenses approved business records directly from companies for AI training and evaluation, which gives that inventory one more possible use.
Apply one test before you schedule anything: would a customer who never licenses a record still rate the session worth attending? If your draft agenda fails that test, cut it until it passes or cancel it.
Who to invite. Customer executives and operations leaders. Only the customer's CEO can authorize a licensing discussion and sign for the company, so attendees from operations, finance or IT are carrying information back, not deciding. Say so in the session; it removes pressure from everyone on the call.
Who signs off on your side.
| Role at your company | What they approve | Why it matters |
|---|---|---|
| Partnerships director | Agenda, presenter, measures and stop rule | Owns the session and its outcomes |
| Privacy or legal | How the invitation list is built, the disclosure wording, recording and retention | Keeps the session inside your own promises about customer data |
| Customer success leadership | Which accounts are excluded, for example those mid-escalation | Protects live relationships |
| Marketing operations | Sending through your normal system with a working unsubscribe | Keeps the invitation compliant |
The customer-owned data education format
Forty minutes, six segments, one rule running through all of them: no example, number or screenshot comes from your product.
| Segment | Minutes | What it covers | What stays out |
|---|---|---|---|
| 1. Why your own records matter | 5 | The difference between records a company creates and records it only holds for others | Any reference to your platform's data |
| 2. What you own and what you do not | 10 | Employee-created material, contractor material, client-owned material and personal data | Advice on any attendee's own contracts |
| 3. Map your records | 10 | A worksheet each attendee fills in privately, metadata only | Uploads, screen shares of real records, polls that collect volumes |
| 4. How direct licensing works | 8 | The public SourceX screening profile, who authorizes and what review decides | Price, earnings estimates, buyer names |
| 5. Who it rarely fits | 4 | The cases SourceX lists as usually not a fit | Pressure to self-qualify live |
| 6. Disclosure and close | 3 | The disclosure slide and how to request a note to the CEO | A sales follow-up sequence |
Segment 2 in practice. The Copyright Office's Circular 30 explains that a work an employee creates within the scope of employment is a work made for hire, with the employer treated as its author. That is why a company's own procedures and project histories are usually its own, while material from outside contractors may not be unless rights were assigned. Say clearly that this is general information and that each company's counsel decides its own case; the circular itself notes that the Copyright Office cannot give legal advice about a particular work. Then name the cases that usually fail: personal consumer data, scraped data, material that belongs to the company's clients and one-off files with no documentation or context. The guide to telling company data from customer-owned data has worked distinctions you can adapt.
Segment 3, the worksheet. Attendees keep it; you never collect it.
| Record type | System | Oldest readable year | Administered by | Created by |
|---|---|---|---|---|
| Example: field service work orders | Example: dispatch system | Example: 2012 | Example: operations manager | Example: employees |
Segment 4, the facts to present. SourceX looks for established companies with 50 or more full-time employees at peak, contractors excluded, several years of documented operations, original material the company created and the rights to license it. 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. Relevance to SourceX's current data needs is decided in its review, so nobody on the call can say whether a company qualifies. Point attendees to the company fit checker, which is a preliminary, non-binding screen.
Segment 6, the disclosure slide.
We are part of the SourceX referral program. If a company introduced by us later licenses records to SourceX, SourceX may pay us a referral reward. It is paid by SourceX, it is never deducted from what SourceX pays your company, and it does not affect your subscription with us. If your CEO would like a short note about the program, reply to the recap email. Otherwise you will not hear from us about it.
Prepare for the question you will get. Somebody will ask whether you, the vendor, train AI on their data. Answer from your own current terms, and have that answer approved before the session. Customers can check any vendor's paperwork with the method in is my SaaS vendor training AI on my data.
Keep hosting access out of the invitation, slides and follow-up
Hosting a customer's records gives you access to run the service, not a view on what the customer should do with them. Three habits keep that line visible.
| Your access as the vendor | The customer's rights |
|---|---|
| You host and process records to run the service | The customer owns them and decides any other use |
| You may know their seat count or storage volume | None of it appears in the invitation, the slides or the follow-up |
| You hold the registrant list | It stays with you and is never passed to SourceX |
| You can describe the program | Only the customer's CEO decides whether to discuss licensing |
| You could technically export data | You never do it on the customer's behalf; any delivery runs under the customer's own agreement with SourceX |
Records your customers keep in your product are theirs and may be among the things they choose to discuss. Which records, and whether their own client contracts allow it, is settled between the customer, its counsel and SourceX's rights review. The mirror case, a software company licensing records it created itself, is covered in whether a SaaS company can license data for AI training.
The invitation and follow-up rules
The FTC's CAN-SPAM compliance guide states that the law makes no exception for business-to-business email, that commercial messages must explain clearly how to opt out and that opt-out requests must be honored within 10 business days. It also says that hiring another company to send your email does not hand over your legal responsibility. Treat the invitation as commercial email and follow these rules:
- Build the list from contacts you may already email about events, and send through your normal system with its unsubscribe working.
- Put the reward disclosure in the invitation itself, not only on the slide.
- Send one recap to all registrants: slides, the blank worksheet and the who qualifies page.
- Make a personal follow-up only to people who reply asking for a note to their CEO.
- For contacts outside the U.S., have counsel confirm the local email rules before sending.
How to word the CEO note without recommending an outcome is set out in making an introduction without endorsing.
Pilot one session and measure trust
SourceX has not published attendance, conversion or acceptance figures for customer webinars, and none are reported here. Run one session for a defined group, measure the following and decide from your own numbers.
| Measure | Definition | Threshold to set in advance |
|---|---|---|
| Useful-anyway score | Attendees rating "useful even if we never license" 4 or 5 out of 5 | Your normal webinar satisfaction level |
| Invitation unsubscribes | Opt-outs from the invitation compared with your usual customer newsletter | No higher than your newsletter's rate |
| Worksheet use | Attendees who say they completed it (yes or no, contents never collected) | Shows whether segment 3 worked |
| CEO notes requested | Replies to the recap asking for a note | The program-related output |
| Complaints | Any comment that the session used product data or felt like a pitch | Zero; one triggers a review |
Illustrative example. The operations director of a 220-person civil engineering firm attends, fills in the worksheet and finds 14 years of design review records and site inspection reports written by the firm's own engineers. She takes it to her CEO, who replies to the recap asking for a note. Your partner lead sends it, copied to her, and the CEO decides whether to apply. If that firm's Actual Supplier Payout were USD 100,000, the default reward on the first qualifying transaction would be USD 55,000; at USD 400,000 it would be USD 70,000. Illustrative figures only, not a forecast or a quote.
The company, not an individual presenter, should register as the partner and sign the SourceX Channel Partner Agreement before submitting. If attendees later apply, credit for each referred company goes to a single partner: the one whose valid introduction came earliest in the 90-day attribution window, with credit settled once the company submits a verified application. Any reward is payable only once the conditions in the terms are met, and falls due within 60 calendar days of whichever comes later: the dataset's completed handoff, or the Acquisition Partner's final acceptance, given in writing, of the complete, validated dataset. For an approach with no customer event at all, see the introduction-only program guide; for a quarterly touchpoint, see the optional QBR module.
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.
Once your draft agenda passes the useful-anyway test, register for a partner link, check the facts for segment 4 against who qualifies and read the program terms before the invitation goes out. Background for software audiences is on the software and SaaS industry page and in the guides hub.