Annual User Conference (or Customer Summit): The Playbook

Most B2B SaaS companies who attempt their first user conference do it too early, scope it too big, build it on the wrong assumption (that "if we host it, customers will come"), spend $250K-1M of cash + 6 months of team focus, and walk away with 80 attendees, $40K of pipeline, and a company hangover. The lessons everyone learns the hard way: a conference is a product launch with a deadline, not a marketing campaign; you need the audience BEFORE you announce the conference, not after; the speaker lineup matters more than the venue; and the "ROI" never shows up in the quarter you spent the money — it shows up 18 months later as customer expansion + advocacy.

When done right, the annual user conference is the highest-leverage company event you'll ever run: 24 hours where every customer becomes more committed, every prospect closes faster for 9 months after, every employee gets recharged about why they're building this, and the press gets the year's biggest story all in one place. Salesforce's Dreamforce (170K+ attendees), HubSpot's INBOUND (~10K), Notion's Make (~2K), Linear's first conference (~500 in 2023), Anthropic's first dev day (~500 in 2024) — every category-defining SaaS eventually does this, and the ones who do it early often punch above their stage.

The trick is doing it AT the right stage with the right scope. Not before. Not bigger than warranted.

What Done Looks Like

A successful first or recurring user conference produces:

200-2000+ attendees (size-appropriate for your ARR + customer base)
60-80% customer + 20-40% prospect mix
25-50 customer-led sessions or fireside chats (the customers ARE the program)
A keynote that ships actual product news (3-7 launches stack-released at the event)
A press story that lands beyond your existing media reach
Net New ARR sourced/influenced visible by Q+2 (typically 10-25% of pipeline for a quarter)
An NPS lift among attendees (+10 to +20 vs non-attendees)
5-10 expansion conversations that close in the following quarter
A sales+CS team that comes back recharged
A program that the team WANTS to do again (the team-energy test)

Plus a real artifact: a recap video, a content library (recorded sessions), a press kit, and the next year's date announced before the close-out.

This pairs with Product Launch playbooks (the keynote IS a launch), Press Outreach (PR shoulder), Customer Advisory Board (the seed of speaker lineup), Customer Marketing Program (this IS customer marketing at peak), Behind the Scenes (content for the year), Webinars (smaller-scale equivalent), and Conference & Event Marketing (different motion: attending OTHER people's events).

When NOT to Run a User Conference

Don't run one if any of these apply:

ARR <$5M. Below this you don't have enough customers to populate a real attendee mix. A "conference" with 30 customers + 20 prospects is a customer dinner with a stage. Just do the dinner. (Notable exceptions: Linear at <$5M; some PLG-led tools. The threshold isn't absolute — it's the question "can we credibly fill a room with peers helping each other?")

You don't have customers who'd fly to attend. A conference is a peer-learning event. If your customers don't want to meet OTHER customers (because they don't view themselves as peers, or your product is too utilitarian), the conference falls flat regardless of program quality. Run a customer roundtable instead.

You're pre-PMF. A conference signals "we're an established platform you can build on." If the product is still finding its shape, customers feel the dissonance.

Your team's GTM motion can't absorb the lift. A conference produces a pipeline spike + an expansion-conversation spike. If sales + CS can't follow up within 7 days, the conference produces nothing measurable beyond a great Twitter weekend.

You're competing for the team's focus with a major product launch. A conference IS a product launch with a deadline. Don't try to also ship a major launch in the same 60-day window — one will shortchange the other.

You can't commit $200K+ AND 6 months of team time. Smallest credible first conference: ~$200K all-in. Plan for $300-600K for 200-500 attendees. The team-time cost is bigger than the cash cost.

Your CEO won't headline the keynote. If founders don't show up center-stage, customers feel snubbed. CEO time is non-delegable for the keynote.

You have a major fundraise in flight. The optical conflict (lavish event vs. tight runway) is rough, and the founder-time conflict is real.

If any of these apply, do something smaller (regional dinners, a 1-day customer summit at your office, an online-only event) and revisit conference next year.

When You're Ready

Hire-grade signals:

ARR is $5M+ (or you have 200+ active engaged customers, e.g. PLG-tier).
20-40 customers will say YES to fly-and-stay if you ask honestly.
5-10 customers will say YES to speak (this is the dealbreaker test — if no customer will speak, the conference is a marketing event, not a community event).
You have 3-7 product news items to stack-release at the keynote.
You have a marketing or events person (employee or strong contractor) with conference experience.
You can lock the CEO + 5 senior leaders for 60% of an 8-week pre-conference window + 3 days of conference.
You have $200K-1M cash earmarked.
The team WANTS to do this (energy matters; a forced conference is grim).

If 7+ of those are true, you're ready. Begin 9-12 months before event date.

Picking the Format and Scope

The biggest first-conference mistake: scoping like Dreamforce when your stage warrants Linear's first event.

Format options to consider:

1. INVITATION-ONLY CUSTOMER SUMMIT
   - 50-150 attendees, all customer
   - 1.5 days at a destination resort or city venue
   - Heavy peer learning, deep workshops, executive-led discussions
   - $100K-300K all-in
   - Best for: ARR $5-25M, enterprise-led, deep account development

2. SMALL OPEN CONFERENCE
   - 200-500 attendees, ~70% customer / 30% prospect
   - 1-2 days, urban venue (often hotel ballroom or design-forward space)
   - Mix of keynotes, breakouts, customer-led sessions, networking
   - $250K-700K all-in
   - Best for: ARR $25-100M, broad SMB+mid-market base
   - Sweet spot for first conferences in 2024-2026 era

3. MID-SIZE CONFERENCE
   - 500-2000 attendees
   - 2-3 days, dedicated convention hall or large hotel
   - Multi-track program; full sponsor expo; press track
   - $700K-3M all-in
   - Best for: ARR $100M-1B
   - Wait until you've run the smaller version twice

4. LARGE INDUSTRY CONFERENCE (Dreamforce-tier)
   - 2K-100K+ attendees
   - 3-5 days, dedicated venue + city takeover
   - Sponsorship marketplace; major artist concert; press hub
   - $5M-100M+ all-in
   - Best for: ARR $1B+
   - Don't think about this for 5+ years

5. ONLINE-ONLY (or Hybrid)
   - 1K-10K+ attendees online (often free tier)
   - 1-2 day livestreamed event
   - Lower-cost alternative; broader reach; lower engagement
   - $50K-300K all-in (mostly production)
   - Best for: PLG products with global distributed customers
   - Note: "hybrid" is HARDEST mode; pick lane fully

Default for first conference at $5-50M ARR:
- SMALL OPEN CONFERENCE (200-400 attendees, 1.5 days, urban venue)

This format is the highest-leverage starting point. It's small enough to feel intimate, big enough to feel like a real event, and the budget is recoverable.

The decision rule: under-scope your FIRST conference. You can always go bigger next year. You cannot recover from a flat first event.

The 9-12 Month Calendar

Conference planning is gantt-chart territory. The pattern that works:

T-12 months: GO/NO-GO decision
- Pick date (avoid your industry's other conferences; check sales-team conflicts)
- Pick format and scope
- Lock budget
- Identify owner (events manager / outsourced producer)
- Decision: city + general venue requirements

T-9 months: VENUE + CORE TEAM
- Sign venue contract (book 9-12 months out for popular cities)
- Lock production agency / event-tech vendor
- Lock travel coordinator
- Begin sponsor/partner conversations (if applicable)
- Pick brand identity (event has distinct logo, color, story)
- Reserve hotel block (10% of attendees x 1.5 nights average)

T-6 months: PROGRAM + FIRST PROMO
- Lock 5-10 anchor speakers (CEO + senior + headline customers)
- Soft-announce conference + date to customers (sales/CS slack to outreach)
- Public announcement with simple landing page (date, city, "save the date")
- Begin building the call-for-speakers funnel (open the form)
- Confirm headline customer keynote(s)
- Start press list-building

T-4 months: AGENDA + REGISTRATION
- Open registration with launch incentive (50% off / first-week-free / tier-locked)
- Publish ~50% of agenda (keynote topic, headline speakers)
- Close call-for-speakers; select breakout speakers
- Confirm all sponsors
- Lock food, AV, run-of-show production company
- Begin email-marketing sequence (every 2-3 weeks until event)

T-3 months: REGISTRATION RAMP
- Publish full agenda
- Drive registration via email + sales + CS + paid social
- Recruit volunteer "ambassadors" (engaged customers who'll get social-amplifying perks)
- Confirm all logistics: catering, A/V, internet, security, parking
- Build the recap-video plan

T-2 months: REGISTRATION PUSH
- Sales + CS personally invite top accounts (1:1 invites convert 10x cold)
- Lock the keynote rehearsal schedule
- Press list outreach (early-access to news, exclusive interviews)
- Build the launch-day press kit
- Run all-hands rehearsal of run-of-show
- Confirm 2-3 backup plans for tech failures

T-1 month: LOCK + REHEARSE
- Lock attendee count for catering / swag / nameplates
- All keynote speakers do FULL rehearsal in-venue (or remote with full slide review)
- Final email cadence to attendees with practical info (parking, agenda, etc.)
- Press embargoes set; analyst briefings scheduled
- All sponsor logistics confirmed
- Backup plan for venue/airline/sickness disruptions

T-1 week: GAME WEEK
- Daily team standups
- Setup begins T-3 days
- Run-of-show walked through twice in venue
- Full tech rehearsal T-1 day
- Sound check, slide check, livestream check, internet check

EVENT DAYS:
- Run-of-show executed by production team
- Founder/CEO + execs are guests of honor; do NOT manage logistics
- Owner makes 100 micro-decisions per hour; team escalates only fires
- Daily debrief; daily fixes for tomorrow
- Press events scheduled; analyst briefings scheduled

T+1 day: HANGOVER + START WIN-BACK
- All-hands debrief
- Send recap email to all attendees within 24 hours
- Send pipeline-actions list to sales (every conversation, every interest)
- Schedule recap-video editing

T+1 week: ASSET DROP
- Recap video published
- Recorded sessions begin uploading
- Press recap blog post
- Customer testimonials captured at event begin appearing in marketing
- Sales follow-up cadence in week 1 hits

T+1 month: LESSON-LEARNED + RECONNAISSANCE
- Post-mortem (what worked, what didn't, what to skip next year)
- Survey attendees (NPS, what they'd want differently)
- Decision: do we run again? When?
- Begin contracting venue for next year (if yes)

The Program Design Principles

The mistake that kills conferences: too many vendor sessions; too few customer voices.

Rules of thumb for content (200-400 attendee conference, 1.5 days):

- 1 main keynote (CEO, 45-60 min, ships product news)
- 1 closing keynote (founder + customer or visionary, 30-45 min)
- 4-8 customer-led sessions (35-45 min each, peer learning)
- 4-8 vendor-led breakouts (30-45 min each, deep technical content)
- 2-3 fireside chats (15-25 min, conversational format)
- 1 "AMA with executives" (45 min, public Q&A)
- Networking time: 30-40% of total scheduled hours
- Hosted lunch + dinner + happy hour
- 1 special moment (concert, dinner-on-rooftop, surprise speaker, art exhibit)

Customer:vendor session ratio: at least 50:50; ideally 60:40 customer-led.

Sourcing speakers:
- Customer Advisory Board members (always pre-asked)
- Customers who self-nominate via call-for-speakers
- "Who's quoted in our case studies" → invite
- Curated invites (your most referenceable customers)
- Some external thought-leaders (not too many; this is YOUR community)

Themes that work in B2B SaaS first-conference content:
- "How we use [Product] at [Company]" — pure customer-led
- "The future of [your category]" — visionary panel
- "Lessons from scaling [function] from 10 → 100" — peer learning
- Live product demos (interactive, not just slides)
- Hard-truths track (e.g. "What we got wrong" panels)
- Founder origin story / company values track

Themes that don't work in first-conference content:
- "Sponsor demos" (kills energy)
- "Industry futures" panels with no customer voices
- Multi-vendor partner panels (turns into a sponsor pitch)
- Pre-recorded sessions (always feels lower-tier than live)
- Long sit-and-listen sessions (>45 min unless headline keynote)

Production-side:
- Hire a real keynote-tier production team if budget allows ($30-100K)
- Slides, lights, music transitions matter; investment is visible
- Stage design: bold but not corporate
- Step-and-repeat backdrops for press / social photos
- Hire a videographer for both the recap AND in-the-moment livestreams to social
- Photographer at every panel (you'll use these all year)

The Keynote: Treat It as a Product Launch

The keynote IS the launch event for the year's biggest product news. Plan it that way.

Keynote design rules:

Length: 45-60 minutes, 60 absolute max.

Structure:
- 0-5 min: Welcome, energy-setting, gratitude to customers
- 5-15 min: "Where we've been" — accomplishments since last conference (10-12 stats, customer logos, milestones)
- 15-35 min: "What we're shipping" — 3-7 product news items, each 2-5 minutes
- 35-50 min: Customer story (live demo with a real customer onstage; the BEST part of any keynote)
- 50-60 min: "Where we're going" — vision moment; one signature future-facing statement
- Close: thank-you, sponsorship credits, "Have a great conference"

Product news stacking:
- Save your year's biggest features for the keynote
- 3-7 launches stacked: one signature; 2-3 medium; 2-4 smaller
- Press releases drop the morning of keynote (with embargo)
- Each launch needs: live demo, 1-line value prop, link to docs/blog, clear "available today" or "available in [Q]"
- Don't pre-announce; let the keynote be the news

Speaker craft:
- The CEO/founder is the keynote
- Practice 8-15 times before stage day (this is non-negotiable)
- Cue cards are fine; teleprompters break authenticity
- Pace: slower than you think
- Smile when announcing customer wins
- Pause for laughter; pause for applause
- Customer-onstage moments are gold; rehearse them too

Demos:
- All live, no exceptions
- Have backup-pre-recorded version for catastrophic failure
- Internet failure plan (mobile hotspot + downloaded fallback)
- Practice the demo 20+ times to remove every "uh let me click here"

What to AVOID:
- Reading bullet points
- Long product roadmap slides
- Self-congratulatory metrics that don't ladder to customer benefit
- Too many speakers cycling on stage (kills momentum)
- Surprise lawyer-driven copy edits 24 hours before keynote

Money: Building the Budget

Rough budget breakdown for a 200-400 attendee conference, 1.5 days, urban venue, mid-market B2B SaaS:

CATEGORY              TYPICAL %     EXAMPLE ($)

Venue + AV            25-35%        $80,000-200,000
Production            10-15%        $30,000-90,000
Catering              10-15%        $30,000-90,000
Travel for team       5-10%         $15,000-60,000
Speaker travel        3-7%          $10,000-40,000
Marketing/comms       5-10%         $15,000-60,000
Swag + experience     3-7%          $10,000-40,000
Photographer/video    3-5%          $10,000-30,000
Insurance + perm      1-3%          $3,000-15,000
Contingency           10%           $30,000-50,000+

TOTAL                              $230,000-675,000

Lower the budget by:
- Smaller venue / suburban location
- Day-of catering only (no fancy dinners)
- Skip the keynote production agency (DIY)
- Limit team travel
- Less swag (one good item beats five mediocre ones)

Raise the budget if:
- You have major sponsors offsetting cost
- You're courting press / analysts (extra hospitality matters)
- You want a "wow factor" moment (concert, off-site dinner)

Sponsor offsets:
- Don't take sponsors year 1 (they distract from customer focus)
- Years 2+: ecosystem partners pay $25-100K for table + speaking slot
- Cap sponsor count to <20% of attendee slots; over-sponsoring kills feel
- Customer-only events (no sponsors) feel different from sponsor-marketplace events

Driving Registration

The attendance ceiling is set by the announcement, not the venue. Treat registration like a product launch.

Registration drivers (in order of conversion rate):

1. Sales + CS personal 1:1 invites
   - Conversion: 30-50% of personally-invited senior contacts
   - "I personally want you there; let me cover registration"
   - Owner: every AE/CSM has a list of 5-10 must-attend accounts

2. Customer-of-the-year-style awards drives attendance
   - "[Customer] won our [Innovation] Award; come accept it"
   - Conversion: 70%+ for nominated customers + their teams
   - Owner: customer marketing

3. Speaking-slot acceptances
   - Speaker + 2-3 colleagues attend
   - Conversion: 95% (they have to be there to speak)
   - Owner: program team

4. Email cadence to all customers
   - 6-8 touches, 4 months out → event
   - Conversion: 5-12% of contacts
   - Owner: marketing

5. Public landing page + paid social
   - Conversion: 0.5-2% of traffic
   - Owner: marketing
   - Use sparingly; prospect attendance is bonus, not primary

6. Partner / referral channels
   - Investors invite their portfolio
   - Sponsors bring their network
   - Conversion: variable

7. Press / earned media
   - Conversion: low for attendance; high for awareness

Pricing strategy:
- Free for top 100 customers (white-glove)
- $99-499 for additional customer seats (creates commitment, supports breakeven)
- $999-2499 for prospect / general
- Free or discounted for sponsor staff
- Free for press / analysts (with code)

Don't fully-discount paid tickets to fill seats — empty paid seats feel BETTER than discounted seats; the room still looks full at 80%, and the financial math survives.

What Not to Do (Common Failure Modes)

Failure: Conference scoped like a competitor's; team breaks
- Pattern: "Salesforce does Dreamforce, we'll do half of that" — 5,000 attendees, year 1, $5M budget
- Reality: 200 attendees + $4M wasted; team is exhausted; unspoken "never again"
- Fix: under-scope first conference; always

Failure: Too many vendor sessions, too few customer voices
- Pattern: 70% sessions are vendor-led; customer is implicit
- Reality: feels like a marketing event; attendees fade post-keynote
- Fix: 50:50 customer-vendor minimum; aim 60-40 customer-led

Failure: Picked wrong dates (vs major holidays or competing events)
- Pattern: scheduled mid-July, two weeks after big competitor event
- Reality: half the customer ICP is unavailable; competitor stole press cycle
- Fix: research industry calendar; pick 6-8 weeks before fiscal close OR after major holidays

Failure: Underspent on production
- Pattern: hotel ballroom + DIY A/V → looks amateur on social
- Reality: feels small even if attendance is good
- Fix: invest in keynote-tier production; the photos/recap will pay back

Failure: CEO stayed offstage too much
- Pattern: CEO does opening keynote, then disappears for 36 hours
- Reality: customers feel snubbed; relationships go cold
- Fix: CEO present for 60%+ of conference time; doing 1:1s, AMAs, hallway chats

Failure: Press / analysts not pre-briefed
- Pattern: reporter walks in cold; gets generic news; story is mediocre
- Reality: keynote news doesn't land; press cycle weak
- Fix: 4-week pre-briefing tour with embargoed news; tier-1 outlets get exclusives

Failure: Pipeline follow-up was sloppy
- Pattern: 50 prospects gave business cards; sales follows up in week 3; pipeline cools
- Reality: ROI never visible; doubt cast on next year
- Fix: same-day pipeline import; <72-hour personalized follow-up; 14-day cadence

Failure: Tried to ship a major product launch in same window
- Pattern: conference + launch overlap; both shortchanged
- Reality: keynote feels rushed; launch lacks prep
- Fix: don't do both; launch news AT the conference is fine; major non-conference launches stay 60+ days separate

Failure: Speakers under-rehearsed
- Pattern: customer speakers prepared themselves; talk runs long; demo fails
- Reality: program quality varies wildly
- Fix: dedicated speaker coach; 2-3 rehearsals per speaker mandatory

Failure: No "moment" — event was forgettable
- Pattern: standard keynote + breakouts + dinner
- Reality: nothing memorable; no Twitter thread; minimal earned media
- Fix: design ONE special moment (surprise customer onstage, signature visual, signature party); cut a corner elsewhere if needed

Failure: Sponsorship-led too early
- Pattern: ARR $8M; took 25 sponsors year 1; conference feels like trade show
- Reality: customers feel like product
- Fix: years 1-2 are sponsor-light; bring partners in year 3+

Failure: Hybrid mode disappointing both audiences
- Pattern: tried to serve in-person AND online; both got 70% of a great event
- Reality: hybrid is operationally 2x harder than either alone
- Fix: pick lane: in-person primary OR online primary, secondary version is "good enough"

What Done Looks Like (recap)

A successful annual user conference produces:

Plus a discipline: the conference becomes an annual rhythm. Years 2-3 build muscle. By year 4 it's a fixture customers plan their year around. That's when conference compounds into category-defining moat.

Mistakes to Avoid

Scoping for the company you want, not the company you have. Smaller first event always; grow into it.
Saying yes to sponsors year 1. Stay customer-focused; bring sponsors in year 3+.
Underestimating the team-time cost. This isn't 6 weeks of marketing — it's 6 months of senior-team focus.
Picking a date without industry calendar research. A great conference scheduled wrong is half-attended.
Skipping CEO rehearsals. Keynote is the keynote; founder must invest 8-15 rehearsal hours.
Hosting in a hotel ballroom for cost reasons. Production matters; venue matters; audience reads it.
Minimal customer voices on stage. This kills conferences. The customers ARE the program.
Hybrid by default. Pick lane fully — in-person primary OR online primary.
Sloppy pipeline follow-up post-event. The ROI is in the 90-day follow-through, not the keynote moment.
Designing a flat program (just keynotes + breakouts). Add ONE special moment that becomes the Twitter thread.
Not announcing next year's date at close. The momentum should compound; gap-year conferences feel like one-offs.
Trying to recoup year 1 cost via attendee fees. Year 1 is investment; never breakeven; price for community feel.
Confusing user conference with industry conference. This is YOUR community; not a category-wide event. Don't dilute by inviting too many non-customers.
Making the conference about the company, not the customer. Vendor-led from start to finish is the failure pattern.