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

Preorder Cap

Preorder Cap gives independent bakeries and florists a hosted live-capacity page that self-decrements as preorder slots are claimed, exports sold-out days as a calendar feed, and generates the Instagram and WhatsApp reply text the owner retypes a hundred times a week.

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.74/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct Instagram DM outreach to bakeries and florists who posted a holiday preorder announcement in the last seven days.
Who pays

Owner-operator of a single-location independent bakery, cake studio, or florist doing roughly $3k-$40k per month in the US, UK, Canada, or Australia, currently taking holiday preorders through Instagram DMs, WhatsApp, and phone.

Biggest execution risk

Monetization potential 5.0/10

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

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

0/12
Entry price
$99
Solo build
5 days
30d base revenue
$990
30d hackathon profit
$950
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a single-location independent bakery, cake studio, or florist doing roughly $3k-$40k per month in the US, UK, Canada, or Australia, currently taking holiday preorders through Instagram DMs, WhatsApp, and phone.

Why now

The Thanksgiving-to-Christmas preorder rush falls entirely inside the 30-day window, so the pain is live and dated during the contest itself.

Problem

Remaining holiday capacity lives in the owner's head or a paper notebook, goes stale within an hour, and causes an overbooked Saturday before Christmas: refunds, all-night baking, and apologetic DMs.

Solution

The owner enters holiday dates, per-day caps, cutoff times and blackout dates; Preorder Cap publishes a mobile page plus QR code showing each day Open, Low or Sold Out, a claim form that atomically decrements the count, generated social/DM reply text per state, and an .ics plus CSV export.

Differentiation · No POS integration, no per-order commission, no marketplace, and no change to how the owner already takes orders; it replaces the notebook, not the business.

1. Product opportunity and positioning

Independent bakeries and florists sell holiday preorders through Instagram DMs, WhatsApp and phone. Capacity is tracked in a notebook or in the owner's head. That works in October and fails the week before Christmas, when the same person is answering DMs, baking, and serving walk-ins. The failure mode is specific and expensive: an overbooked Saturday, refunds, a 3am bake, and apologetic messages to customers who had already told their family they were covered.

Preorder Cap does not try to be fulfilment software. It replaces one artifact, the notebook, with a hosted page at a clean URL. The owner enters which days accept preorders, how many slots each day holds, the cutoff time, and blackout dates. The page shows each day as Open, Low or Sold Out, and a one-tap claim form decrements the count instantly and atomically. When a day flips to sold out, the product writes the Instagram Story, WhatsApp broadcast and DM reply text the owner would otherwise retype dozens of times, and it publishes an .ics feed so the owner's own phone calendar blocks the sold-out days.

The buyer is identifiable today by a public artifact: an Instagram post saying preorders are open for specific dates. That means outreach can open with a screenshot of a working page already populated with that shop's real dates, not a description of software. The decision is made by one person in minutes, and the price is a season pass that pays for itself the first time it prevents one overbooked Saturday.

The positioning is deliberately narrow: one buyer, one month, one output. The JEV score of 67.4 (band B) reflects that strength and its ceiling. Speed to first revenue scores 8.89 because the offer is a screenshot plus a Stripe link. Monetization scores 5.04 and defensibility 5.80 because the season pass is one-time and the workflow is copyable. The plan below therefore treats the 30 days as a cash-and-learning sprint, not a platform build: ship in four days, DM from day seven, and use every buyer conversation to decide whether the $19 monthly Year Round tier is a real second act or a polite thank-you.

2. Smallest sellable MVP

A single-tenant-agnostic hosted page per merchant with: day list with caps, cutoffs and blackouts; an atomic claim form that cannot overbook; a copy generator for open, low and sold-out states; an .ics feed and per-day CSV; Stripe Checkout for the season pass; magic-link dashboard. Nothing else. No POS, no merchant-side payments, no route planning, no multi-location, no custom domains, no automated social posting. If a feature does not help close a DM conversation this week, it waits.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres, Stripe Checkout, Resend, Tailwind. The only genuinely hard part is the claim: a days row holds cap and claimed, and a claim runs inside a Postgres transaction with SELECT ... FOR UPDATE on that row so two simultaneous claims on the last slot cannot both succeed. Test it with 20 parallel requests against a cap of 5 before touching the UI. Everything else is rendering and email. The public page is cached at the edge and revalidated on claim; the editor is authenticated by emailed magic link; order confirmation to the owner is a Resend email containing a structured order line. The copy generator is a small template engine with LLM polish optional and off by default, so delivery cost stays near zero.

4. Pricing and monetization

Season Pass $99 one-time through December 31; Season Pass + Setup $149 with a 15-minute guided call and a printable counter QR card; Year Round $19/month for owners who keep the page after the holidays. Sell the $99 first and only mention $149 when the owner hesitates on setup. Expected first-transaction value is $99; blended ARPU in the scenarios below stays at $99 for conservatism.

5. First-customer acquisition

One channel: direct Instagram DM to shops that posted a holiday preorder announcement in the last seven days. Build a 150-handle list in one metro area, pre-fill demo pages for the top 20 with their real dates, and attach a screenshot in the first message. Convert on a 10-minute screen share where the page goes live and payment is taken by Stripe link on the call. Follow up at 48 hours and after their first weekend. The only compounding loop is asking each buyer for one introduction inside their local vendor group.

6. 30-day execution roadmap

Days 1-5 build: schema and auth, public page and editor, atomic claim, Stripe plus copy generator plus feeds, then deploy with three demo shops. Days 6-7 prospect: 150-handle list, 20 pre-filled demos, first 20 DMs. Days 8-14: 40 DMs per day, objection script, screen-share calls, first sale targeted for day 12, weekend recap emails. Days 15-21: push the $149 tier to repliers, batch setup calls, publish sold-out templates, ask for introductions, cut any message angle under 5% reply. Days 22-28: second and third metro areas, pitch the $19 monthly at checkout, fix the top support question in product. Days 29-30: close outstanding Stripe links and freeze the build.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 buyers at $99 = $297 gross, $12 processing, $0 refunds, $0 ads, $25 operating. Base: 10 buyers = $990 gross, $40 processing, $45 operating. Upside: 25 buyers = $2,475 gross, $99 processing, $50 refunds, $150 paid ads, $90 operating. Hackathon profit counts revenue minus refunds, chargebacks, processing and ad spend only; business profit additionally subtracts operating cost. No scenario assumes an existing customer, partner or audience.

8. Main risks and validation experiments

Instagram DM rate limits cap reach per day, so prospect volume must be front-loaded before day 20. Urgency arrives late, because most shops have not yet hit a sold-out day by December 16. Free Google Forms are the real competitor once holiday pressure passes. Each risk has a cheap test below; the kill signal is a reply rate under 5% across 200 DMs with two different screenshot angles.

9. First 24 hours

Repo and database first, then a working public page for a fictional test shop, then a concurrency test that proves the cap holds. By hour 24 the founder should have a deployable page and a first draft of the 150-handle prospecting list. No landing page copy, no logo.

Section 2 of 8

Smallest sellable MVP

A hosted, self-decrementing holiday capacity page at a public URL plus QR code, sold as a $99 season pass through Stripe Checkout.

Must-have features

  • Public mobile capacity page showing each holiday date as Open, Low or Sold Out
  • Merchant editor for days, per-day caps, cutoff times and blackout dates with bulk date generation
  • Atomic claim form that reserves a slot and blocks overbooking at the cap
  • Copy generator producing Instagram Story, WhatsApp broadcast and DM reply text for each state
  • ICS calendar feed of sold-out days and per-day CSV export of claimed orders
  • Stripe Checkout for Season Pass and Season Pass + Setup, delivered via emailed magic link
  • Resend confirmation email per claim plus a daily digest of tomorrow's preorders

Explicitly out of scope

  • No POS, Shopify, Square or website-builder integrations
  • No card handling or deposits for the merchant's own customers
  • No route planning or driver dispatch
  • No multi-location or staff seats
  • No white-label domains or advanced branding
  • No automated Instagram or WhatsApp posting

Demo flow (what the buyer sees)

  1. Founder opens the editor for a demo shop and enters Dec 19-24 with caps of 12 per day
  2. Founder publishes, copies the public URL and QR, and screenshots the mobile page
  3. Buyer opens the page, taps a day, submits name and pickup time
  4. Slot decrements; page shows Low, then Sold Out at the cap
  5. Owner receives a structured order email and sees tomorrow's digest
  6. Owner copies the sold-out Story and WhatsApp text and subscribes to the ICS feed
  7. Owner pays via Stripe Checkout and lands on the magic-link dashboard
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase PostgresStripe CheckoutResendTailwind CSSVercel edge cachingqrcode libraryICS feed generated server-side

Architecture

A single Next.js app hosts the authenticated editor, the public capacity page, and API routes. Supabase holds merchants, days (with cap and claimed counters), and orders. A claim runs in one Postgres transaction that locks the day row before incrementing, so the cap cannot be exceeded. Stripe Checkout creates the subscription or one-time pass and a webhook flips the merchant to paid. Resend sends per-claim emails and a scheduled daily digest. The public page is edge-cached and revalidated on each claim so buyers see accurate capacity without a database read on every view.

Build steps

  1. Create Next.js repo, deploy to Vercel, create Supabase project
  2. Write merchants, days, orders tables with a unique constraint on merchant_id plus date
  3. Ship magic-link auth and the protected dashboard shell
  4. Build the merchant editor with caps, cutoffs, blackouts and bulk holiday date generation
  5. Build the public capacity page rendering Open, Low and Sold Out states
  6. Implement the claim API with SELECT FOR UPDATE and increment inside one transaction
  7. Load-test the claim route with 20 parallel requests against a cap of 5
  8. Add Resend order confirmation email and the daily digest cron
  9. Add Stripe Checkout, the webhook, and the paid-state gate
  10. Build the copy generator templates for open, low and sold-out states
  11. Add the ICS feed endpoint and per-day CSV export
  12. Generate a QR code and public URL copy button in the editor
  13. Seed three demo shops with realistic holiday dates and load-test the public page on mobile

AI components

  • Optional LLM polish pass for generated reply text, disabled by default to keep per-merchant delivery cost near zero
Hardest technical risk: Concurrency on the last slot: two simultaneous claims must not both succeed, and a race here destroys the entire promise of the product.
Section 3 of 8

Pricing and monetization

Season Pass

Entry offer
$99 one-time

For Solo owner needing a live capacity page through December 31

  • Hosted capacity page with QR code
  • Unlimited holiday date caps and blackout dates
  • Sold-out reply text generator
  • ICS feed and CSV order export

Season Pass + Setup

$149 one-time

For Owner who wants the page built with them on a 15-minute call

  • Everything in Season Pass
  • Guided setup call with all holiday dates pre-loaded
  • Printable counter QR card PDF

Year Round

$19 / month

For Owner who keeps the page after the holiday season

  • Permanent capacity page
  • Recurring weekly and custom date patterns
  • Monthly digest of claimed preorders

Model: One-time season pass for the holiday window, an assisted setup upgrade, and a low monthly tier for owners who keep the page afterwards.

First revenue offer: A screenshot of a live page already populated with the shop's own December dates, sent by DM, with the line: '$99 for the season if you keep it, Stripe link here, live in eight minutes.'

Expected ACV: $99

Upsell path: Offer the $149 setup call when the owner hesitates, then pitch the $19 monthly Year Round tier at checkout and again in the post-holiday recap email.

Target customers
30
Revenue model
$2,970
Costs
$140
Profit model
$2,830
Section 4 of 8

First-customer acquisition

Primary channel

Direct Instagram DM outreach to bakeries and florists who posted a holiday preorder announcement in the last seven days.

Where to find them

  • Instagram search for bakery and florist accounts posting 'preorders open' or 'Christmas orders' this week
  • Instagram location tags for one metro area's bakery and florist clusters
  • Google Maps listings for independent bakeries and florists in the same metro
  • Local market Facebook and WhatsApp vendor groups named in buyer introductions
  • Shop websites that list a phone number and an Instagram handle side by side

Exact outreach motions

  • Build a 150-row sheet with handle, city, posted preorder dates, and DM channel
  • Create a demo page for the top 20 using their real dates and plausible caps
  • Send DM one with a screenshot and the shop's own URL, no product description
  • At 48 hours, follow up with the sold-out Story and WhatsApp text templates
  • At any positive reply, offer a 10-minute screen share and take the Stripe link on the call
  • After their first weekend, send a recap email with claimed counts and the CSV
  • Ask every buyer for one introduction inside their local vendor group

Message template

Hi [name] - saw you posted preorders open for Dec 19-24. I built you a live slot page for those exact dates so you stop recounting DMs: [link]. Customers see Open / Low / Sold Out, the count drops itself, and it writes your sold-out Story and WhatsApp text. Free to look. $99 for the season if you keep it.
Week-one goal: 150 handles collected, 20 pre-filled demo pages built, 60 DMs sent, and at least 6 replies logged by end of day 10.
Section 5 of 8

30-day execution roadmap

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

Schema and auth

  • Create Next.js repo, deploy to Vercel, create Supabase project.
  • Write merchants, days and orders tables with a unique merchant_id plus date constraint.
  • Ship magic-link auth and the dashboard shell.

Deliverable: Deployed skeleton with working login.

Day 2Public page

Capacity page and editor

  • Build the mobile public page with Open, Low, Sold Out states.
  • Build the one-page editor for dates, caps, cutoffs and blackouts.
  • Add bulk holiday date generation.

Deliverable: Live public page for a test shop.

Day 3Claims

Atomic decrement

  • Implement the claim API with SELECT FOR UPDATE inside one transaction.
  • Add Resend order confirmation email to the owner.
  • Load-test 20 parallel claims against a cap of 5.

Deliverable: Overbooking provably blocked.

Day 4Money and outputs

Stripe, copy, feeds

  • Wire Stripe Checkout for $99 and $149 plus the paid-state webhook.
  • Build the copy generator for open, low and sold-out states.
  • Add the ICS feed endpoint and per-day CSV export.

Deliverable: Paid signup to first order end-to-end.

Day 5ShipMVP shipped

MVP live

  • Polish mobile page speed and add QR generation plus copy-link button.
  • Add the daily digest cron email.
  • Seed three demo shops with real holiday dates.

Deliverable: MVP live with three demo URLs.

Day 6Prospecting

Build the 150 list

  • Collect 150 bakery and florist handles posting preorders this week.
  • Record city, posted dates and DM channel for each.

Deliverable: 150-row outreach sheet.

Day 7First DMs

20 pre-filled demos

  • Build demo pages for the top 20 with their real dates and caps.
  • Screenshot each page and send DM one.

Deliverable: 20 DMs sent with 20 personalised screenshots.

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

40 DMs

  • Send 40 DMs from the screenshot angle.
  • Log every reply in the sheet within the hour.
  • Follow up on day-7 non-openers.

Deliverable: 40 DMs sent, reply table current.

Day 9Objections

Script and volume

  • Write answers to the three most common objections.
  • Send 40 DMs.
  • Book first screen-share calls.

Deliverable: Objection script plus 2 booked calls.

Day 10Calls

Live demos

  • Send 40 DMs.
  • Run screen shares and publish the page live on the call.
  • Send Stripe link inside the call.

Deliverable: 3 live demos completed.

Day 11Close

Payment day

  • Run remaining demos and collect payment by Stripe link.
  • Send the 48-hour template follow-up to all warm replies.
  • Send 25 fresh DMs.

Deliverable: At least one paid merchant or a clear objection log.

Day 12First revenueFirst sale target

First sale target

  • Close the first Season Pass.
  • Onboard that merchant with real dates and a printed QR.
  • Send 40 DMs.

Deliverable: First Stripe payment collected.

Day 13Momentum

Volume plus proof

  • Send 40 DMs referencing a live customer page as social proof.
  • Follow up on all 48-hour non-replies.
  • Fix the top friction found on calls.

Deliverable: 3 total paying merchants.

Day 14Recap

Retention and referral

  • Send weekend recap emails with claimed counts and CSV.
  • Ask each buyer for one local vendor introduction.
  • Review reply rate by message angle.

Deliverable: Referral asks sent, angle data recorded.

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

$149 tier

  • Pitch Season Pass + Setup to every replier who hesitated.
  • Send 40 DMs.
  • Generate counter QR card PDFs for setup buyers.

Deliverable: First $149 sale or documented rejection reason.

Day 16Setup

Batched onboarding

  • Run batched 15-minute setup calls.
  • Pre-load all holiday dates before the call starts.
  • Send 25 DMs.

Deliverable: All setup buyers live with printed QR.

Day 17Lead magnet

Template pack

  • Publish the sold-out Story and WhatsApp template pack as a free page.
  • Link it in every follow-up.
  • Send 40 DMs.

Deliverable: Template pack live and linked in outreach.

Day 18Referrals

Compounding loop

  • Ask all buyers for one introduction in their vendor group.
  • Send 40 DMs to referred handles first.
  • Log which intro source converts.

Deliverable: 5 warm introductions in progress.

Day 19Review

Cut what fails

  • Compute reply rate per angle and per metro.
  • Drop any angle under 5% reply across 100 sends.
  • Send 30 DMs with the surviving angle only.

Deliverable: One winning message angle documented.

Day 20Second metro

Geographic expansion

  • Build a 60-handle list in a second metro.
  • Send 40 DMs with local screenshots.
  • Follow up on day-15 through day-18 non-replies.

Deliverable: Second-metro list built and messaged.

Day 21Proof

Recap round two

  • Send claimed-count recaps to every buyer.
  • Record one short screen-capture of a sold-out page flipping.
  • Send 30 DMs attaching the capture.

Deliverable: Video proof asset plus recaps sent.

Week 4 · Scale what works · 7 days
Day 22Recurring

$19 monthly pitch

  • Add the Year Round $19 monthly option at checkout.
  • Pitch it to every buyer in the recap email.
  • Send 40 DMs.

Deliverable: First monthly subscription or clear refusal pattern.

Day 23Product pull

Fix top support question

  • Fix the single most-asked support question in product.
  • Send 40 DMs.
  • Update onboarding email with the fix.

Deliverable: Support volume per merchant reduced.

Day 24Volume

Sustain outreach

  • Send 40 DMs.
  • Follow up on all unresolved threads.
  • Refresh 30 stale handles from the sheet.

Deliverable: Pipeline still moving at day 24.

Day 25Setup batch

Service revenue

  • Run a second batched setup-call day.
  • Record the call script for reuse.
  • Send 25 DMs.

Deliverable: Setup calls cleared, script documented.

Day 26Third metro

Reach

  • Build a 50-handle list in a third metro.
  • Send 40 DMs using the winning angle.
  • Log replies by metro.

Deliverable: Third-metro test running.

Day 27Quality

Refunds and copy

  • Review any refund requests and tighten the December-only scope wording.
  • Check every live page for stale caps.
  • Send 30 DMs.

Deliverable: Refund rate under control, pages audited.

Day 28Last push

Final full outreach day

  • Send 40 DMs before the late-December fatigue window.
  • Follow up on every open thread.
  • Confirm remaining Stripe links are valid.

Deliverable: Final outreach day complete.

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

Collect outstanding

  • Follow up on all outstanding Stripe links.
  • Close any setup-call commitments.
  • Do not start new features.

Deliverable: All outstanding payments resolved.

Day 30Freeze

Wrap and hand over

  • Export the final numbers: revenue, refunds, processing, ads, operating cost.
  • Send every buyer a season-end thank-you with the monthly option.
  • Freeze the build; leave the pages running through December 31.

Deliverable: Final profit numbers and intact customer pages.

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/Base/Upside: ARPU is held at $99 with zero $149 or $19 revenue counted, because the higher tiers are unproven.
  • Conservative: 3 buyers from roughly 600 DMs sent, a roughly 0.5% conversion.
  • Base: 10 buyers from roughly 900 DMs sent, a roughly 1.1% conversion.
  • Upside: 25 buyers from roughly 1,000 DMs sent plus referrals and $150 of paid sponsored posts, a roughly 2.5% blended conversion.
  • Payment processing assumed on Stripe Checkout at 2.9% plus $0.30, modelled at approximately 4% of collected revenue.
  • Refunds are $0 in Conservative and Base; Upside assumes 2 refunds from late-December buyers who see no remaining dates.
  • Chargebacks assumed $0 across all scenarios; 3DS and Stripe Radar are on.
  • Ad spend is $0 in Conservative and Base because the channel is organic DM outreach; Upside includes $150 of paid sponsored posts or a small paid shoutout.
  • Operating cost covers Vercel and Supabase hosting, domain, Resend email and any LLM usage: $25 / $45 / $90 across the three scenarios.
  • No figure here is verified revenue, an existing customer count, or a promised outcome; all three are projections.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$25
Business profit
$260

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$40
Paid marketing
$0
Hackathon profit
$950
Operating costs
$45
Business profit
$905

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$50
Chargebacks
$0
Payment fees
$99
Paid marketing
$150
Hackathon profit
$2,176
Operating costs
$90
Business profit
$2,086

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$990
Payment fees (3.9%)
$39
Paid marketing
$0
Hackathon profit
$951
Business profit
$906

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. They are not verified revenue, not existing customers, and not a forecast of contest placement.

Section 7 of 8

Main risks and validation experiments

Risk 1Instagram DM rate limits and spam flagging cap how many buyers are reachable per day.

Mitigation

Front-load outreach before day 20, keep sends at 40 or fewer per day, and rotate message angles.

Validation experiment

Send 40 DMs over two days and measure reply rate plus any platform warnings.

Kill criteria

Reply rate under 5% across 200 DMs with two distinct screenshot angles.

Risk 2The window ends before most shops experience a sold-out holiday day, so urgency arrives late.

Mitigation

Target shops whose posted dates fall inside the next 14 days and lead with the overbooking consequence.

Validation experiment

Split 60 DMs between a 'prevent overbooking' angle and a 'see live counts' angle.

Kill criteria

Both angles under 5% reply across 60 sends each.

Risk 3Owners may find a free Google Form or notes app sufficient.

Mitigation

Sell the atomic cap and generated reply text as the paid difference, with December-only scope wording.

Validation experiment

Ask 10 owners what they use today and what breaks under volume; record verbatim answers.

Kill criteria

Eight of ten say their method is fine and none names an overbooking incident.

Risk 4Refunds from late-December buyers with no remaining dates.

Mitigation

State the December 31 season end on the checkout page and in the DM.

Validation experiment

Track refund requests against purchase date for the first 10 buyers.

Kill criteria

Refunds exceed 10% of buyers before any ad spend.

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 connect credentials.

Output: Deployed app with a live database connection.

Hours 3-5

  • Write merchants, days and orders tables with the merchant_id plus date unique constraint.
  • Add magic-link auth and the protected dashboard shell.

Output: Schema live and login working.

Hours 6-9

  • Build the merchant editor for dates, caps, cutoffs and blackouts.
  • Add bulk holiday date generation for Dec 19-24.

Output: A shop's holiday calendar saved to the database.

Hours 10-13

  • Build the mobile public capacity page with Open, Low and Sold Out states.
  • Deploy and open it on a real phone.

Output: A public page a buyer could use today.

Hours 14-17

  • Implement the claim API with SELECT FOR UPDATE and increment in one transaction.
  • Run a 20-parallel-request test against a cap of 5.

Output: Proof that overbooking is blocked.

Hours 18-24

  • Start the 150-handle prospecting sheet with the first 40 handles and their posted dates.
  • Draft the first DM and screenshot template.

Output: 40 qualified handles and a ready DM.

Complete report

Full 30-day launch report

Read the full generated report

1. Product opportunity and positioning

Independent bakeries and florists sell holiday preorders through Instagram DMs, WhatsApp and phone. Capacity is tracked in a notebook or in the owner's head. That works in October and fails the week before Christmas, when the same person is answering DMs, baking, and serving walk-ins. The failure is specific and expensive: an overbooked Saturday, refunds, a 3am bake, and apologetic messages to customers who had already told their family they were covered.

Preorder Cap does not try to be fulfilment software. It replaces one artifact, the notebook, with a hosted page at a clean URL. The owner enters which days accept preorders, how many slots each day holds, the cutoff time, and blackout dates. The page shows each day as Open, Low or Sold Out, and a one-tap claim form decrements the count instantly and atomically. When a day flips to sold out, the product writes the Instagram Story, WhatsApp broadcast and DM reply text the owner would otherwise retype dozens of times, and it publishes an .ics feed so the owner's own phone calendar blocks the sold-out days.

The buyer is identifiable today by a public artifact: an Instagram post saying preorders are open for specific dates. Outreach can therefore open with a screenshot of a working page already populated with that shop's real dates, not a description of software. One person decides in minutes, and the price is a season pass that pays for itself the first time it prevents one overbooked Saturday.

The positioning is deliberately narrow: one buyer, one month, one output. That narrowness is the strength and the ceiling. The offer is easy to say, easy to demo and easy to price, but it is a seasonal one-time purchase in a category where a free form is the default alternative. The plan therefore treats the 30 days as a cash-and-learning sprint, not a platform build: ship in four days, DM from day seven, and use every buyer conversation to decide whether the monthly tier is a real second act or a courtesy.

2. Smallest sellable MVP

One hosted page per merchant with a day list, per-day caps, cutoffs and blackout dates; a claim form that cannot overbook; a copy generator for the three states; an .ics feed and a per-day CSV; Stripe Checkout for the pass; and an emailed magic-link dashboard. Nothing else. No POS integration, no card handling for the merchant's customers, no routing, no multi-location, no custom domains, no automated posting. If a feature does not help close a DM conversation this week, it waits.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres, Stripe Checkout, Resend, Tailwind. The only genuinely hard part is the claim. A days row holds cap and claimed, and a claim runs inside a Postgres transaction that locks that row before incrementing, so two simultaneous claims on the last slot cannot both succeed. Test it with 20 parallel requests against a cap of 5 before touching the UI. Everything else is rendering and email: the public page is edge-cached and revalidated on claim, the editor is protected by an emailed magic link, and each claim sends the owner a structured order line. The copy generator is a small template engine with optional model polish, so per-merchant delivery cost stays near zero and never threatens the per-sale margin.

4. Pricing and monetization

Season Pass at $99 one-time through December 31, Season Pass + Setup at $149 with a 15-minute guided call and a printable counter QR card, and Year Round at $19 per month for owners who keep the page. Lead every conversation with $99 and mention $149 only when setup hesitation appears. Scenario modelling keeps blended ARPU at $99 and counts no upgrade revenue, so the numbers are conservative by construction.

5. First-customer acquisition

One channel, Instagram DM, to shops that posted a holiday preorder announcement in the last seven days. Build a 150-handle list in one metro, pre-fill demo pages for the top 20 with their real dates, and attach a screenshot rather than a pitch. Convert on a 10-minute screen share where the page goes live and payment is taken by Stripe link during the call. Follow up at 48 hours with sold-out templates and after their first weekend with a claimed-count recap. The only compounding loop is asking each buyer for one introduction inside their local vendor group.

6. 30-day execution roadmap

Days 1-5 are build: schema and auth, public page and editor, atomic claim, Stripe plus copy generator plus feeds, then deploy with three demo shops. Days 6-7 are prospecting: the 150-handle list, 20 pre-filled demos, the first 20 DMs. Days 8-14 run 40 DMs a day with an objection script, screen-share calls, a first-sale target on day 12, and weekend recap emails. Days 15-21 push the setup tier to repliers, batch the calls, publish the template pack, ask for introductions, and cut any message angle below a 5% reply rate. Days 22-28 open second and third metro areas, pitch the monthly tier at checkout, and fix the top support question in product. Days 29-30 close outstanding Stripe links and freeze the build.

7. Revenue and profit scenarios

Every figure is a projection from stated assumptions, not verified revenue. Conservative: 3 buyers at $99 gives $297 gross, $12 processing, $0 refunds, $0 ads and $25 operating. Base: 10 buyers gives $990 gross, $40 processing and $45 operating. Upside: 25 buyers gives $2,475 gross, $99 processing, $50 refunds, $150 paid ads and $90 operating. Hackathon profit counts revenue minus refunds, chargebacks, processing and ad spend; business profit also subtracts operating cost. No scenario assumes an existing customer, partner or audience.

8. Main risks and validation experiments

DM rate limits cap daily reach, so volume must be front-loaded before day 20. Urgency may arrive after the window closes, because most shops hit a sold-out day later in December. A free form is the real competitor once the pressure passes. Service load from the setup tier can eat build time. Each risk has a cheap test: a two-angle DM split, a direct question on ten calls about what breaks under volume, refund tracking against purchase date, and timing three setup calls back to back.

9. First 24 hours

Repo and database first, then a working public page for a test shop, then a concurrency test proving the cap holds, then the first 40 prospecting handles. By hour 24 there should be a deployable page, a proven claim path, and a DM ready to send. No landing page copy, no logo, no pricing page polish.

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 →