DropPlate
DropPlate turns a home cook's WhatsApp menu into a pre-order page with portion caps, pickup slots, and an auto-generated shopping list.
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.
Solo home cooks and micro-caterers (1-3 people) in London, Brussels or Lagos already selling 10-50 pre-ordered meals a week through Instagram and WhatsApp.
Market demand 5.1/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 11; 35 sales at $29 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.9/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
12 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Solo home cooks and micro-caterers (1-3 people) in London, Brussels or Lagos already selling 10-50 pre-ordered meals a week through Instagram and WhatsApp.
Why now
These cooks already have buyers and a weekly deadline, so the product sells into an existing workflow with no marketplace cold-start and no food-handling regulation.
Problem
They collect orders in DMs, chase payments, tally portions by hand and overbuy ingredients, losing hours each week and wasting food.
Solution
The cook pastes their weekly menu text, DropPlate parses it into capped dishes with pickup windows, publishes a mobile order page, and after cutoff generates a Drop Sheet with an aggregated shopping list, prep schedule and pickup roster as PDF/CSV.
Opportunity
Menu Next Door did not fail on demand. It failed on structure: a two-sided marketplace needs cooks and eaters to arrive together, and each new city restarts that cold start. On top of that, it put a non-professional cook's kitchen inside a regulated food transaction, which meant every market added compliance cost before it added revenue.
DropPlate removes both failure modes by refusing to be a marketplace. It does not list cooks for discovery, does not take commission on meals, does not process payments for the cook, and never touches food. It sells one workflow to one cook who already has customers: turn the menu they were going to paste into WhatsApp anyway into a pre-order page with portion caps, then hand them the shopping list that follows from the real orders.
Buyer
A solo home cook or micro-caterer running 10-50 pre-ordered meals a week in London, Brussels or Lagos. They post a menu on Instagram, take orders in DMs, chase bank transfers, tally portions in a notes app, and shop from memory. The cost is 3-6 hours a week plus one wasted shopping trip per month. They are reachable by direct message, decide alone, and pay by card.
Why this wedge scores the way it does
JEV scored this exact concept 64.3/100 (band C, confidence 0.72). The profile matters more than the total: speed to first revenue is 7.88/10 and solo build feasibility is 7.40/10, while market demand (5.12) and competitive defensibility (5.62) are the weak axes.
That is the signature of a tool sold by hand into a narrow, already-active niche. Nothing here depends on a market forming, an SEO ramp, or a partnership. The first dollar comes from one cook saying yes to a page that was built for them before they were asked.
The weak axes are real and must be respected. Demand is not proven, so the 30 days are a demand test, not a scaling exercise. Defensibility is thin, so the moat is the Drop Sheet output and the switching cost of a cook's live order link, not features. Do not broaden into a marketplace, delivery or compliance to fix either weakness inside 30 days.
Positioning against the alternative
The competitor is not Shef or Too Good To Go. It is a Google Form, a notes app and a spreadsheet, or nothing at all. DropPlate wins on setup time (paste, not build), on portion caps that close a dish by itself, and on a shopping list computed from orders instead of guessed.
Smallest sellable MVP
A magic-link login, a paste box that parses a menu into capped dishes with a pickup window, a public mobile order page that auto-closes, an order dashboard with a paid toggle, and a Drop Sheet PDF/CSV export.
Must-have features
- Paste-menu parser returning dish name, description and price as validated JSON
- Menu editor with portion caps per dish and pickup time windows
- Public mobile order page at an unguessable slug with countdown and sold-out auto-close
- Order dashboard with cutoff timer and manual paid/unpaid toggle
- Drop Sheet export: ingredient-aggregated shopping list, prep schedule, pickup roster (PDF and CSV)
- Shareable link and QR code per drop
- Email confirmation to buyers and cutoff notice to the cook via Resend
- Magic-link auth and cook onboarding
Explicitly out of scope
- Marketplace or discovery feed
- Delivery logistics or driver tracking
- Food safety compliance, allergen or label generation
- Payment processing on the cook's behalf
- Multi-cook or team accounts
- Native mobile app
- Custom domains for Starter tier
- SMS reminders in the first release
Demo flow (what the buyer sees)
- Cook signs in with a magic link
- Pastes last week's WhatsApp menu text
- Parser returns editable dishes with prices
- Cook sets portion caps, cutoff time and pickup window
- Page publishes to a shareable link and QR code
- Buyer orders on mobile; email confirmation is sent
- At cutoff the drop closes and the cook downloads the Drop Sheet
Technical implementation plan
Stack
Architecture
A Next.js app on Vercel reads and writes Supabase Postgres. The parser endpoint calls OpenAI once per paste with a strict JSON schema and Zod validation, falling back to a manual edit screen. Orders rows reference a drop and dish; a Postgres function decrements remaining portions and flips a dish to sold out at zero. The public page at /d/[slug] renders a cached snapshot with a client-side countdown. A Vercel Cron flips drop status at cutoff and emails the cook. Drop Sheet generation aggregates order_items by normalised ingredient text and renders a PDF server-side. Stripe Billing handles the $29/$79 subscriptions, all revenue flowing through the TrustMRR-connected account from the first charge.
Build steps
- Create the Next.js repo and deploy an empty app to Vercel
- Provision Supabase, enable magic-link auth, write schema for cooks, drops, dishes, orders, order_items
- Create Stripe Starter and Pro products and connect TrustMRR, run a $1 test charge
- Build the paste box and the OpenAI parse endpoint with strict JSON schema validation
- Add the manual edit screen for dishes, prices, portion caps and pickup windows
- Build the public order page with countdown and sold-out auto-close
- Add the orders table, paid/unpaid toggle and cutoff timer
- Aggregate ingredients and render the Drop Sheet as PDF and CSV
- Wire Resend confirmations and QR code generation
- Add signup-to-first-drop self-serve flow and end-to-end test with fake orders
AI components
- OpenAI extraction of dishes, descriptions and prices from free-text menus
- Ingredient name normalisation used to aggregate the shopping list
Pricing and monetization
Starter
Entry offerFor Solo home cook running one weekly meal drop
- 1 active meal drop
- Unlimited pre-orders
- Drop Sheet PDF/CSV
- Shareable link and QR code
- Email confirmations
Pro
For Micro-caterer running multiple drops or pickup windows per week
- Up to 4 active meal drops
- SMS reminders to buyers
- Custom domain
- Priority email support
Model: Flat monthly subscription per cook, paid by card, no commission and no per-order fee.
First revenue offer: I built your [dish] menu from [date] into a live pre-order page — here is your link. Keep it after your next drop for $29/month, or let it expire.
Expected ACV: $29
Upsell path: Starter renews monthly; cooks running a second drop or a second pickup window move to Pro at $79. Every paying cook is asked for one referral to another cook in their network, which compounds within a city.
First-customer acquisition
Instagram DM to home cooks who posted a menu in the last seven days.
Where to find them
- Hashtag searches: #homecooklondon, #tiffinlondon, #mealpreplondon, #homecookbrussels
- Commenters on recent home-cook menu posts in the same city
- Facebook groups for home cooks and micro-caterers in London, Brussels and Lagos
- WhatsApp broadcast links posted in cook bios
- Following lists and tagged posts of already-converted cooks
Exact outreach motions
- Build the cook's page by hand from their posted menu before sending anything
- Send the DM with their personal live link, not a pitch
- Follow up once after 48 hours with a screenshot of their own order page
- After their next drop, ask whether it saved time and send the $29 payment link
- Ask every converted cook for one introduction to another cook they know
Message template
Hi [name] — I turned your [dish] menu from [date] into a pre-order page so you can see orders before you shop. It's live and free here: [link]. Want me to add your pickup window?
30-day execution roadmap
Week 1 · Build & validate · 6 days
Repo, auth, payments plumbing
- Create the Next.js repo and deploy an empty app to Vercel.
- Provision Supabase and enable magic-link auth.
- Create Stripe Starter and Pro products and connect TrustMRR with a $1 test charge.
Deliverable: Deployed skeleton with working login and one successful test charge.
Paste-to-menu extraction
- Build the paste box and the OpenAI parse endpoint with strict JSON schema.
- Add validation and a manual edit fallback screen.
- Collect 30 real messy menus into a parser fixture set.
Deliverable: Paste any WhatsApp menu and get editable dishes with prices.
Public mobile page and caps
- Render the public drop page with a live countdown.
- Implement portion caps and sold-out auto-close.
- Store pickup windows and the cutoff timestamp.
Deliverable: A shareable mobile order page that closes itself when sold out or cut off.
Orders, dashboard, shopping list
- Build the orders table and dashboard with a paid/unpaid toggle.
- Aggregate order items into a normalised shopping list.
- Render the Drop Sheet as PDF and CSV with prep schedule and pickup roster.
Deliverable: One-click Drop Sheet export from live orders.
Email, QR, end-to-end test
- Wire Resend buyer confirmations and the cook cutoff notice.
- Generate a QR code per drop.
- Run an end-to-end test with five fake orders and fix blockers.
Deliverable: Feature-complete MVP with no known blockers.
Ship publicly and build the prospect list
- Publish the live product as brand-new software.
- Build a 50-row prospect sheet of cooks who posted a menu in the last seven days.
- Hand-build three sample pages from public menus as proof.
Deliverable: Live product, 50-row prospect sheet, three sample pages.
Week 2 · Launch & first sale · 7 days
First ten hand-built pages
- Build ten cook pages by hand from their posted menus.
- Send ten DMs, each with the cook's own link.
- Log every reply and non-reply in the sheet.
Deliverable: Ten pre-built pages and ten DMs sent.
Volume and message fit
- Send twenty new DMs.
- Follow up the day-7 batch once.
- Rewrite the message based on the first three replies.
Deliverable: Twenty new DMs and the first replies logged.
Sustain the daily DM floor
- Send twenty new DMs.
- Follow up all unopened DMs.
- Answer every reply within the hour.
Deliverable: Thirty total conversations started.
Get a page actually published
- Walk free cooks through publishing their link.
- Check which cooks posted the link to their audience.
- Fix the single biggest step where cooks drop off.
Deliverable: Two cooks with a live published drop.
Ask for the first $29
- Send the Stripe payment link to every cook who ran a drop.
- Offer the first month at $29 with setup already done.
- Follow up same day with a voice note if unopened.
Deliverable: First paying customer, or a written reason why not.
Convert the free cohort
- Send twenty new DMs.
- Convert remaining free setups to paid.
- Record every objection verbatim.
Deliverable: Three paying cooks targeted and objections documented.
Testimonials and case study
- Ask each paying cook for one sentence and a drop-page screenshot.
- Publish a one-page case study.
- Ask each for one referral name.
Deliverable: Five paying cooks targeted, two testimonials captured.
Week 3 · Repeat & systematize · 7 days
Remove the founder from onboarding
- Ship signup-to-first-drop without manual help.
- Add an onboarding email with a paste example.
- Test the flow on a clean browser.
Deliverable: A cook can onboard without the founder.
Accuracy on real menus
- Re-run the 30-menu fixture set and record pass rate.
- Fix the top five failure patterns in prompt and post-processing.
- Add a one-tap correction for prices.
Deliverable: Logged parser accuracy on 30 real menus.
Second drop activation
- Identify which paying cooks ran a second drop.
- Email cooks who did not with their own drop stats.
- Add a duplicate-last-drop button.
Deliverable: Second-drop activation list with actions sent.
Multi-drop support
- Enable up to four active drops per account.
- Add the custom domain field and priority support label.
- Set Pro to $79 in Stripe Billing.
Deliverable: Pro tier purchasable end to end.
Micro-caterer segment
- Build a 25-cook list of micro-caterers posting multi-dish trays.
- Send twenty-five DMs with a hand-built page attached.
- Log reply rate against wave one.
Deliverable: 25 DMs sent to a second segment with reply comparison.
Elasticity on stalled cooks
- Offer $19 first month to five stalled cooks.
- Record acceptance and reasons for refusal.
- Decide whether a launch discount becomes permanent.
Deliverable: Written price-response result on five cooks.
Funnel audit
- Chart DM to reply to page to live drop to paid.
- Find the single worst conversion step.
- Cut or fix that step this week.
Deliverable: One-page funnel review with a decision.
Week 4 · Scale what works · 7 days
Turn customers into a channel
- Ask every paying cook for one introduction.
- Offer one free month for a converted referral.
- Send introduction requests from the cook's own account where allowed.
Deliverable: At least five referral names in the pipeline.
List building
- Pick one second city based on wave-one reply data.
- Build a 40-row prospect list there.
- Prepare two sample pages in local menu style.
Deliverable: 40-row second-city list ready to message.
Outreach
- Send twenty DMs in the second city.
- Follow up day-21 referrals.
- Log reply rate by city.
Deliverable: 20 DMs sent with city-level reply data.
Fix the top cancellation reason
- Interview two cooks who stopped using it.
- Ship one change that addresses the stated reason.
- Email all lapsed cooks the fix.
Deliverable: One churn fix shipped and announced.
Second case study
- Write a case study from a Pro or high-volume cook.
- Publish it and link it in the DM first line.
- Add the Drop Sheet screenshot as social proof.
Deliverable: Second case study live.
Upgrade Starter to Pro
- Identify three Starter cooks running multiple drops.
- Send a one-line upgrade offer with the price difference.
- Enable Pro in their account on acceptance.
Deliverable: At least one Pro upgrade collected.
Convert the pipeline
- Follow up all referral introductions.
- Send twenty new DMs.
- Close or archive every stale thread.
Deliverable: Referral pipeline resolved and 20 DMs sent.
Days 29-30 · Consolidate · 3 days
Second-month collection
- Check which day-11 cohort subscriptions renewed.
- Email any failed payment with a direct link to update the card.
- Record renewal status per cook.
Deliverable: Renewal status for every cohort-one cook.
Last conversions
- Send twenty-five DMs with the strongest case study attached.
- Offer every free user a paid plan one last time.
- Collect any pending payment links.
Deliverable: Final cohort conversions attempted and logged.
Reconcile and submit
- Reconcile TrustMRR against Stripe for the full window.
- Export the revenue and fee report.
- Submit the entry with the verified profit figure.
Deliverable: Entry submitted with a reconciled profit number.
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: 6 paying cooks, organic DM only, no paid marketing.
- Base: 20 paying cooks with a small Pro mix lifting blended ARPU above $29.
- Upside: 45 paying cooks with meaningful Pro uptake and one boosted-post test.
- All figures are 30-day projections from stated assumptions, not verified revenue.
- Blended ARPU exceeds $29 because Pro upgrades and second charges inside the window are averaged in.
- Payment fees assumed at 6% blended: Stripe 2.9% + $0.30 plus non-US card and FX surcharges.
- Ad spend is $0 in conservative and base because the channel is organic DM; $60 in upside covers boosted posts.
- Operating cost covers Vercel, Supabase, Resend, domain and OpenAI parsing, rising with order volume.
- Refunds assumed below 2% of gross; chargebacks near zero with card subscriptions and a clear cancel path.
- No commission on meal sales is collected, so revenue equals subscription charges only.
Conservative
6 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $11
- Paid marketing
- $0
- Hackathon profit
- $175
- Operating costs
- $42
- Business profit
- $133
Base case
20 customers- Refunds
- $29
- Chargebacks
- $0
- Payment fees
- $40
- Paid marketing
- $0
- Hackathon profit
- $611
- Operating costs
- $78
- Business profit
- $533
Optimistic
45 customers- Refunds
- $58
- Chargebacks
- $29
- Payment fees
- $102
- Paid marketing
- $60
- Hackathon profit
- $1,461
- Operating costs
- $165
- Business profit
- $1,296
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $580
- Payment fees (3.9%)
- $23
- Paid marketing
- $0
- Hackathon profit
- $557
- Business profit
- $479
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.
Main risks and validation experiments
Risk 1Instagram DM response rate is too low to reach enough cooks.
Send in small batches, personalise with a live page every time, and follow up once per thread.
Send 20 DMs on day 6 and count replies within 48 hours.
Under 10% reply after 60 DMs: switch to WhatsApp and Facebook cook groups in the same city before day 12.
Risk 2Cooks do not want another tool and stay on WhatsApp plus a spreadsheet.
Build the page for them before asking, so the first interaction is a finished artifact.
Hand-build 10 pages and measure how many cooks post the link to their audience within 7 days.
Under 2 of 10 publish a link: reposition to micro-caterers running three or more drops per week.
Risk 3Menu parsing fails on real messy or multilingual menu text.
Manual edit screen as fallback and a growing fixture set of real menus.
Run 30 real menus collected during outreach through the parser and measure exact item-and-price match.
Under 85% accuracy: sell manual setup as the product and remove the paste promise from messaging.
Risk 4Cooks resist $29 per month.
First month offered after a drop is already done, with setup free and cancel anytime.
Ask five free cooks directly what they would pay and test a $19 first-month offer.
Zero of five accept any paid plan: cut Starter to $19 or switch to a per-drop credit pack.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the TrustMRR-connected Stripe account and run a $1 test charge.
- Create the Next.js repo and deploy an empty app to Vercel.
Output: Live test charge and a deployed empty app URL.
Hours 3-6
- Provision Supabase and write the schema for cooks, drops, dishes, orders, order_items.
- Enable magic-link auth and verify a login end to end.
Output: Working schema and a verified magic-link login.
Hours 7-10
- Build the paste box and the OpenAI parse endpoint with strict JSON schema.
- Add validation and log one parse failure for the fixture set.
Output: Paste a menu and receive structured dishes with prices.
Hours 11-14
- Render the public order page from one hard-coded drop.
- Add the countdown and sold-out state.
Output: A deployed, shareable order page that can be screenshotted for outreach.
Hours 15-18
- Write the first ten prospect rows from hashtag searches, each with the menu text captured.
- Draft the DM template with a placeholder for the personal link.
Output: Ten-row prospect sheet and a finalised DM template.
Hours 19-24
- Run a full manual dry run: parse one real menu, publish, place three fake orders.
- Write down every blocker as tomorrow's task list.
Output: Dry-run notes and a prioritised day-2 task list.
Full 30-day launch report
Read the full generated report
DropPlate — 30-Day Launch Report
1. Product opportunity and positioning
Menu Next Door failed on structure, not on demand. A two-sided marketplace needs cooks and eaters to arrive together, and every new city restarts that cold start; on top of that it placed a non-professional cook's kitchen inside a regulated food transaction, so each market added compliance cost before it added revenue.
DropPlate removes both failure modes by refusing to be a marketplace. It lists no cooks for discovery, takes no commission on meals, processes no payments for the cook, and never touches food. It sells one workflow to one cook who already has buyers: turn the menu they were going to paste into WhatsApp anyway into a pre-order page with portion caps, then hand them the shopping list that follows from the real orders.
The buyer is a solo home cook or micro-caterer in London, Brussels or Lagos running 10-50 pre-ordered meals a week. Their weekly job is unchanged everywhere: post a menu, collect DMs, chase transfers, tally portions in a notes app, shop from memory. It costs 3-6 hours plus one wasted shopping trip per month. They decide alone and they pay by card.
JEV scored this concept 64.3/100 (band C, confidence 0.72). The profile matters more than the total: speed to first revenue is 7.88/10 and solo build feasibility 7.40/10, while market demand (5.12) and defensibility (5.62) are the weak axes. That is the signature of a tool sold by hand into a narrow, already-active niche. Demand is not proven, so these 30 days are a demand test. Defensibility is thin, so the moat is the Drop Sheet output and the switching cost of a live order link, not features.
The real competitor is a Google Form, a notes app and a spreadsheet. DropPlate wins on setup time (paste, not build), on portion caps that close a dish automatically, and on a shopping list computed from orders instead of guessed.
2. Smallest sellable MVP
One page that turns pasted menu text into an order link, plus one PDF. Concretely: magic-link login, a paste box, an editable menu with portion caps and a pickup window, a public mobile order page with countdown and sold-out auto-close, an order dashboard with a paid/unpaid toggle, and the Drop Sheet export. Email confirmation and a QR code complete it.
Excluded on purpose: marketplace discovery, delivery logistics, compliance and labelling, team accounts, native apps, and payment processing on the cook's behalf. The cook keeps their existing bank transfer or payment link; DropPlate only marks paid or unpaid. That exclusion is what keeps operating cost near zero and keeps the product away from the wall that stopped the original.
Demo path: paste a WhatsApp menu, get parsed dishes, set caps, publish, a buyer orders, cutoff passes, Drop Sheet PDF appears.
3. Technical implementation plan
Next.js on Vercel, Supabase Postgres with magic-link auth, Tailwind, OpenAI for parsing, Resend for email, Stripe Billing for the $29 and $79 subscriptions, and a TrustMRR-connected payment account from the first invoice.
Parsing is a single OpenAI call returning strict JSON (item, description, price), schema-validated, with a manual edit screen as fallback so a bad parse costs one correction instead of a cook. Orders are keyed to a drop; a Postgres function decrements remaining portions and flips a dish to sold out at zero. The public page renders a cached snapshot with a client-side countdown. Cutoff is a stored timestamp; a Vercel Cron flips status and emails the cook. Drop Sheet generation aggregates order items by normalised ingredient text and renders a PDF server-side. Public pages use an unguessable slug, so nothing depends on SEO.
The hardest risk is parser accuracy on messy, mixed-language WhatsApp text with prices like "£8" or "2 for £15". Mitigation is the edit screen plus a 30-message fixture set assembled on day 2.
4. Pricing and monetization
Starter is $29/month: one active drop, unlimited pre-orders, Drop Sheet PDF/CSV, link and QR, email confirmations. Pro is $79/month: four active drops, SMS reminders, custom domain, priority support. Monthly card billing, cancel anytime, no commission and no per-order fee. At ten orders of $12 a drop, $29 is roughly two orders of margin, which sits below the pain threshold.
The first revenue offer is a page already built from their last menu: "keep it after your next drop for $29/month, or let it expire." That converts on demonstrated output instead of a promise. Upsell runs Starter to Pro when a cook adds a second drop, and every paying cook is asked for one referral, which compounds inside a city.
5. First-customer acquisition
One channel: Instagram DM. No ads, no SEO, no marketplace.
Build a list of 50 cooks who posted a menu in the last seven days using hashtag searches (#homecooklondon, #tiffinlondon, #mealpreplondon, #homecookbrussels) and the commenters on those posts. Build each page by hand from the posted menu before messaging. The DM carries their own live link, not a pitch. Follow up once after 48 hours with a screenshot of their order page, then ask for $29 after their next drop.
Week-one goal: 10 hand-built pages, 10 DMs sent, at least 3 replies, and 3 cooks running a live drop by day 7. From day 6 onward the daily floor is 20 new DMs and 10 follow-ups before any code.
6. 30-day execution roadmap
Days 1-5 are build only. Parser on day 2, public order page on day 3, Drop Sheet on day 4, email and QR on day 5.
Day 6 is launch plus list building: product public, 50-row prospect sheet, three sample pages. Days 7-13 are manual onboarding and volume outreach, with the first payment ask on day 11 and five paying cooks targeted by day 13.
Days 14-20 shift from manual to machine: self-serve signup on day 14, parser accuracy measured on 30 real menus on day 15, Pro tier live on day 17, a second outreach wave on day 18, a $19 price test on day 19, and a funnel audit on day 20 that kills the worst step.
Days 21-27 are referrals, a second city, a churn fix and the first Pro upgrade. Days 28-30 reconcile TrustMRR against Stripe, chase failed renewals and submit.
7. Revenue and profit scenarios (projections only)
All three scenarios are projections from stated assumptions. None of this is verified revenue, and no customers exist at the start.
Conservative: 6 paying cooks at a blended $31 first-month ARPU gives $186 gross. Base: 20 cooks at $34 gives $680. Upside: 45 cooks at $38 with real Pro uptake gives $1,710. Blended ARPU above $29 reflects Pro upgrades and second charges inside the window; it is a modelling choice, not an observed average.
Processing is assumed at 6% blended (Stripe 2.9% + $0.30 plus non-US card and FX surcharges). Ad spend is $0 in conservative and base because the channel is organic DM, and $60 in upside for boosted posts. Operating cost covers Vercel, Supabase, Resend, domain and OpenAI parsing at $42, $78 and $165 as volume rises.
Hackathon profit subtracts refunds, chargebacks, fees and ad spend only; hosting and AI delivery costs sit outside ranking but inside business profit. The honest reading: the upside lands near $1.4k of hackathon profit, the base near $600, and the conservative case under $200.
8. Risks and validation experiments
DM response rate. Test 20 DMs on day 6 and count 48-hour replies. Under 10% after 60 DMs means moving to WhatsApp and Facebook cook groups before day 12.
Cooks do not want another tool. Hand-build 10 pages and count how many post the link within 7 days. Under 2 of 10 means repositioning to micro-caterers running three or more drops a week.
Parser failure. Run 30 real menus through the parser and measure exact item-and-price match. Under 85% means selling manual setup as the product and dropping the paste promise.
Price resistance. Ask five free cooks what they would pay and test a $19 first month. Zero of five accepting any paid plan means cutting Starter to $19 or moving to a per-drop credit pack.
9. First 24-hour action plan
Hours 1-2: TrustMRR-connected Stripe account, $1 test charge, deployed Vercel app. Hours 3-6: Supabase schema and magic-link auth. Hours 7-10: paste box and parse endpoint with strict JSON. Hours 11-14: public order page from one hard-coded drop. Hours 15-18: first ten prospect rows and the final DM template. Hours 19-24: full manual dry run and a prioritised day-2 task list.
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 →Kitchen Sheet
Kitchen Sheet turns a cloud kitchen's messy WhatsApp lunch orders into a print-ready kitchen prep sheet, one label per order, and a delivery run order in under 60 seconds.
Bulletin Nounou
Bulletin Nounou turns a French childminder's month of attended days into a ready-to-send bulletin de salaire PDF plus a copy-paste Pajemploi figure card, in under three minutes per child.
Mise Packet
Turns a personal chef's weekly menu into a client-ready prep packet — branded menu, aisle-sorted consolidated shopping list with pack-size rounding, and a batch-cook run sheet — in minutes instead of an evening.