# Venture community data calendar built on questions | SourceX

Canonical: https://refer.sourcex.si/guides/a-community-calendar-built-around-questions-not-repeated-launches
Last updated: 2026-11-04

Build the calendar from the questions your members ask, not from the referral program. Log every question about AI data licensing and introductions with the asker's company details removed, group the questions into clusters, and give a session only to a cluster that three or more members raised and that a named person can answer from a published page. Announce the program once. Every seat stays optional, and a question that needs one company's facts goes to that company's own conversation with SourceX.

A calendar built this way will sometimes leave a month empty, and that is a finding, not a failure. It also produces something a monthly "meet the program" session never does: a dated record of what your members want to know, how many of them asked and which questions are still waiting.

## Why a calendar of repeated launches stops working

Relaunching the same program in a new format each month, a webinar in March, a lunch in April, a feature in May, carries three costs.

- **It answers the host's question.** "How do we get introductions?" is the host's concern. Members came with their own questions, and a relaunch leaves them unanswered.
- **It reads as selling.** A community that hears the same pitch every month learns to treat the calendar as a sales channel. When the host is a registered partner who could be paid, that reading is correct, and trust in every other session suffers.
- **It teaches you nothing.** Attendance at a relaunch shows who had a free hour, not what anyone needed to know.

The program gives no reason to repeat yourself either. Credit goes to the first valid introduction of a company within the 90-day attribution window, and only when that company files a verified application (terms, section 2). Frequency of sessions does not enter into it. A calendar cannot produce a CEO who wants the conversation; at most it can answer the questions that come before one.

## The questions the calendar is built from

Questions arrive through channels the community already runs: office hour bookings, replies to the newsletter, threads in the members' forum or chat, event feedback forms and messages sent straight to the community lead. One log collects them all, and it is built so that no founder's company data ever lands in it.

| Field | What it holds | What it never holds |
|---|---|---|
| Date and channel | When and where the question arrived | The asker's name, in any copy others can open |
| Question, generalized | The member's wording with the company taken out, for example "Can records from a system we no longer pay for still be licensed?" | Company names, headcounts, system names, customers or figures |
| Cluster | A short label shared by questions one answer would settle | A guess about whether the asker's company would fit |
| Distinct askers | A count of members, not of messages | A list of who they are |
| Answerer | The person who will settle it and the published page they will rely on | "SourceX will cover it," unless SourceX has agreed in writing |
| Status | Waiting, scheduled, answered in writing, routed privately or on hold | Notes about follow-up the member never asked for |

Cluster the log once a month in one sitting. Nielsen Norman Group describes affinity diagramming in three steps, generating items, clustering them and then prioritizing the clusters, and warns against forcing items into groups: small clusters can still matter, and a cluster's label should fit every note under it (our paraphrase). For a community log that means a question which fits nowhere stays on its own instead of being bent into its nearest neighbor, and a label like "rights" is too loose if half its questions are really about who signs.

## The question-led editorial calendar

Every cluster faces the same three tests before it gets a slot.

1. **Demand.** Three or more distinct members raised it since the last planning date.
2. **An answerer.** A named person can settle it from a published source, such as SourceX's terms, its screening page or its how-it-works page, or SourceX has agreed in writing to send a speaker.
3. **A general answer.** What is said holds for any member. A question only one company's facts could settle fails here.

A cluster that fails the first test gets a short written answer in the next newsletter or waits for more askers. One that fails the second is put on hold, and the log says so openly. One that fails the third goes to the private lane described below.

**One half-year for a 300-member venture community (Illustrative).** Generic community, invented counts.

| Month | Cluster, in members' words | Distinct askers | Format | Answerer and source | Kept out of the session |
|---|---|---|---|---|---|
| 0 | The program itself | Not counted | One written note: what SourceX licenses, a link to the screening page and the host's own interest | Community lead; terms and who-qualifies | Any hint that members' companies would qualify |
| 1 | "Who at a company has to say yes?" | 7 | 30-minute call, questions taken in writing | Community lead; the CEO decides under SourceX's program | Any member's own board politics |
| 2 | "Do records our customers send us count as ours?" | 5 | Guest session, only if SourceX agrees in writing | SourceX speaker; the screening page on client-owned material | A reading of any member's contracts |
| 3 | "How is the introducer paid, and does the company get less?" | 4 | Written answer in the newsletter, no event | Community lead; terms section 4 | Payout estimates for anyone |
| 4 | No cluster reached three askers | None | No session | Nobody | Nothing to keep out |
| 5 | "Who decides once we have been acquired?" | 3 | One office hour slot | Community lead; before closing the target's CEO decides, after it the acquirer's | Any live deal |
| 6 | "Can a company that never raised venture money take part?" | 6 | Written answer and one short call | Community lead; none of the screening checks mentions funding | Lists of members' portfolio or LP companies |

Month 3's answer is short. The reward is paid separately by SourceX and is never deducted from the company's agreed compensation, so a company receives the same amount whether or not a partner introduced it. Month 4 is the calendar working as designed: no filler session, no relaunch.

When SourceX publishes a new version of its terms, every written answer that version touches gets a dated correction. A change in the program is a reason to correct, not to launch again. Whether a session that has already run deserves a second outing is a separate call, made with [the repeat-demand rubric](/guides/when-to-repeat-a-session-and-when-to-change-the-topic).

**Method note.** The three tests and the threshold of three askers are this page's design, built from SourceX's published terms and screening page (both read on 2026-10-27) and NN/g's description of affinity clustering. The threshold suits a community of a few hundred active members. It has not been tested against outcomes, and no data on question-led calendars has been published.

## Optional seats, disclosure and the private lane

- **Nothing is gated.** Reading a written answer never requires registering for an event or clicking a referral link; [offering a link without forcing event registration](/guides/how-to-offer-a-referral-link-without-forcing-event-registration) shows how to keep the two apart.
- **Say who could be paid.** If the host or community lead is a registered SourceX partner, the launch note says so, and so does the opening of any session where SourceX comes up. Say what it means in practice: SourceX may pay the introducer, and the company's payout does not change.
- **Ask before naming SourceX.** Section 4.5 of the sample Channel Partner Agreement says neither side may publicly identify the other as a partner without written authorization. Until SourceX agrees in writing, a public calendar lists the question, not the company.
- **No implied promises.** Nothing on the calendar may suggest that members qualify, that SourceX endorses the community, that anyone gets preferential access to a company's data or that the community can decide for a company. Each company's CEO decides, and nobody collects records, headcounts or system lists for SourceX.
- **The private lane.** When a question needs one company's own facts, the room hears the general rule and stops there. The member's CEO can open a conversation with SourceX directly, as [handling questions that need private company context](/guides/what-to-do-with-questions-that-require-private-company-context) sets out. Questions nobody in the community can answer belong in [a backlog routed to the right answerer](/guides/a-backlog-for-founder-questions-your-platform-team-cannot-answer).

## Measuring whether the calendar answers what was asked

Count the calendar's own job, which is answering, once a quarter. Measuring a single session's turnout is a different exercise, covered in [measuring event quality beyond registrations](/guides/how-to-measure-event-quality-beyond-registrations).

| Measure | Count | Out of | What it shows |
|---|---|---|---|
| Coverage | Clusters answered, live or in writing, within 60 days of passing the tests | Clusters that passed the tests | Whether the calendar keeps pace with members |
| Oldest wait | Days the longest-waiting passed cluster has sat unanswered | Not a rate | Whether a hard question is being avoided |
| Understood | Askers who replied "answered" to one optional question sent with the answer | Askers in that cluster who received it | Whether the answer landed |
| Follow-up asked for | Members who asked, unprompted, for a next step | Distinct askers that quarter | Interest the member started; counted, never targeted |
| Corrections | Written answers corrected after a terms change | Written answers published | Whether old answers stay current |

Introductions are deliberately absent from this table. They come from CEOs, on their own timing, and a calendar scored on them drifts back toward launches.

## Where a question-led calendar can mislead

- **Frequent askers look like demand.** Two members who post weekly can outweigh twenty who never post. Count distinct people, never messages.
- **Silence is not disinterest.** Operators of older, larger companies may never use the chat, so the log can under-represent exactly the companies most likely to pass SourceX's screen. Ask in the channels they do use.
- **Small communities stall.** Below about 100 active members few clusters reach three askers; a quarterly written digest serves better than a calendar.
- **Answers age.** A written answer correct under one terms version can mislead under the next. The corrections count exists for that reason.
- **The thesis is unmeasured.** Our hypothesis is that question-led calendars keep members' trust longer than repeated launches. No study has measured it; the coverage and understanding counts above are how a community can test it on itself.
- **Demand is decided elsewhere.** Whether SourceX needs any member company's records is settled in its review, and a well-run calendar changes none of that.

More planning guides sit in the [guides library](/guides), and the program overview for platform teams is on [the venture platform page](/for/venture-platform-teams).

## 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 one cluster keeps returning to your log, [register as a partner](/register) and sign the Channel Partner Agreement before anyone in the community submits an introduction, send askers to [who qualifies](/who-qualifies) rather than answering fit yourself, and cite the [program terms](/terms) by version in every written answer.

Running a members' calendar is referral work; a reader who wants to study SourceX as a company to invest in can ask for materials through [SourceX's investor page](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/documents/partner/SourceX_Channel_Partner_Agreement_Sample.pdf
- https://www.nngroup.com/articles/affinity-diagram/
- https://sourcex.si/investors
