GTM
What a $100K booth actually buys
The full accounting from SaaStr, including the line items most conference recaps leave out.
Alex Turnbull3 min readConference recaps are useless because nobody publishes the denominator. Everyone posts the photo and the "amazing energy" and nobody says what it cost or what came out the other end.
So here's ours from SaaStr, as close to complete as I can make it.
In
100k, gold sponsor level, out of my own pocket.
That number is not the booth fee. The booth fee is a chunk of it and then there's everything else: the build, shipping the build, flights and hotels for the team in San Francisco in May which is its own special expense, the panda mascot costumes, the sign holders we hired for Gate 15, the Hawaiian shirts, the videographer, the swag, the dinners, and the two weeks of team time before and after that nobody puts in the spreadsheet but should.
Add the opportunity cost of 10 people not building for a week and the real number is higher than 100k. I'm not going to pretend I've calculated that precisely.
Out
125 ICP-fit demos across 3 days.
The qualifier is doing a lot of work in that sentence, so: b2b saas, roughly $1M to $50M arr, someone with a support function and an opinion about it, who sat down and watched the product. Badge scans were a multiple of that and badge scans are a vanity number.
From those 125, we're closing $50k mrr or so, with cohorts locked for fall and winter.
At 100k spent, that's payback inside the first few months of those contracts, before you count anything they expand into. On paper it's the best money we've spent.
The line items nobody publishes
The pipeline decays fast. Roughly half the value of those 125 conversations was gone within 3 weeks. Conference intent has a half-life and it's short. If your follow-up sequence isn't built and staffed before you fly out, you are lighting money on fire and you'll find out in a month.
We built the follow-up playbook after the event, which was too late. Call 1 agenda, objection handling, the whole thing. It's good now. It should have existed in April.
We wrecked our email domain. 125 demos plus the wider list turned into outreach volume that helply.com had never seen, and Google Postmaster went to "Bad." That's a separate post because the fix took weeks, but it belongs in the SaaStr P&L and it never shows up in anyone's recap.
Booth traffic and demo quality are inversely related. The busiest hours produced the worst conversations. Our best 20 demos came from quiet periods and from dinners, which is an argument for spending less on attracting a crowd and more on the ability to have a real conversation when someone good shows up.
What the money actually bought
Three things, in order of value.
A deadline. 125 companies knowing what you're shipping is a commitment device you can't buy any other way. I've written about this separately and it's still the single highest-return part of the 100k.
Proof the positioning works on strangers. We'd tested "$0 per seat" on friendly audiences. Watching it land, repeatedly, on people who'd never heard of us, in a hallway, in 8 seconds, is worth a lot of research.
Pipeline. Genuinely third. The pipeline is what pays for it, and it's still the least interesting thing we got.
The next one
Customer Success Summit in September. 60k as the headliner slot, which is a different shape of spend: less booth, more stage.
Same play, except the product is real this time, and the follow-up machine exists before we land. Then SHIFT in Barcelona in October and Support Driven in NYC, which are smaller and cheaper and might turn out to be the better ratio.
The honest problem
Conferences are a spike. They're not a channel.
You can't run one in week 3 of a quarter because the number's soft. The calendar decides, and between events you're back to LinkedIn and outbound and hoping the content works. Building a company on top of 4 events a year means 4 good months and 8 nervous ones.
I know what our repeatable motion needs to look like. We're maybe 60% of the way to having it. Until then I'm spending 100k a pop on forcing functions and telling myself it's a strategy.
Sometimes it is.
I'm still figuring this stuff out too.
I write about what I'm learning building B2B companies.
Get the next one, straight to your inbox.
Building a B2B company?
I'm putting together 25 founders to work through the hard decisions together.