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

MeetMatch Digest

Turns an attendee CSV into personalized 'who to meet' digests for every attendee before a B2B event.

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.97/10
MVP build (solo)
4 days
Launch price
$299
Sales to $1,000 revenue
4 customers
First paying customer
Direct DM or email to organizers of upcoming Luma and Meetup B2B events with 50-500 attendees and a public organizer contact.
Who pays

Organizer of a paid B2B meetup or conference with 50-500 attendees, a 1-5 person team, and an event date 2-6 weeks out in an English-speaking market.

Biggest execution risk

Operational simplicity 4.3/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

Why this could work in 30 days: one founder can ship the MVP in 4 days; the plan targets a first sale on day 9; 4 sales at $299 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.4/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

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

0/14
Entry price
$299
Solo build
4 days
30d base revenue
$2,992
30d hackathon profit
$2,896
Section 1 of 8

Product opportunity and positioning

Target customer

Organizer of a paid B2B meetup or conference with 50-500 attendees, a 1-5 person team, and an event date 2-6 weeks out in an English-speaking market.

Why now

The event date is fixed and already paid for, so the organizer must close the networking gap in days; the deliverable is a one-time file, not an app install or a subscription.

Problem

Attendees arrive not knowing who to meet; the organizer has a full attendee CSV but manual matching does not scale and event apps require attendee adoption.

Solution

Organizer uploads a consented attendee CSV, reviews AI-ranked top-3 matches per attendee with rationale and icebreakers in a dashboard, then exports send-ready HTML emails, CSV and print PDF.

Differentiation · No attendee signup, no app, no social scraping, no ongoing intros. Consent flag is enforced at upload, and output is a per-person artifact the organizer can send from their own inbox.

1. Product opportunity and positioning

MeetMatch Digest sells to exactly one buyer: the organizer of a paid B2B meetup or conference with 50-500 attendees, a 1-5 person team, and an event date 2-6 weeks out. That organizer has already collected attendee data through the ticket form - name, role, company, goals, interests, seniority, consent flag. They have already promised 'networking' on the ticket page. What they do not have is a scalable way to make 200 strangers useful to each other. Spreadsheet matching costs a full day and produces a list, not a conversation. Event apps cost more, need attendee adoption, and need configuration time the organizer does not have.

The trigger is a date. That is what makes this sellable inside a 30-day window: the organizer is not evaluating a networking strategy, they are filling a gap in an event that happens whether or not they solve it. There is no procurement cycle, no security review, no integration work. The deliverable is a file they can send.

Positioning: your attendee list, turned into 200 personal 'who to meet' digests before the doors open. The real competitor is not LinkedIn or a networking app - it is the organizer's own spreadsheet and the generic 'here is the attendee list' email. MeetMatch wins because it produces a per-person artifact: top 3 matches, why each match makes sense, an icebreaker, and a forwardable intro line, generated in minutes from a CSV with zero attendee signup.

JEV scored this concept 59.7/100 (band C, confidence 0.73). Strong dimensions: speed to first revenue (8.43/10) and solo build feasibility (7.62/10). Weak dimensions: market demand (4.34), monetization (4.58) and operational simplicity (4.33). This plan attacks all three directly - narrow to organizers whose event date falls inside the contest window, attach a second purchase (next event) to every first purchase, and keep delivery stateless on managed services with no human step in the paid path.

Who this is not for: free community meetups with no budget, conferences more than 8 weeks out, and organizers who cannot supply consented attendee rows. Saying no to those keeps the funnel honest and the refund rate near zero.

Differentiation versus the generic alternative: no attendee accounts, no mobile app, no social scraping, no subscription, and a consent flag enforced at upload. The privacy objection becomes a checkbox, not a blocker.

Section 2 of 8

Smallest sellable MVP

A single-page app where an organizer uploads an attendee CSV, approves AI-generated top-3 matches per attendee, and downloads HTML email bodies plus a print PDF for the whole event.

Must-have features

  • CSV upload with column mapping and consent flag validation
  • Profile normalizer over role, company, goals, interests, seniority
  • Pair matcher combining keyword overlap and embeddings
  • LLM-generated match rationale and icebreaker per matched pair, cached per pair
  • Organizer review dashboard to approve, edit or exclude matches
  • Export of per-attendee HTML email, flat CSV and print-ready PDF
  • Stripe checkout with $299 and $499 one-time payment links
  • Sample digest generator so the founder can deliver a free 5-attendee proof

Explicitly out of scope

  • Full event app, ticketing or badge printing
  • Attendee chat, profiles or social feed
  • LinkedIn or any social media scraping
  • CRM integration or ongoing email automation
  • Marketplace of attendees or organizers
  • Mobile app in the first 30 days
  • Recurring subscription billing
  • Human concierge matching for customers

Demo flow (what the buyer sees)

  1. Founder opens /sample and uploads a 5-row demo CSV
  2. Column mapper guesses fields; consent column is validated
  3. Matcher scores all pairs and picks top 3 per attendee
  4. LLM writes rationale plus one icebreaker per pair
  5. Dashboard shows each attendee card with approve and exclude toggles
  6. Founder clicks Export and gets 5 HTML email bodies plus one PDF
  7. Buyer receives the sample email and a Stripe link for the full event
  8. After payment, the same flow runs on the full 200-row CSV and exports
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase PostgresOpenAI API (embeddings plus chat completions)Stripe Checkout and webhooksreact-pdf for print exportResend for transactional email

Architecture

A Next.js app on Vercel holds the dashboard and the public sample generator. Supabase Postgres stores events, attendees, match pairs and orders. Matching is two-stage: cheap deterministic keyword and seniority scoring narrows each attendee to ~10 candidates, then OpenAI embeddings rank those 10. Only the final 3 pairs per attendee are sent to the chat model for rationale and icebreaker, and results are cached by pair hash so reruns cost nothing. Stripe Checkout creates a one-time order; a webhook flips the event to paid and unlocks full-event export. All processing is synchronous per request with a serverless timeout budget, so there is no queue or worker to operate.

Build steps

  1. Create Next.js repo, deploy to Vercel with a Supabase project
  2. Schema: events, attendees, matches, orders, with consent boolean on attendees
  3. CSV upload with papaparse, column mapping UI and consent validation
  4. Profile normalizer producing a single text blob plus structured fields per attendee
  5. Two-stage matcher with deterministic filter then embedding cosine ranking
  6. LLM call with strict JSON schema for rationale plus icebreaker, cached by pair hash
  7. Digest renderer: HTML email template and react-pdf layout
  8. Review dashboard with approve, exclude, edit and regenerate controls
  9. Stripe Checkout for $299 and $499, webhook unlocking export
  10. Export endpoints for HTML, CSV and PDF, then a rate-limited public sample page

AI components

  • OpenAI embeddings for semantic similarity between attendee goal and interest text
  • OpenAI chat completions for match rationale, icebreaker and forwardable intro line
  • Deterministic keyword and seniority scoring as a pre-filter to cut token cost
Hardest technical risk: Matching quality on sparse profiles: attendees who give only name and company produce generic matches that make the digest look like a random pairing. Mitigation is a normalizer that flags thin profiles and a dashboard warning that excludes them rather than shipping a bad match.
Section 3 of 8

Pricing and monetization

Event Digest

Entry offer
$299 one-time

For Organizer of a B2B event up to 150 attendees

  • Per-attendee match digest
  • Top 3 matches with rationale
  • Icebreaker lines
  • HTML and CSV export

Large Event Digest

$499 one-time

For Organizer of a B2B event up to 500 attendees

  • Everything in Event Digest
  • Up to 500 attendee digests
  • Print-ready PDF export
  • Priority processing

Model: One-time per-event fee, priced by attendee volume, paid before the organizer sends the digests.

First revenue offer: Send a free 5-attendee digest for their actual upcoming event within 24 hours, then a $299 Stripe link for the full attendee list before the event date.

Expected ACV: $399

Upsell path: After the event, offer a repeat digest for their next event at the same price, then a two-event bundle at $549; each buyer is asked for one referral to another organizer.

Target customers
250
Revenue model
$99,750
Costs
$3,407
Profit model
$96,343
Section 4 of 8

First-customer acquisition

Primary channel

Direct DM or email to organizers of upcoming Luma and Meetup B2B events with 50-500 attendees and a public organizer contact.

Where to find them

  • Luma upcoming B2B events with public organizer profiles
  • Meetup groups in SaaS, fintech, AI and product categories with paid events
  • Eventbrite B2B conferences scheduled 2-6 weeks out
  • X posts from organizers announcing an upcoming event
  • Founder and event-ops Slack and Discord communities
  • Referrals from each paying organizer after their event

Exact outreach motions

  • Send a 3-line DM offering a free 5-attendee digest for their listed event
  • Attach one real sample digest built from a fictional demo CSV so they see the format
  • Offer to run it on their actual attendee rows if they reply with a consented sample
  • After delivery, send the $299 full-event link with a 48-hour founding price note
  • Follow up once after 48 hours, then stop and move on
  • After payment, ask for one intro to another organizer running an event this quarter

Message template

Hi [Name] - I saw [Event] on [date] with ~[N] attendees. I build pre-event 'who to meet' digests: each attendee gets their top 3 matches, why they fit, and an icebreaker, built from your existing CSV. I will do 5 attendees free so you can see one. Want it?
Week-one goal: 60 organizers contacted, 8 replies, 3 free sample digests delivered.
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

Repo, schema, checkout

  • Create Next.js repo and deploy to Vercel.
  • Create Supabase project with events, attendees, matches and orders tables.
  • Wire Stripe test checkout and connect the payment account to TrustMRR.

Deliverable: Deployed landing page with working test checkout.

Day 2Ingest

CSV to normalized profiles

  • Build CSV upload with column mapping UI.
  • Validate consent column and block rows without consent.
  • Normalize role, company, goals, interests, seniority into one profile object.

Deliverable: A 200-row CSV stored as normalized attendee records.

Day 3Matching

Pair scoring

  • Implement deterministic keyword and seniority pre-filter.
  • Add OpenAI embeddings and cosine ranking over the shortlist.
  • Cache results by attendee pair hash.

Deliverable: Match table populated for a 200-row test CSV.

Day 4GenerationMVP shipped

Rationale and icebreakers

  • Call the chat model with a strict JSON schema per pair.
  • Render per-attendee digest cards.
  • Flag thin profiles and exclude them from output.

Deliverable: End-to-end MVP run on a full test CSV.

Day 5Export

Deliverables organizers can send

  • Build HTML email template per attendee.
  • Build react-pdf print export.
  • Add CSV export of all matches.

Deliverable: Three export formats working from the dashboard.

Day 6Proof asset

Sample generator

  • Publish a public /sample page with a 5-row demo CSV.
  • Generate three example digests for the outreach sheet.
  • Add a Stripe link at the end of each sample.

Deliverable: Shareable sample digest page and PDF.

Day 7Outreach start

First 20 messages

  • Build a 60-row list of upcoming Luma and Meetup B2B events with organizer contacts.
  • Send the first 20 messages with the free 5-attendee offer.
  • Log every send in a sheet with event date and attendee count.

Deliverable: 60-row target list and 20 logged sends.

Week 2 · Launch & first sale · 7 days
Day 8Outreach volume

Second wave and follow-ups

  • Send 20 more messages.
  • Follow up on day-7 non-replies once.
  • Reply within two hours to every response.

Deliverable: 40 total sends, at least 5 replies.

Day 9First saleFirst sale target

Sample delivery to payment

  • Deliver free samples within 24 hours of each yes.
  • Attach the $299 full-event link in the sample email.
  • Close the first paid event.

Deliverable: First paid order and first delivered full-event digest.

Day 10Friction removal

Conversion path

  • Fix the top two issues seen in sample delivery.
  • Add one-click 'run full event' from the sample page.
  • Add a dashboard status email for paid orders.

Deliverable: Sample-to-checkout path with no manual steps.

Day 11Outreach volume

Third wave

  • Send 20 more messages.
  • Post the sample in two founder or event-ops communities without spamming.
  • Track reply rate per segment.

Deliverable: 60 total sends and a segment reply table.

Day 12Follow-up

Recover stalled threads

  • Follow up on all unanswered threads once.
  • Ask every replier for one organizer intro.
  • Deliver any outstanding free samples.

Deliverable: 10 follow-ups sent, 2 referral names captured.

Day 13Tier two

Larger events

  • Enable the $499 Large Event tier.
  • Add print PDF to the large tier output.
  • Test the flow on a 400-row synthetic CSV.

Deliverable: Second price tier live and load-tested.

Day 14Week review

Message rewrite

  • Compute reply rate and sample-to-paid rate.
  • Rewrite the outreach message around the best-performing angle.
  • Cut segments with zero replies.

Deliverable: Revised message and a metrics sheet.

Week 3 · Repeat & systematize · 7 days
Day 15Scale outreach

25 sends per day

  • Send 25 messages.
  • Add 30 new targets to the list.
  • Deliver samples same day.

Deliverable: 25 sends and updated target list.

Day 16Scale outreach

25 sends per day

  • Send 25 messages.
  • Follow up on day-15 threads.
  • Ship any dashboard bug reported by buyers.

Deliverable: 50 sends in the week.

Day 17Proof

Testimonials

  • Ask each paying organizer for two sentences of feedback.
  • Publish anonymized before-and-after on the landing page.
  • Add the quote to the outreach message.

Deliverable: Two usable testimonials on the site.

Day 18Scale outreach

25 sends per day

  • Send 25 messages.
  • Target organizers with events in the final week of the contest window.
  • Log replies within the hour.

Deliverable: 75 total sends in week three.

Day 19Delivery quality

Match review

  • Manually audit 20 generated digests for weak matches.
  • Tune the embedding prompt and pre-filter weights.
  • Add an 'exclude attendee' toggle default for thin profiles.

Deliverable: Audited sample with documented tuning changes.

Day 20Scale outreach

25 sends per day

  • Send 25 messages.
  • Follow up on all prior threads once.
  • Record every objection verbatim.

Deliverable: Objection log with at least 8 entries.

Day 21Week review

Cohort numbers

  • Compute cumulative sends, replies, samples, paid orders.
  • Kill the worst-performing segment.
  • Decide whether to add a second channel.

Deliverable: Cohort dashboard and a go or no-go note.

Week 4 · Scale what works · 7 days
Day 22Repeat revenue

Second event offer

  • Email every past buyer with a repeat digest offer for their next event.
  • Offer a two-event bundle at $549.
  • Add repeat purchase tracking to the orders table.

Deliverable: Repeat offer sent to all buyers.

Day 23Scale outreach

25 sends per day

  • Send 25 messages.
  • Use the strongest testimonial in the opener.
  • Add 20 new targets.

Deliverable: 100 cumulative sends in week four.

Day 24Referrals

Organizer to organizer

  • Ask each buyer for one named intro.
  • Send a 2-line forwardable blurb they can reuse.
  • Follow up on named intros within 24 hours.

Deliverable: Three warm intros requested.

Day 25Scale outreach

25 sends per day

  • Send 25 messages.
  • Follow up on all open threads.
  • Deliver every pending sample same day.

Deliverable: 125 total sends in week four.

Day 26Trust

Objection handling

  • Publish a short consent and data-handling page.
  • Add a one-line data deletion promise with 24-hour turnaround.
  • Put the consent requirement in the pricing page copy.

Deliverable: Live data handling page linked from checkout.

Day 27Scale outreach

Final wave

  • Send 25 messages to events happening before day 30.
  • Follow up on every unanswered thread.
  • Prioritize organizers with events inside the contest window.

Deliverable: 150 total sends in week four.

Day 28Week review

Close pipeline

  • List every warm thread and rank by likelihood.
  • Send a closing note with a same-day delivery promise.
  • Remove anything that cannot close by day 30.

Deliverable: Ranked close list of at most 10 threads.

Days 29-30 · Consolidate · 2 days
Day 29Closing

Convert remaining threads

  • Work the ranked close list all day.
  • Deliver any paid event within 24 hours.
  • Confirm every payment landed in the TrustMRR-connected account.

Deliverable: All pending orders paid or explicitly lost.

Day 30Wrap

Reconcile and handoff

  • Reconcile Stripe totals against TrustMRR before the 13:00 UTC cutoff.
  • Export the full customer and delivery log.
  • Write the one-page retro with what to sell next month.

Deliverable: Reconciled revenue record and retro note.

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

  • All figures are projections from stated assumptions, not verified revenue or existing customers.
  • Conservative case: 3 paid events at a blended $349 ARPU, weighted toward the $299 tier.
  • Base case: 8 paid events at a blended $374 ARPU, a mix of $299 and $499 tiers.
  • Upside case: 20 paid events at a blended $399 ARPU driven by a mix skewed to $499.
  • Payment processing assumed at Stripe 2.9% plus $0.30, about 3.2% of collected revenue on these ticket sizes.
  • Refunds are 0 in Conservative and Base because delivery is manual and checked before export; Upside assumes one refunded $299 event.
  • No chargebacks assumed in any scenario; the product is delivered before the event date.
  • Ad spend is 0 in all scenarios because acquisition is organic DM and email only.
  • Operating costs cover Vercel, Supabase, OpenAI tokens and email at roughly $6-10 per delivered event plus about $15 fixed tooling.
  • Each sale must cover delivery cost: worst-case delivery is under $10 against a $299 minimum price.
  • Hackathon profit excludes hosting and AI delivery cost by rule; business profit deducts operating costs.

Conservative

3 customers
$1,047
collected revenue · avg payment $349
Refunds
$0
Chargebacks
$0
Payment fees
$34
Paid marketing
$0
Hackathon profit
$1,013
Operating costs
$30
Business profit
$983

Base case

8 customers
$2,992
collected revenue · avg payment $374
Refunds
$0
Chargebacks
$0
Payment fees
$96
Paid marketing
$0
Hackathon profit
$2,896
Operating costs
$78
Business profit
$2,818

Optimistic

20 customers
$7,980
collected revenue · avg payment $399
Refunds
$299
Chargebacks
$0
Payment fees
$255
Paid marketing
$0
Hackathon profit
$7,426
Operating costs
$190
Business profit
$7,236

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,392
Payment fees (3.9%)
$93
Paid marketing
$0
Hackathon profit
$2,299
Business profit
$2,221

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.

Scenario models from stated assumptions, not verified revenue. No customers, partnerships or traction are claimed.

Section 7 of 8

Main risks and validation experiments

Risk 1Organizers refuse to share attendee data over privacy or consent concerns.

Mitigation

Enforce a consent flag at upload, publish a data-handling page, and promise deletion within 24 hours of delivery.

Validation experiment

Send 20 messages to organizers and count how many reply with data or ask a consent question versus ignore entirely.

Kill criteria

Fewer than 2 of 20 reply with any attendee rows after 40 messages sent.

Risk 2Outreach on Luma and Meetup is ignored or read as spam.

Mitigation

Lead with a finished sample digest for their actual event, keep messages to three lines, and send from a personal address.

Validation experiment

Track reply rate on the first 40 sends; if under 8%, rewrite the opener around the event date.

Kill criteria

Reply rate under 5% after 100 sends with two different openers.

Risk 3Matching quality is weak on sparse profiles and buyers refund or do not send the digests.

Mitigation

Flag thin profiles, exclude them by default, and let the organizer edit any match before export.

Validation experiment

Audit 20 generated digests from the first two free samples against organizer judgment.

Kill criteria

More than 30% of matches judged unusable by two different organizers.

Risk 4Volume target of 250 sales in 30 days is unreachable for a solo founder.

Mitigation

Plan and rank on the 8-sale base case; treat higher volume as upside, not the plan.

Validation experiment

Compare actual paid orders on day 14 to the base-case pace of 4.

Kill criteria

Zero paid orders by day 16 after 120 sends and 6 delivered samples.

Risk 5Organizers say an existing event app already covers networking.

Mitigation

Position against the attendee list email, not the app, and offer the digest as a pre-event layer the app does not do.

Validation experiment

Ask five organizers what they currently send attendees before the event and log the answer verbatim.

Kill criteria

All five name a tool that already produces per-attendee matches they are happy with.

Risk 6Payment or TrustMRR setup delays the first sale.

Mitigation

Complete account connection on day 1 and run a live $1 test charge before any outreach.

Validation experiment

Take one live test payment on day 1 and confirm it appears in the connected account.

Kill criteria

Payments still not landing in the connected account by day 3.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and deploy an empty page to Vercel.
  • Create the Supabase project and write the five-table schema.
  • Connect the Stripe payment account to TrustMRR and confirm the link.

Output: Live URL, schema file, connected payment account.

Hours 3-5

  • Build CSV upload with a column mapper.
  • Add consent column validation and row-level rejection.
  • Write the profile normalizer.

Output: Working upload that turns a CSV into normalized attendee records.

Hours 6-8

  • Implement the deterministic shortlist matcher.
  • Add OpenAI embeddings and cosine ranking on the shortlist.
  • Run it against a 50-row synthetic CSV.

Output: Scored match pairs for a test event.

Hours 9-10

  • Generate rationale and icebreaker with a strict JSON schema.
  • Render one attendee digest card in the dashboard.

Output: One readable digest card end to end.

Hours 11-12

  • Draft the 60-row outreach list of upcoming Luma and Meetup B2B events.
  • Write and queue the first 10 messages.
  • Set the next-day task list.

Output: Outreach list started and 10 messages ready to send.

Complete report

Full 30-day launch report

Read the full generated report

MeetMatch Digest - 30-Day Launch Plan

Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. Solo founder. Every revenue figure in this document is a projection, not verified revenue, and no customers or partnerships are claimed.

1. Product opportunity and positioning

The buyer is the organizer of a paid B2B meetup or conference with 50-500 attendees, a team of one to five people, and an event 2-6 weeks away. They already collected attendee data through the ticket form. They already promised networking on the ticket page. What they do not have is any scalable way to make 200 strangers useful to each other. Spreadsheet matching costs a full day and produces a list, not a conversation. Event apps need attendee adoption and configuration time the organizer does not have.

The trigger is a date. That is what makes the concept sellable inside 30 days: the organizer is not evaluating a networking strategy, they are filling a gap in an event that happens regardless. There is no procurement, no security review, no integration. The deliverable is a file they send from their own inbox.

Positioning: your attendee list, turned into personalized 'who to meet' digests before the doors open. The real competitor is the organizer's own spreadsheet and the generic attendee-list email. MeetMatch wins because it produces a per-person artifact - top 3 matches, why each fits, an icebreaker, a forwardable intro line - in minutes, from a CSV, with zero attendee signup.

JEV scored this concept 59.7/100 (band C, confidence 0.73). Speed to first revenue (8.43) and solo build feasibility (7.62) carry it. Market demand (4.34), monetization (4.58) and operational simplicity (4.33) drag it. This plan attacks those three: narrow to events inside the contest window, attach a repeat purchase to every first purchase, and keep delivery stateless on managed services.

2. Smallest sellable MVP

One page, one CSV, one export. The organizer uploads attendee rows, the app normalizes five fields plus a consent flag, ranks pairs, and shows each attendee with their top 3 matches, a rationale and an icebreaker. The organizer excludes anyone who looks wrong, then exports HTML email bodies, a flat CSV and a print PDF.

Deliberately excluded: event app, ticketing, chat, social scraping, CRM sync, recurring billing, mobile app, and human concierge matching. Each of those adds days and none of them is required for a first $299 payment.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres, OpenAI for embeddings and generation, Stripe Checkout, react-pdf for print, Resend for delivery email.

Matching runs in two stages so cost stays near zero. A deterministic keyword and seniority filter cuts each attendee to about ten candidates. Embeddings rank those ten. Only the top three pairs per attendee reach the chat model, and every generation is cached by pair hash so reruns are free. Everything is synchronous per request inside serverless timeouts: no queue, no worker, no database of record to babysit.

The hardest risk is sparse profiles. An attendee who gives only a name and company produces a match that looks random, and a bad digest kills word of mouth. Mitigation is a normalizer that scores profile completeness, a dashboard warning, and default exclusion of thin rows.

4. Pricing and monetization

Two one-time tiers: $299 for events up to 150 attendees, $499 up to 500 with print PDF and priority processing. Blended target ARPU is $399. Payment is collected before the organizer sends anything, which removes collection risk.

Revenue grows by repeat, not by subscription. After delivery, every buyer gets an offer for their next event and a two-event bundle at $549. Every buyer is asked for one named intro to another organizer. A one-time charge is the right shape here: the buyer's need is episodic and the alternative - a monthly networking subscription - is exactly the vitamin problem the original Weave ran into.

5. First-customer acquisition

Only one channel for 30 days: direct DM and email to organizers of upcoming Luma and Meetup B2B events with a public contact and 50-500 attendees.

The offer is not a demo. It is a finished 5-attendee digest for their actual event, delivered within 24 hours, followed by a $299 link for the full list. Three lines in the message, one attachment, no calendar link. Follow up once after 48 hours, then stop.

Week one goal: 60 organizers contacted, 8 replies, 3 free samples delivered.

6. 30-day execution roadmap

Days 1-5 build: repo, schema, checkout, CSV ingest, matcher, generation, exports. Days 6-7 ship the public sample page and a 60-row target list, send the first 20 messages. Day 8 second wave. Day 9 target for the first paid order. Days 10-14 remove friction, enable the $499 tier, follow up, rewrite the message from real reply data. Days 15-21 scale to 25 sends per day, collect two testimonials, audit match quality, log objections verbatim. Days 22-28 push repeat offers, referrals, a data-handling page, and a final wave targeted at events happening before day 30. Days 29-30 close ranked threads, deliver, reconcile Stripe against the TrustMRR-connected account before the 13:00 UTC cutoff, and write the retro.

7. Revenue and profit scenarios

Projections only.

Conservative: 3 events at $349 blended ARPU, $1,047 gross, $34 processing, no refunds, no ad spend, $30 operating. Base: 8 events at $374, $2,992 gross, $96 processing, $78 operating. Upside: 20 events at $399, $7,980 gross, one $299 refund, $255 processing, $190 operating.

Hackathon profit ignores hosting and AI cost by rule. Business profit subtracts operating cost, which stays under $10 per delivered event against a $299 floor, so no sale is ever below cost. Refunds are held at zero in two of three scenarios because the founder verifies the digest before the organizer sends it; the upside case carries one refund as a hedge.

8. Main risks and validation experiments

Privacy and consent refusal is risk one: enforce the flag at upload, publish a data-handling page, delete data 24 hours after delivery. Test it in the first 20 messages and count who shares rows.

Outreach being ignored is risk two: track reply rate on the first 40 sends, rewrite the opener around the event date if it falls under 8%.

Weak matches are risk three: audit 20 digests from the first two samples against organizer judgment; if more than 30% are judged unusable, retune before scaling.

Volume is risk four: the plan is paced on the 8-sale base case, not the 250-sale figure in the concept math. Zero paid orders by day 16 after 120 sends and 6 samples is the stop signal.

Payment plumbing is risk five: connect the account on day 1 and take one live test charge before any outreach.

9. First 24-hour action plan

Hours 1-2: repo, Supabase schema, Stripe connected to TrustMRR, live empty page. Hours 3-5: CSV upload, column mapping, consent validation, normalizer. Hours 6-8: deterministic shortlist plus embeddings on a 50-row synthetic CSV. Hours 9-10: LLM rationale and icebreaker rendered as one digest card. Hours 11-12: start the 60-row outreach list and queue the first 10 messages.

By the end of day one the founder has a deployed shell, a working payment account, and a matcher that produces one readable digest. That is the shortest path to the day-9 first sale.

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 →