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

Mutual Yes

A QR check-in and post-event match-report tool for speed-dating and singles-mixer hosts: guests tap who they liked, and every guest gets an email with only their mutual matches minutes after the event ends.

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.

Promising6.72/10
MVP build (solo)
4 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Cold email and Instagram DM to named organizers of publicly listed speed-dating and singles-mixer events dated between 20 November and 15 December, sourced from public event listings in ten metros.
Who pays

Owner-operator of an independent speed-dating or singles-mixer business (1-3 people) running 1-8 events a month with 20-120 guests in the US, Canada or the UK.

Biggest execution risk

Operational simplicity 4.6/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 10; 26 sales at $39 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/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

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

0/13
Entry price
$39
Solo build
4 days
30d base revenue
$780
30d hackathon profit
$706
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of an independent speed-dating or singles-mixer business (1-3 people) running 1-8 events a month with 20-120 guests in the US, Canada or the UK.

Why now

Holiday singles parties and year-end mixers cluster between 20 November and 15 December, QR scanning is native to every phone camera, and managed hosting, database and email keep delivery cost near zero.

Problem

After every event the host spends 1-3 late-night hours transcribing paper scorecards into a spreadsheet to find two-way matches, and gets it wrong often enough that guests do not rebook.

Solution

Host creates an event and pastes the guest list, prints a QR poster for the door, guests tap their name and later tap yes/no on people they met, and the host clicks one button to email each guest only their two-way matches plus a summary CSV.

Differentiation · It is a host-side reporting utility priced per event, not a consumer dating app: no profiles, photos, chat or GPS, and because only two-way yeses are ever revealed, no guest learns a one-way result.

Mutual Yes - 30-Day Public Report

Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. One founder, no team, no ad budget, revenue through a TrustMRR-connected Stripe account created before the first sale. JEV scored this concept 67.2/100 (band B). Speed to first revenue is the strongest criterion (8.34); operational simplicity is the weakest (4.63). The plan below is shaped by that split: sell within ten days, and keep the machine deliberately boring.

1. Product opportunity and positioning

The buyer is the owner-operator of an independent speed-dating or singles-mixer business: one to three people, one to eight events a month, twenty to one hundred and twenty guests per event, based in the US, Canada or UK. The trigger is concrete. They open registration for the next event and remember they will be hand-matching paper scorecards at midnight on a Friday.

That work is one to three hours of spreadsheet labour: collect cards, transcribe names, cross-reference, then email people one at a time. Errors are common and commercially expensive, because a guest who receives a late, wrong or empty result does not rebook. The host also carries a quiet consent problem: there is no defensible record of who agreed to be contacted.

Mutual Yes is not a dating app. It is a post-event reporting tool for the person who already assembles the crowd. The original location-based product died of cold start: it needed local density it could never bootstrap. The host has density by definition, has a dated recurring pain, and is individually findable by name on public event listings.

Why now: holiday singles parties cluster between 20 November and 15 December, inside the window. Every phone camera reads QR codes natively, so guest onboarding needs no app install and no app-store review. Managed hosting, database and transactional email keep delivery cost under $70 for the month at this volume.

Differentiation: ticketing platforms and dating apps sell guest-facing software. Nobody sells the two-way-only debrief as a $39 per-event utility. The mutual-only reveal is the product's core privacy guarantee, not a marketing line - no guest ever learns a one-way result and the host never has to adjudicate an awkward match.

2. Smallest sellable MVP

One host, one event, one artifact: a QR poster on the door and a per-guest email of mutual matches after the event. Everything else is deferred.

In scope: host magic-link login, event creation with name and date, guest list paste or CSV import (first name, last initial, email), a downloadable QR poster PNG, a public check-in page where a guest taps their name with no account, a post-event tap screen where each guest marks yes or no on the roster entries the host flagged as met, a deterministic two-way match engine that never surfaces one-way answers, a one-click debrief send through Resend, and a host summary CSV.

Out of scope for the full 30 days: native apps, profiles and photos, in-app chat, GPS, ranking or who-liked-you teasers, white-label branding, custom domains, SMS delivery, and multi-staff seats. Each of those would add weeks and none of them is required to collect the first $39.

3. Technical implementation plan

Next.js deployed on Vercel, Supabase Postgres with magic-link auth for hosts only, Resend for debrief emails, Stripe Checkout plus webhooks for credits, and the qrcode library for the poster. No LLM is involved: matching is a set intersection, which is cheaper and more auditable than inference.

Data model: hosts, events (status, host id, date, credit id), guests (event id, display name, email, checked_in_at), answers (event id, from guest, to guest, value), and matches derived at send time, never stored as a public record. Row-level security scopes every host query to their own events. Guest pages use an unguessable event slug plus a signed cookie so one phone stays attached to one guest.

Build order: scaffold and auth, then event creation and guest import, then QR poster, then guest check-in, then the tap screen and match engine, then Resend debrief and CSV, then Stripe gating, then a full seeded dry run on a real phone.

Hardest technical risk is email deliverability and timing on event night: the debrief must land within minutes of the host's click without tripping spam filters. Mitigation is a warmed sending domain with SPF, DKIM and DMARC set on day 6, plain-text-shaped HTML, a single link, and a manual resend button. Second risk is guests abandoning a long roster: mitigation is a name search box and a two-tap flow.

4. Pricing and monetization

Event Pass at $39 one-time (one event, up to 80 guests, QR poster, debrief email, summary CSV). Host Pro at $99 per month (unlimited events, three concurrent, custom sender name, match-rate summary). Studio at $299 per month (ten concurrent events, branded email header, all-event CSV, priority email support). Stripe Checkout, gated at event creation so no work happens before payment.

The first-revenue offer is deliberately small: $39 for this event, first five hosts only. The subscription is sold at the second event, not the first. Blended first-payment value used in the projections is $65 to $99 depending on mix.

5. First-customer acquisition

One channel: cold email and Instagram DM to named organizers of publicly listed singles events happening between 20 November and 15 December, sourced from public listings in ten metros. No ads, no partnerships, no marketplace.

The message is three lines, quotes their event name and date, and closes with a price. The 40-second screen recording of a real debrief email arriving in an inbox is the pitch artifact, attached or linked in the first message. Follow-ups on day 2 and day 5 are one line: is your event on that date still running? Week-one goal: 55 messages sent, at least 3 live conversations, first payment by day 10.

6. 30-day execution roadmap

Days 1-5 build the product to a paid, deployed v1. Days 6-7 build the prospect list of 60 events, warm the sending domain and record the demo. Days 8-14 are the first sale plus first live event support. Days 15-21 add a pilot testimonial loop, ship the search box and CSV export, and run a funnel review. Days 22-28 push volume, close subscription conversions, and add the Studio tier page. Days 29-30 handle late events and reconcile every dollar before the 13:00 UTC cutoff. The full day-by-day task list is in the roadmap object.

7. Revenue and profit scenarios

Three projections, all hypotheses. Conservative: 4 customers at a $49 blended first payment, $196 gross, no refunds, $9 in processing fees, $30 operating cost. Base: 12 customers at $65 blended, $780 gross, $39 refunds, $35 fees, $55 operating. Upside: 30 customers at $99 blended, $2,970 gross, $99 refunds, $134 fees, $90 paid marketing, $95 operating. Processing is modelled at 4.5 percent (Stripe standard plus international cards). Hosting, database, email and domain are the only operating lines. None of these are verified revenue, customers or traction - they are arithmetic from stated assumptions.

8. Risks and validation experiments

Event-timing slip is the biggest one: a host who buys in December may run their event after the cutoff, so prioritise events dated 20 November to 15 December. Thin guest participation is second: measure tap-through at the first live event and add a name search if it falls below 50 percent. Consent and privacy is third: keep the mutual-only reveal, add an opt-out line in every debrief email, and let guests self-add rather than only appear from a host list. Cancellations drive refunds, which cut profit directly, so offer credit toward a future event before refunding. Deliverability and evening support are handled by a warmed domain and a single stated support window.

9. First 24-hour action plan

Hours 1-2: create the Stripe account and connect it to TrustMRR, register the domain, open the Vercel and Supabase projects. Hours 3-5: ship the schema and magic-link host auth. Hours 6-8: build event creation and guest-list paste. Hours 9-11: build the QR poster generator and verify a real print at 100 percent scale. Hours 12-14: build the guest check-in page and test it on two phones. Hours 15-18: build the tap screen and match engine, run a six-guest simulation, and confirm that a one-way yes never appears anywhere in any email or export.

Disclaimer

All revenue, profit and customer figures in this report are forward-looking projections built from the stated assumptions. They are not verified revenue, existing customers, traction or partnerships.

Section 2 of 8

Smallest sellable MVP

A host pays $39, pastes a guest list, prints a QR poster, and minutes after the event every guest receives an email containing only their mutual matches.

Must-have features

  • Host magic-link signup and event creation with name, date and city
  • Guest list paste or CSV import using first name, last initial and email
  • Downloadable QR door poster PNG with a unique event code
  • Guest check-in page: tap your name from the roster, no account, no install
  • Post-event yes/no tap screen against the roster entries the host flagged as met
  • Two-way match engine that stores one-way answers privately and never reveals them
  • One-click debrief send via Resend with per-guest mutual matches and contact details
  • Host summary CSV with match counts per guest
  • Stripe Checkout for the $39 event credit and $99 monthly plan, gated at event creation

Explicitly out of scope

  • Native iOS or Android app and any app-store submission
  • Photos, bios, self-descriptions or public profiles
  • In-app chat or messaging between guests
  • GPS or any live location feature
  • Ranking, recommendations or who-liked-you teasers
  • White-label branding, custom domains or SMS delivery
  • Multi-staff seats, roles or permissions
  • Any LLM or third-party data enrichment

Demo flow (what the buyer sees)

  1. Founder opens the dashboard and creates a test event dated tomorrow.
  2. Pastes six guest rows into the importer and downloads the QR poster.
  3. Scans the poster with a phone and taps a name on the check-in page.
  4. Marks the host-flagged roster entries as yes or no.
  5. Switches to a second guest, marks the first guest yes, and submits.
  6. Clicks Send Debrief and the first guest inbox receives only the mutual match.
  7. Downloads the host summary CSV showing one match across six guests.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres with row-level securitySupabase magic-link auth for hostsResend for transactional debrief emailsStripe Checkout and webhooksqrcode library for poster generationTailwind CSSNamecheap or Cloudflare domain

Architecture

A single Next.js app serves three surfaces: an authenticated host dashboard, a public guest page at an unguessable event slug, and a webhook endpoint for Stripe. Supabase Postgres stores hosts, events, guests and raw answers; matches are computed at send time by intersecting answers, so a one-way yes is never written to any outbound payload. A signed cookie binds a phone to one guest record so a guest cannot vote as someone else. Resend sends one email per guest when the host clicks send. Vercel runs everything serverless; there is no queue, no worker and no human in the loop.

Build steps

  1. Scaffold the Next.js app, deploy to Vercel, create the Supabase project and push the schema.
  2. Add magic-link auth and an empty protected dashboard shell.
  3. Build event creation and the guest list paste/CSV importer with email validation.
  4. Generate the event slug and a downloadable QR poster PNG at 100 percent print scale.
  5. Build the public check-in page with a roster tap list, a name search field and a self-add fallback.
  6. Build the post-event tap screen limited to roster entries the host marked as met.
  7. Implement the two-way match engine and assert in code that no one-way answer can be serialised into an email or CSV.
  8. Wire Resend with a debrief template, a resend button and a delivery log.
  9. Add Stripe Checkout, webhook credit granting and gating at event creation.
  10. Run a six-guest end-to-end test on two real phones against production.
  11. Deploy v1 publicly, set SPF, DKIM and DMARC on the sending domain, and warm it with low-volume sends.

AI components

  • None. Matching is a deterministic two-way set intersection, which is cheaper, faster and auditable.
Hardest technical risk: Debrief email deliverability and timing on event night: the send must land within minutes of the host click without tripping spam filters, so the sending domain is warmed from day 6 and every email is a single plain-shaped message with one link and a manual resend.
Section 3 of 8

Pricing and monetization

Event Pass

Entry offer
$39 one-time

For Independent organizer running a single event inside the next 30 days

  • One event with up to 80 guests
  • QR door poster PNG
  • Per-guest mutual-match debrief email
  • Host summary CSV

Host Pro

$99 / month

For Organizer running 2-8 events per month

  • Unlimited events
  • Up to 3 concurrent events
  • Custom sender name on the debrief email
  • Match-rate summary per event

Studio

$299 / month

For Multi-city singles event operator

  • Up to 10 concurrent events
  • Branded debrief email header
  • CSV export of all events
  • Priority email support

Model: Per-event credit for the first purchase, monthly subscription at the second event, with Stripe Checkout gating event creation.

First revenue offer: You are running [event] on [date]. I built a QR check-in that emails every guest only their mutual matches about ten minutes after the event ends, so you do not rebuild the spreadsheet at midnight. $39 for this event, first five hosts only.

Expected ACV: $78

Upsell path: Event Pass buyers are offered Host Pro at $99 per month when they open their second event, and Studio at $299 when they run events in more than one city or exceed three concurrent events.

Target customers
30
Revenue model
$2,970
Costs
$70
Profit model
$2,900
Section 4 of 8

First-customer acquisition

Primary channel

Cold email and Instagram DM to named organizers of publicly listed speed-dating and singles-mixer events dated between 20 November and 15 December, sourced from public event listings in ten metros.

Where to find them

  • Public event listings for speed-dating and singles-mixer nights in 10 US, Canadian and UK metros
  • Meetup and Eventbrite public event pages for singles mixer organizers
  • Instagram accounts of independent singles-event brands with upcoming dated posts
  • Public holiday singles-party listings dated 20 November to 15 December

Exact outreach motions

  • Send 25 personalised emails on day 7 quoting the event name and date and linking a 40-second demo recording.
  • DM 10 organizers on Instagram whose public posts show an upcoming dated event.
  • Follow up on day 2 and day 5 with a one-line check on whether the event date is still running.
  • Send 30 more messages on day 9 targeting organizers with events dated 1-15 December.
  • Offer a free pilot event to three organizers in exchange for a 60-second video testimonial.
  • Ask every paying host for permission to name their event in future outreach.

Message template

Hi [name], you are running [event] on [date] in [city]. I built a QR check-in that emails every guest only their mutual matches about ten minutes after the event ends, so you do not rebuild the spreadsheet at midnight. 40-second demo: [link]. $39 for this event, first five hosts only. Want the poster for your door?
Week-one goal: 60 qualified organizer prospects listed, 55 personalised messages sent, at least 3 live conversations, and the paid v1 deployed and accepting payments by day 5.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 5First sale target: day 1030 days planned
Week 1 · Build & validate · 7 days
Day 1Scaffold

Deployable app with auth and schema

  • Create the Next.js app, Supabase project and Vercel deployment.
  • Push tables: hosts, events, guests, answers.
  • Add host magic-link auth and a protected dashboard shell.

Deliverable: Live skeleton URL with working host login.

Day 2Event setup

Host can create an event and print a poster

  • Build the event create form with name, date, city and guest cap.
  • Add guest list paste parser and CSV upload with email validation.
  • Generate the event slug and a downloadable QR poster PNG.

Deliverable: A created event with a printable QR poster.

Day 3Guest check-in

Zero-friction guest entry

  • Build the public check-in page listing roster names for tap-to-claim.
  • Add a name search field and a self-add fallback for unlisted guests.
  • Bind a phone to one guest with a signed cookie.

Deliverable: Guest scans the poster, taps a name, sees a confirmation screen.

Day 4Matching and debrief

The artifact the buyer pays for

  • Build the post-event yes/no tap screen over host-flagged roster entries.
  • Implement the two-way match engine and block one-way answers from any outbound payload.
  • Wire the Resend debrief email and the host summary CSV.

Deliverable: End-to-end run with a mutual match email received in an inbox.

Day 5Paywall and dry runMVP shipped

Paid, public v1

  • Add Stripe Checkout for the $39 credit and $99 monthly plan with webhook credit granting.
  • Gate event creation behind a credit and test the refund path manually.
  • Run a six-guest dry run on two real phones against production.

Deliverable: Public v1 at the product domain with the paywall enforced.

Day 6Outreach assets

List, domain warm, demo video

  • Build a 60-row prospect sheet of listed singles events in 10 metros with organizer name, date and contact route.
  • Set SPF, DKIM and DMARC and warm the sending domain with low-volume sends.
  • Record a 40-second screen capture of a debrief email arriving.

Deliverable: Prospect sheet, warmed domain and a 40-second demo clip.

Day 7First outreach

Open 25 conversations

  • Send 25 personalised messages quoting event name, date and city.
  • Post once in three organizer communities where self-promotion is allowed.
  • Log every send with status and follow-up date.

Deliverable: 25 messages sent and a live reply tracker.

Week 2 · Launch & first sale · 7 days
Day 8Second wave

Volume plus follow-up

  • Follow up on day-2 non-replies with a one-line question.
  • Send 30 new messages to organizers with events dated 1-15 December.
  • Send the demo clip to every warm replier.

Deliverable: 55 total messages out and at least 3 open conversations.

Day 9Objection handling

Turn conversations into checkout links

  • Answer privacy questions with the mutual-only guarantee in one sentence.
  • Send Stripe checkout links to every interested host.
  • DM 10 organizers on Instagram with dated public event posts.

Deliverable: At least 3 checkout links delivered to named hosts.

Day 10First saleFirst sale target

Collect the first $39

  • Close the warmest host on a live call or DM thread.
  • Set up their real event and generate the poster during the call.
  • Confirm payment reached the TrustMRR-connected account.

Deliverable: First payment collected and a real event configured.

Day 11Onboarding

Make the first host succeed

  • Send the host a one-page runbook for door and debrief timing.
  • Import and verify their full guest list.
  • Test the guest flow on the host's own phone.

Deliverable: Host-confirmed event ready for the night.

Day 12Live event night

Run the first real event

  • Monitor check-in count during the event window.
  • Be reachable 18:00-22:00 for that one event only.
  • Send the debrief on the host's go-ahead and confirm delivery.

Deliverable: First real mutual-match debrief delivered to guests.

Day 13Fix from feedback

Reduce guest drop-off

  • Add a roster search box for events above 40 guests.
  • Cut the tap flow to two taps maximum.
  • Add an opt-out line to every debrief email.

Deliverable: Shorter guest flow and opt-out shipped.

Day 14Week review

Turn the first event into an asset

  • Capture an anonymised screenshot of a delivered debrief email.
  • Ask the first host for one sentence we may quote.
  • Update the landing page hero with that quote.

Deliverable: One anonymised proof artifact and a quote on the site.

Week 3 · Repeat & systematize · 7 days
Day 15Holiday push

Target December parties

  • Send 30 messages to organizers of holiday singles parties dated 5-15 December.
  • Lead with the December date pressure in the subject line.
  • Log replies and prioritise hosts with events in the window.

Deliverable: 30 new targeted messages out.

Day 16Pilot loop

Buy testimonials with free runs

  • Offer 3 free pilot events in exchange for a 60-second video.
  • Cap pilots at three to protect the support window.
  • Record a second demo clip using the pilot's real flow.

Deliverable: Up to 3 pilot hosts booked with testimonial terms agreed.

Day 17Upsell

Convert pass buyers to subscription

  • Offer the first buyer Host Pro at $99 for their second event.
  • Ship the custom sender name field.
  • Add a match-rate summary line to the host CSV.

Deliverable: First subscription offer sent with the feature live.

Day 18Volume

30 more messages plus follow-ups

  • Send 30 messages to a second set of metros.
  • Send day-5 nudges to the day-15 wave.
  • Close any open checkout links that stalled.

Deliverable: 30 new sends and stalled links resolved.

Day 19Reliability

Make event night boring

  • Add email retry and a manual resend button.
  • Ship all-event CSV export.
  • Add a delivery log the host can see.

Deliverable: Retry, resend, export and delivery log shipped.

Day 20Second live event

Measure participation

  • Support the second live event end to end.
  • Record guest check-in and tap-through rates.
  • Note every support request and its cause.

Deliverable: Participation rate measured on a real event.

Day 21Funnel review

Kill the worst segment

  • Compute messages to replies to checkouts to payments by metro and segment.
  • Drop the two worst-performing metros from outreach.
  • Double the message count in the best-performing segment.

Deliverable: Written funnel table with the next week's segment decided.

Week 4 · Scale what works · 7 days
Day 22Expand tiers

Open the higher price point

  • Publish the Studio $299 tier page.
  • Send 30 messages including a multi-city operator angle.
  • Add a concurrent-event limit check at event creation.

Deliverable: Studio tier live and 30 messages sent.

Day 23Proof distribution

Use customer names with permission

  • Ask two paying hosts for permission to name their event in outreach.
  • Rewrite the outreach first line to cite a named event.
  • Update the site with the second quote.

Deliverable: Named-social-proof outreach variant in use.

Day 24Batch delivery

Two more events on one night

  • Support two live events in the same evening.
  • Batch debrief sends and verify each one.
  • Watch for any duplicate or missing match report.

Deliverable: Two events delivered with verified debriefs.

Day 25Money hygiene

Clean books for the ranking

  • Send Stripe receipts and handle any refund request as event credit first.
  • Verify payouts route to the TrustMRR-connected account.
  • Export a running revenue, refund and fee ledger.

Deliverable: Reconciled ledger through day 25.

Day 26Last-call outreach

Events dated 10-15 December

  • Send 30 last-call messages for events inside the window.
  • State plainly that setup must happen before 16 December.
  • Follow up within 24 hours on every reply.

Deliverable: 30 last-call messages sent.

Day 27Case note

Publish real anonymised numbers

  • Publish a three-sentence case note with guest count and matches delivered.
  • Add it to the outreach signature.
  • Check the site claims match what was actually delivered.

Deliverable: Case note live and used in outreach.

Day 28Convert subscriptions

Recurring revenue before cutoff

  • Offer Host Pro to every event-pass buyer with a second dated event.
  • Confirm the first monthly charge lands before 16 December.
  • Cancel any subscription started for a host who cannot run an event in time.

Deliverable: Subscription conversions charged inside the window.

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

Late events and late buyers

  • Onboard any host whose event falls on 15 December.
  • Pre-schedule debrief sends for late events.
  • Run a final outreach push of 20 messages.

Deliverable: All remaining events configured and queued.

Day 30Reconcile and submit

Close the contest cleanly

  • Count gross revenue, refunds, chargebacks and Stripe fees from the export.
  • Confirm no unpaid invoices remain and no ad spend is unrecorded.
  • Submit before 13:00 UTC and archive the ledger.

Deliverable: Submitted entry with a reconciled Stripe CSV.

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

  • Conservative case: 4 paying hosts, blended first payment of $49 across $39 event passes and an early $99 monthly.
  • Base case: 12 paying hosts at a blended $65, assuming roughly two thirds buy the $39 pass and one third the $99 monthly.
  • Upside case: 30 paying hosts at a blended $99, matching the concept's stated 30-customer target; this is a projection, not observed behaviour.
  • Payment processing is modelled at 4.5 percent of gross, assuming Stripe standard pricing plus a share of international cards.
  • Refunds are modelled at 0 percent conservative, 5 percent base and 3.3 percent upside; cancelled events are the main driver.
  • Chargebacks are modelled at zero in all three scenarios; volume is too low for a meaningful chargeback rate.
  • Paid marketing is zero in conservative and base because the channel is organic cold email and DM; the upside line covers a small sponsored-newsletter test.
  • Operating cost covers Vercel, Supabase, Resend, the domain and delivery email volume only; hosting and API costs are excluded from hackathon profit by rule.
  • Every figure is a forward-looking projection from these assumptions, not verified revenue, traction or existing customers.

Conservative

4 customers
$196
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$9
Paid marketing
$0
Hackathon profit
$187
Operating costs
$30
Business profit
$157

Base case

12 customers
$780
collected revenue · avg payment $65
Refunds
$39
Chargebacks
$0
Payment fees
$35
Paid marketing
$0
Hackathon profit
$706
Operating costs
$55
Business profit
$651

Optimistic

30 customers
$2,970
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$134
Paid marketing
$90
Hackathon profit
$2,647
Operating costs
$95
Business profit
$2,552

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$468
Payment fees (3.9%)
$18
Paid marketing
$0
Hackathon profit
$450
Business profit
$395

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. All figures are projections and carry no claim of existing customers, traction or collected money.

Section 7 of 8

Main risks and validation experiments

Risk 1Organizers plan weeks ahead, so hosts who buy in December may run their event after the 16 December cutoff, slipping revenue outside the window.

Mitigation

Prioritise events dated 20 November to 15 December in every outreach wave and state the setup deadline plainly in the last-call messages.

Validation experiment

On day 7, log the event date of every prospect and count how many fall inside the window before sending anything.

Kill criteria

If fewer than 25 of 60 listed prospects have events inside the window, abandon the December cohort and reframe outreach around January events with a paid deposit.

Risk 2Guest participation falls below 50 percent, producing thin or empty match lists and immediate churn.

Mitigation

Roster search box, two-tap flow, an in-room reminder script supplied to the host, and a resend nudge the morning after.

Validation experiment

Measure check-in and tap-through rate at the first live event on day 12 and compare against a 50 percent floor.

Kill criteria

If tap-through is below 35 percent across two live events, stop selling until the guest flow is redesigned.

Risk 3Consent and privacy exposure when hosts upload guests who never opted in, especially under UK GDPR and CAN-SPAM.

Mitigation

Only mutual yeses are ever revealed, every debrief email carries an opt-out line, and the importer shows a host attestation checkbox before an event activates.

Validation experiment

Add the attestation checkbox on day 3 and ask the first three hosts in conversation whether it would block them from buying.

Kill criteria

If two or more prospects refuse because of the attestation, stop selling to UK organizers and restrict to US and Canada until the flow is reworked.

Risk 4Cold email from a new domain is throttled, so messages do not reach organizers.

Mitigation

Warm the domain from day 6, cap sends at 30 per day, keep the message plain text with one link, and route Instagram DM as the backup channel.

Validation experiment

Compare reply rates on the day-7 email wave against the day-9 Instagram wave.

Kill criteria

If email reply rate is under 3 percent after 60 sends, stop email and run the rest of the month entirely on Instagram DM.

Risk 5Event cancellations trigger refunds that cut hackathon profit one for one.

Mitigation

Offer event credit toward a future date before refunding, and confirm the event is still running 48 hours before the debrief send.

Validation experiment

Track how many booked events are still running at the 48-hour check across the first four events.

Kill criteria

If more than 20 percent of booked events cancel across four events, move to a deposit-on-booking model with credit-only terms.

Risk 6Live-event support lands on evenings and weekends, conflicting with the no-24/7-support constraint.

Mitigation

Publish a single stated support window of 17:00-22:00 on event nights only, and make the host-side flow self-serve with a one-page runbook.

Validation experiment

Count inbound support messages per delivered event during week 2 and week 3.

Kill criteria

If any event requires more than three support messages, ship the missing self-serve control before accepting another booking.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Stripe account and connect it to TrustMRR before any customer exists.
  • Register the product domain and open Vercel and Supabase projects.

Output: Payment account connected, domain registered, empty deployment live.

Hours 3-5

  • Push tables: hosts, events, guests, answers.
  • Add host magic-link auth and row-level security scoping every query to the owning host.

Output: Working host login at a live URL with an empty dashboard.

Hours 6-8

  • Build the event create form with name, date, city and guest cap.
  • Build the guest list paste parser with email validation.

Output: An event can be created and a guest list imported.

Hours 9-11

  • Generate the event slug and QR poster PNG.
  • Print one poster at 100 percent scale and scan it with two phones.

Output: A printable QR poster that scans reliably.

Hours 12-14

  • Build the public check-in page with a roster tap list and a name search field.
  • Bind a phone to one guest with a signed cookie.

Output: A guest can check in from a poster scan with no account.

Hours 15-18

  • Build the post-event yes/no tap screen over host-flagged roster entries.
  • Implement the match engine and assert one-way answers can never appear in any email or CSV.
  • Run a six-guest simulation end to end.

Output: Verified mutual-match computation with a one-way answer leak test passing.

Complete report

Full 30-day launch report

Read the full generated report

Mutual Yes - 30-Day Public Report

Contest window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. One founder, no team, no ad budget, all revenue through a TrustMRR-connected Stripe account created before the first sale. JEV scored this concept 67.2/100 (band B). Speed to first revenue is the strongest criterion (8.34); operational simplicity is the weakest (4.63). The plan below is shaped by that split - sell within ten days, and keep the machine deliberately boring.

1. Product opportunity and positioning

The buyer is the owner-operator of an independent speed-dating or singles-mixer business: one to three people, one to eight events a month, twenty to one hundred and twenty guests per event, based in the US, Canada or UK. The trigger is concrete. They open registration for the next event and remember they will be hand-matching paper scorecards at midnight on a Friday.

That work is one to three hours of spreadsheet labour: collect cards, transcribe names, cross-reference, then email people one at a time. Errors are common and commercially expensive, because a guest who receives a late, wrong or empty result does not rebook. The host also carries a quiet consent problem: there is no defensible record of who agreed to be contacted.

Mutual Yes is not a dating app. It is a post-event reporting tool for the person who already assembles the crowd. The original location-based product died of cold start - it needed local density it could never bootstrap. The host has density by definition, has a dated recurring pain, and is individually findable by name on public event listings.

Why now: holiday singles parties cluster between 20 November and 15 December, inside the window. Every phone camera reads QR codes natively, so guest onboarding needs no app install and no app-store review. Managed hosting, database and transactional email keep delivery cost under $70 for the month at this volume.

Differentiation: ticketing platforms and dating apps sell guest-facing software. Nobody sells the two-way-only debrief as a $39 per-event utility. The mutual-only reveal is the product's core privacy guarantee, not a marketing line - no guest ever learns a one-way result, and the host never has to adjudicate an awkward match.

2. Smallest sellable MVP

One host, one event, one artifact: a QR poster on the door and a per-guest email of mutual matches after the event. Everything else is deferred.

In scope: host magic-link login, event creation with name and date, guest list paste or CSV import using first name, last initial and email, a downloadable QR poster PNG, a public check-in page where a guest taps their name with no account, a post-event tap screen where each guest marks yes or no on the roster entries the host flagged as met, a deterministic two-way match engine that never surfaces one-way answers, a one-click debrief send through Resend, and a host summary CSV.

Out of scope for the full 30 days: native apps, profiles and photos, in-app chat, GPS, ranking or who-liked-you teasers, white-label branding, custom domains, SMS delivery and multi-staff seats. Each would add weeks and none is required to collect the first $39.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres with magic-link auth for hosts only, Resend for debrief emails, Stripe Checkout plus webhooks for credits, and the qrcode library for the poster. No LLM is involved: matching is a set intersection, which is cheaper and more auditable than inference.

Data model: hosts, events, guests, answers, and matches computed at send time rather than stored as a public record. Row-level security scopes every host query to their own events. Guest pages use an unguessable event slug plus a signed cookie so one phone stays attached to one guest.

Build order: scaffold and auth, event creation and guest import, QR poster, guest check-in, tap screen and match engine, debrief email and CSV, Stripe gating, then a full seeded dry run on real phones.

The hardest technical risk is deliverability and timing on event night: the debrief must land minutes after the host click without tripping spam filters. Mitigation is a warmed sending domain with SPF, DKIM and DMARC set on day 6, a single-link plain-shaped email, and a manual resend button. Second risk is guests abandoning a long roster; mitigation is a name search box and a two-tap flow.

4. Pricing and monetization

Event Pass at $39 one-time covers one event, up to 80 guests, the QR poster, the debrief email and the summary CSV. Host Pro at $99 per month covers unlimited events with three concurrent, a custom sender name and match-rate summaries. Studio at $299 per month covers ten concurrent events, a branded email header, all-event CSV and priority support. Checkout gates event creation, so no work happens before payment.

The first-revenue offer is deliberately small: $39 for this event, first five hosts only. The subscription is sold at the second event, not the first. Blended first-payment value used in the projections is $49 to $99 depending on mix.

5. First-customer acquisition

One channel: cold email and Instagram DM to named organizers of publicly listed singles events dated between 20 November and 15 December, sourced from public listings in ten metros. No ads, no partnerships, no marketplace.

The message is three lines, quotes their event name and date, and closes with a price. The 40-second screen recording of a real debrief email arriving is the pitch artifact. Follow-ups on day 2 and day 5 are one line: is your event on that date still running? Week-one goal: 55 messages sent, at least 3 live conversations, first payment by day 10.

6. 30-day execution roadmap

Days 1-5 build to a paid, deployed v1. Days 6-7 build the 60-event prospect list, warm the sending domain and record the demo. Days 8-14 cover the first sale, the first live event and the fixes it forces. Days 15-21 add a pilot testimonial loop, ship reliability work, and run a funnel review that drops the worst-performing metro. Days 22-28 push outreach volume, publish the Studio tier and convert pass buyers to subscriptions. Days 29-30 run late events and reconcile every dollar before the 13:00 UTC cutoff. The full day-by-day task list sits in the roadmap object above.

7. Revenue and profit scenarios

Three projections, all hypotheses. Conservative: 4 customers at a $49 blended first payment, $196 gross, no refunds, $9 in processing fees, $30 operating cost. Base: 12 customers at $65 blended, $780 gross, $39 refunds, $35 fees, $55 operating. Upside: 30 customers at $99 blended, $2,970 gross, $99 refunds, $134 fees, $90 paid marketing, $95 operating. Processing is modelled at 4.5 percent, assuming Stripe standard pricing plus a share of international cards. Hosting, database, email and domain are the only operating lines. None of these are verified revenue, customers or traction - they are arithmetic from the stated assumptions.

8. Risks and validation experiments

Event-timing slip is the biggest: a host who buys in December may run their event after the cutoff, so only events dated 20 November to 15 December are prioritised. Thin guest participation is second; measure tap-through at the first live event and add a search box if it falls below 50 percent. Consent and privacy is third; keep the mutual-only reveal, add an opt-out line to every debrief email, and require a host attestation checkbox before an event activates. Cancellations drive refunds that cut profit one for one, so offer credit toward a future date before refunding. Deliverability is handled by a warmed domain and a 30-per-day send cap, with Instagram DM as the backup channel. Evening support is bounded to a stated 17:00-22:00 window on event nights and made self-serve with a one-page runbook.

9. First 24-hour action plan

Hours 1-2: connect Stripe to TrustMRR, register the domain, open Vercel and Supabase. Hours 3-5: ship the schema and magic-link host auth. Hours 6-8: event creation and guest list paste. Hours 9-11: QR poster generator, verified with a real print and two phone scans. Hours 12-14: guest check-in page and the phone-to-guest cookie. Hours 15-18: tap screen, match engine and a six-guest simulation with an explicit assertion that a one-way yes can never appear in any email or export.

Disclaimer

All revenue, profit and customer figures in this report are forward-looking projections built from the stated assumptions. They are not verified revenue, existing customers, traction or partnerships.

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 →