This page is for community leads in venture networks who are thinking of running an ask-me-anything thread about introducing companies to SourceX, in a forum, a Slack workspace or a community platform. Booked one-to-one clinics are covered in the AI data office hour, sessions with a SourceX speaker in the guest session guide, and everyday threads in the moderator's private-routing rules. This page covers the time-boxed, public, written format.
What an AMA does well for referral questions, and what it does badly
Reddit's help article describes an AMA as a live question-and-answer event in which a guest opens the floor to questions on a topic. It suggests setting aside at least an hour, answering a variety of questions rather than only the easy ones, and it says an AMA has to be authentic: not run by someone else on the host's behalf, and not assembled from answers written for other interviews (our paraphrase).
For referral questions, those traits cut both ways.
| Trait of the format | Where it helps | Where it hurts |
|---|---|---|
| Public | One written answer about how the program works serves every reader | A founder who describes their company has described it to everyone |
| Persistent | The thread becomes a reference people can check against SourceX's pages | A wrong answer, or an answer that terms later changed, keeps being read |
| Ranked by votes | Shows what the community actually wants to know | Money questions rise to the top whether or not anyone can answer them |
| Fast | Many questions handled in an hour | Panelists improvise under time pressure |
So the format is strong on program mechanics, published rules and the host's own interest, and weak on anything about one company. The routing guide below exists to keep each question on the right side of that line.
Who sits on the panel, and who moderates
- The host's platform lead, posting under their own name. If the fund is a registered SourceX partner, the panel is an interested party, and the pinned post says so.
- A SourceX representative only by written agreement. Settle any appearance with SourceX in advance, in writing. Without SourceX on the panel, every answer about SourceX is secondhand, which is why route A always carries a link.
- A moderator who is not answering. The moderator tags each question with its route, removes what must go, and keeps the queue moving. Splitting the roles stops the person who could be paid from deciding which questions get answered.
Preparation means gathering the published pages each likely question rests on. The panelist still writes each answer in the thread, which keeps the authenticity Reddit's guidance asks for.
The pinned post, before the thread opens
Seven items, posted when the thread opens for early questions and left at the top throughout.
- Who is answering, by name and role.
- The interest. The fund is a registered SourceX referral partner. If a company it introduces licenses data to SourceX, SourceX may pay the fund a reward, paid by SourceX and not deducted from the payout the company agrees.
- The sources. SourceX's program terms (version 2026-10-22.2, since replaced by version 2026-11-04), its who qualifies page and its referral process page, each read on the date shown.
- What the panel will not answer in public: any named company's fit, any company's likely payout, legal advice, and questions about investing in SourceX.
- How to ask privately, and the promise that a private question goes to one named person and nowhere else.
- What gets removed: records, screenshots, customer names and other members' details.
- When the thread closes, and the date by which written answers to questions left open will be posted. That date is the host's own commitment, not SourceX's.
If early questions are allowed, add one line: details in a question can identify a company, so ask about your company privately.
The moderated question-routing guide
The moderator tags every question with one route before any panelist answers it.
| Route | Use it when the question | Who answers | What goes in the thread |
|---|---|---|---|
| A. Source link | Is settled by a published SourceX page | A panelist | The answer in plain words, the link and the date it was read |
| B. Host answers | Concerns the host's own interest, policy or conduct | The host | The host's policy in its own words, signed by name |
| C. Nobody publishes it | Asks for a figure or forecast no one has published | A panelist | "Nobody has published that," followed by what is published |
| D. Company's counsel | Turns on the company's own contracts, rights or law | The company's CEO and counsel | A pointer to who can answer, and no opinion |
| E. Private reply | Is about one identifiable company | One named panelist, once, privately | "Answered privately," with any general rule left public |
| F. Remove, then message | Contains records, screenshots, customer names or another member's details | The moderator | A removal note; the poster is told why |
| G. Out of scope | Asks about investing in SourceX, or asks the panel to decide for a company | The moderator | A pointer to the investor overview, or "only your CEO decides" |
Four rules for the moderator.
- Route first, answer second. No panelist replies to an untagged question.
- Votes order the queue, never the route. The most-voted question still gets route C if nobody publishes the answer.
- Split mixed questions. The general rule goes in public under route A; the company's own facts go to route E.
- One answer per question. A correction is an edit marked with its date, never a second answer that contradicts the first.
Methods note. The routes follow SourceX's published terms, screening page and referral process page, read on 27 October 2026, and Reddit's guidance on hosting an AMA. The queue below is invented, and the routes have not yet been tested on a live thread.
One AMA queue, routed (Illustrative)
Illustrative. Invented questions and votes from a generic venture community.
| Question | Votes | Route | What the thread says |
|---|---|---|---|
| "What do companies typically get paid?" | 41 | C | SourceX publishes no typical figures for companies. It does publish the reward arithmetic: on a USD 100,000 actual supplier payout the partner's reward is USD 55,000 |
| "Is the partner's reward taken out of what our company is paid?" | 27 | A | No. SourceX pays it separately, and section 4 of the terms says it is never deducted from the company's agreed compensation |
| "We are a 70-person staffing firm. Do we fit?" | 19 | E | In public: a staffing firm counts its own full-time employees, not workers it has placed with clients. In private: the firm's own figures |
| "Can we license records that mention our customers?" | 12 | D | That turns on the company's contracts, SourceX's rights review and the company's counsel; SourceX's screening page says material that belongs to clients is usually not a fit |
| "Does the fund get paid if we sign?" | 9 | B | The host's disclosure, in the host's words, with the reward basis linked |
| "Should we invest in SourceX?" | 4 | G | Outside this thread; the investor overview is linked |
The question with the most votes is the one the panel can answer least. Routing it to C in the first minutes, with the arithmetic SourceX does publish, stops the rest of the hour from circling it.
During the hour, and after the thread closes
During. Answer route C and G questions early with short, standard replies, then work the answerable queue by votes. Repost the disclosure halfway through for people who arrive late. Panelists never open a private conversation; a private reply happens only when the asker requests one.
After. Add a dated header: the terms version and the date the pages were read. Post the written answers promised in the pinned post by the date it named. When SourceX publishes a new terms version, recheck every route A answer and append a visible correction wherever one changed. Private replies stay private, and nothing from the thread goes to SourceX. SourceX's referral process leaves the company in control of whether to proceed, what scope to offer and which terms to accept, and says a partner never needs to export, upload or describe confidential records, so the thread never asks anyone for either a commitment or a file.
An introduction follows only a CEO's written request after the thread, submitted by a person who has signed the Channel Partner Agreement. Only one partner can be credited for a company, so the host decides in advance who submits. A reply that answers a question the CEO actually asked, as in the answer-led follow-up, is the only follow-up worth sending.
Measuring the AMA by what people understood and asked for
| Measure | How to count it | Read it as |
|---|---|---|
| Route mix | Questions per route ÷ all questions | A high route C share means people want figures nobody publishes; say so in the next pinned post |
| Sourced answers | Route A answers with a link ÷ route A answers | Should be every one |
| Split questions | Questions answered partly in public, partly in private | Company questions were handled without exposing the company |
| Corrections | Edits marked corrected after posting | Some are healthy; none across several threads may mean nobody rechecks |
| Removals | Posts removed under route F | Each one points to pinned-post wording that needs to be plainer |
| Private replies kept | Private replies sent once ÷ private replies requested | The host kept its word |
| CEO introduction requests | Written requests from CEOs after the thread | Counted, never targeted |
No benchmarks for community AMAs on this topic have been published, so compare one thread with the next. The event quality funnel shows how these counts sit alongside other formats, and the event brief carries the boundary lines a pinned post can reuse.
Where an AMA goes wrong
- Exposure is permanent. A founder who names their company in a question has published it. Routing to E afterward cannot recall a screenshot, which is why the pinned post warns first.
- Votes favor money. A thread dominated by route C answers frustrates people. If early questions are mostly about payouts, publish a short written answer before the live hour.
- Confident errors persist. An improvised wrong answer keeps being read; dated corrections are the only remedy.
- Secondhand answers. Without SourceX on the panel, answers about SourceX are only as good as the page they cite.
- Small communities. Everyone may know who asked. Lean harder on private replies.
- Stale answers. Terms change after a thread closes. The dated header and rechecks matter more than the hour itself.
- The host's interest remains. Disclosure names it; it does not remove it. Questions a CFO would ask before any licensing decision are collected in questions to ask before licensing company data, and more event guides are in the guides library.
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 you open the thread, register as a partner so the pinned disclosure is accurate, link who qualifies for every route A answer about fit and read the program terms the dated header will name.
Running a referral AMA is one decision; looking at SourceX as an investment is another, and route G's pointer for that is the SourceX investor overview, where investor materials can be requested.
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.