Score C · 5.94/10Free to read$100K Hackathon · November 16, 2026 → December 16, 2026Nov 16, 2026

Speaker Packet

Speaker Packet turns an event's speaker list into one fill-in packet page per speaker plus a live completion dashboard, so organizers stop chasing bios, headshots and AV details through email threads.

One product, one founder, thirty days. Everything below is built to be executed inside the contest window — the official rules still decide what counts.

Decide in 20 seconds

The facts that decide whether this is worth thirty days of yours.

Speculative5.94/10
MVP build (solo)
5 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
Cold email to named organizers of events whose call for speakers closed in the last 60 days or closes this month, each email linking to a portal pre-built from that event's publicly listed speaker names.
Who pays

The single person who owns speaker logistics for an English-speaking event of 30-300 attendees and 10-60 speakers, in the 2-8 weeks after the call for speakers closes, paying with a company or personal card.

Biggest execution risk

Market demand 3.9/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 9; 7 sales at $149 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.9/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

10 concrete actions. Tick them off as you go — nothing is saved or sent.

0/10
Entry price
$149
Solo build
5 days
30d base revenue
$1,490
30d hackathon profit
$1,430
Section 1 of 8

Product opportunity and positioning

Target customer

The single person who owns speaker logistics for an English-speaking event of 30-300 attendees and 10-60 speakers, in the 2-8 weeks after the call for speakers closes, paying with a company or personal card.

Why now

Events run on dated deadlines and the buyer has a card and no procurement, so a $149 one-time charge can clear in a single email thread this week, and November-December is when spring-event speaker onboarding happens.

Problem

Bios, headshots, abstracts and AV needs arrive as scattered email replies; the organizer rebuilds a spreadsheet by hand, re-asks the same five people, and hands the MC an inconsistent pack the night before.

Solution

Paste event details and a speaker list, get one no-login packet link per speaker, watch a per-field completion grid with timestamps, send one-click reminders only to incomplete speakers, then export a print-ready speaker packet and a full CSV.

Differentiation · A form tells you someone answered; Speaker Packet tells you which speaker is missing which field as of when, reminds only those people, and produces the MC-ready pack. It is one artifact for one event, not a blank-canvas builder.

1. Product opportunity and positioning

Speaker Packet sells to one person: the organizer who owns speaker logistics for an event of 30-300 attendees with 10-60 speakers, in the two to eight weeks after their call for speakers closes. That person is not shopping for event software. They are staring at an inbox of half-finished bio replies and a headshot folder with four files in it, three weeks before the program goes to print.

The wedge is deliberately narrow. The product is one artifact for one event: a fill-in packet page per speaker plus a completion dashboard. The organizer pastes the speaker list. The product mints one no-login link per speaker. Each speaker fills bio (with a character counter that matches the program layout), headshot, session title and abstract, AV requirements, travel notes and social handles. The organizer sees a grid of who completed what and when, reminds only the incomplete speakers in one click, and exports a print-ready speaker pack for the MC plus a CSV of everything.

The positioning sentence against the generic alternative is the entire sale: a Google Form plus a spreadsheet tells you that someone answered; Speaker Packet tells you which speaker is missing which field, since when, and hands you a pack the MC can read the night before. It is explicitly not a blank-canvas builder, not a call-for-speakers review tool, not an agenda builder, and not a speaker-management platform with procurement attached.

The JEV score of 59.4 (band C) is honest about where this concept is weak. Market demand scores 3.91 normalized and monetization 4.63 — the organizer's pain is real but rarely already budgeted as a line item, and a one-time $149 charge has no automatic renewal. The strong criteria are speed to first revenue (7.91) and solo build feasibility (7.57). The 30-day plan therefore front-loads a four-day build and spends every remaining day buying down demand risk with outreach rather than adding features. Every dollar of the projection comes from cold email to named organizers, so the pipeline is built on day 5, not on day 25.

The repeat-purchase path is the Season Pass: associations, meetup chapters and community teams run several events a year, and the same roster carries across them. That is the only route to more than one charge per buyer inside 30 days, and it is offered at the moment of first sale, never as a prerequisite.

Section 2 of 8

Smallest sellable MVP

An organizer pastes an event and a speaker list, gets one signed no-login packet link per speaker, watches a per-field completion grid, sends one-click reminders to incomplete speakers, and exports a print-ready speaker packet plus CSV — unlocked by a $149 Stripe Checkout.

Must-have features

  • Event creation form with name, date, venue, brand colour and public slug
  • Organizer magic-link email login (no passwords)
  • Speaker import by CSV paste or plain-text list, generating one signed no-login token per speaker
  • Speaker packet page: bio with character counter, headshot upload via presigned URL, session title/abstract, AV needs, travel notes, social handles
  • Completion dashboard: per-speaker, per-field status with last-updated timestamps
  • Filters for 'missing headshot' and 'not started'
  • One-click reminder email to incomplete speakers only, with editable template and send log
  • Print-ready speaker packet export (single printable page) and full CSV export
  • Stripe Checkout that activates an event for publishing, reminders and exports

Explicitly out of scope

  • No call-for-speakers submission forms or abstract scoring
  • No agenda, schedule or calendar-sync builder
  • No travel booking, reimbursement or expense handling
  • No video upload or AV file hosting
  • No custom domains or full white-label branding in the first 30 days
  • No integrations with third-party event platforms
  • No team roles or multi-user permissions
  • No AI-generated bios

Demo flow (what the buyer sees)

  1. Organizer opens the site and signs in with an emailed magic link.
  2. Organizer pastes event name, date, venue and a speaker list in plain text.
  3. Product creates the event and shows one copy-ready packet link per speaker.
  4. Speaker opens their link, fills bio, uploads a headshot, sets AV and travel notes, submits.
  5. Organizer dashboard updates that speaker's row to complete, with a timestamp.
  6. Organizer clicks 'Remind incomplete' and only the outstanding speakers receive email.
  7. Organizer clicks 'Export speaker pack' and browser-prints a single document for the MC.
Build plan

Technical implementation plan

Stack

Next.js (App Router) on VercelPostgres on NeonCloudflare R2 with presigned PUT URLs for headshotsResend for magic links and reminder emailStripe Checkout (one-time payment) plus webhookTailwind CSS for packet pages and dashboardVercel Cron for one daily reminder-batch job

Architecture

A single Next.js app serves three surfaces: the marketing page, the organizer dashboard behind a magic-link session cookie, and the public speaker packet page reached by a signed token in the URL. Postgres holds events, speakers, field values, reminder sends and activation status. Headshots live in R2 and are reached through short-lived signed URLs; the database stores only the object key. Stripe Checkout creates a one-time payment per event and a webhook flips events.activated_at, which gates publishing, reminders and exports. Resend sends both login links and reminder batches. No long-running workers, no queue, no per-customer infrastructure.

Build steps

  1. Scaffold Next.js app, connect Neon Postgres, define events/speakers/fields/reminders schema with migrations.
  2. Implement organizer magic-link auth: token table, Resend send, session cookie.
  3. Build event creation with slug generation and brand colour.
  4. Build speaker import: CSV header detection plus plain-text one-name-per-line fallback.
  5. Mint signed speaker tokens (HMAC with event id and speaker id) and render the packet page.
  6. Add bio character counter, session fields, AV checkboxes, travel notes, social handles.
  7. Add headshot upload via R2 presigned URL with size and MIME limits.
  8. Build the completion grid with per-field status, timestamps and filters.
  9. Build the reminder sender: template, recipient filter, per-speaker send log.
  10. Build the print-ready packet export with print CSS and the CSV export.
  11. Integrate Stripe Checkout and the activation webhook; gate paid features.
  12. Add public read-only speakers page toggle, terms, and a delete-my-event control.
  13. Deploy, run one full end-to-end test event with five real links, and fix what breaks.

AI components

  • Optional LLM call to parse messy pasted speaker lists into name/email/title rows when the delimiters are inconsistent
  • Optional LLM call to draft a reminder email variant per incomplete speaker; both are non-blocking fallbacks, and the product works with them disabled
Hardest technical risk: Headshot uploads failing or producing broken image links: presigned URL CORS, MIME and size limits, and signed-URL expiry are the most common silent failure, and a broken headshot is exactly what the product promises to fix.
Section 3 of 8

Pricing and monetization

Single Event

Entry offer
$149 one-time

For One conference, meetup or community event with up to 75 speakers

  • Unlimited speaker packet links
  • Headshot uploads and completion dashboard
  • Unlimited reminder emails
  • Print-ready speaker packet and CSV export
  • Public speakers page toggle

Season Pass

$399 one-time

For Associations, meetup chapters and agencies running several events in 12 months

  • Five event activations
  • Everything in Single Event
  • Reusable speaker roster across events

Model: One-time per-event activation, with a five-event Season Pass for repeat organizers.

First revenue offer: Free setup on a portal already seeded with your publicly listed speaker names; $149 to activate before the first reminder goes out, refunded in full if you never send a speaker link.

Expected ACV: $149

Upsell path: At activation, offer the $399 Season Pass for five events; after the event, ask for one introduction to another organizer in exchange for a free second-event credit.

Target customers
30
Revenue model
$4,470
Costs
$60
Profit model
$4,410
Section 4 of 8

First-customer acquisition

Primary channel

Cold email to named organizers of events whose call for speakers closed in the last 60 days or closes this month, each email linking to a portal pre-built from that event's publicly listed speaker names.

Where to find them

  • 'CFP closes' and 'speakers announced' posts on X and LinkedIn
  • Conference and meetup 'speakers' or 'program' pages with listed names and an organizer contact
  • Meetup.com chapter pages for English-speaking cities with upcoming events
  • Community Slack and Discord organisers who post event announcements
  • Local tech-conference lists and association event calendars

Exact outreach motions

  • Send 25 emails a day linking a live seeded portal for that event, subject line naming the event.
  • Follow up on day 3 with a screenshot of that event's 'missing headshots' view.
  • Follow up on day 7 with the print-ready speaker packet generated from their public bios.
  • DM the CFP poster on LinkedIn with the same live link when no email is published.
  • Post one build-in-public thread showing a before/after of the completion grid.
  • Ask every buyer for one introduction to another organizer for a free second-event credit.

Message template

Subject: your speaker packet page for [Event]

Hi [Name] — I built the speaker packet page for [Event] using only the speaker names already on your site: [link]

Each speaker gets their own no-login link to add bio, headshot, session abstract and AV needs. You get one screen showing who is missing what, and a print-ready pack for the MC. Nothing to install.

If it's useful, $149 activates it before your first reminder goes out, refunded if you never send a link. Want me to add the rest of your speakers?

— [Founder]
Week-one goal: 150 events listed with a named contact, 40 seeded demo portals built, 100 cold emails sent, and at least 3 replies asking for access.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 4First sale target: day 930 days planned
Week 1 · Build & validate · 7 days
Day 1Foundation

Schema and auth

  • Scaffold Next.js on Vercel and connect Neon Postgres.
  • Create events, speakers, field values and reminder-send tables.
  • Ship organizer magic-link login through Resend.
  • Deploy a stub event page to production.

Deliverable: Deployed app with working organizer login and database schema.

Day 2Packet links

Event creation and speaker import

  • Build event creation with slug and brand colour.
  • Add speaker import by CSV paste and plain-text list.
  • Mint signed no-login token per speaker.
  • Ship the packet page with bio counter, session fields and social handles.

Deliverable: Organizer can create an event and hand out live packet links.

Day 3Dashboard

Completion grid and reminders

  • Add headshot upload via presigned R2 URLs.
  • Build the per-field completion grid with timestamps.
  • Add 'missing headshot' and 'not started' filters.
  • Send one-click reminders to incomplete speakers with a send log.

Deliverable: Live completion dashboard and working reminder sender.

Day 4Revenue pathMVP shipped

Exports and payment

  • Build print-ready speaker packet export with print CSS.
  • Add full CSV export.
  • Wire Stripe Checkout and the activation webhook.
  • Add public speakers page toggle, terms and delete-my-event control.

Deliverable: Feature-complete MVP gated by a $149 Stripe Checkout.

Day 5Launch

Go live and seed pipeline

  • Run one full end-to-end test event with five real links.
  • Publish pricing page and launch post.
  • Build a list of 150 events with CFPs closed or closing in 60 days.
  • Hand-build five demo portals from publicly listed speaker names.

Deliverable: Live product, 150-event list, five seeded portals.

Day 6Outreach day 1

First cold batch

  • Send 25 emails linking seeded portals.
  • Set up a shared inbox and a one-paragraph reply template.
  • Post the launch in three organizer communities within their rules.
  • Log every reply, bounce and objection.

Deliverable: 25 emails sent and a reply log started.

Day 7Outreach day 2

Volume and follow-up

  • Send 25 more emails.
  • Follow up on day-3 non-responders with the missing-headshots screenshot.
  • Seed ten more demo portals.
  • Triage objections into a single fix list.

Deliverable: 50 emails sent total, first objection list.

Week 2 · Launch & first sale · 7 days
Day 8Reply handling

Convert interest to paid

  • Reply to every response within two hours.
  • Run any live walkthroughs offered by organizers.
  • Add the top requested small fix from the objection list.
  • Send 25 new emails.

Deliverable: All week-one replies handled, one fix shipped.

Day 9First sale pushFirst sale target

Close the warmest thread

  • Send the $149 activation offer to the three warmest organizers.
  • Offer the Season Pass at $399 on any multi-event thread.
  • Send 25 new emails.
  • Build ten more seeded portals.

Deliverable: Activation offers out on three live threads.

Day 10Proof loop

Turn one payment into evidence

  • Deliver hands-on setup for any paying organizer.
  • Capture a redacted screenshot of a real completion grid.
  • Add that screenshot to the outreach email.
  • Send 25 new emails.

Deliverable: First redacted proof asset in the outreach email.

Day 11Second channel

LinkedIn and communities

  • DM 20 CFP posters on LinkedIn with live links.
  • Answer three community threads with the packet link, not a pitch.
  • Follow up on day-7 non-responders with the generated speaker pack.
  • Send 20 new emails.

Deliverable: Second channel live with 20 DMs sent.

Day 12Pipeline review

Measure conversion

  • Compute reply rate, seeded-portal click rate and conversion by segment.
  • Cut the worst-performing segment from the list.
  • Send 25 emails to the best-performing segment.
  • Fix the top friction point in the speaker packet page.

Deliverable: Segment performance table and a pruned list.

Day 13Repeat buyers

Season Pass motion

  • Pitch Season Pass to every buyer with a chapter or association.
  • Offer a free second-event credit for one introduction.
  • Send 25 new emails.
  • Run a live demo for any organizer who asked.

Deliverable: Referral and Season Pass offers in flight.

Day 14Midpoint audit

Two-week numbers

  • Count paid activations, refunds and pending offers.
  • Rewrite the email subject line from the best reply so far.
  • Send 25 new emails with the winning subject.
  • Ship one dashboard quality fix.

Deliverable: Two-week revenue tally and revised email.

Week 3 · Repeat & systematize · 7 days
Day 15Volume

List expansion to 300

  • Add 150 more events with contacts.
  • Seed 15 new portals for the highest-value events.
  • Send 30 emails.
  • Follow up on all day-7 threads.

Deliverable: 300-event list and 30 emails sent.

Day 16Volume

Association and meetup chapters

  • Email 20 meetup chapter organisers with a multi-event angle.
  • Send 25 emails to conference organizers.
  • Post one build-in-public update with a real grid screenshot.
  • Handle all inbound replies same day.

Deliverable: 20 chapter conversations opened.

Day 17Conversion

Offer friction

  • Test a $99 first-event price on five threads to find the floor.
  • Add a one-click 'add my remaining speakers' reply action.
  • Send 25 emails.
  • Follow up on all pending activation offers.

Deliverable: Price-floor data point and faster onboarding path.

Day 18Product pull

Fix what buyers hit

  • Interview any buyer who used the product live for 15 minutes.
  • Ship the single highest-friction fix.
  • Send 25 emails.
  • Chase every unpaid activation offer.

Deliverable: One shipped fix plus a buyer interview note.

Day 19Volume

Follow-up waves

  • Send day-3 follow-ups to the whole batch.
  • Send 25 new emails.
  • Seed 10 new portals.
  • Log all objections in one place.

Deliverable: Follow-up wave complete, objections consolidated.

Day 20Third channel

Organizer communities

  • Post one concrete teardown of speaker-onboarding email threads.
  • Comment with the live link in five relevant threads.
  • Send 25 emails.
  • Reply to all inbound in under two hours.

Deliverable: Third channel live with measurable clicks.

Day 21Three-week audit

Pipeline honesty

  • Count paid activations and cash collected to date.
  • Kill the worst segment and the worst email variant.
  • Send 30 emails to the surviving segment.
  • Confirm hosting and email costs against the model.

Deliverable: Three-week tally and pruned outreach playbook.

Week 4 · Scale what works · 7 days
Day 22Close sprint

Warm threads only

  • Call every warm thread that has not paid.
  • Send 30 emails to fresh events with CFPs closing this month.
  • Offer free setup on any event closing within 14 days.
  • Handle all replies same day.

Deliverable: Every warm thread contacted by voice or direct message.

Day 23Close sprint

Urgency on dated events

  • Email events with a program going to print in December.
  • Send 30 new emails.
  • Follow up on all Season Pass offers.
  • Ship any blocker fix from a live call.

Deliverable: December-deadline segment contacted.

Day 24Referral

Buyer introductions

  • Ask every buyer for one organizer introduction.
  • Give the free second-event credit on each introduction.
  • Send 25 emails.
  • Seed 10 new portals.

Deliverable: Referral requests sent to all buyers.

Day 25Volume

List refresh

  • Add 100 newly announced events.
  • Seed 10 portals.
  • Send 30 emails.
  • Follow up on all unanswered day-3 threads.

Deliverable: Refreshed list of 400 contacts.

Day 26Polish

Delivery quality

  • Fix print layout issues reported by buyers.
  • Verify headshot signed URLs never expire mid-session.
  • Send 25 emails.
  • Answer all support within the day.

Deliverable: Print and upload reliability fixes shipped.

Day 27Close sprint

Last-week urgency

  • Send a 48-hour activation reminder to every unpaid offer.
  • Send 30 new emails.
  • Post one public result with a real activation count.
  • Handle all replies.

Deliverable: All open offers chased with a deadline.

Day 28Renewals

Season Pass

  • Offer Season Pass to every single-event buyer.
  • Offer a free second event to anyone who refers a paying organizer.
  • Send 25 emails.
  • Tally revenue, refunds and fees.

Deliverable: Renewal and referral offers out to all buyers.

Days 29-30 · Consolidate · 2 days
Day 29Final push

Close and deliver

  • Close every pending checkout.
  • Deliver setup for each paying event before the window ends.
  • Send 25 emails to events with CFPs closing in December.
  • Freeze feature work.

Deliverable: All pending payments resolved and events delivered.

Day 30Wrap

Reconcile and record

  • Reconcile collected cash, refunds, fees and ad spend.
  • Export per-event delivery records.
  • Publish a short retro with the real numbers.
  • Email every buyer a renewal note for their next event.

Deliverable: Reconciled hackathon profit figure and buyer renewal notes.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Payment processing assumed at roughly 4% blended on Stripe Checkout (2.9% + $0.30) — applied to all scenarios.
  • Conservative: 3 paid events at $149; cold email converts around 1% in the first two weeks before the email list matures.
  • Base: 10 paid events at $149; requires roughly 300 targeted emails plus follow-ups and referrals.
  • Upside: 22 paid events at an average of $154, reflecting a mix of Single Event at $149 and a few Season Passes at $399.
  • Ad spend is paid marketing only; the primary channel is organic cold email at $0.
  • Operating costs cover Vercel, Neon, R2 storage and egress, Resend sends and any optional LLM parsing calls; they are not deducted from hackathon profit but are deducted from business profit.
  • Refunds are assumed at zero in Conservative and Base because the offer includes a refund if no speaker link is ever sent; Upside carries one refunded event.
  • No chargebacks are assumed in any scenario; a first-month one-time charge with email-delivered value rarely disputes, but this is untested.
  • All figures are projections from stated assumptions, not verified revenue, customers or traction.
  • Delivery cost per active event is assumed to stay under $0.25 for storage, email and hosting at these volumes.

Conservative

3 customers
$447
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$18
Paid marketing
$0
Hackathon profit
$429
Operating costs
$15
Business profit
$414

Base case

10 customers
$1,490
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$60
Paid marketing
$0
Hackathon profit
$1,430
Operating costs
$40
Business profit
$1,390

Optimistic

22 customers
$3,388
collected revenue · avg payment $154
Refunds
$149
Chargebacks
$0
Payment fees
$142
Paid marketing
$120
Hackathon profit
$2,977
Operating costs
$95
Business profit
$2,882

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,490
Payment fees (3.9%)
$58
Paid marketing
$0
Hackathon profit
$1,432
Business profit
$1,392

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

All scenarios are projections built from stated assumptions, not verified revenue, existing customers or real traction. Actual results depend entirely on cold-email response rates during the contest window.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold email from a brand-new domain lands in spam or goes unanswered, collapsing the only acquisition channel.

Mitigation

Warm the sending domain before launch, cap at 25-30 emails per day, keep the message short and plain text, and open a second channel (LinkedIn DM to CFP posters) in week two.

Validation experiment

Send 25 emails on day 6 and measure delivered, opened and replied counts in a plain sheet.

Kill criteria

Fewer than 2 replies from 100 delivered emails by day 12 means the message or channel must change before more build continues.

Risk 2Organizers already use a form tool or a speaker-management platform and defer to their next event.

Mitigation

Lead with the live pre-built portal so the organizer sees their own speaker names in the grid, and price at $149 to stay under discretionary approval.

Validation experiment

On day 10, count how many prospects click the seeded portal link versus reply without clicking.

Kill criteria

Portal click rate below 10% across 100 emails means the seeded-portal angle is not the hook and the offer needs rewriting.

Risk 3Pre-building a portal from publicly listed speaker names reads as presumptuous and triggers complaints.

Mitigation

Use only names already published on the event's own site, never private data, and include a one-line delete-my-portal link in every email.

Validation experiment

Track complaints and opt-outs per 100 emails in the first two weeks.

Kill criteria

More than 2 complaints per 100 emails means switching to unseeded demo portals with a generic example event.

Risk 4One-time pricing produces no recurring revenue, so the 30-day number depends on Season Passes or repeat events landing inside the window.

Mitigation

Pitch the $399 Season Pass on the first call to any chapter, association or agency buyer and offer a free second-event credit for an introduction.

Validation experiment

Offer the Season Pass to the first five buyers and record accept rate.

Kill criteria

Zero Season Pass interest from ten buyers means pricing stays single-event and the revenue target is reset to the Conservative case.

Risk 5Headshot uploads or signed URLs break, and the product fails at the exact thing it promises to fix.

Mitigation

Test uploads on iOS Safari, Android Chrome and desktop before launch, cap file size and MIME types client-side, and verify signed-URL expiry covers a full session.

Validation experiment

Run a five-speaker end-to-end test event on day 5 across three devices.

Kill criteria

Any upload failure that is not fixed within one day of the first buyer hitting it stops further outreach until it is resolved.

Risk 6Refunds and chargebacks from organizers who pay but never send the links out.

Mitigation

Keep the refund promise narrow and explicit (refunded if no speaker link is ever sent), and offer free setup so activation happens before payment.

Validation experiment

Track how many buyers send their first link within 24 hours of paying.

Kill criteria

More than one refund in the first ten sales means moving to setup-first then charge.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel project, Neon database and R2 bucket.
  • Commit the initial schema migration for events, speakers and field values.

Output: Deployed skeleton with a live database connection.

Hours 3-5

  • Build organizer magic-link auth through Resend.
  • Build the event creation form with slug generation.

Output: An organizer can sign in and create an event.

Hours 6-8

  • Build speaker import from CSV paste and plain-text list.
  • Mint signed no-login packet tokens per speaker.

Output: Working packet links for a test event with five speakers.

Hours 9-11

  • Render the speaker packet page with bio counter, session fields and AV checkboxes.
  • Test the page on mobile Safari.

Output: A speaker can complete their packet on a phone.

Hours 12-14

  • Upload the first draft of the 40-event outreach list.
  • Write the cold email and the seeded-portal variant.

Output: First 10 target events with named contacts and an email draft.

Complete report

Full 30-day launch report

Read the full generated report

Speaker Packet — 30-Day Launch Report

1. Product opportunity and positioning

Speaker Packet sells to one person: the organizer who owns speaker logistics for an event of 30-300 attendees with 10-60 speakers, in the two to eight weeks after the call for speakers closes. That person is not shopping for event software. They are staring at an inbox of half-finished bio replies and a headshot folder with four files in it, three weeks before the program goes to print.

The wedge is deliberately narrow. The product is one artifact for one event: a fill-in packet page per speaker plus a completion dashboard. The organizer pastes the speaker list. The product mints one no-login link per speaker. Each speaker fills bio (with a character counter matching the program layout), headshot, session title and abstract, AV requirements, travel notes and social handles. The organizer sees a grid of who completed what and when, reminds only the incomplete speakers in one click, and exports a print-ready pack for the MC plus a CSV.

The positioning sentence against the generic alternative is the entire sale: a Google Form plus a spreadsheet tells you that someone answered; Speaker Packet tells you which speaker is missing which field, since when, and hands you a pack the MC can read the night before. It is explicitly not a blank-canvas builder, not a CFP review tool, not an agenda builder, and not a speaker-management platform with procurement attached.

The JEV score of 59.4 (band C) is honest about the weakness. Market demand at 3.91 normalized and monetization at 4.63 are the soft criteria — the pain is real but rarely budgeted, and a one-time $149 charge does not renew itself. The strong criteria are speed to first revenue (7.91) and solo build feasibility (7.57). So the plan front-loads a four-day build and spends every remaining day buying down demand risk with outreach instead of adding features. Every projected dollar comes from cold email to named organizers, so the pipeline is built on day 5, not day 25.

2. Smallest sellable MVP

The sellable unit is: create an event, paste the speaker list, get one signed link per speaker, watch a per-field completion grid, remind the incomplete speakers only, export the print-ready pack and the CSV — unlocked by a $149 Stripe Checkout. Nothing else earns money. The packet page carries bio with counter, headshot upload, session title and abstract, AV needs, travel notes and social handles. The dashboard carries status, timestamps and two filters: missing headshot, not started. Out of scope for 30 days: CFP submission forms, abstract scoring, agenda building, travel booking, video hosting, custom domains and third-party integrations.

3. Technical implementation plan

One Next.js app on Vercel with three surfaces: marketing, organizer dashboard behind a magic-link session cookie, and the public packet page reached by an HMAC-signed token in the URL. Neon Postgres holds events, speakers, field values, reminder sends and activation status. Headshots go to Cloudflare R2 through presigned PUT URLs; the database stores the object key only and reads use short-lived signed GET URLs. Resend sends login links and reminder batches. Stripe Checkout takes the one-time payment and a webhook sets the activation timestamp that gates publishing, reminders and exports. A single daily Vercel Cron job handles reminder batching. No queues, no workers, no per-customer infrastructure.

The hardest technical risk is the headshot upload — presigned URL CORS, MIME and size limits, and signed-URL expiry are the classic silent failures, and a broken headshot is precisely the promise being sold. Test on iOS Safari, Android Chrome and desktop before taking money. Optional LLM calls parse messy pasted speaker lists and draft reminder variants, both with fallbacks so the product runs with AI disabled.

4. Pricing and monetization

Single Event is $149 one-time, covering up to 75 speakers, unlimited links, unlimited reminders, both exports and the public speakers toggle. Season Pass is $399 one-time for five activations, aimed at associations, meetup chapters and agencies — this is the only way a buyer pays twice inside the window. The first offer is deliberately low-friction: free setup on a portal already seeded with that event's publicly listed speaker names, $149 to activate before the first reminder goes out, refunded in full if they never send a link. Upsell path is Season Pass at activation, then a free second-event credit for one introduction to another organizer.

5. First-customer acquisition

One channel: cold email to named organizers of events whose CFP closed in the last 60 days or closes this month, sourced from 'CFP closes' posts on X and LinkedIn and from event 'speakers' pages. For the top prospects, pre-build a portal from names already public on that event's site so the email links to something real. Message angle: 'I built your speaker packet page — each speaker fills in their own bio and headshot, you see who is missing what.' Follow up on day 3 with the missing-headshots screenshot for their event, and on day 7 with the print-ready pack generated from their public bios. Cap sending at 25-30 per day, watch the reply log, and ask every buyer for one introduction.

6. 30-day execution roadmap in phases

Days 1-4 are pure build, in dependency order: schema and auth, then event creation with signed speaker links, then the completion grid and reminder sender, then exports, Stripe and the legal minimum. Day 4 is the MVP deadline and day 9 is the first-sale target — the gap exists because outreach starts on day 6, not because the product is unfinished.

Days 5-7 are launch and first contact: ship, build the 150-event list, seed five portals, send 50 emails, log replies. Days 8-14 are the conversion sprint: handle every reply within two hours, send activation offers on the three warmest threads, replace the email with one containing a redacted real dashboard screenshot, open LinkedIn DMs as a second channel, and prune the worst-performing segment on day 12. Day 14 is the first honest revenue tally.

Days 15-21 scale volume to 300-400 contacts, add meetup chapters and associations to reach Season Pass buyers, and test a $99 first-event price on five threads to find the floor. Days 22-28 are a close sprint on dated December events: voice and direct message every warm thread, chase every unpaid offer with a 48-hour deadline, and pitch Season Pass to every single-event buyer. Days 29-30 close pending checkouts, deliver setup, reconcile cash, refunds and fees, and email renewal notes.

7. Revenue and profit scenarios

These are projections from stated assumptions, not verified revenue. Conservative: 3 events at $149, $447 gross, no refunds or chargebacks, about $18 in Stripe fees, zero ad spend, $15 operating cost. Base: 10 events at $149, $1,490 gross, $60 in fees, zero ad spend, $40 operating cost. Upside: 22 events at an average of $154 (a mix of Single Event and a few Season Passes), $3,388 gross, one $149 refund, $142 in fees, $120 of paid marketing, $95 of operating cost. Hackathon profit deducts only refunds, chargebacks, processing fees and paid marketing — hosting, domains and delivery costs are not deducted there, but they are deducted from business profit. Charges are one-time, so the base case assumes no repeat buyer lands inside the window.

8. Main risks and validation experiments

Spam placement is the top risk. Mitigation: warm the domain, cap volume, plain text only, and a LinkedIn second channel by week two. Test: 25 emails on day 6 with delivered/replied counts tracked. Kill signal: fewer than 2 replies per 100 delivered by day 12.

Switching cost is second: organizers mid-cycle defer. Test: seeded-portal click rate across 100 emails. Kill signal: below 10% clicks means the hook is wrong.

Presumption is third: a portal built from public names can annoy rather than impress. Test: opt-outs and complaints per 100 emails. Kill signal: more than 2 complaints per 100 switches to a generic example portal.

Revenue concentration is fourth: one-time pricing has no renewal. Test: offer Season Pass to the first five buyers. Kill signal: zero interest from ten buyers resets the target to the Conservative case. A fifth risk — broken headshot uploads — is contained by a five-speaker, three-device test on day 5 before any money is taken.

9. First 24-hour action plan

Hours 1-2: create Vercel project, Neon database and R2 bucket; commit the schema. Hours 3-5: magic-link auth and event creation form. Hours 6-8: speaker import and signed packet tokens. Hours 9-11: render the packet page with bio counter, session fields and AV checkboxes, tested on mobile Safari. Hours 12-14: draft the 40-event outreach list and the cold email plus seeded-portal variant. Output at hour 14 is a deployed app that can issue real speaker links and ten named targets with a message ready to send.

This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.

Related ideas

All ideas →