# Event questions needing private company context | SourceX

Canonical: https://refer.sourcex.si/guides/what-to-do-with-questions-that-require-private-company-context
Last updated: 2026-11-05

Split the question. Answer, out loud, the part that holds for every company, from SourceX's published pages, and stop where the answer would depend on one company's records, contracts, customers or numbers. Hand that part back to the founder with a single route: the company's own conversation with SourceX, which its CEO can start by applying, with no files. The host never answers the private part for the room, never writes it down and never carries it to SourceX on the company's behalf.

This is a workflow for the moment a private question surfaces in a live room: a portfolio session, a dinner talk, a webinar's question time. Running a whole session without records is the subject of [the closed-door session protocol](/guides/how-to-run-a-closed-door-session-without-sharing-company-records), and the same call in an online thread is made in [when a community moderator should route a question privately](/guides/when-a-community-moderator-should-route-a-question-privately).

## Six signs a question has crossed into one company's private facts

Questions rarely announce that they are private. They give themselves away by their grammar.

| Sign | An example heard in a session (Illustrative) | Why the room cannot answer it |
|---|---|---|
| Possession: "our records", "our system" | "Would our 11 years of dispatch logs fit?" | Fit is settled in SourceX's review of that company against current programs |
| A number | "We have about two million tickets. What is that worth?" | SourceX publishes no price, its offers stay indicative until a Dataset Deal Confirmation is signed, and everyone in the room hears the number |
| A customer or a contract clause | "Our biggest customer's contract has a confidentiality clause. Can we still license?" | Rights turn on the actual contracts, read by the company's counsel and SourceX's rights check |
| Earlier dealings with SourceX | "We spoke to SourceX last year. Does that matter?" | Only SourceX can see its own records |
| A transaction in progress | "We're being acquired in March. Should we wait?" | Who decides changes at closing, and the deal itself is confidential |
| Another company | "Does our competitor license its data?" | Nobody in the room can speak for another company, and SourceX says neither side publicizes a deal |

The fourth sign matters for more than tact. Under section 3 of SourceX's terms, a company SourceX already dealt with, whether through an application, an account, a lead or simply an exchange of emails, is a duplicate, and no later partner is credited for it. Whether last year's conversation counts is SourceX's to check, and saying anything about it in public only spreads a guess.

## Why a confidentiality rule does not make the room the right place

Hosts often reach for the Chatham House Rule. As Chatham House describes it, participants may use the information they receive but may not reveal who said it or whom they represent, and organizers should make clear from the outset whether the Rule applies, with the agreement recorded in writing (our paraphrase). The Rule protects attribution. It does not protect content. A founder's record count, a customer's name or a contract problem said aloud can still be used by everyone present.

Investor-hosted rooms make this sharper. They can hold competitors, other investors and people who sell to the companies in the room. The host may also know a company's situation from board materials, and that knowledge never belongs in a public answer, however general it sounds.

## The public-to-private escalation workflow

Six steps, the first two taken in seconds.

| Step | The host says or does | Never |
|---|---|---|
| E1 Hear the sign | Notice one of the six signs as the question starts | Wait for the founder to finish the details |
| E2 Pause the details | "Let me stop you before the specifics, so I can answer the part that applies to everyone." | Let the founder read out figures, customers or clauses |
| E3 Answer the general rule | Answer from a published page and name it: the screening profile, the terms or the process page | Judge this company's case in front of the room |
| E4 Name what is left and who owns it | "Whether your records fit is for SourceX's review, whether your contracts allow it is for your counsel and SourceX's rights check, and whether to start at all is your CEO's decision." | Suggest it will probably work out |
| E5 Give the route | The company's own conversation with SourceX: the CEO can apply, or can ask the host in writing for an introduction | Offer to take the details and pass them on |
| E6 Keep only the general question | Add it to the session's public answers, worded so no company can be recognized | Note the founder, the company or the facts |

**What E3 sounds like.** For the dispatch logs: SourceX screens on a full-time workforce that peaked at 50 or more people, years of records the company created in its own work, the rights to license them and a CEO who authorizes the discussion, and it checks fit with its current programs during review. SourceX's screening page also lists material belonging to the company's clients as usually not a fit, which tells the founder what to look at before applying. A page such as [whether one system's records can be enough](/questions/one-system-company-data-enough-for-licensing) answers the general version of many such questions.

**What E5 offers.** SourceX's application opens with a fit check of three screens, about seven minutes, asks for no files, passwords or API tokens, and says that applying licenses or transfers nothing and does not mean an offer or payment. After that, SourceX's process page says it checks fit, completes the inventory with the company and runs the rights check. That is the company's own conversation, and every private part of the question belongs in it. If the CEO would rather be introduced, the host, having signed the SourceX Channel Partner Agreement first, sends one written introduction naming the company and its CEO, with nothing about its records. Credit, if any, goes to the first valid introduction within 90 days, once the company submits a verified application, and only one partner can be credited.

**When the founder follows the host out of the room.** The workflow does not change in a corridor. Give the route again, explain how the application works if asked, and decline the details. Which questions belong to the partner, the company and SourceX is mapped further in [which eligibility questions belong with SourceX](/guides/which-eligibility-questions-belong-with-sourcex).

## Optional participation and the line the host keeps

Set the boundary before the first question, so pausing a founder never comes as a surprise.

- **Say it at the start.** Tell the room that company-specific questions will get a general answer and a route, and why: whatever rule the session runs under, what is said can be used by anyone present.
- **Make speaking optional.** Accept written or anonymous questions, and never make asking one the price of a seat.
- **Disclose the host's interest.** The fund or platform may be a registered SourceX partner that could be paid a reward if a company it introduces licenses data; SourceX pays any reward, does not deduct it from the payout the company agrees, and attaches conditions.
- **Imply nothing.** Taking part does not mean a company qualifies, that SourceX endorses the host or that anyone gets preferential access to a company's data. The host cannot decide for a company; its CEO does.
- **Collect nothing for SourceX.** No attendee list, question log or company fact leaves the host. Nobody collects company data for SourceX.
- **Brief any SourceX speaker.** If someone from SourceX speaks, agree beforehand that the same split applies to their answers. A room is still a room.

For questions the host simply cannot verify, the response bank in [when a contact wants details you cannot verify](/guides/when-a-contact-wants-details-you-cannot-verify) has wording that admits it.

## One session, eight questions (Illustrative)

Illustrative. An invented 40-minute investor-hosted session; no company or outcome is real.

| # | The question, as generalized afterwards | Handled | Route given |
|---|---|---|---|
| 1 | Who in a company decides whether to license? | Answered in the room | The terms and screening page |
| 2 | What kinds of records usually fit? | Answered in the room | The screening page |
| 3 | Would a company's long run of dispatch records fit? | Split | General rule aloud; the company's own application |
| 4 | What is a large ticket archive worth? | Split | No price is published; SourceX's review |
| 5 | Can a company license despite a customer confidentiality clause? | Split, after a near-miss | The company's counsel and SourceX's rights check |
| 6 | How would the host be paid? | Answered in the room | The reward basis and its conditions, disclosed |
| 7 | Does an earlier conversation with SourceX matter? | Split | Only SourceX can check its own records |
| 8 | Does a named competitor license its data? | Declined | Nobody speaks for another company |

In question 5 the founder named the customer before the host could pause. The host did not repeat the name, answered the general rule and left the name out of the written answers. Two CEOs later asked the host in writing for an introduction. Those two requests are the only follow-up the session produced, and they are counted as requests, not as results.

## Counting splits, near-misses and requests

| Measure | How to count it | Read it as |
|---|---|---|
| Split rate | Questions split, divided by questions asked | Shows how often sessions draw company-specific questions |
| Near-misses | Sessions where private details were spoken before the pause, divided by sessions held | Any at all means the opening announcement needs work |
| Understood | Founders who said the general answer told them their next step, divided by those asked | The main benefit measure |
| Introductions requested | CEOs who asked in writing, divided by attendees | Counted, never targeted |
| Felt cut off | Founders who said the pause felt dismissive, divided by splits | The cost of the workflow |

No host or SourceX has published figures like these. Collect them for three sessions before drawing conclusions.

## What could go wrong when a host splits questions

- **It can feel dismissive.** A founder stopped mid-sentence may disengage. Announcing the practice at the start, and explaining it, reduces that.
- **A general answer can mislead.** A founder may rule the company in or out from the general rule alone. Each SourceX program applies its own criteria, so the honest close is always that SourceX decides in review.
- **Signs get missed.** Some details spill before anyone can pause them, and the Chatham House description makes clear that a confidentiality rule will not stop them being used.
- **The route depends on the CEO.** Some companies that might fit will never apply. That is the cost of leaving the decision where it belongs.
- **Board knowledge leaks.** A host who knows a company's facts may shade a "general" answer toward them. Answer only from published pages.

**Methods note.** The six signs and six steps are a design drawn from SourceX's program terms (Version 2026-10-22.2, since replaced by version 2026-11-04), its screening, application and process pages and Chatham House's description of its Rule, all read on 27 October 2026. They have not been tested with founders, and the example session is invented. More event formats are in the [guides library](/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.

Before your next session, [register as a partner](/register) if the host may ever introduce a company, keep [who qualifies](/who-qualifies) open for every E3 answer, and read the [program terms](/terms) so each disclosure matches what SourceX publishes.

Hosting founder questions is network work; evaluating SourceX as a company to invest in is a separate decision, and materials for that are available on request through the [SourceX investor overview](https://sourcex.si/investors).

This article is for information only and is not an offer to sell or a solicitation of an offer to buy securities. Any offering by SourceX is made only to verified accredited investors through its offering documents.

## Sources

- https://refer.sourcex.si/terms
- https://refer.sourcex.si/who-qualifies
- https://sourcex.si/apply
- https://sourcex.si/how-it-works
- https://www.chathamhouse.org/about-us/chatham-house-rule
- https://sourcex.si/investors
