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

DropCount Lunch Desk

DropCount turns a small caterer's daily single menu into a shareable order page with a hard cutoff, then produces one kitchen drop sheet with exact per-dish counts and per-building drop groupings.

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.

Speculative6.44/10
MVP build (solo)
4 days
Launch price
$79 · monthly
Sales to $1,000 revenue
13 customers
First paying customer
Instagram and Google Maps prospecting of small kitchens that post office-lunch content in two dense business districts, followed by a personalised DM containing a live DropCount order page and drop sheet built from that kitchen's own posted dish.
Who pays

Owner-operator of a 1-10 person independent caterer, traiteur, tiffin service or cloud kitchen delivering weekday lunch to offices of 15-60 people, triggered by a recurring weekly drop request or a first multi-floor quote.

Biggest execution risk

Market demand 4.5/10

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

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

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

Your first 24 hours

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

0/10
Entry price
$79
Solo build
4 days
30d base revenue
$2,370
30d hackathon profit
$2,213
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a 1-10 person independent caterer, traiteur, tiffin service or cloud kitchen delivering weekday lunch to offices of 15-60 people, triggered by a recurring weekly drop request or a first multi-floor quote.

Why now

Small kitchens already run office lunch on WhatsApp and a spreadsheet that is stale by 09:00, and the holiday office-lunch season makes count errors expensive right now; a working page can be built from the kitchen's own posted dish today, so no procurement, brand or trust cycle is needed.

Problem

Orders arrive as scattered WhatsApp replies with names, floors, dietary notes and changes of mind; the owner hand-counts before cooking, has no enforced cutoff, over- or under-prepares the single daily dish, and risks the recurring office account on a wrong count or wrong floor list.

Solution

Owner publishes today's dish, price, capacity, cutoff and up to five drop zones; gets a public no-login order page link plus a paste-ready WhatsApp message; at cutoff the page locks and a one-page drop sheet PDF prints with per-dish totals, orders grouped by building and floor, allergen flags per person and per-office subtotals, plus CSV export.

Differentiation · Google Forms plus a spreadsheet has no enforced cutoff, no live count, no grouped floor list and no printable drop sheet; multi-restaurant marketplaces sell to diners, not to the kitchen's own operations.

1. Product opportunity and positioning

The buyer is narrow on purpose: the owner-operator of a 1-10 person caterer, traiteur, tiffin service or cloud kitchen that already delivers — or is trying to win — weekday lunch to offices of 15-60 people. The trigger event is concrete: an office asks for a recurring weekly lunch drop, or the kitchen quotes a multi-floor delivery for the first time. At that moment the owner runs lunch on WhatsApp screenshots and a spreadsheet that is stale by 09:00. There is no enforced cutoff and no reliable count, so they either over-cook the single daily dish or arrive with the wrong number and the wrong floor list, and the recurring account is at risk.

DropCount replaces that with one link, one cutoff, one printable drop sheet. Positioning is operational, not platform: the kitchen keeps its customers, its food and its meal money. DropCount never touches diner payments, delivery routing or office discovery, which is why it can be sold in a DM rather than through procurement.

JEV scored this concept 64.4/100 (band C, confidence 0.78). The strengths are speed to first revenue (8.46/10) and solo build feasibility (7.74/10): a live order page can be generated from a kitchen's own posted dish in about 90 seconds, before any trust cycle exists. The weak point is market demand (4.49/10). Whether an owner-operator used to spreadsheets will pay $79/month is the assumption this plan tests in week one rather than asserts. The answer to that weakness is the narrow wedge plus the visible artifact — a drop sheet PDF printed in under two minutes — and, if the week-one reply rate does not support it, the kill criteria in section 8.

The addressable behaviour is already there: these kitchens post dishes publicly on Instagram and Maps daily, and each already has at least one office contact to send a link to. The product does not need to supply demand, only to remove the counting step.

Section 2 of 8

Smallest sellable MVP

A live order page built from one kitchen's own posted dish, with a hard cutoff and a one-page drop sheet PDF that prints exact per-dish and per-building counts.

Must-have features

  • One-screen daily menu editor: dish name, optional photo, unit price, portion capacity, cutoff time, up to five named drop zones
  • Public no-login order page on a shareable link with visible countdown to cutoff: name, drop zone, quantity, allergen, note
  • Hard cutoff enforcement at the server plus a live count dashboard per drop zone
  • One-page kitchen drop sheet PDF: per-dish totals, orders grouped by drop zone, allergen flags per person, per-office subtotal
  • WhatsApp-ready share text generator packaging dish, price, link and cutoff
  • CSV export of the day's orders
  • Stripe Checkout with 14-day trial gated after three published menus, plus a $199 one-time plan
  • Branded order page: kitchen name, logo upload, accent colour

Explicitly out of scope

  • Collecting payments from office staff or diners
  • Delivery routing, driver app, GPS or dispatch
  • Kitchen marketplace or office discovery
  • POS, accounting or inventory integrations
  • Nutrition database or recipe costing
  • Multi-kitchen franchise management, roles or permissions

Demo flow (what the buyer sees)

  1. Founder opens the kitchen's public Instagram post and copies the dish name and price
  2. Creates a workspace, publishes the menu with cutoff 10:30 and three drop zones
  3. Copies the order page link and the generated WhatsApp text
  4. Submits eight test orders across three zones, including two allergen notes
  5. Shows the live count dashboard before cutoff
  6. Waits for cutoff, shows the page locked
  7. Downloads the one-page drop sheet PDF and CSV
Build plan

Technical implementation plan

Stack

Next.js on Vercel (single app, serverless routes)Supabase Postgres with email magic-link auth for owner login onlyStripe Checkout and Billing PortalReact-PDF for the drop sheetResend for transactional emailTailwind CSS, mobile-first order pageVercel Cron for the cutoff reminder job

Architecture

One Next.js app on Vercel. Supabase holds kitchens, menus, drop_zones and orders; the public order page is a server-rendered route keyed by kitchen slug that reads the active menu and writes orders through a serverless handler. Cutoff is enforced server-side by comparing menu.cutoff_at in the kitchen's timezone, so the browser clock cannot be spoofed. A single PDF route loads the day's orders, groups them by drop zone, and renders React-PDF to a one-page buffer that is streamed to the owner. Stripe webhooks flip the plan state; a menu-publish counter gates the trial at three published menus. Vercel Cron sends a cutoff reminder to the owner each morning at cutoff minus 45 minutes.

Build steps

  1. Scaffold Next.js on Vercel, create Supabase project, run schema migration for kitchens, menus, drop_zones, orders
  2. Add owner magic-link auth and a single dashboard shell
  3. Build the daily menu editor with dish, price, capacity, cutoff and five drop zones
  4. Build the public order page at /k/{slug} with countdown and no-login order form
  5. Add live count dashboard, per-zone totals and server-side cutoff lock returning 410
  6. Generate the drop sheet PDF and CSV export
  7. Add branded page settings (logo upload, accent colour)
  8. Wire Stripe Checkout for $79 monthly and $199 one-time, plus trial gate on menu publish count
  9. Add Resend cutoff reminder and Vercel Cron job
  10. Run a 12-order end-to-end test on a phone, then two real kitchen demos

AI components

  • No LLM in the core loop; the WhatsApp share text is templated from the menu fields.
  • Later, not in the 30 days: optional parsing of a WhatsApp screenshot into menu fields.
Hardest technical risk: The drop sheet must always fit on exactly one page with variable row counts, allergen lines and per-office subtotals; overflow during a real lunch rush breaks the core promise. Mitigation: fixed layout bands with a compact row mode above 60 orders, tested at 10, 40 and 80 orders.
Section 3 of 8

Pricing and monetization

Kitchen

Entry offer
$79 / month

For Owner-operator of a small caterer or meal-prep kitchen already doing or quoting weekday office lunch drops

  • Unlimited daily single-menu order pages
  • Hard cutoff enforcement and live count dashboard
  • One-page kitchen drop sheet PDF per day
  • WhatsApp share text generator
  • CSV export of daily orders

Opening Month

$199 one-time

For Kitchen owners who refuse subscriptions or are testing a single holiday-season office contract

  • Branded order page with logo and accent colour
  • 10 saved menu templates and five pre-configured drop zones
  • Branded drop sheet PDF
  • 30 days of full Kitchen features

Model: Monthly subscription for kitchens running recurring office drops, plus a one-time opening-month plan for owners who refuse subscriptions.

First revenue offer: 14 days free on the Kitchen plan, then $79/month, or $199 one-time for the Opening Month plan — Stripe link sent in the same reply thread as the personalised demo page.

Expected ACV: $79

Upsell path: Monthly kitchens renew after the 14-day trial; one-time Opening Month buyers convert to monthly when the office contract renews, and referral asks after each payment bring additional kitchens from the same supplier WhatsApp group.

Target customers
30
Revenue model
$2,370
Costs
$120
Profit model
$2,250
Section 4 of 8

First-customer acquisition

Primary channel

Instagram and Google Maps prospecting of small kitchens that post office-lunch content in two dense business districts, followed by a personalised DM containing a live DropCount order page and drop sheet built from that kitchen's own posted dish.

Where to find them

  • Instagram hashtags #traiteur, #plateaurepas, #tiffin, #mealkitchen, #officecatering
  • Google Maps listings for caterers and traiteurs in two dense business districts
  • Instagram posts tagged at office addresses showing lunch drops
  • Recent 'plateau repas' story highlights from kitchens with 500-10,000 followers

Exact outreach motions

  • Build a 400-row list with owner name, handle, city and one recent posted dish
  • Generate a live order page and drop sheet screenshot from each of the first 60 kitchens' own dishes
  • Send 30-40 personalised DMs per day with the screenshot and the demo link, no deck
  • Follow up on day 2 and day 5 with a different menu day from the same kitchen's feed, then stop after three touches
  • On reply, send both plans and the Stripe link in the same thread within 10 minutes
  • After each payment, ask for one intro to another kitchen in the same supplier group

Message template

Hi [name] — I built your Tuesday dish ([dish]) as an order page with a 10:30 cutoff and three drop zones. Here is the drop sheet it printed: [screenshot]. Want the link for tomorrow's menu? 14 days free, then $79/month or $199 one-time.
Week-one goal: 400-row prospect list built, 20 personalised demo pages generated, 70 personalised DMs sent, at least 6 replies and 3 Stripe links out.
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

Deployed skeleton with auth and schema

  • Create Next.js app on Vercel and Supabase project
  • Define tables: kitchens, menus, drop_zones, orders
  • Wire owner magic-link login

Deliverable: Deployed app with empty dashboard and migrated database

Day 2Menu and order page

Owner publishes a menu and shares a link

  • Build one-screen menu editor with cutoff and five drop zones
  • Render public order page at /k/{slug} with countdown
  • Test at 375px width on a phone

Deliverable: Live order page rendered from a real menu

Day 3Orders and cutoff

Collect orders and lock at cutoff

  • Build order form: name, drop zone, quantity, allergen, note
  • Add live count dashboard per drop zone
  • Enforce cutoff server-side, return 410 after lock

Deliverable: Orders counted live; page locks at cutoff

Day 4Drop sheet

One-page PDF, share text, CSV

  • Generate React-PDF drop sheet with totals, zone grouping, allergen flags, per-office subtotal
  • Build WhatsApp share text generator
  • Add CSV export endpoint

Deliverable: Printable drop sheet PDF and CSV from 12 test orders

Day 5PaywallMVP shipped

Take money (MVP deadline)

  • Wire Stripe Checkout for $79 monthly and $199 one-time
  • Gate trial after three published menus; test both plans in test mode
  • Add logo upload and accent colour

Deliverable: MVP live; both plans purchasable

Day 6Prospect list

400 kitchens in two districts

  • Mine Instagram hashtags for office-lunch kitchens
  • Pull Google Maps caterer listings in two business districts
  • Log owner name, handle, city and one recent dish per row

Deliverable: 400-row prospect spreadsheet

Day 7Demo assets

Personalised pages for first 20

  • Build an order page from each of 20 kitchens' own posted dish
  • Screenshot each generated drop sheet
  • Send 10 DMs as a soft test of the template

Deliverable: 20 personalised demos and 10 DMs sent

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

First real sending day

  • Send 30 personalised DMs with each kitchen's own demo link
  • Log reply status per row
  • Fix the first onboarding blocker a reply exposes

Deliverable: 30 DMs sent, 30 live demo pages

Day 9Replies

Handle conversations fast

  • Send 40 personalised DMs
  • Answer every reply within 10 minutes with both plans and the Stripe link
  • Book three 10-minute screen shares

Deliverable: 40 DMs, 6+ live conversations

Day 10Follow-up

Second touch on silent leads

  • Send 40 new DMs
  • Follow up on day-2 leads with a different menu day
  • Ship one requested fix

Deliverable: 40 DMs and 30 follow-ups sent

Day 11Proof

Convert warm replies

  • Send 40 DMs
  • Run three screen shares and generate the kitchen's page live on the call
  • Send Stripe links to the three warmest leads

Deliverable: 3 live demos delivered, 3 payment links out

Day 12First saleFirst sale target

Collect the first payment

  • Send Stripe links to the 12 warmest leads with a pay-today framing
  • Offer the $199 Opening Month to anyone hesitating on subscription
  • Record first payment received

Deliverable: First paid kitchen inside the contest window

Day 13Onboarding

Make the first kitchens succeed

  • Onboard each paying kitchen in 15 minutes on a call
  • Publish their real tomorrow menu and share link
  • Send them the drop sheet from their first live day

Deliverable: Paying kitchens live with a real published menu

Day 14Week two review

Fix what blocks payment

  • Ship the top three requested fixes
  • Build the second-city prospect list
  • Recheck PDF layout at 10, 40 and 80 orders

Deliverable: Second-city list and a hardened PDF

Week 3 · Repeat & systematize · 7 days
Day 15Second city

Repeat the proven message

  • Send 40 DMs into the second district
  • Refresh demo pages with each kitchen's newest dish
  • Log which dish type gets replies

Deliverable: 40 DMs, reply-rate breakdown by dish type

Day 16Referrals

Ask after payment

  • Ask each paying kitchen for one intro
  • Send 30 DMs
  • Ship the cutoff reminder email if not live

Deliverable: 3 referral asks sent, 30 DMs

Day 17Proof artifact

Anonymised drop sheet in the DM

  • Create an anonymised drop sheet example from a live kitchen
  • Attach it to all new DMs
  • Send 40 DMs

Deliverable: Updated DM with proof image, 40 sent

Day 18Objections

Learn the real reason for no

  • Call three owners who did not reply
  • Send 40 DMs
  • Rewrite one paragraph of the message from call notes

Deliverable: Objection log with three verbatim reasons

Day 19Trial conversion

Push trials to the paywall

  • Email trial kitchens before their third published menu
  • Send 40 DMs
  • Send Stripe link to every trial older than five days

Deliverable: Trial-to-paid pushes sent to all trials

Day 20Volume

Stay on the only channel

  • Send 40 DMs
  • Follow up on day-2 and day-5 touches
  • Collect a one-line quote from any paying kitchen

Deliverable: 40 DMs and follow-ups; first quotes

Day 21Week three review

Stability and money

  • Reconcile Stripe charges against TrustMRR records
  • Harden cutoff lock and PDF against edge cases
  • Send 30 DMs

Deliverable: Reconciled payment log, hardened release

Week 4 · Scale what works · 7 days
Day 22Holiday angle

Sell the one-time plan

  • Send 40 DMs pitching the $199 Opening Month for holiday office contracts
  • Target kitchens posting seasonal menus
  • Update share text to mention the one-time option

Deliverable: 40 DMs with the one-time offer

Day 23Volume

Keep the daily send

  • Send 40 DMs
  • Follow up with anyone who opened but did not reply
  • Ship a fix from support notes

Deliverable: 40 DMs and 20 follow-ups

Day 24Referral loop

Turn buyers into leads

  • Request one intro from every paying kitchen
  • Send 40 DMs
  • Add referral line to the onboarding email

Deliverable: Referral request sent to all paying kitchens

Day 25Volume

Second half of the list

  • Send 40 DMs into untouched rows
  • Rebuild demos for the 20 warmest silent leads
  • Log all replies in one sheet

Deliverable: List 70% contacted, warm-lead shortlist

Day 26Support batch

Keep support under 30 minutes

  • Batch-answer support in one 30-minute window
  • Send 40 DMs
  • Publish two how-to screenshots for owners

Deliverable: Support backlog zero, 40 DMs sent

Day 27Final push

Largest send day

  • Send 50 DMs
  • Send pay-today offer to all warm leads
  • Confirm no pricing experiments remain open

Deliverable: 50 DMs, all warm leads re-contacted

Day 28Week four review

Close every open trial

  • Reconcile revenue and fees in Stripe
  • Send Stripe links to every remaining trial
  • Send 30 DMs

Deliverable: Clean revenue ledger, all trials invoiced

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

Call every warm lead

  • Call or voice-note the 20 warmest leads
  • Send Stripe link with a pay-before-close framing
  • Fix any last checkout failure

Deliverable: All warm leads contacted with a payment link

Day 30Close-out

Verify and log

  • Verify every charge landed before Wed 16 Dec 13:00 UTC
  • Refund any accidental or duplicate charge
  • Export the revenue CSV and log what converted

Deliverable: Verified revenue record and a written post-mortem

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • All three scenarios are projections from stated assumptions, not verified revenue or existing customers.
  • Conservative: 8 paying kitchens from roughly 400 personalised DMs and follow-ups, an implied ~2% close rate on cold DM.
  • Base: 30 paying kitchens, matching the concept's 7.5% implied close rate on 400 personalised demo DMs.
  • Upside: 45 paying kitchens with a blended ARPU of $92 because a share buys the $199 Opening Month plan instead of $79 monthly.
  • ARPU is computed on collected cash inside the contest window only; monthly renewals after Dec 16 are excluded.
  • Payment fees assume Stripe at 2.9% + $0.30 per charge (roughly 3.3% blended on these basket sizes).
  • Ad spend is zero in Conservative and Base because the channel is organic outreach; Upside assumes $150 on boosted posts and one paid creator mention.
  • Operating costs cover Vercel, Supabase, Resend, domain and PDF rendering; they are excluded from hackathon profit but included in business profit.
  • No refund assumptions in Conservative; Base assumes one monthly refund; Upside assumes three refunds and one chargeback.
  • Each sale is priced far above marginal delivery cost, so no unit is sold below cost.

Conservative

8 customers
$632
collected revenue · avg payment $79
Refunds
$0
Chargebacks
$0
Payment fees
$21
Paid marketing
$0
Hackathon profit
$611
Operating costs
$25
Business profit
$586

Base case

30 customers
$2,370
collected revenue · avg payment $79
Refunds
$79
Chargebacks
$0
Payment fees
$78
Paid marketing
$0
Hackathon profit
$2,213
Operating costs
$60
Business profit
$2,153

Optimistic

45 customers
$4,140
collected revenue · avg payment $92
Refunds
$237
Chargebacks
$92
Payment fees
$134
Paid marketing
$150
Hackathon profit
$3,527
Operating costs
$95
Business profit
$3,432

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$2,370
Payment fees (3.9%)
$92
Paid marketing
$0
Hackathon profit
$2,278
Business profit
$2,218

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. Hackathon profit excludes hosting and tooling; business profit deducts them. Nothing here is a customer, a signed contract or collected money.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM response rates to small food businesses are low enough that 400 contacts produce fewer than 8 payments.

Mitigation

Send 30-40 personalised DMs per day from day 7, with a demo built from the kitchen's own dish, and log reply rate per dish type.

Validation experiment

Send 70 DMs in week one and measure reply rate and Stripe-link requests before building anything beyond the MVP.

Kill criteria

If 70 personalised DMs produce fewer than 3 replies and 0 Stripe-link requests by day 11, change the message and the demo artifact before spending more days on outreach.

Risk 2The Instagram or email account used for outreach gets rate-limited, cutting the only acquisition channel.

Mitigation

Keep a second Instagram account and an email alias ready; move warm replies to WhatsApp immediately.

Validation experiment

Warm up both accounts in week one and cap sends at 40 per day per account.

Kill criteria

If both accounts are restricted for more than 48 hours with no working backup, switch the same message to Google Maps phone numbers and email.

Risk 3Owners decide Google Forms plus a spreadsheet is good enough once they see the order page concept.

Mitigation

Lead the demo with the drop sheet PDF and the locked cutoff, not the order form; those are the parts a form cannot do.

Validation experiment

Ask every non-replying owner one question: what does your 09:00 count look like today, and show the sheet next to it.

Kill criteria

If 10 owners explicitly say the form is enough and none converts, the wedge is wrong and the drop sheet must be sold as a standalone daily artifact.

Risk 4Office staff keep ordering by WhatsApp reply instead of the link, leaving the drop sheet incomplete.

Mitigation

Generate a ready-to-paste message the owner forwards, with the countdown and cutoff stated in one line.

Validation experiment

In the first three paying kitchens, compare link orders against WhatsApp replies on day one and day two.

Kill criteria

If fewer than 60% of orders arrive through the link in a paying kitchen, add a manual order-entry box for the owner by day 20.

Risk 5Food-service cash flow is tight, so free trials push payment past the contest deadline.

Mitigation

Offer the $199 one-time plan with pay-today framing to hesitant leads from day 12.

Validation experiment

Split the first 20 warm leads between trial-first and pay-today offers and compare conversion inside the window.

Kill criteria

If trial-first converts below half of pay-today by day 20, drop trial-first for the remaining list.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel project, Supabase project and repository
  • Run the schema migration for kitchens, menus, drop_zones and orders

Output: Deployed skeleton with a live database

Hours 2-4

  • Build the one-screen menu editor
  • Add drop-zone fields and cutoff picker

Output: Owner can publish a menu

Hours 4-6

  • Build the public order page at /k/{slug}
  • Add the countdown and no-login order form

Output: A shareable order page accepting orders

Hours 6-8

  • Add the live count dashboard
  • Enforce cutoff server-side

Output: Page locks at cutoff with live counts

Hours 8-10

  • Add the React-PDF drop sheet route
  • Generate the WhatsApp share text

Output: A one-page drop sheet PDF from test orders

Complete report

Full 30-day launch report

Read the full generated report

DropCount Lunch Desk — 30-Day Solo Launch Report

Window: Mon 16 Nov 2026 13:00 UTC to Wed 16 Dec 2026 13:00 UTC. One founder. Ranked by verified profit, and only money collected inside the window counts.

1. Product opportunity and positioning

The buyer is narrow on purpose: the owner-operator of a 1-10 person caterer, traiteur, tiffin service or cloud kitchen delivering weekday lunch to offices of 15-60 people. The trigger is concrete — an office asks for a recurring weekly drop, or the kitchen quotes a multi-floor delivery for the first time. At that moment the owner runs lunch on WhatsApp screenshots and a spreadsheet that is stale by 09:00: no enforced cutoff, no reliable count, no floor list. They over-cook the single daily dish or arrive with the wrong number, and the recurring account is at risk.

DropCount replaces that with one link, one cutoff, one printable drop sheet. Positioning is operational, not platform: the kitchen keeps its customers, its food and its meal money. DropCount never touches diner payments, routing or discovery, which is why it can be sold in a DM rather than through procurement.

JEV scored this concept 64.4/100, band C, confidence 0.78. Speed to first revenue (8.46) and solo build feasibility (7.74) are the strengths: a live order page can be generated from a kitchen's own posted dish in about 90 seconds. Market demand (4.49) is the weak point. Whether an owner used to spreadsheets pays $79/month is tested in week one, not assumed. Section 8 defines when to change the wedge.

2. Smallest sellable MVP

The sellable unit is one loop: owner publishes today's dish, price, capacity, cutoff and up to five drop zones; receives a public no-login order page plus a paste-ready WhatsApp message; office staff order with name, zone, quantity and allergen note; the page locks at cutoff; a one-page PDF prints per-dish totals, orders grouped by building and floor, allergen flags per person and per-office subtotals; CSV exports for the books. Branding (logo, accent colour) is in scope because the link must look like the kitchen's own, not a third-party tool. Nothing else ships before day 5.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres with email magic-link auth for the owner only, Stripe Checkout, React-PDF, Resend, Tailwind, and a Vercel Cron job for the cutoff reminder. The public order page is a server-rendered route keyed by kitchen slug. Cutoff is enforced server-side against the kitchen's timezone so the browser clock cannot be spoofed. The PDF route groups the day's orders by drop zone and streams a one-page buffer. A Stripe webhook flips plan state; a menu-publish counter gates the trial at three published menus.

Hardest technical risk is the PDF: it must always fit one page with variable rows and allergen lines. Use fixed layout bands with a compact row mode above 60 orders and test at 10, 40 and 80 orders. There is no LLM in the core loop; the share text is templated from menu fields. Ordering a dish list out of a screenshot is a later feature, not a day-30 feature.

4. Pricing and monetization

Two prices, no negotiation: $79/month for the Kitchen plan, and $199 one-time for Opening Month, aimed at owners who refuse subscriptions or are testing a single holiday office contract. The monthly plan sits under a discretionary approval threshold, so no procurement appears. The offer sent this week is 14 days free then $79/month, or $199 one-time — Stripe link in the same reply thread as the personalised demo page. Revenue grows by converting one-time buyers at contract renewal and by referral asks after each payment.

5. First-customer acquisition

One channel: Instagram and Google Maps prospecting of small kitchens posting office-lunch content in two dense business districts, followed by a personalised DM. Build a 400-row list with owner name, handle, city and one recent dish. For the first 60, spend 90 seconds generating a live order page and drop sheet screenshot from that kitchen's own posted dish. The message is one link and one screenshot, no deck. Follow up on day 2 and day 5 with a different menu day, then stop after three touches. Reply within 10 minutes. Week-one goal: 400 rows, 20 demos, 70 DMs, 6 replies, 3 Stripe links.

6. 30-day execution roadmap

Days 1-5 (build): the MVP ships on day 5 with both Stripe plans purchasable. Do not start outreach before the paywall works, or replies will hit a dead end.

Days 6-7 (list and demos): 400 prospects, 20 personalised demo pages with screenshots.

Days 8-13 (first revenue): 30-40 DMs per day, day-2 and day-5 follow-ups, three live screen shares. Day 12 is the first-sale target: Stripe links to the 12 warmest leads with pay-today framing and the $199 option for hesitators. Day 13 onboards paying kitchens in 15 minutes each so their first real drop sheet is generated.

Days 14-21 (repeat and harden): second district, anonymised drop sheet as proof in every DM, objection calls, trial pushes before the third published menu, payment reconciliation against TrustMRR. Day 21 is the stability gate — if the PDF or cutoff lock fails, fix it before more volume.

Days 22-28 (holiday angle and volume): pitch the $199 Opening Month to kitchens posting seasonal menus, 40-50 DMs per day, referral asks after every payment, support batched into one 30-minute window.

Days 29-30 (close): call or voice-note the 20 warmest leads, invoice every open trial, verify each charge landed before 16 Dec 13:00 UTC, refund anything accidental, export the ledger.

7. Revenue and profit scenarios

All figures are projections, not verified revenue. Conservative: 8 kitchens, $79 ARPU, $632 gross, $21 fees, $25 operating — roughly a 2% close rate on cold DM. Base: 30 kitchens, $2,370 gross, $79 refunded, $78 fees, $60 operating — the concept's 7.5% implied close rate. Upside: 45 kitchens at a $92 blended ARPU because some buy the $199 plan, $4,140 gross, $237 refunds, $92 chargeback, $134 fees, $150 boosted posts, $95 operating.

Hackathon profit is gross minus refunds, chargebacks, fees and ad spend; hosting, domains and tooling are not deducted there and only reduce business profit. Fees assume Stripe at 2.9% + $0.30. Every price sits far above marginal delivery cost, so nothing is sold below cost.

8. Risks and validation experiments

The demand risk dominates. Experiment one: 70 personalised DMs by day 11 and measure replies and Stripe-link requests; fewer than 3 replies and 0 link requests means stop and rebuild the message around the drop sheet artifact. Experiment two: ask non-replying owners what their 09:00 count looks like, then show the printed sheet beside it; if 10 say a Google Form is enough and none converts, sell the drop sheet as a standalone daily artifact rather than a platform. Experiment three: split the first 20 warm leads between trial-first and pay-today and compare in-window conversion; if trial-first converts below half, drop it for the remaining list. Two operational risks sit alongside: account restriction on the only channel (keep a second Instagram account and an email alias warm, cap 40 sends per account per day) and office staff ordering by WhatsApp instead of the link (measure link share in the first three paying kitchens; below 60%, add manual order entry by day 20).

9. First 24-hour action plan

Hours 1-2: create the Vercel and Supabase projects, run the schema migration. Hours 2-4: menu editor with cutoff and drop zones. Hours 4-6: public order page with countdown and no-login form. Hours 6-8: live count dashboard and server-side cutoff lock. Hours 8-10: React-PDF drop sheet and WhatsApp share text. By hour 10 a kitchen's own dish can be turned into a working page and a printable sheet — the artifact the entire acquisition message depends on.

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 →