LaunchWeek.ai

Back to Day 5: Launch

Launch at a Conference Without Burning $20K and a Week

Most indie founders treat conference launches as either too expensive ("conferences are for funded startups") or too easy ("we'll just hand out stickers"). The version that works sits in between — a deliberate launch tied to a single high-leverage moment at a conference your ICP attends, with most of the work happening before and after the event, not during it. Done well, a single conference produces 50-200 qualified leads, 1-3 named press mentions, and 5-10 customer/partner conversations that compound for the next 12 months. Done badly, a conference is a $20K, week-long distraction with no measurable result.

Why Most Founder Conference Launches Fail

Three failure modes hit founders the same way:

  • The "we'll just be there and see what happens" plan. Founder buys a $4K booth, prints stickers, shows up, stands behind the booth for 3 days, and goes home with a stack of business cards and a hangover. No pre-event outreach, no scheduled meetings, no specific moment to launch around. The week's ROI is "we met some people."
  • The "I have to give a keynote to launch" trap. Founder optimizes the entire trip around a 30-minute talk, ignores the 99% of the conference that isn't the talk. The talk goes well; the talk is the only outcome. Could have had 50 conversations with prospects but didn't.
  • The post-event ghost. Founder collects 200 emails at the booth or via the conference app. Sends one generic "great meeting you" email. Never follows up again. Six weeks later, zero customers from the conference. The conference produced leads; the post-event motion produced nothing.

The version that works is structured: pick the conference deliberately, do 80% of the work before the event (meetings booked, press pitched, content prepped), execute a tight on-site plan, and run a structured 4-week follow-up that converts conversations into pipeline.

This guide assumes you have already done Customer Discovery Interviews (you know which conferences your ICP attends), have shipped a Demo Video and Pitch Deck, and have a Launch Announcement plan that the conference can plug into.

When Conference Launches Are and Aren't Right

Run a conference launch when:

  • A specific conference is the established gathering place for your ICP (every category has 1-3 of these — for example: SaaStr Annual for B2B SaaS, MicroConf for indie SaaS, RSA for security, Strange Loop for developers, etc.)
  • You have something specific to launch / announce (a product, a feature, a partnership, a new market entry)
  • You can budget $5K-$30K (booth + travel + collateral + post-event spend) and 2-3 weeks of focused work
  • You have or can build a pre-event meeting calendar of 15-30 prospects who'll be at the event
  • The conference has fewer than ~5,000 attendees (smaller is better for startups; 50,000-person mega-conferences favor large companies with massive booths)

Skip conference launches when:

  • You haven't validated PMF (a conference launch with no product is a pitch, not a launch)
  • Your ICP is geographically dispersed and doesn't gather at conferences (some categories — solo developers, certain B2C audiences — don't conference)
  • You can't sustain the 4-week follow-up motion (the conference is half the work; follow-up is the other half)
  • The conference doesn't have a clear "moment" structure (you need a launch announcement, a customer reveal, or a specific keynote — not just "we'll be there")

The Five Launch Surfaces at a Conference

A conference is many channels, not one. Pick deliberately which surfaces to invest in.

1. Booth Presence

A physical/virtual booth where attendees can find you, see a demo, talk to the team.

  • Cost: $2K-$30K depending on conference + booth size; smaller "kiosk" or "demo pod" tiers usually exist
  • Best for: products with strong visual demo + audiences that wander floors
  • Anti-pattern: a generic 10x10 booth with two people and a roll-up banner; nobody stops

2. Speaking Slot

You give a talk on stage — keynote, panel, breakout session, lightning talk.

  • Cost: usually free if accepted (CFP submissions); sometimes paid for sponsored slots ($5K-$30K)
  • Best for: technical / educational topics; founders comfortable on stage
  • Anti-pattern: a sales pitch dressed up as a talk; audiences tune out

3. Sponsored Activation

A specific event or experience tied to your brand — sponsored happy hour, dinner, breakout, after-party, lounge.

  • Cost: $3K-$50K depending on activation type
  • Best for: relationship-building with a curated audience (15-50 people you actually want to talk to)
  • Anti-pattern: throwing a generic "all welcome" party that attracts the wrong audience

4. Press / Media Briefing

1:1 or small-group meetings with journalists / analysts / industry influencers attending the conference.

  • Cost: usually free if you do the outreach work; sometimes facilitated by conference PR partners
  • Best for: any company with a launch announcement worth a press story
  • Anti-pattern: showing up without pitching anyone in advance

5. 1:1 Customer / Prospect Meetings

Pre-booked meetings with named prospects, customers, partners, journalists who'll be at the event.

  • Cost: opportunity cost (your time on-site)
  • Best for: every conference launch
  • Anti-pattern: showing up with no meetings booked, hoping serendipity will fill the calendar

For most indie SaaS in 2026: 1:1 meetings (pre-booked) + a small activation (dinner or happy hour for 20-30 prospects) is the right starting investment. Skip the booth at the first conference; consider it for the second.

1. Pick the Conference

The single most consequential decision. The right conference makes everything else easy; the wrong one wastes the budget.

Help me pick the right conference for [your product] at [your-domain.com]. My ICP is [from your ICP work]. My budget for conference launch is approximately [$X]. My team can dedicate [N people] for [N days].

Selection criteria:

1. **ICP density**: at least 30%+ of attendees match your ICP. Verify by:
   - Reading past attendee lists / sponsor lists / speaker lists
   - Talking to companies who attended last year — what's the audience really like?
   - Conference's own pitch deck / media kit

2. **Right size**: 500-3,000 attendees is the sweet spot for indie SaaS launches
   - <500: too small; not enough density of ICP
   - >5,000: you're a small fish in a big pond; mega-conferences favor large companies

3. **Right tier of company**: who else sponsors? If everyone is enterprise-tier, your $5K booth looks lost. If everyone is indie-scale, you fit.

4. **Right format**: does the conference have moments your launch can plug into?
   - Demo days
   - "Startup spotlight" sessions
   - New-product showcase areas
   - Lightning-talk slots
   If none, you're paying for floor space with no built-in launch moment.

5. **Right time**: does the conference timing fit your launch window?
   - 90+ days notice ideal (CFP deadlines, booth deals)
   - <30 days notice = expensive premium for last-minute booking
   - Right time of year for your category (post-holiday for B2B, fall conferences are typically biggest)

For my situation, generate 5 candidate conferences:
- Name + date + location
- Estimated attendance + ICP density estimate
- Cost range (booth tier I'd consider + travel + activation)
- 3 specific reasons this conference fits my product
- 1 specific reason it might NOT fit (be honest)

Rank by ICP density + cost-effectiveness. Pick #1 and develop the plan.

Sanity check: if I can't name 5 customers / prospects who'll be at the conference, the ICP density is wrong; pick differently.

Three principles I've watched founders re-learn:

  • Smaller, niche conferences beat mega-conferences for indie SaaS launches. A 1,000-person conference with 40% ICP density produces more pipeline than a 30,000-person mega-conference with 5% density.
  • The conference structure matters more than the size. A small conference with a built-in "launch moment" (Hacker House demo days, MicroConf, Indie Hackers events, etc.) produces better outcomes than a larger conference where you're invisible.
  • Pick the conference where your customers tell you they go. Customer-discovery interviews tell you the answer. Don't pick by Google search; pick by customer testimony.

2. Submit a Speaking Proposal (CFP)

If the conference has a Call for Proposals open, submit. A speaking slot is the single highest-leverage way to launch at a conference.

Help me write a CFP submission for [conference name]. Their tracks are [list of tracks if known]. The audience is [from research].

CFP submission structure:

**1. Title**: specific and outcome-led, not generic
- Bad: "AI in Customer Support"
- Good: "How we cut customer support response time 70% with one AI workflow (and the 3 mistakes we made first)"
- The title gets the slot; spend disproportionate time here

**2. Abstract** (200-300 words):
- The problem (audience-relevant, not product-relevant)
- The non-obvious insight or framework
- 3 specific takeaways the audience will leave with
- Why this audience specifically should care

**3. Speaker bio** (100 words):
- Founder credibility + product credibility
- Why I'm credible to speak on this topic specifically
- Past speaking experience if any
- Links to videos of past talks if available

**4. Outline** (5-10 bullets):
- Show you have a structure, not just a topic
- Include 1-2 specific data points or examples
- Promise actionable takeaways

CFP success rates are 5-15% at most conferences. Submit early. If accepted, the talk is the highest-leverage moment of the conference.

If NOT accepted: the conference often offers a sponsored speaking slot ($5K-$30K). Consider only if the sponsorship fits your budget AND the conference is high-priority. Don't pay for a slot at a marginal conference.

Output:
1. The CFP submission with title, abstract, bio, outline
2. The fallback if rejected (pursue sponsored slot? or skip and rely on other surfaces?)
3. The follow-up: if accepted, what specific announcement / launch moment plugs into the talk?

The single most useful tip for CFP success: lead with a specific outcome, not a generic topic. "AI in B2B" is rejected; "How we cut a 12-day onboarding to 2 days" gets accepted. Specific = teachable = valuable.

3. Book Pre-Event 1:1 Meetings

This is where 80% of the conference's pipeline is made. The booth and the talk are visible; the 1:1 calendar is invisible and decisive.

Help me build the pre-event meeting plan. Goal: 15-30 booked 1:1 meetings before the conference begins.

The targets:

**Prospects**: 10-20 people in your ICP who are publicly attending
- Find them via the conference app / Sched / LinkedIn "events" feature
- Filter by ICP fit (job title + company size + signal of relevant pain)
- Cold outreach 4-6 weeks before with: "I noticed you'll be at [conference]. I'm launching [thing]. I'd love a 20-minute coffee — happy to come to you anywhere on-site."

**Existing customers**: invite your customers attending to a curated dinner / breakfast / coffee
- 5-15 customers in one room is more powerful than 100 strangers at a booth
- Customers introduce you to other customers; relationships compound

**Partners and integrations**: companies you want to partner with
- Pre-pitch a 30-minute "let's grab time at [conference]"

**Press and analysts**: journalists / influencers covering your space
- Pitch the launch story 2-3 weeks before the conference (per [Press Outreach](press-outreach.md))
- Target: 3-5 press meetings on-site

**Investors / advisors** (if applicable): use the proximity to do warm intros

The cold-outreach template:
> Subject: Coffee at [Conference]?
>
> Hi [name],
>
> I noticed you'll be at [conference]. I'm [role] at [company] — we're launching [specific thing] there.
>
> Given your work on [specific thing they wrote / posted / shipped], I think there's a good fit. Would you have 20 minutes for a coffee on-site? I'm flexible on time and place.
>
> No pressure if timing's tight — would love to grab a beer at the [happy hour] otherwise.
>
> [your name]

Calendar tooling:
- Use [Cal.com](https://cal.com) or Calendly to send specific time-slot links
- Don't make people email back-and-forth to schedule
- Block your conference calendar with travel/talk/sleep, leave the rest open

Output:
1. The target list (15-30 names)
2. The cold-outreach templates (prospect, customer, partner, press)
3. The Cal.com event setup
4. The customer dinner / event plan if applicable

Three principles:

  • The pre-conference 1:1 list is your real launch target. Booked meetings convert 10-20x better than chance encounters. Spend the pre-event week filling the calendar.
  • Customer dinners outperform booths. A curated dinner of 12 customers + 8 prospects produces more pipeline than three days at a booth.
  • The press pitch happens before the conference. Journalists don't have time to write stories on-site; they preview the pitch 1-2 weeks before, schedule the meeting on-site, write afterwards.

4. Plan the Launch Moment

A conference launch needs a specific moment. Most attendees won't notice you exist if the launch is a vague "we're here this week."

Design the specific launch moment for the conference.

The format options:

**Option A: Tied to a speaking slot**
- The talk ends with the launch announcement
- Specific phrase: "Today, we're launching [X]. Here's how to try it."
- Press pitched in advance to be in the room

**Option B: Tied to a press / analyst briefing**
- A specific briefing meeting with press the morning of Day 1
- Embargo until Day 1 morning of conference
- Coverage drops mid-conference, amplifying the on-site presence

**Option C: Tied to a customer dinner / activation**
- Reveal the launch at a curated event for 30-50 ICP attendees
- Customers and prospects experience it first; turn them into advocates
- Drives word-of-mouth across the rest of the conference

**Option D: Tied to a Product Hunt / Hacker News launch**
- Schedule the [Product Hunt](product-hunt.md) or [Hacker News](hacker-news.md) launch to coincide with the conference's first day
- The conference becomes both an in-person and online amplifier
- Often produces the best results — multiple channels stacking

**Option E: Tied to a partnership / customer announcement**
- The launch is a partnership with a recognized brand
- Co-marketing piece announced at the conference
- Both parties amplify; press coverage is easier

For most indie SaaS in 2026: Option D (combined PH/HN launch + conference) is the highest-leverage if the timing aligns. Option C (customer dinner reveal) is the second-best if you have the customer relationships.

Output:
1. The specific launch moment (date + time + format)
2. The asset checklist for the moment (announcement post, demo, talking points, press release)
3. The amplification plan: how does the in-person launch get amplified online (founder posts, customer posts, attendee retweets, conference-organized social)
4. The post-launch follow-up sequence per [Launch Announcements](launch-announcements.md)

The single highest-leverage tactic: stack the conference with another launch channel. A combined Product Hunt + conference launch produces dramatically more coverage than either alone. The conference makes the online launch feel "real"; the online launch makes the conference feel newsworthy.

5. Execute on the Ground

Most founders mismanage time on-site. Discipline matters.

Build the on-site execution plan. Common mistakes to avoid:

**Mistake 1: Trying to do everything yourself**
- The booth, the talk, the meetings, the press, the dinner — all on one founder
- Result: late, hungover, low-energy by Day 2
- Fix: bring at least one team member; split duties; rotate booth coverage

**Mistake 2: Filling the calendar 100%**
- 8 hours of back-to-back meetings + booth time + talk + dinner
- No buffer for unexpected conversations (where the best deals come from)
- Fix: 60-70% calendar utilization; leave gaps for serendipity

**Mistake 3: Skipping conference parties / hallway conversations**
- The hallway conversations are where deals happen
- After-parties are where industry relationships form
- Fix: prioritize 1-2 specific evening events; show up; talk to strangers

**Mistake 4: Drinking too much**
- Conference culture often pushes alcohol; founders go along
- Result: bad meetings, slept-through morning slots, embarrassing photos
- Fix: drink less than you think; sleep more than you think

**Mistake 5: Failing to capture context for follow-up**
- Meet 50 people; remember 3 of them by name two weeks later
- Fix: 60-second voice notes after every meeting (name + company + specific topic + next step) — listen back during follow-up

**Daily structure**:

- **Morning** (8am-noon): scheduled 1:1s, press meetings, prep for talk if applicable
- **Mid-day** (noon-5pm): booth time, talk if applicable, hallway conversations
- **Evening** (5pm-9pm): customer/prospect dinner (private) OR conference-organized happy hour (broader networking)
- **Night**: sleep. The next day matters more than the after-party.

**Booth do's and don'ts** (if you have one):
- DO: have one specific demo flow, repeated. Don't try to demonstrate the whole product.
- DO: collect contact info via QR code → form → automatic CRM entry. Don't rely on physical business cards.
- DO: have a swag item that's actually useful (notebook, charger, water bottle) not just stickers.
- DON'T: have a 4-person staff that scares away introverts.
- DON'T: pitch from behind the booth; come around to the front.

Output:
1. The daily schedule template
2. The voice-note follow-up template
3. The booth-specific runbook
4. The "do not skip" list (sleep, water, breakfast, post-meeting notes)

The most-skipped tactic: voice notes after every meeting. A 60-second voice memo capturing "Anna at Acme, she's the head of customer success, struggling with X, wants demo next Tuesday" is the difference between a 3% follow-up conversion and a 30% follow-up conversion.

6. Run the Post-Event Follow-Up Sequence

Most founders' conference ROI lives in the 4 weeks after the event. Most founders skip this entirely.

Design the 4-week post-event follow-up sequence.

**Week 1: Personal follow-ups**
- Within 48 hours of the conference ending, every meaningful conversation gets a personal email
- Reference the specific topic discussed (the voice notes pay off here)
- Suggest a specific next step: "Let's set up a call next week — here's my Cal link"
- For prospects: link to demo / trial
- For customers: link to a relevant feature update / case study
- For partners: link to a partnership-discussion doc
- For press: any embargoed-info follow-up + thank-you

**Week 2: Group nurture**
- Anyone who got a generic-template email in week 1 (those without specific conversations) gets a second touch
- This is the email-list-style follow-up: "Thanks for stopping by our booth at [conference]. Here's what we launched + 3 takeaways from the show. [link to demo]"
- Lower personalization; broader reach

**Week 3: Press push for any embargoed coverage**
- If press meetings happened on-site, follow up on coverage status
- Push for placement in week 3-4 (often the natural cadence for trade press)
- Amplify any coverage on social

**Week 4: Pipeline review**
- Categorize all conference contacts by stage:
  - **Hot**: had a meaningful conversation; expressed buying intent; deserves immediate sales follow-up
  - **Warm**: had a positive conversation but no specific intent; nurture into the regular pipeline
  - **Cold**: collected at booth, didn't talk meaningfully; standard email nurture only
- Move hot contacts to weekly follow-up cadence with the founder
- Move warm contacts to monthly nurture
- Sunset cold contacts after 60 days unless they engage

**Week 4 deliverable: the conference ROI review**
- Total cost (booth + travel + collateral + activation)
- Total leads collected
- Total qualified pipeline ($)
- Hot conversations → demos booked
- Press coverage achieved
- Customer / partner relationships strengthened
- Verdict: was this conference worth re-attending next year?

Output:
1. The 4-week follow-up cadence
2. The personal email templates (prospect, customer, partner, press)
3. The pipeline categorization rubric
4. The post-event ROI template
5. The "decide on next year" criteria

The single most important habit: schedule the post-event follow-up before you go. Block 4-5 hours each week for the 4 weeks after the conference. Without it, the daily grind absorbs the time, and the conference's pipeline evaporates.

7. Special Cases: Smaller Events and Virtual Conferences

Not every conference is a 3,000-person trade show. Adapt for smaller and virtual formats.

For non-standard conference formats, adjust the playbook.

**Smaller events (50-300 attendees: meetups, mastermind-style, invite-only)**:
- The whole event IS the activation; the boundary between "official program" and "your launch" blurs
- Focus on attending fully (no booth needed; no formal launch moment)
- Pre-book 1:1s with the 5-10 most important people there
- Bring something specific to share / launch — even if low-key (a beta invite, a partnership announcement, an early customer reveal)

**Virtual / hybrid conferences**:
- Booth = your sponsored profile + scheduled video meeting slots
- Talk = same; you're remote
- 1:1 meetings = Zoom / video; book aggressively (less travel friction means more meetings possible)
- Activation = sponsored Zoom dinner or coffee chat; small group; curated invitation
- Press = same outreach, conducted remotely
- Post-event = same; even more important because the in-person serendipity is missing

**Owned events / small dinners (you host)**:
- Best ROI per dollar at indie scale
- Curated 12-30 person dinner / breakfast / cocktail at a relevant city
- $3K-$15K total cost (venue + food + drinks)
- Attendance: 80% ICP fit, mix of customers + prospects + partners
- Specific format: founder remarks (10 min) + structured discussion topic (30 min) + free networking (60+ min)
- Per [Customer References](../4-convert/customer-references.md): customer-attended dinners build advocacy

For most indie SaaS in 2026: 1 conference launch per year + 2-4 owned dinners = a balanced event presence.

Output:
1. The format-specific adjustments for my situation
2. The owned-event template if relevant
3. The annual event-budget allocation across conferences vs. owned events

The most underrated format: the owned dinner. A 25-person dinner you host, with 15 of your ICP at it, produces more pipeline at a lower cost than most 5,000-person conferences.

What Done Looks Like

By end of conference week:

  1. Conference picked with explicit ICP-density rationale
  2. CFP submitted (and accepted, ideally) OR sponsored slot booked OR speaking-free strategy decided
  3. 15-30 1:1 meetings booked before the event
  4. Specific launch moment scheduled (talk, press, dinner, or stacked PH/HN)
  5. Customer dinner or activation planned for the curated set
  6. Pre-event press pitches sent
  7. On-site execution plan with daily structure

Within 4 weeks post-event:

  • 4-week follow-up cadence executed
  • 5-10 hot pipeline conversations actively in motion
  • 1-3 press placements published
  • Post-event ROI review completed
  • Decision on attending next year documented

Within 12 months:

  • Pipeline conversion measurable: of the conference contacts, how many became paying customers?
  • Press coverage drove organic attribution
  • Customer relationships strengthened (renewals, expansion, referrals)
  • A repeatable conference-launch playbook documented for the next event

Common Pitfalls

  • Showing up without meetings booked. Pre-event 1:1s are 80% of the value.
  • Optimizing for a keynote that's the only thing. A 30-minute talk + 50 1:1s > a 60-minute keynote alone.
  • Generic "great meeting you" emails after. Specific follow-ups based on the actual conversation convert 10x.
  • Picking the conference by size, not by ICP density. Niche beats mega for indie launches.
  • No specific launch moment. "We're here this week" is not a launch.
  • Burning the team. Two founders on-site for 4 days, no breaks; performance dies on Day 2.
  • Drinking through the conference. Deals die in hangovers.
  • Skipping voice notes after meetings. Memory fades; the follow-up suffers.
  • No ROI review. Without it, you can't decide whether to attend next year.
  • Over-investing in the booth. A booth alone, without 1:1s and a launch moment, has poor ROI.

Where Conference Launches Plug Into the Rest of LaunchWeek

Verdict

Conference launches work for indie SaaS in 2026 when run as 80%-pre-work / 15%-on-site / 5%-luck. The teams that pick the right niche conference, book 25 meetings before arriving, design a specific launch moment, and run a structured 4-week follow-up reliably produce 10-30 qualified customers per event. The teams that "just show up" produce stickers.

For most indie SaaS: 1 conference launch per year is the right cadence. Pick deliberately, prepare aggressively, execute tightly, follow up religiously. The compounding payoff: customer relationships built at one conference become testimonials at the next; press coverage becomes case studies; conference talks become evergreen content; the network compounds.

Back to Day 5: Launch

← PreviousBehind the Scenes: How We Built This Site with AgentsNext →Find Your First 10 Paying Customers