How to add a data opportunity to a QBR without derailing it: a four-minute optional module that runs last, needs the sponsor's opt-in and never quotes product data

Short answer

Put it last, make it optional and keep it to four minutes. The data opportunity belongs after the customer's outcomes, adoption review and agreed actions, and only if the executive sponsor ticked an opt-in line on the pre-read. Talk about the operating records the customer created across its own business, never about what your product's analytics show. End with one question: would your CEO like a short, no-obligation note about licensing those records? A yes routes to the CEO. Anything else ends the item.

Visual briefFull-size diagram
A QBR agenda drawn as a bar of customer-owned segments, followed by an opt-in gate and a dashed four-minute optional module that branches into three exits: a note to the CEO, a revisit date or a logged no.
The module sits after agreed actions and only behind the sponsor's opt-in. Timings follow the method on this page.

A QBR that loses its agenda to a vendor's side offer costs more trust than any introduction can repay. The module below is built so that skipping it costs nothing and running it never touches your product data. MSPs have their own version in the MSP QBR agenda template, which works from the provider's system documentation.

Why a data item derails a QBR, and which rule stops each failure

Each rule in the module removes one common cause of derailment.

How the meeting goes wrongWhat usually causes itModule rule that prevents it
The customer's outcomes get squeezedThe side topic is placed earlyIt runs after agreed actions, with a hard four-minute stop
The sponsor feels ambushedNobody warned themAn opt-in line on the pre-read; no tick, no module
"How do you know that about us?"The vendor cites usage, storage or record counts from its productOnly the customer's own statements and public facts are used
It sounds like a bargaining chipRaised while price or renewal is being negotiatedSkipped whenever a renewal, price change or amendment is open
The wrong person is asked to decideThe sponsor is pushed for a commitmentThe only ask is whether the CEO wants a note
The customer suspects a commission pushAn individual is paid per referralThe company registers as partner and the reward stays out of quotas

Pass the benefit test before the opt-in line reaches a pre-read

The benefit has to be the customer's, not yours. SourceX licenses approved business records directly from companies for AI training and evaluation and pays the company under its own agreement. For a customer with years of documented operations, that can be a new use for records it already keeps; for one without them, the item is noise. So before the opt-in line goes on a pre-read, the account should pass a benefit test built only from evidence that does not come from your product:

  1. Size. 50 or more full-time employees at peak, contractors excluded, from the customer's public footprint or from what the sponsor has told you.
  2. History. Several years of documented operations the company created itself: procedures, project histories, QA records, support workflows.
  3. Rights. Material the company owns. Records that belong to the customer's own clients are usually not a fit.
  4. Location. 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.
  5. A path to the CEO. A sponsor who could carry a note to the chief executive if asked.

The fifth point matters because the QBR sponsor is usually the leader of the function that uses your product: a VP of operations, a head of support. That person can champion the idea internally, but the CEO authorizes a licensing discussion and signs for the company. The module asks the sponsor only whether the CEO hears about it, since a note that reaches SourceX without the chief executive's knowledge is, by its screening guidance, usually not a fit.

The optional QBR discussion module

Copy this card into your QBR template. Every field is fixed in advance so nobody improvises in the room.

ElementSpecification
SlotFinal item, after agreed actions and owners are confirmed
Time boxFour minutes; if the meeting overruns, the item becomes an email the sponsor asked for, or is dropped
Entry conditionThe sponsor ticked the optional line on the pre-read
PresenterThe customer success lead, never the person negotiating price
Evidence allowedWhat the customer has said about its own systems and history; public facts such as headcount
Evidence bannedUsage analytics, storage volumes, record counts or any content from your product
Leave-behindOne link: the public who-qualifies page
The only question"Would your CEO want a short note about it?"
Exit: yesA note to the CEO within two business days, copied to the sponsor
Exit: laterA revisit date the sponsor chooses, written in the minutes
Exit: noLogged with the date; not raised again for two quarters
RecordA consent field in your CRM: who agreed, to what, on which date

The pre-read line. It does the opting in, so it carries the disclosure:

Optional item, four minutes, last on the agenda: some companies license records created in their own operations to SourceX, a direct data licensing company, for AI training and evaluation. Tick if you would like a short overview. If your company later licenses data, we may receive a referral reward from SourceX. It does not change your pricing with us and is never deducted from what SourceX pays your company.

The three lines in the room.

  1. "You asked for the optional item, so four minutes on it. This is about records your company created across its whole operation, not anything inside our product."
  2. "SourceX looks for companies with 50 or more full-time employees at peak, several years of documented operations and the rights to license them. From what you have told us, you may be one. Whether any records qualify is decided only in SourceX's review."
  3. "Would your CEO want a short note? If not, we stop here."

Never say: what you can see in your platform about their volumes or activity; that your team could export anything for them; anything that links the item to renewal, discounts or support priority; any figure for what they might earn.

The derail test. Remove the module from this QBR if any of these is true:

  • An open severity-one incident or executive escalation on the account.
  • A renewal, price change or contract amendment under negotiation.
  • No tick on the pre-read.
  • Size, history or location unknown or failing.
  • The only records the sponsor wants to discuss belong to the customer's own clients.

How to word the CEO note so it introduces without recommending is covered in making an introduction without endorsing; the double opt-in pattern explains why the CEO's yes comes before any name reaches SourceX.

Choose accounts without mining the tenant for prospects

Your access to a customer's data exists to run your service. Under the GDPR, the contract between a controller and its processor must require the processor to handle personal data only on the controller's documented instructions (Article 28(3)(a)). A data processing agreement written to that standard was not drafted to let you mine the tenant for prospects for someone else's program. Separately, FTC staff warned AI model-as-a-service companies in January 2024 that privacy and confidentiality commitments to customers can create liability under the laws the FTC enforces, wherever those commitments appear, including terms of service, marketing materials and online marketplaces. Your company may not sell AI, but it is a useful test: if a customer read how you chose them for the opt-in line, would it match what you promised about their data?

QuestionYour company, the vendorThe customer
Who holds the records in your product?Hosts and processes them to run the serviceOwns them and decides any other use
Who decides whether to discuss licensing?Nobody on your teamThe customer's CEO
Who reviews rights to the records?Not your teamSourceX's rights review, with the customer's own counsel
What leaves your systems for SourceX?NothingOnly what the customer agrees in its own agreement
Who exports or delivers any data?Never your team on the customer's behalfThe customer, under its agreement with SourceX

Records the customer keeps in your product are the customer's, and they may well be part of what it chooses to discuss. That choice, and whether customer contracts limit reuse, sits with the customer and SourceX's review. The SaaS training-rights question covers the mirror case, where a software company looks at licensing its own records. If your team wants a motion with no product touchpoint at all, the introduction-only program guide lays out what you sign, build and never touch.

Run the module as a two-quarter pilot and watch sponsor comfort

Run the module as a two-quarter pilot before it enters every QBR template. SourceX has not published opt-in, conversion or acceptance rates for introductions made this way, and this page has none to report; your pilot produces the numbers that matter.

MeasureDefinitionWhy it matters
Opt-in ratePre-reads with the line ticked, divided by pre-reads sentShows whether customers want the item at all
Time-box adherenceModules finished within four minutes, divided by modules runShows whether the item stays small
Sponsor comfortAnswer to "Was the optional item appropriate?" (1 to 5) in the post-QBR surveyCatches trust damage early
CEO notes requestedYes exits, counted per quarterThe real output of the module
Verified applicationsIntroduced companies that submit a verified applicationThe point at which attribution is credited
ComplaintsEscalations or survey comments that mention the itemTriggers the stop rule

Stop rule. One complaint that the item felt like pressure, or a fall in sponsor comfort below your normal QBR survey baseline, pauses the pilot for a review of wording and account selection.

Illustrative example. A 340-person regional property management company uses your maintenance-ticketing product. Its VP of operations, the QBR sponsor, ticks the line. In the module she says the company has kept documented work orders, vendor approvals and inspection reports since 2011, across three systems, one of them yours. The customer success lead asks the one question and she says yes. The note goes to the CEO within two business days, copied to her, with links to the who-qualifies page and the program terms. The CEO decides to hear more and the company applies. Which records qualify, if any, and on what terms is settled in SourceX's review and the company's own agreement; your team never exports a record. If the Actual Supplier Payout for that company were $250,000, the default reward on its first qualifying transaction would be $62,500 (USD 50,000 plus 5%); at $400,000 it would be $70,000, with no cap, and a further qualifying transaction first agreed within 12 months would pay 15%. Illustrative figures only, not a forecast.

Illustrative counterexample. A 45-person design studio is your most enthusiastic customer. It fails the size test, so the line never goes on its pre-read.

Two program rules shape the pilot's paperwork. The company that submits signs the SourceX Channel Partner Agreement first (a copy signed under its former title, the Channel Partner Non-Circumvention and Non-Disclosure Agreement, still stands). And the program credits just one partner per company: the partner whose valid introduction landed first inside the 90-day attribution window, once the customer has submitted a verified application. If a reseller or implementation consultant also knows the customer, agree who submits before the note goes out. Any reward is payable only after the conditions in the terms are met, and it is paid no later than 60 calendar days after both steps are done: the Acquisition Partner's final written acceptance of the complete, validated dataset, plus the dataset's completed handoff. If the supplier payout is later reduced or reversed, the reward is reduced too.

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.

If an account passes the benefit test on evidence that never came from your product, register for a partner link, check it against who qualifies and read the program terms before the opt-in line goes on its next pre-read. More playbooks for partner teams are in the guides hub, including what customer success handover records look like as data.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Can the account executive run the module during a renewal QBR?

Skip it. When a renewal, price change or amendment is under negotiation, any side topic reads as a bargaining chip, so the module waits for the next quarter or a separate note the sponsor asks for. Keep the module with customer success, not with the person negotiating price.

May we pick which accounts get the opt-in line by looking at usage or storage data?

No. Select accounts on what the customer has told you and on public facts such as headcount. Your access to records in your product exists to run the service, and the customer decides any other use of what it owns.

Who should register as the partner, the CSM or the company?

The company. One partner is credited per referred company, the reward is paid by SourceX and never deducted from the customer's payout, and keeping it out of individual quotas keeps the module genuinely optional.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. eur-lex.europa.eu/legal-content/EN/TXT
  4. ftc.gov/policy/advocacy-research/tech-at-ftc/2024/01…

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment