FridgeDrop Prep
FridgeDrop Prep turns a small caterer's week of office meal orders into one print-ready Monday Prep & Drop Sheet: batch totals per recipe, container counts, per-office packing labels and a delivery sheet grouped by postcode.
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.
The owner or ops lead of a 1-20 person independent meal-prep or office-lunch catering company that drops individually packed meals into 5-50 office fridges, in the US, UK, Ireland or Canada.
Market demand 4.9/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; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/10.
Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.
Your first 24 hours
12 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
The owner or ops lead of a 1-20 person independent meal-prep or office-lunch catering company that drops individually packed meals into 5-50 office fridges, in the US, UK, Ireland or Canada.
Why now
Office-lunch volume is back and small independents absorbed it without buying software; the task is weekly, the buyer approves $99 alone, and the deliverable is a printed sheet, so there is no integration, hardware or procurement step.
Problem
Orders arrive as WhatsApp messages, emailed spreadsheets and Google Forms, then someone manually totals meals per SKU, converts recipes to batch quantities, hand-writes container labels and rebuilds the drop list every single week.
Solution
The caterer pastes or uploads the week's orders into a fixed schema, maps each SKU to a recipe with portions-per-batch and container size, and exports a label PDF plus a drop sheet PDF/CSV grouped by delivery day and postcode.
1. Opportunity and positioning
The buyer is not a facilities team. It is the owner of a 1-20 person independent caterer that packs individual meals into 5-50 office fridges. They already sell, already have orders, and already lose money on one recurring manual task.
That task is Monday prep. Orders live in WhatsApp threads, emailed spreadsheets and Google Forms. Someone totals meals per SKU by hand, converts recipes into batch quantities, writes container labels, tags allergens, and rebuilds a drop list from memory. Two to five hours of owner time a week, and the failure mode is expensive: overproduction on slow SKUs, a missed item, a mislabelled allergen container, a late drop. Any of those threatens the office contract that pays the bills.
Two trigger events make the pain acute enough to buy: winning a new office contract that pushes volume past what a spreadsheet handles, and a Monday prep error that already cost money. The outreach and the sample sheet are built around those two events, not around "caterers" in general.
FridgeDrop Prep converts the order file they already collect into one artifact: a Monday Prep & Drop Sheet. It contains batch totals per recipe rounded to whole batches with leftover portions shown, container counts by size per SKU and per office, one print-ready label sheet per office carrying pack date and allergen tags, and a drop sheet grouped by delivery day and postcode. Nothing to onboard offices onto, no hardware, no data migration, no ordering portal.
The generic alternatives are weak at exactly this output. A spreadsheet template needs rebuilding every week and cannot print labels. A catering ERP module is priced and shaped for a much larger kitchen. A generic label printer app does labels but has no idea what a batch of recipe X yields. Combining order totals, recipe batching, labels and routing in one export is the whole wedge.
JEV scored this concept 65.1/100 (band B), with market demand the weakest criterion at 4.92. The plan answers that directly: narrow to the two trigger events, prove the artifact with a personalised free sheet, and only then widen to more metros. Positioning is deliberately unglamorous — this is a print job that saves four hours and one mistake a week, sold to the person who does the printing.
Smallest sellable MVP
A fixed-schema order importer, a SKU-to-recipe map, one on-screen totals screen, and two print-ready PDF exports behind a Stripe subscription gate.
Must-have features
- Paste/CSV importer with a column mapper to six fixed fields and row-level validation errors
- SKU-to-recipe editor: portions per batch, batch yield, container size, allergen tags
- Batch aggregation rounded to whole batches with leftover portions per recipe
- Container counts by size, per SKU and per office
- Avery-compatible label PDF per office with pack date and allergen tags
- Drop sheet PDF and CSV grouped by delivery day and postcode
- Week duplication so the second week takes minutes
- Stripe Checkout subscription with an export license gate
Explicitly out of scope
- Ingredient inventory and stock tracking
- Invoicing or payment collection for the caterer's own customers
- Live route optimisation or driver GPS
- An office-facing ordering portal or mobile app
- POS, ERP or accounting integrations
- Any fridge hardware, telemetry or IoT
- Human-operated setup service beyond founder onboarding during launch
Demo flow (what the buyer sees)
- Caterer pastes last week's order file into the importer.
- Mapper assigns columns; unknown SKUs are flagged with row numbers.
- Caterer confirms the SKU-to-recipe map with batch yield, container size and allergens.
- Engine sums portions per recipe and rounds up to whole batches.
- Screen shows container counts by size and leftover portions.
- One click renders the label PDF on an Avery grid.
- Second click renders the drop sheet grouped by postcode and delivery window.
- Caterer prints, packs and delivers.
Technical implementation plan
Stack
Architecture
A single Next.js app on Vercel holds all UI and server actions. Supabase stores accounts, saved column mappings, SKU-recipe maps, week templates and subscription state per account. Order files never leave the request: parsing, aggregation and container maths run as pure functions in the server action, then pdf-lib renders the label and drop-sheet PDFs in memory and streams them back. Stripe Checkout handles payment; a webhook writes active/inactive subscription state into Supabase and the export route checks that flag before rendering. Resend sends the lifecycle emails off the same webhook.
Build steps
- Scaffold Next.js on Vercel with Supabase auth and one workspace row per account.
- Define the fixed order schema and write the PapaParse parser returning per-row error objects.
- Build the column mapper UI and persist one saved mapping per account.
- Build the SKU-to-recipe table with batch yield, container size and allergen multi-select.
- Implement aggregation as pure TypeScript with unit tests on three fixture weeks.
- Implement container counts by size, per SKU and per office.
- Render the label PDF on an Avery 5160/5163 grid, paginating at 30 labels.
- Render the drop sheet PDF and CSV sorted by delivery day then postcode.
- Add Stripe Checkout for both plans, the webhook, and export gating.
- Add week duplication, Resend lifecycle emails and export error logging before the first outreach send.
AI components
- Optional LLM suggestion for column mapping when the header row does not match, always confirmed by the user before import.
- Optional LLM normalisation of dietary tag text such as GF, gluten free and no gluten onto one allergen list.
- No LLM in batch maths, container counts or pricing; those stay deterministic so the same input always prints the same sheet.
Pricing and monetization
Kitchen Solo
Entry offerFor Solo owner-operator running up to 25 office fridges
- Unlimited weekly prep sheets
- Label and drop-sheet PDF export
- One saved week template
Kitchen Plus
For Kitchen team of 2-5 staff running 25-50 offices
- Everything in Kitchen Solo
- Up to 3 kitchen logins
- Custom label templates
- Unlimited week templates and multi-route drop sheets
Model: Two flat monthly subscriptions sold through Stripe Checkout, with exports gated on an active subscription.
First revenue offer: Send their own week back as a finished Monday Prep & Drop Sheet within 24 hours, free, then load their SKU and office map into a Kitchen Plus account at $99 for the first month.
Expected ACV: $99
Upsell path: Solo accounts crossing 25 offices move to Plus at $99; Plus accounts with a second kitchen location add a second workspace; every paying account is asked for one peer introduction in a different city.
First-customer acquisition
Direct outreach to independent office-lunch caterers found on Google Maps and Instagram, with a personalised free sample sheet as the wedge.
Where to find them
- Google Maps listings for office lunch catering in 4 metros, starting with 2
- Instagram hashtags used by meal-prep and office-lunch kitchens
- Facebook groups for independent caterers and meal-prep owners
- Reddit threads in catering and small-business communities where owners describe prep errors
- Local food-business association and chamber directories
Exact outreach motions
- Send a short DM or email with one anonymised sample sheet attached and the line about a 10-minute free sheet.
- Follow up on day 3 with a second sample built for a different office count so the range is visible without a call.
- Follow up on day 7 asking one question: how many hours does Monday prep take you now.
- On reply, request their last order file and return a real sheet within 24 hours.
- Deliver the sheet and the checkout link in the same message, so the ask lands at peak value.
- Ask every paying customer for one peer introduction in a different city.
Message template
Hi [name] - I saw you drop packed lunches into office fridges. I turn a week of orders into one printed Monday Prep & Drop Sheet: batch totals, container counts, labels, drop list by postcode. Send me last week's order spreadsheet and I'll send your sheet back in 10 minutes, free. Want me to?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Lock schema and stand up a deployed shell
- Freeze the six-field order schema.
- Create Next.js repo on Vercel and Supabase project with auth.
- Connect Stripe to TrustMRR before any payment exists.
- Point a bought domain at production.
Deliverable: Live app shell on a custom domain with compliant payment rail.
CSV paste and column mapping
- Build paste/upload screen with PapaParse.
- Ship the column mapper for the six fixed fields.
- Return row-level validation errors with row numbers.
Deliverable: Any order file maps into the schema with visible errors.
SKU-to-recipe editor
- SKU table with portions per batch, batch yield, container size.
- Allergen multi-select per SKU.
- Persist the map per account in Supabase.
Deliverable: A caterer can map 20 SKUs in under ten minutes.
Batch and container maths
- Sum portions per recipe and round up to whole batches.
- Show leftover portions per recipe.
- Container counts by size per SKU and per office.
Deliverable: On-screen totals verified against a manual count.
Label and drop-sheet PDFs
- Avery-grid label PDF with office, SKU, pack date, allergens.
- Drop sheet PDF and CSV sorted by delivery day then postcode.
- Print both on a real printer and correct alignment.
Deliverable: MVP complete: two print-ready PDFs from one import.
Stripe subscription and export gate
- Stripe Checkout for the $49 and $99 monthly plans.
- Webhook writes subscription state to Supabase.
- Magic-link auth plus Resend welcome email.
Deliverable: Unpaid account sees the paywall; paid account exports.
List of 150 and one real sample sheet
- Build 150 prospects from Google Maps and Instagram across four metros.
- Produce one sample sheet from a real anonymised order file.
- Write and test the four-line outreach message.
Deliverable: 150 prospects with contact routes and one sample PDF.
Week 2 · Launch & first sale · 7 days
First 30 sends
- Send 30 personalised messages with the sample PDF.
- Log every send and reply in a tracker.
Deliverable: 30 sends logged with reply status.
Batch two and day-3 follow-ups
- Send 30 more messages in two additional metros.
- Follow up every day-1 thread with a second sample at a different office count.
Deliverable: 60 total sends; follow-up cadence running.
Fulfilment within 24 hours
- Ask repliers for last week's order file with a one-line request.
- Build and return a custom sheet for each within 24 hours.
Deliverable: 3-5 personalised sample sheets delivered.
Samples to paid accounts
- Preload each replier's SKU and office map into their account.
- Send the $99 first-month checkout link.
Deliverable: Checkout links sent to every warm lead.
Close customer one
- Voice-note or call every warm lead instead of emailing again.
- Close the first $99 payment through the TrustMRR-linked account.
Deliverable: First verified payment inside the contest window.
Watch customer one run a week
- Screen-share their import and export end to end.
- Log every friction point and ship the top two fixes.
Deliverable: Friction list and two shipped fixes.
Week-2 numbers and week templates
- Count sends, replies, samples and payments.
- Ship duplicate-last-week template.
- Decide whether the $99 offer needs a second sample attached.
Deliverable: Funnel numbers and shipped template feature.
Week 3 · Repeat & systematize · 7 days
Batch three and first referral ask
- Send 30 more messages in two new metros.
- Ask every paying customer for one peer introduction.
Deliverable: 90 contacted; referral asks made.
Custom label templates
- Editable label fields with a custom header line.
- Save as an account-level label template.
Deliverable: Label template editor live in Plus.
Public page with inline checkout
- One page: sample sheet image, four bullets, price, Stripe link.
- Add a send-me-your-last-order-file form.
Deliverable: Landing page live and linked in all outreach.
Onboarding email sequence
- Three Resend emails: welcome, first import, week-two check.
- Trigger them from the Stripe webhook.
Deliverable: Automated onboarding sequence live.
Second push on stale threads
- Re-send sample sheets to non-repliers with a new office count.
- Offer to load their SKU map for free.
Deliverable: 20 reactivated threads in play.
Close the loudest support request
- Ship dietary-tag mapping from order text.
- Add CSV totals export for the kitchen.
Deliverable: Top support issue closed and confirmed.
Week-3 checkpoint
- Tally paying accounts, MRR and refunds.
- Pick the next channel bet from actual replies, not assumptions.
Deliverable: Checkpoint numbers and a go/no-go on channel two.
Week 4 · Scale what works · 7 days
Batch four
- Send 40 more messages across the last two metros.
- Target caterers who mention a new office contract.
Deliverable: 130 total prospects contacted.
Make Plus worth $99
- Ship three kitchen logins per account.
- Ship multi-route drop sheets.
Deliverable: Clear feature gap between Solo and Plus.
Peer introductions
- Ask all paying customers for one intro in a different city.
- Send each intro a pre-built sample for their city.
Deliverable: Five referral asks sent.
Solo to Plus
- Identify Solo accounts above 25 offices.
- Send a one-line upgrade offer.
Deliverable: Upgrade offers out with accepts tracked.
Follow-ups and pipeline hygiene
- Follow up every thread older than seven days once.
- Remove dead prospects and log the reason.
Deliverable: Clean pipeline with reply rate by metro.
PDF edge cases
- Test 200-SKU weeks, 60 offices, long names and nine allergens.
- Add error logging on every export path.
Deliverable: Zero known export failures.
Week-4 numbers and visibility
- Reconcile Stripe payouts, refunds and chargebacks.
- Post one build-in-public note in two owner communities.
Deliverable: Reconciled ledger and two published posts.
Days 29-30 · Consolidate · 2 days
Final conversion push
- Offer every warm lead a same-day sheet before the window closes.
- Confirm each payment will settle before 16 December 13:00 UTC.
Deliverable: All closable leads contacted and payment timing checked.
Verify and hand over
- Match Stripe payouts to TrustMRR records.
- Write the month-two plan: retention, referrals, one new metro.
Deliverable: Verified revenue tally and a month-two plan.
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 scenarios assume the $99 Kitchen Plus plan; $49 Solo sales would lower blended ARPU (Base).
- Conservative: 3 paying accounts from roughly 60 sends, a 5% close rate on contacted prospects.
- Base: 10 paying accounts from about 130 sends, matching the stated 30-day target.
- Upside: 25 paying accounts, requiring a 19% close rate plus referral spillover.
- Payment processing modelled at a 4.0% blended rate: 2.9% plus $0.30 domestic, with a buffer for international cards and Stripe Billing.
- No paid marketing in any scenario; acquisition is organic outreach, so ad_spend_usd is 0 throughout.
- Operating costs cover Vercel Pro, Supabase, domain, Resend and PDF/AI usage only; founder time is not deducted for ranking.
- Refunds modelled at 0 in Conservative and Base and $50 in Upside; chargebacks 0 in all cases.
- Each scenario counts one month of subscription collected inside the contest window; annual prepay is not offered in month one.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $12
- Paid marketing
- $0
- Hackathon profit
- $285
- Operating costs
- $25
- Business profit
- $260
Base case
10 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $40
- Paid marketing
- $0
- Hackathon profit
- $950
- Operating costs
- $45
- Business profit
- $905
Optimistic
25 customers- Refunds
- $50
- Chargebacks
- $0
- Payment fees
- $99
- Paid marketing
- $0
- Hackathon profit
- $2,326
- Operating costs
- $90
- Business profit
- $2,236
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $490
- Payment fees (3.9%)
- $19
- Paid marketing
- $0
- Hackathon profit
- $471
- Business profit
- $426
Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.
Scenario models from stated assumptions, not verified revenue. No customers, revenue or traction exist at launch.
Main risks and validation experiments
Risk 1Caterers treat the prep sheet as a one-off job and never renew.
Frame every send as a weekly recurring task, and show week two taking four minutes via the saved template.
Deliver week one free, then ask for a card to unlock week two; count accepts from the first 10 sheets.
If fewer than 2 of 10 free-sheet recipients pay for week two by day 21, stop volume outreach and re-target only new-office-contract caterers.
Risk 2Order formats vary so much that every customer needs manual column mapping.
Fixed schema plus one saved mapping per account, with the founder mapping the first file during launch only.
Time the mapping of three real order files from three different caterers.
If median mapping time exceeds 45 minutes per customer, ship saved format presets and narrow outreach to one format family.
Risk 3The contact is a head chef with no card authority.
Address owner and ops-lead roles only, and ask in the first reply who approves a $99 monthly charge.
Track the stated role in every reply across the first 60 sends.
If more than 30% of replies say they must ask someone, write a one-page approval note and re-target owner-titled contacts.
Risk 4Allergen or label errors create liability and slow adoption.
Allergens are entered manually per SKU, never inferred from SKU names, and the label prints only what the caterer entered.
Ask two caterers to review five generated labels against their own allergen list.
If both flag correctness concerns needing a feature not shippable in three days, ship totals and drop sheet only and sell Solo at $49.
Risk 5Free samples generate interest but no payment inside the window.
Put the checkout link in the same message that delivers the finished sheet, at peak perceived value.
Send the first 60 messages with the sample attached and log reply-to-payment rate weekly.
If 60 sends produce zero payments by day 14, change the message angle once; if still zero by day 20, the wedge is wrong.
Hour-by-hour: the first 24 hours
Hours 1-2
- Read the official rules page and confirm the contest window and profit definition.
- Create the Stripe account and connect it to TrustMRR before any payment exists.
Output: Compliant payment rail with zero prior transactions.
Hours 3-5
- Buy the domain.
- Create Vercel and Supabase projects and deploy the Next.js starter.
Output: Live URL on the custom domain with auth enabled.
Hours 6-10
- Write the six-field order schema.
- Build the paste screen and the first version of the column mapper.
Output: Working importer that flags unmapped columns.
Hours 11-14
- Hand-build one Monday Prep & Drop Sheet from a synthetic 40-order, three-office dataset.
- Export it as a PDF for outreach.
Output: Sample sheet PDF and a clear picture of the required layout.
Hours 15-20
- Build the first 40 rows of the prospect list from Google Maps in metro one.
- Record contact route and office count where visible.
Output: 40 prospects with contact routes.
Hours 21-24
- Finalise the outreach message and tracker.
- Send the first five messages to the warmest prospects.
Output: Five sends logged and a running tracker.
Full 30-day launch report
Read the full generated report
FridgeDrop Prep - 30-day launch report
Window: Monday 16 November 2026 13:00 UTC to Tuesday 15 December 2026, with 16 December held as a settlement buffer before the 13:00 UTC close. One founder, no team, no ad budget, no funding, no prior customers. Every number in section 7 is a projection.
1. Product opportunity and positioning
The buyer is the owner or ops lead of a 1-20 person independent caterer that packs individual meals into 5-50 office fridges. They already sell. They already have orders. What they do not have is a clean Monday.
Orders arrive as WhatsApp threads, emailed spreadsheets and Google Forms. Someone totals meals per SKU by hand, converts recipes to batch quantities, writes container labels, tags allergens and rebuilds the drop list from memory. That is two to five hours weekly, and the failure mode is expensive: overproduction on slow SKUs, a missing item, a mislabelled allergen container, a late drop. Any one of those puts the office contract at risk.
Two events make the pain buyable: a new office contract that pushes volume past what a spreadsheet handles, and a prep error that already cost money. All outreach targets those events, not caterers in general.
FridgeDrop Prep takes the order file the caterer already collects and returns one artifact: the Monday Prep & Drop Sheet. Batch totals per recipe rounded to whole batches with leftover portions, container counts by size per SKU and per office, a print-ready label sheet carrying pack date and allergens, and a drop sheet grouped by delivery day and postcode. No portal for offices, no hardware, no migration.
The alternatives are weak at exactly this output. A spreadsheet template needs rebuilding each week and cannot print labels. A catering ERP is priced and shaped for a much larger kitchen. A label app does labels but knows nothing about batch yield. Doing totals, batching, labels and routing in one export is the wedge.
JEV scored this concept 65.1/100, band B, with market demand the weakest criterion at 4.92. The answer is narrowness: one trigger-event segment, one proof artifact, one metro at a time.
2. Smallest sellable MVP
Sellable on day 5 means: import an order file, map it to six fields, confirm a SKU-to-recipe map, see correct batch and container totals, and export two PDFs that a kitchen can print and tape to a wall. The label grid must survive a real printer, not just a browser preview. Week duplication ships in the same build because the second week is where the subscription is won or lost.
Not built in month one: ingredient inventory, invoicing for the caterer's own customers, route optimisation, driver tracking, an office-facing app, POS or ERP integrations, and any fridge hardware. Every one of those either needs a partner, a longer build, or a buyer we cannot reach in 30 days.
The demo is the product: paste last week's file, print the sheet. The founder can run it live in ten minutes with no slides.
3. Technical implementation plan
Next.js on Vercel with Supabase for accounts, saved column mappings, SKU-recipe maps, week templates and subscription state. Stripe Checkout sells the two plans; a webhook flips an export gate in Supabase. pdf-lib renders labels and drop sheets server-side and streams them back. PapaParse handles the import. Resend sends lifecycle email. All batch arithmetic is deterministic TypeScript with unit tests on three fixture weeks, so the same input always prints the same sheet.
The real technical risk is label geometry. Avery grids fail by half a millimetre, and a shifted label looks like a software bug to a kitchen. Print, measure and correct on day 5, then re-test at day 27 with 200 SKUs, 60 offices, long item names and nine allergens.
The AI surface is deliberately thin: an optional suggestion for column mapping, and optional normalisation of dietary text such as GF or no gluten onto one allergen list. Neither touches the maths, so no customer ever gets a different total because a model drifted.
4. Pricing and monetization
Kitchen Solo at $49 monthly for a solo operator up to 25 fridges. Kitchen Plus at $99 monthly for a two-to-five-person kitchen running 25-50 offices, with three logins, custom label templates and multi-route drop sheets. Exports are gated, so an expired subscription degrades to viewing only.
The first offer is concrete: their own week returned as a finished sheet within 24 hours, free, then Kitchen Plus at $99 for the first month with their SKU and office map already loaded. Approval sits with one person, below any procurement threshold, and the alternative is another Monday of hand-counting.
Delivery cost per account is cents: hosting, database and a PDF render. That makes every sale profitable on day one and keeps the contest's delivery-cost rule satisfied. Upside comes from Solo-to-Plus upgrades and second-location workspaces, not from raising the price. No annual prepay in month one, because the ranking only counts money collected inside the window and a monthly plan keeps refund exposure to one month.
5. First-customer acquisition
One channel: direct outreach to independent office-lunch caterers found on Google Maps and Instagram, in four metros, two at a time. No marketplace, no SEO ramp, no ads.
The wedge is a personalised free sheet, not a demo call. The message is four lines: what I do, attach one anonymised sample, ask for last week's order file, promise the sheet back in ten minutes. Follow up on day 3 with a second sample at a different office count, and on day 7 with a single question about how long Monday prep takes now.
When someone replies, build their sheet within 24 hours and put the checkout link in the same message that delivers it. That is the moment of peak perceived value, and it is the only conversion moment that reliably works without a call.
Volume targets: 60 sends by day 9, 90 by day 15, 130 by day 22. Every paying customer is asked for one peer introduction in a different city; that referral loop is the only compounding channel available in month one.
6. 30-day execution roadmap
The month runs in five blocks.
Days 1-7 build and arm. Days 1-5 ship the MVP: importer, recipe map, totals, label PDF, drop sheet PDF, with a physical print check on day 5. Day 6 adds Stripe and the export gate. Day 7 builds the 150-prospect list and the first real sample sheet. No outreach happens before the sample exists, because the sample is the pitch.
Days 8-14 prospect and close. 60 sends, two follow-up passes, custom sheets for every replier, and checkout links at delivery. Day 12 is the first-sale target. Day 13 is spent watching the first customer run a real week; Day 14 reviews the funnel and decides whether the offer needs a second sample.
Days 15-21 widen. Batch three of outreach, the public landing page with inline checkout, an automated three-email onboarding sequence, and reactivation of stale threads. Product work concentrates on the things that make Plus worth $99: custom label templates and better tag mapping.
Days 22-28 convert and harden. Batch four, referral asks, Solo-to-Plus upsells, and a hardening day that throws 200-SKU weeks and 60-office routes at the PDF generator. Day 28 reconciles the ledger against Stripe payouts.
Days 29-30 close. Every warm lead gets a same-day offer; every payment is checked against the 16 December 13:00 UTC deadline; day 30 writes the month-two plan.
7. Revenue and profit scenarios
These are projections from stated assumptions, not verified revenue.
Conservative assumes 3 Kitchen Plus accounts at $99: $297 collected, $12 processing at a 4% blended rate, no refunds, no chargebacks, no ad spend, $25 operating cost. Hackathon profit $285; business profit $260.
Base assumes 10 accounts: $990 collected, $40 processing, $45 operating cost. Hackathon profit $950; business profit $905.
Upside assumes 25 accounts: $2,475 collected, $50 refunds, $99 processing, $90 operating cost. Hackathon profit $2,326; business profit $2,236.
No paid marketing appears in any scenario, because the channel is organic outreach. Hosting, domain, tooling and AI/PDF delivery costs sit in operating cost and are not deducted for contest ranking, but they are real money and each sale covers them many times over. A single refund at $99 wipes out the conservative margin, which is why the monthly plan is not discounted below $49.
8. Main risks and validation experiments
One-off usage. The biggest threat is a caterer who buys a single sheet and leaves. Test: give week one free, ask for a card for week two, count accepts from the first ten sheets. If fewer than two convert by day 21, stop volume outreach and target only caterers who just signed a new office contract.
Format variance. Every caterer's order file looks different. Time the mapping of three real files; if the median exceeds 45 minutes, ship format presets and narrow to one format family rather than accepting a manual queue.
Approval authority. The head chef may want it and not be able to buy it. Track the stated role in every reply across the first 60 sends; if more than 30% must ask someone, produce a one-page approval note and re-target owner-titled contacts.
Allergen liability. Labels carry food-safety weight. Allergens are entered manually per SKU and never inferred. Two caterers review five labels; if both raise concerns needing a feature that cannot ship in three days, sell totals and drop sheet only at $49.
Interest without payment. If 60 sends produce zero payments by day 14, change the message angle once. If it is still zero by day 20, the wedge is wrong and the plan must change, not the wording.
9. First 24-hour action plan
Hours 1-2: read the official rules, confirm the window and the profit definition, open Stripe and connect TrustMRR before any payment exists.
Hours 3-5: buy the domain, create Vercel and Supabase projects, deploy the app shell.
Hours 6-10: write the six-field schema, ship the paste screen and a first column mapper that flags unmapped columns.
Hours 11-14: hand-build one Monday Prep & Drop Sheet from a synthetic 40-order, three-office dataset and export it as a PDF. This file is the entire sales pitch for the next three weeks.
Hours 15-20: build the first 40 prospect rows from Google Maps in metro one, with contact routes.
Hours 21-24: finalise the outreach message and tracker, and send the first five messages. Day one ends with a deployed app, a sample sheet and five live conversations.
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 →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.
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.
ArtisanQuote
ArtisanQuote turns a messy corporate event email into a branded, allergen-tagged, margin-checked catering quote PDF in under two minutes.