# Customer advisory board data partnerships plan | SourceX

Canonical: https://refer.sourcex.si/guides/the-customer-advisory-board-discussion-about-data-partnerships
Last updated: 2026-11-04

A customer advisory board is the right place to learn whether your customers want to hear about licensing their own operating records, and the wrong place to recruit them. Run the session as research: ask what members' companies keep, what would worry them and who would decide. Never quote their usage data. Offer an introduction to SourceX only afterwards, in a separate step, to members who ask for one and whose CEO wants the conversation.

Your company's role stays introduction-only from the first invitation to the last email. SourceX licenses business records directly from the company that created them, and that company's CEO decides whether to discuss it. Nothing in the plan below needs your product, your data team or a single customer record.

## What the CAB session is for, and what it cannot settle

The session answers one question: would members value knowing that their company could license its own records, and on what conditions would they want to hear about it from you? It cannot settle whether any member's company qualifies, what its records are worth or whether a licensing discussion should begin. Those depend on facts only the member's company holds, and on SourceX's own review.

The line between research and selling is old and well drawn. The ICC/ESOMAR International Code, the market research profession's global code, tells researchers to keep a clear distinction between research and non-research activities. Its 2025 text adds that people must be told about any promotional or commercial follow-up before data collection begins, and that a non-research purpose needs its own consent. A CAB is not a formal survey and the code binds its signatories, not your product team, but the logic carries over cleanly: a referral offer is commercial follow-up. Announce it in the pre-read, keep it out of the discussion and let members choose it separately.

Members also arrive with a fair suspicion: when a vendor says "data partnerships", it may mean the vendor wants their data. Answer that in the first five minutes, before anyone has to ask. Advisors who sit on one company's advisory board face a different, one-to-one version of this conversation, covered in the [advisory board guide](/guides/how-to-be-a-good-advisory-board-member); this plan is for a vendor talking to its customer board.

## Who in the room benefits, and who can say yes

The benefit belongs to the member's company, not to you. A company that licenses records to SourceX is paid by SourceX under an agreement it negotiates and signs itself, and its subscription with you does not change. Your company may earn a referral reward if it introduces that company, and members should read that in the pre-read rather than discover it later.

Most CAB seats are held by functional leaders, which shapes what each person can tell you.

| Seat-holder | What they can describe | What they cannot do |
|---|---|---|
| Head of support or operations | Which record types the team keeps and for how long, at category level | Authorize a licensing discussion |
| CIO or IT director | Which systems hold the history and who administers them | Decide what the company licenses |
| CFO or controller | Whether records were ever licensed before, or rights granted to vendors | Sign for the company |
| CEO, or an owner who is CEO | All of the above, at a high level | Authorize the discussion and sign, if the company proceeds |

Under the program the CEO is the person who authorizes a licensing discussion. A head of support who loves the idea is a sponsor inside their own company; the plan treats them as one and never as the decision.

## The CAB research discussion plan

Forty-five minutes in six blocks, plus a pre-read. A neutral moderator runs it, ideally a researcher or product manager with no renewal target. The partnerships director observes and takes notes.

**The pre-read, sent a week ahead, in four sentences.** It names the topic (how companies think about licensing their own operating records for AI training and evaluation). It says the session is research and nothing said in it will be used to contact anyone. It says a separate, optional follow-up exists for members who later want an introduction to SourceX, and that your company may receive a referral reward from SourceX if one leads to a license. And it promises that no data from your product will be referenced.

| Block | Minutes | Prompt to the room | What the note-taker records | Leave out |
|---|---|---|---|---|
| 1. Frame | 5 | "Some AI developers license business records directly from the companies that created them. We are not part of that and see none of your records. We want to know how you think about it." | Questions members ask | Rewards, SourceX's process beyond one sentence |
| 2. What you keep | 10 | "Which kinds of operating records does your company keep for five years or more, and roughly where?" | Record categories and system types, tallied by how many members name each | Volumes from your product, named clients, files |
| 3. What would worry you | 10 | "If a vendor raised this with you, what would make you uneasy?" | Concerns in members' words, unattributed | Rebuttals; the moderator only asks follow-ups |
| 4. Who decides | 8 | "In your company, whose decision would this be, and who would they consult first?" | Roles named | Pressure to name a person |
| 5. What would help | 7 | "Which would you want from us: nothing, a short reading list, or an introduction later?" | Count of each choice | Taking introduction requests in the room |
| 6. Close | 5 | "The follow-up is separate and optional, and it will come by email." | Nothing new | Sign-up sheets passed around the table |

Block 2 is where sessions go wrong. Members describe categories, such as dispatch notes since 2012 or a support desk run for nine years, and the note-taker tallies them. If someone reads out a number from your product's admin screen, the moderator thanks them and moves on: that figure came from your platform, and the session should not trade on it. The [SaaS operating-knowledge guide](/guides/how-to-identify-operating-knowledge-in-a-saas-business) lists the record families members tend to name.

**The readout.** One page: the record categories and how many members named each, the concerns grouped by theme, the decision roles, and the count for each option in block 5. No member names beside concerns and no product metrics. If most members picked "nothing", that is a finding about your customer base, not a failed session.

## Keep the platform's view of each customer out of the plan

Hosting a customer's records gives your company access to them under the subscription. It gives you no right to license them, to describe them to a third party or to choose customers by them. Three rules follow.

1. **Do not choose invitees by data volume.** Use the CAB you already have. A guest list built from storage or ticket counts tells members you looked.
2. **Do not cite what your product knows.** "You have eleven years of work orders with us" is your telemetry speaking, and members will hear it that way.
3. **Watch for records that belong to the member's own clients.** A member that provides services may hold mostly client material, which SourceX's published screening treats as usually not a fit. That is the member's question to raise with its counsel, not yours to answer; the guide to [company data versus customer-owned data](/guides/how-to-distinguish-company-data-from-data-owned-by-its-customers) and the page on [SaaS customer data rights](/questions/saas-customer-data-ai-training-rights) help the member's team do it.

Your own company's internal records, such as its support history and engineering runbooks, are a separate licensing question for your own CEO. Keep them out of a session about customers.

Established co-selling programs apply the same consent discipline. Microsoft's Partner Center tells partners to obtain the customer's consent before giving Microsoft a customer's contact details, because Microsoft can use them to contact the customer directly. Treat a CAB member's name the same way: it reaches SourceX only after the member asks.

## From the session to an introduction, one member at a time

After the readout, send the follow-up the pre-read promised, once, to every member, whatever they chose in block 5. It offers three things: a link to SourceX's [who qualifies](/who-qualifies) page, a named contact at your company for questions, and your partner link for any company that wants to apply.

An introduction then needs two confirmations in writing: the member asks for it, and the member's CEO wants the conversation (or the member is the CEO). Before submitting anything, your company signs the SourceX Channel Partner Agreement; a copy your company signed under the agreement's former title, Channel Partner Non-Circumvention and Non-Disclosure Agreement, stays valid in the form your company signed. Credit goes to the first valid introduction of a company inside the 90-day attribution window and is settled when that company submits a verified application. A click on your link does not decide it.

Fit questions stay at metadata level: full-time headcount at peak (the program looks for 50 or more, contractors excluded), how many years the records span, which systems hold them and who owns them. The company applies itself and shares records only with SourceX, under its own agreement.

Run the plan with one CAB cohort before any wider marketing, and watch three trust signals for 60 days afterwards: tickets or emails asking whether you share customer data, mentions of the session in renewal or QBR notes, and members who leave the board. If any of them rises, find out why before a second cohort hears about it.

## One session, written up (Illustrative)

Illustrative. A fictional vendor and board; the counts are invented to show how a readout is read.

A field-service scheduling vendor runs the plan with its 12-member CAB. In block 2, nine members name work-order or dispatch histories older than five years. In block 3, the two concerns heard most are "Would you see what we send?" and "Does this touch our contract?" In block 5, six choose the reading list, three choose a later introduction and three choose nothing.

Three members ask through the follow-up, and the outcomes differ:

| Member company (Illustrative) | What the follow-up established | Decision |
|---|---|---|
| 70-person HVAC contractor | Owner is the CEO, wants the conversation, 14 years of work orders the company created | Introduced through the partner link |
| 35-person installer | Below 50 full-time employees at peak | Told plainly it does not fit today |
| Facilities outsourcer | Work orders belong mostly to the building owners it serves | Rights question sent to its own counsel; nothing submitted |

One introduction from twelve members is not a conversion rate. It is one company that wanted a conversation, reached without spending anyone's trust. The [software and SaaS industry page](/industries/software-and-saas) and the [guides hub](/guides) cover what comes next on the company side.

## 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.

When your readout shows a member who asked for an introduction and a CEO who wants the conversation, [register for a partner link](/register), check that company against [who qualifies](/who-qualifies) and read the [program terms](/terms) before you submit anything.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://standards.esomar.org/assets/documents/icc-esomar-code-2025.pdf
- https://learn.microsoft.com/en-us/partner-center/referrals/manage-co-sell-opportunities
