A community calendar built around questions, not repeated launches: a question-led plan that gives a month's slot only to a question several members asked, announces the program once and keeps every founder's company facts out of the planning sheet

Short answer

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.

Visual briefFull-size diagram
A treemap of an Illustrative half-year's question log with tiles sized by how many members asked: who says yes 7 (month 1), no VC money 6 (month 6), customer records 5 (month 2), how the introducer is paid 4 (month 3) and after an acquisition 3 (month 5); three small gray tiles of one or two askers read written answer, private lane and hold, and a bar along the top reads month 0, program announced once.
Illustrative log for a 300-member community. Blue tiles follow the asker counts in this page's calendar table; the gray tiles are invented clusters that did not pass. No real members or companies.

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.

FieldWhat it holdsWhat it never holds
Date and channelWhen and where the question arrivedThe asker's name, in any copy others can open
Question, generalizedThe 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
ClusterA short label shared by questions one answer would settleA guess about whether the asker's company would fit
Distinct askersA count of members, not of messagesA list of who they are
AnswererThe person who will settle it and the published page they will rely on"SourceX will cover it," unless SourceX has agreed in writing
StatusWaiting, scheduled, answered in writing, routed privately or on holdNotes 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.

MonthCluster, in members' wordsDistinct askersFormatAnswerer and sourceKept out of the session
0The program itselfNot countedOne written note: what SourceX licenses, a link to the screening page and the host's own interestCommunity lead; terms and who-qualifiesAny hint that members' companies would qualify
1"Who at a company has to say yes?"730-minute call, questions taken in writingCommunity lead; the CEO decides under SourceX's programAny member's own board politics
2"Do records our customers send us count as ours?"5Guest session, only if SourceX agrees in writingSourceX speaker; the screening page on client-owned materialA reading of any member's contracts
3"How is the introducer paid, and does the company get less?"4Written answer in the newsletter, no eventCommunity lead; terms section 4Payout estimates for anyone
4No cluster reached three askersNoneNo sessionNobodyNothing to keep out
5"Who decides once we have been acquired?"3One office hour slotCommunity lead; before closing the target's CEO decides, after it the acquirer'sAny live deal
6"Can a company that never raised venture money take part?"6Written answer and one short callCommunity lead; none of the screening checks mentions fundingLists 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.

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 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 sets out. Questions nobody in the community can answer belong in a backlog routed to the right answerer.

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.

MeasureCountOut ofWhat it shows
CoverageClusters answered, live or in writing, within 60 days of passing the testsClusters that passed the testsWhether the calendar keeps pace with members
Oldest waitDays the longest-waiting passed cluster has sat unansweredNot a rateWhether a hard question is being avoided
UnderstoodAskers who replied "answered" to one optional question sent with the answerAskers in that cluster who received itWhether the answer landed
Follow-up asked forMembers who asked, unprompted, for a next stepDistinct askers that quarterInterest the member started; counted, never targeted
CorrectionsWritten answers corrected after a terms changeWritten answers publishedWhether 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, and the program overview for platform teams is on the venture platform page.

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 and sign the Channel Partner Agreement before anyone in the community submits an introduction, send askers to who qualifies rather than answering fit yourself, and cite the program 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.

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.

  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

May a community's public calendar list a session as being with SourceX?

Only once SourceX has agreed in writing. The sample Channel Partner Agreement bars either side from publicly naming the other as a partner without written authorization, so until that consent arrives the slot carries the question's title and nothing else.

What happens in a month when no question reaches the threshold?

Nothing is scheduled. Questions below the threshold get a short written answer in the next newsletter or wait for more askers, and the empty month is logged as a result rather than filled with another program pitch.

Can a member bring a question about their own company?

Yes, and it is welcome. The planning sheet keeps only the general form of it, the public session answers the general rule, and anything that needs that company's own facts goes to the conversation its CEO may choose to open with SourceX.

Sources

  1. refer.sourcex.si/terms
  2. refer.sourcex.si/who-qualifies
  3. sourcex.si/documents/partner/SourceX_Channel_Partner_Ag…
  4. nngroup.com/articles/affinity-diagram
  5. sourcex.si/investors

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