Virtual Summit Case Study: 1,600 Registrations and $35K Revenue

The Ultimate CIRS Summit used free daily access, a paid replay offer, and sponsorships to report more than 1,600 registrations and $35,000 in gross revenue. The event was Glenn DiTulio's first virtual summit. It ran for six days and brought together 45 speakers across 61 talks.

This refresh resolves conflicting figures in HeySummit's original customer story by using the more precise event summary where the old prose disagreed with it. The results remain customer-reported rather than audited. The historical event and payment records were not available for this refresh, so the article labels estimates and calculations instead of presenting them as exact financial proof.

At a glance

On a phone, swipe sideways to see all columns in this table.

The challenge

Glenn was a first-time summit organizer. He wanted to bring useful CIRS information together in one event, make the sessions accessible without requiring every speaker to appear live, and raise funds through replay access and sponsorship.

The operational challenge was substantial. A multi-day summit needed an event site, registration, a schedule, speaker and talk records, access rules, payments, attendee emails, video delivery, and a way to review results afterward. The event also needed a simple offer that made sense to people who could attend during the summit and those who wanted longer access.

This article focuses on the event model and its reported commercial results. It does not make medical claims about CIRS or treat event revenue as evidence for any health claim.

The event and monetization model

The event used a straightforward free-to-paid structure. Registration gave attendees free access to each day's sessions during the summit. A $49 upgrade provided six months of on-demand replay access.

That structure gave the free ticket a clear job. It helped the event reach a wider audience during the summit. The paid offer solved a different problem for people who could not follow 61 talks across six days or wanted time to revisit the material.

The original case study reported 469 paid replay customers and approximately $22,000 in ticket or replay revenue. Multiplying 469 by $49 produces $22,981, not exactly $22,000. Without the payment records, it would be speculation to attribute the difference to rounding, discounts, refunds, complimentary access, or another cause. This article therefore keeps the reported revenue figure and does not present the multiplication as a reconciled sales ledger.

Sponsorship provided the second reported revenue stream. The old article said sponsors contributed $13,000 in total, but it also said every sponsor paid $2,000. Those statements cannot both be exact without more detail, so the $2,000-per-sponsor claim has been removed. The useful lesson is that sponsorship sat alongside the attendee offer rather than depending on ticket sales alone. Organizers considering a similar model can plan the promised placements and reporting around a current sponsor experience.

How the summit was put together

The case study described a largely pre-recorded program delivered through Vimeo, with HeySummit organizing the event-management layer around it. Pre-recording reduced the need to coordinate every speaker for a live appearance, but it did not remove the work of collecting talks, checking files, building the schedule, setting access rules, and communicating with attendees.

The original prose referred to 48 sessions and 43 experts, while the article's more precise event summary recorded 61 talks and 45 speakers. This refresh uses 61 talks and 45 speakers as the total event figures. It does not assume that every talk used the same recording or delivery setup.

For an event like this, paid event registration controls which content each ticket can access. A current checkout and upsell workflow can present an optional replay offer without forcing the organizer to manage access by hand. The video provider still hosts or delivers the recordings; HeySummit coordinates the event pages, tickets, schedule, access, emails, integrations, and reporting around them.

What the results mean

On a phone, swipe sideways to see all columns in this table.

The original article called $35,000 both revenue and net revenue. The arithmetic supports calling it gross revenue because the reported ticket and sponsor amounts already add to $35,000 before the separate $3,000 cost estimate. The post-cost figure is therefore approximately $32,000, subject to the limits above.

What appears to have worked

The clearest strength was the offer design. Free daily access made it possible to register without paying upfront. The replay upgrade then gave time-constrained attendees a reason to buy. Sponsorship added a separate source of revenue that did not require increasing the attendee price.

Pre-recorded talks also reduced live scheduling pressure. That choice still required production work, but it allowed speakers to contribute without sharing one live timetable. The six-day schedule gave the organizer room to release a large program in stages instead of asking attendees to navigate everything at once.

These are plausible explanations, not causal proof. The available records do not show which reminders, pages, speakers, sponsors, or traffic sources drove individual registrations or purchases. A future event should define those measures before launch and use event reporting and analytics alongside payment and campaign data to reconcile the result.

What another organizer can borrow

• Define the audience and purpose first. Be clear about who the event serves, what they should learn, and what the event must fund or achieve.
• Separate free access from the paid benefit. Give each ticket a clear job. In this case, the paid benefit was time: six months to watch the replay library.
• Model the revenue streams separately. Forecast tickets, replay upgrades, sponsors, and other offers as distinct lines so the final report can reconcile each one.
• Write down the denominator. Decide whether conversion means paid customers divided by registrations, attendees, unique purchasers, or another measure.
• Set sponsor tiers and deliverables before selling them. Record the agreed price, placement, session or booth, promotion, lead access, and post-event report for every sponsor.
• Plan the speaker and session workflow. Track permissions, talk status, video ownership, deadlines, captions, schedule placement, and the person responsible for each handoff.
• Reconcile the event after it ends. Compare registration, ticket, payment, refund, sponsor, platform, and other cost records before publishing a case study or repeating the model.

The model is useful, but it is not a guaranteed revenue formula. Audience trust, speaker fit, promotion, pricing, sponsor demand, costs, and follow-up will differ from one event to another. The practical next step is to build a forecast using the expected audience and offer. The guide to online summit ticket pricing can help with the attendee side, while the guide to virtual event sponsorship packages covers sponsor tiers and deliverables.

Where HeySummit fit

In the original customer story, HeySummit provided the event-management workflow around the summit. That included the event site, registration, ticket access, speaker and talk records, the schedule, attendee communications, video connections, and data for reviewing the event. Vimeo handled the underlying recordings.

That boundary matters. Event software can make the workflow easier to operate, but the organizer still owns the audience promise, speaker relationships, content, sponsor agreements, financial records, and final reconciliation.

See more HeySummit customer stories, or see how HeySummit works when you need one place to manage registration, tickets, speakers, schedules, replays, sponsors, communications, and reporting.