What Hosting Three Summits Taught Me About Whether They're Worth It
Nobody tells you what it costs
The pitch for hosting a summit is straightforward. Gather twenty experts, they all promote it, you build a list from everyone's audiences at once.
Which is true. That part works exactly as advertised.
What doesn't get mentioned is what sits underneath it: the recruiting, the scheduling, the chasing, the tech, the sponsor conversations, the speaker who drops out the week before, the platform that breaks on day two, the fact that half the roster promotes properly and half doesn't.
I've done three seasons.
I'm doing it again. But I'd want anyone considering it to have the actual accounting in front of them first, because most of what's written about hosting is written by people selling a course on hosting.
Is hosting a virtual summit worth it?
Yes, if you want a warm list, a position in your field, and twenty working relationships. No, if you want revenue in a defined window.
That's the honest version.
Hosting asks more of you than any other collaboration format, and it builds things the other formats can't. Both are true, and people mostly only hear the second one.
The question isn't whether it works. It's whether the specific thing it produces is the thing you currently need.
What does hosting actually deliver that contributing doesn't?
The whole list, positioning, and a roster of relationships. Contributors get a slice of the first one and none of the third.
Three things separate the host's seat from the contributor's.
The entire registrant list. Contributors get whoever opts in to their session or their contribution. The host gets everyone. That asymmetry is the single biggest reason to host, and it's not close.
Positioning. Being the person who convened twenty people in your field changes how you're perceived, including by the twenty people. You become the one who brings others together, which is a different thing from being one more expert with an opinion.
Twenty relationships at once. Every contributor now knows your name, has worked with you, and has an opinion about what you're like to work with. That group produces re-invites, referrals, and partnerships for years. It's the part that keeps paying long after the registrant list has been nurtured or lost.
What does it actually cost?
Months of calendar, not hours. Plus real money on tech, and the opportunity cost of everything you don't do during it.
The honest columns.
Time. Recruiting, scheduling, recording, editing, building pages, writing the emails, running the event, following up. It's a project, not a task, and it spans months rather than weeks.
Money. Platform, email sending at higher volume, design, and whatever help you bring in. Not enormous, and not zero.
Chasing. This is the cost nobody warns you about and it's the one that wears people down. Assets that don't arrive, promotion that doesn't happen, reschedules. It's steady low-grade admin for weeks, and it's the part that makes people say never again.
Opportunity cost. Whatever you didn't launch, write, or sell during those months. The largest number in the column, and the one nobody enters.
Do summits make money?
Sometimes, and modestly. Rarely enough to justify hosting on revenue alone. The list and the relationships are the return.
There's usually an all-access pass or upgrade, and it tends to produce something real without being transformative. Some hosts do very well on it. Plenty don't.
What tends to be true: the revenue from the event itself is smaller than the revenue that comes later from the list the event built. Which means judging a summit by what came in during the launch window is measuring the wrong thing at the wrong time.
If you host expecting the event to pay for itself in cash during the event, you'll probably be disappointed and you'll probably also have built something valuable while feeling like you failed at it.
Name the job before you start. If the job is list and positioning, the revenue is a bonus. If the job is revenue, hosting a summit is a strange way to get it.
What changes between the first one and the third?
The work goes down and the results go up, for the same reason: you know people, and people know what you're like to work with.
The first one is the hardest and produces the least, which is a rough combination and it's where most people stop.
What shifts with repetition:
Recruiting gets easier. The first roster is cold outreach. By the third, people say yes because they know you or know someone who's done it.
Promotion gets better. Contributors who had a good experience the first time promote harder the next time. Contributors who didn't don't come back, which solves itself.
The systems exist. Pages, sequences, templates, the whole apparatus. Built once, reused.
Your own list is bigger. Which makes you a more attractive host, which improves the roster, which improves registration.
That compounding is the actual argument for hosting, and it only exists if you do more than one. A single summit is an expensive way to grow a list. A recurring one is a different proposition entirely.
Worth knowing before season one, not during season two.
Should you host or contribute?
Contribute first. Host when you want the whole list and you have the capacity for a months-long project.
Contributing costs you a session and gets you a slice. Hosting costs you a quarter and gets you everything.
Contribute if: you're testing whether summits produce anything for your business, you want the exposure without the project, or your capacity is already committed.
Host if: you want the full list, you want the positioning, you have the months, and you're willing to do it more than once.
The middle path most people don't consider: co-host. Split the work and the list with someone whose audience complements yours. Less than half the effort in practice, because the recruiting gets easier when there are two networks, and it solves the loneliness of the admin stretch.
What would you do differently?
Decide the follow-up before the event, not after.
The pattern I'd flag hardest, and it applies to hosts and contributors both.
Everything gets planned up to the launch date. The sessions, the pages, the promotion, the schedule. Then the event ends, and there's a list of people who've just met you and no plan for what happens next, because all the planning energy went into the part with a deadline on it.
The registrant list is the entire asset. Whatever nurture is going to receive it should exist before the first session goes live, not be improvised in the exhausted week afterward.
When is hosting a bad idea?
When you need money soon, when you can't sustain a months-long project, or when you'd only ever do one.
Three clear passes.
Revenue on a deadline. Covered above. Wrong instrument.
No capacity for a project of that length. The chasing stretch is what breaks people, and it's unavoidable. If the months aren't there, contributing to someone else's gets you a good portion of the benefit for a fraction of the cost.
One and done. The return is in the repetition. If it's a one-off experiment, the effort-to-outcome ratio is poor, and you'll conclude summits don't work when what actually happened is you stopped before the compounding started.
The part I actually care about
A summit builds things that can't be bought at any price.
Twenty people in your field who now know what you're like to work with. A room full of people who watched you think for forty minutes before they ever landed on your list. A position as the person who convenes rather than the person competing for attention.
That's why plenty of hosts with healthy ad budgets run one anyway. Ads and summits aren't alternatives. Ads get you in front of people. A summit gets you vouched for by twenty peers at once, which is a different thing entirely, and there's no line item that produces it.
What it asks for in return is months, and the people selling you on hosting rarely itemize that part.
Three seasons in, the thing worth knowing is that the first one is the investment and the rest is the return. Go in planning for more than one, or contribute to someone else's and keep your quarter.
