# Portfolio webinar iteration: rerun or new topic | SourceX

Canonical: https://refer.sourcex.si/guides/when-to-repeat-a-session-and-when-to-change-the-topic
Last updated: 2026-11-04

Repeat a session when people who missed it are asking for the same content and the answers held up. Rewrite it when a question kept coming back after the session had answered it. Change the topic when the questions arriving have moved to a subject the session never covered, and pause when nobody asked for anything. Make the call from the session's question log and written requests alone: founders' company facts, registrants' headcounts and any guess about who might qualify stay out of it.

This page is for the community or platform lead at a fund who has run a session for founders on company data licensing and now has to choose the next one. The calendar decision goes wrong in both directions: a full room gets rerun though its answers failed, or a small room gets dropped though the people who missed it keep asking. Neither registrations nor the prospect of an introduction says which question the community still has.

## Five calls after a session, and what each one commits you to

| Call | When it fits | What you produce next |
|---|---|---|
| Repeat as is | People who missed it ask for the same content, and the answers held up | The same session on a new date, announced to the whole community |
| Repeat with a rewritten answer | A theme kept coming back after the session answered it | The same topic with the failing segment rebuilt, plus a written correction to the last audience |
| Change the topic | Questions moved to a subject the session never covered | A new session on that subject; the old content becomes a written page |
| Answer in writing | A few questions went unanswered and nobody asked for another session | A written note to everyone who attended, posted where the community reads |
| Pause | Nobody asked for anything | Nothing; the topic waits until someone asks |

Every call except Pause has a visible output, and Pause is a legitimate result. A community that hears from its host only when there is something to answer reads the next invitation more carefully. For one partner's consent-first habits across many introductions, the [repeat referrals case study](/resources/repeat-referral-partner) is the closest live example.

## The audience question decides whether a session is the right format

Write the session's question down before the invitation, in the community's words, for example "How does a company license its records, and who decides?" Then pick the lightest format that answers it.

- **A live session** suits a question many people share and that invites follow-ups.
- **A written answer** suits a single question with a published answer; a rerun adds nothing to it.
- **A private route** suits any question that needs one company's facts. Answer the general rule in the room and send the rest to the company's own conversation with SourceX, as the guide on [questions that need private company context](/guides/what-to-do-with-questions-that-require-private-company-context) sets out.
- **A pre-session survey** can collect the question itself; the [founder survey design](/guides/a-founder-survey-before-a-data-partnership-webinar) asks only what founders want covered.

Whatever the format, a session about SourceX carries the same few facts each time: the company's CEO decides whether it discusses licensing, and once a company is acquired the acquirer's CEO decides for it; funding does not make a company eligible; the host may be paid a referral reward; and nobody collects company data for SourceX.

## The repeat-demand topic selection rubric

Five signals, each scored 0, 1 or 2, all read from what attendees and would-be attendees asked or wrote. Keep the session's Q&A record and one folder of written requests; nothing else feeds the score.

| Signal | What you count | Scores 0 | Scores 1 | Scores 2 |
|---|---|---|---|---|
| S1 Carry-over | Questions still unanswered when time ran out | None | 1 to 3 | 4 or more |
| S2 Return question | A theme asked again, by someone else, after the session answered it | None | One theme | Two or more themes |
| S3 Absent demand | Written requests for the session from people who did not attend | None | 1 or 2 | 3 or more |
| S4 Drift | Share of questions on a subject outside the session's stated scope | Under 20% | 20% to 39% | 40% or more |
| S5 Rerun request | Attendees asking in writing for a rerun, or for a colleague to hear it | None | 1 or 2 | 3 or more |

Read the calls in this order and stop at the first match:

1. S4 scores 2: **change the topic.**
2. S2 scores 1 or more: **repeat with a rewritten answer.**
3. S3 and S5 together reach 3: **repeat as is.**
4. S1 scores 1 or more: **answer in writing.**
5. Anything else: **pause.**

Drift comes first because a better version of the old session still misses a community whose questions have moved. Return questions come before demand because rerunning an answer that failed spreads the failure to a new audience.

**Left out on purpose.** Registrations and attendance count the invitation, not the need. Introductions requested are recorded for the community's own reporting but never steer the topic, since a calendar chosen to produce introductions becomes a funnel. Attendees' companies, their size, systems or likely fit, never enter the score, and neither does any estimate of rewards. How to read a single event beyond its registrations is covered in [the event quality guide](/guides/how-to-measure-event-quality-beyond-registrations); this rubric only compares runs.

**Where the inputs sit.** On Zoom, for example, webinar reports include a Q&A report that shows each question with who asked and who answered it; attendee, Q&A, poll and survey data appear only after the webinar ends; and when a poll is relaunched, the poll report keeps only its last run, so a rerun that needs a comparable poll should use a new one (Zoom support, paraphrased). A post-webinar survey can carry one open question, "What should the next session answer?", and its responses download as a report (Zoom support, paraphrased).

**Methods note.** Measured: counts of questions, themes and written requests from the host's own Q&A record, survey and request folder, coded by one person within a week and checked by a second. The thresholds were set on 27 October 2026 as starting points; they are not tested values, and no benchmark for them has been published. Not measured: what attendees understood beyond the return-question signal, anyone who never attends, and anything about companies.

## What the question log may hold, and who is invited back

- **Themes, not companies.** Code each question by theme and strip company detail while you code: "could our warehouse scan history count?" becomes one tally under records that fit, with no name and no system.
- **Askers, then no names.** Count distinct askers from the named report, then work from a copy with names removed. Questions sent without a name count as one asker each and stay unnamed.
- **Nothing imported.** Board packs, CRM notes and what the fund knows about a founder's company never join the log. The rubric reads the session, not the portfolio.
- **Open invitations.** A rerun is announced to the whole community, and the people who asked for it are told personally. Nobody is registered automatically, and declining needs no reply.
- **The host's interest, stated.** Every invitation says the fund or its platform team may be paid a referral reward by SourceX if a company it introduces licenses data.
- **Nothing to SourceX.** No list, names or themes tied to people leave the host. A company with a real next step takes it itself: its CEO applies to SourceX or asks for an introduction.

## Three runs of one session, scored (Illustrative)

Illustrative. Invented counts for a generic fund community. The session was "How company data licensing works: what fits, who decides, who pays whom", and its stated scope was those three subjects, with customer contracts counted under fit.

| Theme | Run 1 | Run 2 | Run 3 |
|---|---|---|---|
| Who decides | 9 | 3 | 1 |
| Records that fit | 7 | 6 | 3 |
| Who pays whom | 5 | 7 | 6 |
| Customer contracts | 3 | 1 | 2 |
| Sale or acquisition (outside scope) | 1 | 5 | 9 |
| All questions | 25 | 22 | 21 |

| Signal | Run 1 | Run 2 | Run 3 |
|---|---|---|---|
| S1 Carry-over | 2 (5 unanswered) | 1 (2 unanswered) | 1 (3 unanswered) |
| S2 Return question | 0 | 1 (who pays whom) | 1 (who pays whom) |
| S3 Absent demand | 1 (2 requests) | 1 (1 request) | 0 |
| S4 Drift | 0 (1 of 25, 4%) | 1 (5 of 22, 23%) | 2 (9 of 21, 43%) |
| S5 Rerun request | 2 (4 requests) | 1 (2 requests) | 0 |
| Call | Repeat as is | Repeat with a rewritten answer | Change the topic |

**After run 1.** Absent demand and rerun requests together reached 3 with no drift and no return question, so the host ran it again for people who missed it.

**After run 2.** Who pays whom drew seven questions, five of them after the segment that answered it. The host rebuilt that segment around one diagram: SourceX pays the company under the company's own agreement, and any referral reward goes to the partner separately. Section 4 of the terms says the reward is "paid separately by SourceX and is never deducted from the supplier's agreed compensation", and SourceX pays it from its own share, so a company receives the same amount with or without a partner. A short written correction went to run 2's attendees.

**After run 3.** Nine of 21 questions were about a pending sale or acquisition, which the session never covered. The host changed the topic: a new session on licensing questions during a sale, built on the published rule that once a company is acquired the acquirer's CEO decides for it, while before closing the company's own CEO still decides. The basics session became a written page. Who pays whom still drew six questions, two after the rebuilt answer, so the new session's pre-read repeats the diagram.

## Measuring what the next run has to fix

- **Return-question rate per theme.** Questions on a theme asked after the session answered it, divided by all questions on that theme. In the example, who pays whom went from 5 of 7 in run 2 to 2 of 6 in run 3. A falling rate means the rewrite is working.
- **Requests by kind, each over attendees.** Rerun requests, written-answer requests, private-conversation requests and introduction requests, the last recorded and never targeted.
- **Corrections asked for.** Each time an attendee points out a wrong or outdated statement, log it and answer in writing. The target is zero, and a nonzero count beats a hidden one.
- **What is not a measure.** Seats filled, registrations and introductions say nothing about whether the community's question was answered. For more topic ideas drawn from client questions, see [CPA firm client webinar topics](/resources/cpa-firm-client-webinar-topics) and the [guides library](/guides).

## Ways the rubric can mislead you

- **Small numbers.** With about 20 questions a run, one question moves a share by five points. Read the counts beside every percentage.
- **Loud askers.** One person asking six questions can make a theme. Count distinct askers per theme as well as questions.
- **Unnamed questions.** Questions sent without a name cannot be deduplicated, so a theme may be one persistent person.
- **The uninterested are invisible.** People with no interest never ask, so the rubric can show that a topic went unasked, never that it is unwanted.
- **The facts move.** Section 11 of the terms lists five versions published in October 2026 alone, from 2026-10-12 to 2026-10-22.2. A rerun with unchanged slides can repeat a superseded rule, so check the current version before every run.
- **The host's interest.** A fund that can be paid for introductions has a reason to favor topics that produce them. That is why introductions are excluded from the score and why a second person checks the coding.
- **Demand outside the room.** Whether company records stay in demand for AI training is beyond any community's control. No session should suggest that a given company's records will be bought.

## 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 the next run goes on the calendar, [register as a partner](/register) if your platform team will make introductions, since the Channel Partner Agreement is signed before any is submitted, use [who qualifies](/who-qualifies) as the only source for the session's fit slide, and check every slide against the current [program terms](/terms).

Choosing session topics is community work, and weighing SourceX as a possible investment is a separate exercise; anyone doing the latter can request investor materials 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://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0066245
- https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0066485
- https://sourcex.si/investors
