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

Cater Order Pack

Cater Order Pack turns a caterer's WhatsApp or Instagram event chat into an itemized quote, kitchen prep sheet, packing checklist, and deposit payment link.

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.35/10
MVP build (solo)
5 days
Launch price
$99 · monthly
Sales to $1,000 revenue
11 customers
First paying customer
Instagram DM to independent caterers who list 'DM for catering' or a WhatsApp order link in their bio, starting in one metro area.
Who pays

Owner-operators of small catering companies (1-10 staff) in the US, UK and Singapore who take custom event orders through WhatsApp or Instagram DMs and build quotes manually.

Biggest execution risk

Market demand 4.6/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 5 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.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.

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

Product opportunity and positioning

Target customer

Owner-operators of small catering companies (1-10 staff) in the US, UK and Singapore who take custom event orders through WhatsApp or Instagram DMs and build quotes manually.

Why now

The order conversation already exists in the caterer's chat and the deposit is the natural payment trigger, so one event pack can be demonstrated on their own thread in minutes with no storefront change.

Problem

Caterers retype messy DM orders into quotes and prep sheets, miss dietary notes or quantities, and chase deposits manually, causing costly event-day mistakes.

Solution

The caterer pastes an event chat thread; the product extracts client, date, guest count, line items, dietary notes and delivery details into a validated editable order, then generates a branded quote/invoice PDF, kitchen prep sheet, packing checklist and Stripe deposit link.

Differentiation · Spreadsheets still require the retype, storefront builders require a migration, and generic AI chat returns prose that cannot be validated or printed as a prep sheet; this returns a finished printable pack inside the existing channel.

Small caterers run their business inside a chat window. An order arrives as a WhatsApp thread or Instagram DM: a menu typed in fragments, one guest is vegan, a headcount that changes twice, an address buried in the scroll. The owner retypes that into a quote, retypes it again into a prep sheet, then spends the week chasing a deposit. Every retype is where mistakes enter.

Cater Order Pack does not ask the caterer to leave that channel. The merchant pastes the thread; the product extracts client, event date, guest count, line items with quantity and unit price, dietary notes and delivery details into a strict schema; the merchant corrects an editable table; the product emits a branded quote/invoice PDF, a kitchen prep sheet, a packing checklist and a Stripe deposit link with a copyable payment message.

JEV scored this exact concept 63.5/100 (band C, confidence 0.75). Speed to first revenue (8.3) and solo build feasibility (7.39) are its strengths. Market demand (4.61) is its weakest criterion, and that single weakness sets the operating rule for the next 30 days: never sell a tool for caterers, always sell the resolution of one already-booked event that is waiting on a quote or a deposit. A caterer with a date on the calendar and no deposit in the bank has an urgent, budgeted problem. A caterer browsing software does not.

Positioning against the alternatives: spreadsheet templates still require the retype; storefront and e-commerce builders require a migration and a customer-facing change; generic AI assistants return prose that cannot be validated field by field or printed as a kitchen sheet. Cater Order Pack keeps the existing channel and returns a finished, printable pack that a kitchen can act on.

The wedge stays deliberately narrow. No storefront, no POS, no inventory, no QR menus, no delivery logistics. The entire promise is one event conversation in, one complete Event Order Pack out, plus a deposit link the client can actually pay.

Section 2 of 8

Smallest sellable MVP

A paste box that turns one WhatsApp or Instagram event thread into an editable, validated order and a downloadable three-page Event Order Pack PDF plus a Stripe deposit link.

Must-have features

  • Paste area for WhatsApp or Instagram event threads
  • LLM extraction into strict JSON: client, event date, guest count, line items with qty and unit price, dietary notes, delivery address
  • Editable validation table before any document is generated
  • Branded PDF pack: quote/invoice, kitchen prep sheet, packing checklist
  • Stripe deposit/payment link per event plus copyable payment message
  • Merchant dashboard listing events, deposit status and totals
  • CSV export of events and line items
  • Magic-link auth and Stripe Checkout subscription billing for the $99/month plan

Explicitly out of scope

  • No online storefront or website builder
  • No POS, inventory, loyalty or QR menus
  • No WhatsApp Business API or inbox sync in v1
  • No route optimization, rider dispatch or delivery logistics
  • No multi-staff roles, CRM or kitchen display hardware
  • No automated invoice chasing or client messaging

Demo flow (what the buyer sees)

  1. Merchant creates an event and pastes a real redacted chat thread.
  2. Extraction returns a structured order with line items, dietary notes and delivery details.
  3. Merchant fixes one quantity in the editable table and confirms.
  4. Product renders the quote/invoice, prep sheet and packing checklist as one branded PDF.
  5. Product creates a Stripe deposit link and a copyable payment message.
  6. Merchant sends the pack and link to the client and marks the event deposit-pending in the dashboard.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres with row-level securitySupabase magic-link authOpenAI API structured JSON extractionReact-PDF for document renderingStripe Payment Links for depositsStripe Checkout for subscription billingTailwind CSS

Architecture

A single Next.js app on Vercel holds the dashboard, the paste workflow and the PDF route. Supabase stores merchants, events, line items and generated documents behind row-level security keyed to the merchant id. The extraction step posts the raw thread to a serverless route that calls OpenAI with a JSON schema and stores both the raw text and the parsed result so any correction is auditable. The validated event row drives React-PDF rendering and a Stripe Payment Link created per event; subscription billing is a separate Stripe Checkout price at $99 per month.

Build steps

  1. Scaffold Next.js app, deploy to Vercel, wire Supabase magic-link auth.
  2. Create merchants, events, line_items and documents tables with RLS.
  3. Build the paste screen and the OpenAI structured-extraction route with a strict schema.
  4. Persist raw thread plus parsed JSON, and surface low-confidence fields.
  5. Build the editable line-item table with totals and a deposit percentage field.
  6. Render quote/invoice, prep sheet and packing checklist with React-PDF and one merged download.
  7. Create a Stripe Payment Link per event and a copyable payment message.
  8. Add Stripe Checkout subscription for the $99 plan and gate pack generation on active status.
  9. Add dashboard event list, deposit status, totals and CSV export.
  10. Harden with rate limits, error states, deletion endpoint and three synthetic end-to-end runs.

AI components

  • OpenAI structured extraction of the event thread into a strict JSON order schema
  • Heuristic confidence scoring per extracted field to drive validation highlighting
  • Optional normalization of unit and quantity phrasing into comparable line items
Hardest technical risk: Extraction on genuinely messy threads: voice-note transcripts, mixed units such as trays versus portions, and ambiguous headcounts. Mitigation is a mandatory validation table, per-field confidence flags and an explicit 'assumed' marker so the merchant never ships an unchecked number.
Section 3 of 8

Pricing and monetization

Founding Caterer

Entry offer
$99 / month

For Solo caterer or private chef taking 5-30 event orders per month via chat

  • 20 Event Order Packs per month
  • Branded quote/invoice PDF
  • Kitchen prep sheet and packing checklist
  • Stripe deposit/payment links
  • CSV export and event dashboard

Model: Single monthly subscription at $99 with a 20-pack monthly allowance and a per-pack overage add-on.

First revenue offer: I will turn one of your real event chat threads into a finished quote, kitchen prep sheet, packing checklist and deposit link for free. If it saves you the retype, the Founding Caterer plan is $99/month for 20 packs.

Expected ACV: $99

Upsell path: Pack overage at $15 per pack beyond the 20 included, then a higher tier for caterers running more than 30 events per month.

Target customers
15
Revenue model
$1,485
Costs
$80
Profit model
$1,405
Section 4 of 8

First-customer acquisition

Primary channel

Instagram DM to independent caterers who list 'DM for catering' or a WhatsApp order link in their bio, starting in one metro area.

Where to find them

  • Instagram hashtag and location search for 'catering [city]'
  • Instagram bios containing 'DM to order' or 'WhatsApp to order'
  • TikTok search for 'catering [city]' and 'private chef [city]'
  • Local caterer directories and wedding vendor lists for one metro
  • Instagram tagged-photo feeds of small event venues and party planners

Exact outreach motions

  • Collect 50 profiles with handle, city, channel and last post date in a sheet before sending anything.
  • Open with the free pack offer and name the exact artefact you will return, not the software.
  • Ask for one redacted thread or a copy-paste of the order; deliver the pack within two hours.
  • Follow up at 48 hours with one line: reuse this for every event, no storefront change.
  • Send the $99 Founding Caterer start link only after the free pack has been delivered and opened.
  • Ask every paying caterer for one referral to another caterer in their city.

Message template

Hi [name] - I saw you take catering orders by DM. I will turn one of your real event threads into a finished quote, kitchen prep sheet, packing checklist and a Stripe deposit link, free, in about 15 minutes. No signup needed to see it. Want me to do one?
Week-one goal: 50 qualified caterer profiles collected, 40 DMs sent, and at least 5 real threads received for free pack delivery.
Section 5 of 8

30-day execution roadmap

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

App shell, auth, data model

  • Scaffold Next.js on Vercel with Supabase magic-link auth.
  • Create merchants, events, line_items and documents tables with RLS.
  • Ship an empty dashboard with a new-event button.

Deliverable: Deployed skeleton with a logged-in dashboard.

Day 2Extraction

Thread to strict JSON

  • Build the paste screen and OpenAI structured-extraction route.
  • Add three synthetic few-shot examples covering dietary notes and delivery details.
  • Persist raw thread plus parsed JSON per event.

Deliverable: Paste a thread, get a structured event order.

Day 3Validation

Editable order table

  • Build the editable line-item table with qty, unit price and dietary notes.
  • Add event totals and a deposit percentage field.
  • Reject non-catering pastes with a clear error state.

Deliverable: A correctable event order saved to the dashboard.

Day 4Documents

PDF Event Order Pack

  • Render quote/invoice, kitchen prep sheet and packing checklist with React-PDF.
  • Add merchant logo, brand colour and footer settings.
  • Merge the three documents into one downloadable pack.

Deliverable: Branded three-page Event Order Pack PDF.

Day 5Payments

Deposit links and subscription

  • Create a Stripe Payment Link per event for the deposit amount.
  • Add Stripe Checkout subscription for the $99 Founding Caterer plan.
  • Generate a copyable payment message for WhatsApp or Instagram.

Deliverable: Working deposit link and live subscription checkout.

Day 6LaunchMVP shipped

Public v1 live

  • Connect TrustMRR and switch Stripe to live mode with no test data in production.
  • Run three synthetic threads end to end and fix every breakage.
  • Publish a pricing page and a plain refund policy.

Deliverable: Public v1 accepting payments.

Day 7Prospecting

First 50 caterers

  • Build a 50-row prospect sheet for one metro with handle, city and channel.
  • Send the first 20 DMs with the free pack offer.
  • Log every reply and objection in the sheet.

Deliverable: 50-row prospect sheet and 20 DMs sent.

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

Volume and reply logging

  • Send 30 more DMs to the same metro.
  • Add 20 private chef profiles from TikTok search.
  • Tag each reply as interested, later or no.

Deliverable: 50 DMs sent and a working reply log.

Day 9Delivery

Free packs from real threads

  • Deliver up to three free Event Order Packs from redacted threads within two hours each.
  • Record every extraction error in a single log.
  • Fix the top error the same day.

Deliverable: Three delivered packs and an error log.

Day 10Feedback

Price signal

  • Ask each trialist what they would have charged for the pack.
  • Ask which document they used first.
  • Patch the single biggest UI friction.

Deliverable: Feedback notes and one shipped fix.

Day 11Offer

Convert trialists

  • Send the $99 start link to every trialist who opened their pack.
  • Follow up on 48-hour-old DMs with the reuse line.
  • Add a one-click example thread so they can retry alone.

Deliverable: Start links sent to all warm trialists.

Day 12First saleFirst sale target

Close paying customer one

  • DM 20 new caterers, prioritising those with a dated upcoming event.
  • Close the first $99 subscription and confirm the payment landed.
  • Ask the buyer for one referral immediately.

Deliverable: First $99 collected and a referral ask sent.

Day 13Onboarding

Time to first pack

  • Cut steps until a new account produces a pack in under five minutes.
  • Add an in-app example thread button.
  • Remove any field the merchant never edits.

Deliverable: Under five minutes from signup to first pack.

Day 14Iterate

Message variants

  • Send 30 DMs across two opener variants.
  • Compare reply and pack-request rates per variant.
  • Retire the weaker variant.

Deliverable: Winning DM variant selected.

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

Second metro

  • Add 50 profiles from a second metro.
  • Send 40 DMs using the winning variant.
  • Keep the prospect sheet segmented by city.

Deliverable: 100-profile pipeline across two metros.

Day 16Referrals

Warm intros

  • Ask every paying user for one caterer referral by name.
  • Add the referral ask to the post-purchase email.
  • DM referred caterers with the referrer's first name.

Deliverable: Referral asks sent and referred DMs logged.

Day 17Retention

Repeat usage

  • Ship event list filters and CSV export polish.
  • Email active users a prompt to run their next event through it.
  • Fix any event that failed to generate twice.

Deliverable: CSV export shipped and a repeat-use email sent.

Day 18Proof

Credible before/after

  • Write a one-page anonymised before/after from a real user, with written permission.
  • Link it in the DM opener.
  • Do not fabricate numbers or timelines.

Deliverable: Anonymised proof page live.

Day 19Pricing edge

Overage add-on

  • Offer $15 per pack beyond the 20 included to high-volume users.
  • Only pitch overage after a user hits 15 packs.
  • Track attach rate separately.

Deliverable: Overage add-on available in billing.

Day 20Support

Cut repeat questions

  • Publish an FAQ on pasting, privacy and refunds.
  • Add a delete-my-data control.
  • Rewrite any UI label that generated a question twice.

Deliverable: FAQ and data deletion shipped.

Day 21Review

Midpoint decision

  • Compare paid customers against the 10-customer base case.
  • Decide whether DM volume or partner outreach gets the next week.
  • Write a one-paragraph go or no-go note.

Deliverable: Midpoint decision note.

Week 4 · Scale what works · 9 days
Day 22Push

Outreach volume

  • Send 50 new DMs across both metros.
  • Send 20 follow-ups to silent trialists.
  • Log conversion rate by metro.

Deliverable: 70 outreach touches logged.

Day 23Segment

Private chefs

  • Target private chefs doing dinner parties with one-off per-head pricing.
  • Rewrite the DM opener for that pricing shape.
  • Send 25 segment DMs.

Deliverable: Private chef segment test running.

Day 24Trust

Privacy objections

  • Add paste-redaction guidance to the paste screen.
  • Confirm no raw thread is used for model training.
  • Add account-level data deletion in one click.

Deliverable: Privacy objection handled in-product.

Day 25Proof two

Second case page

  • Publish a second anonymised case with permission.
  • Add both cases to the pricing page.
  • Test the pages as link previews in DM.

Deliverable: Two proof pages live.

Day 26Billing hygiene

Clean books

  • Enable Stripe receipts and failed-payment retries.
  • Reconcile every charge against a real merchant.
  • Tag any refund and record the reason.

Deliverable: Reconciled Stripe ledger.

Day 27Close

Final conversion sweep

  • Message every unconverted trialist once with the closing offer.
  • Offer a short call only to caterers with a dated event.
  • Remove friction found in three or more conversations.

Deliverable: All trialists contacted with a closing offer.

Day 28Referrals

Convert intros

  • Follow up every referral lead.
  • Thank referrers publicly only with permission.
  • Add one referral prompt inside the pack download screen.

Deliverable: Referral pipeline converted or closed.

Day 29Verification

Numbers that count

  • Export Stripe payouts, refunds and fees for the contest window.
  • Confirm the TrustMRR ledger matches Stripe.
  • Document any revenue outside the window and exclude it.

Deliverable: Verified profit workbook.

Day 30Close out

Final window before 13:00 UTC

  • Send final DMs and collect any pending subscription starts before the deadline.
  • Freeze the ledger and screenshot the verified totals.
  • Publish a short launch recap with projections clearly labelled.

Deliverable: Frozen, verified 30-day result and a public recap.

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 figures are projections from stated assumptions, not verified revenue or existing customers.
  • Base case: 300 targeted DMs produce roughly 30 replies, 15 free packs delivered and 10 paid subscriptions.
  • Conservative: cold DM reply rate is half of base and only 3 subscriptions close.
  • Upside: the winning DM variant plus referrals push 18 subscriptions, with one refund.
  • Price is $99 per month; the 30-day window collects one month per customer, so arpu is $99.
  • Payment processing is assumed at about 4.5% of collected revenue, blending 2.9% + $0.30 card fees with Stripe Billing and some non-US cards.
  • Ad spend is zero in all scenarios; acquisition is organic DM only.
  • Operating costs cover Vercel, Supabase, OpenAI extraction, PDF rendering and email, roughly $5-7 per customer per month.
  • No paid marketing, no affiliate payouts and no contractor costs are assumed.
  • Churn is not modelled inside the 30-day window because only one billing cycle is collected.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$13
Paid marketing
$0
Hackathon profit
$284
Operating costs
$25
Business profit
$259

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$45
Paid marketing
$0
Hackathon profit
$945
Operating costs
$60
Business profit
$885

Optimistic

18 customers
$1,782
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$80
Paid marketing
$0
Hackathon profit
$1,603
Operating costs
$90
Business profit
$1,513

Model your own numbers

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

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 derived from stated assumptions. These are projections, not verified revenue, customers or traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM response rate lands far below the projection and no first customer appears by day 12.

Mitigation

Prioritise caterers with a visible dated event or a recent 'booking [month]' post; lead with the finished free pack, not the software.

Validation experiment

Send 20 DMs on day 7 with two openers and count pack requests, not replies.

Kill criteria

Fewer than 3 pack requests from 60 DMs by day 12 means the channel or the offer is wrong and needs rewriting before more volume.

Risk 2Extraction errors on messy threads erode trust before the merchant reaches the validation table.

Mitigation

Flag low-confidence fields, mark assumed values explicitly, and require confirmation before any PDF is generated.

Validation experiment

Run 10 synthetic messy threads and count fields the founder has to correct by hand.

Kill criteria

If more than 20% of line items need correction on typical threads, add a guided line-item entry mode instead of full auto-extraction.

Risk 3Caterers refuse to paste client chats into a new tool for privacy reasons.

Mitigation

Offer a redaction step, state that threads are not used for model training, and provide one-click deletion.

Validation experiment

Ask five caterers directly whether they would paste a redacted thread and record the exact objection wording.

Kill criteria

If four of five refuse even with redaction, the paste model fails and the concept needs a different input path.

Risk 4Caterers already have a spreadsheet or quoting habit and see no reason to change mid-season.

Mitigation

Sell against one live event with a deadline, and compare their manual quote time to the returned pack time.

Validation experiment

Time the founder building one pack versus asking the caterer how long their last quote took.

Kill criteria

If trialists deliver a free pack and still do not run a second event through it, the workflow is not sticky enough.

Risk 5Stripe availability or payment-link friction blocks checkout in a target market.

Mitigation

Confirm Stripe account eligibility in the first reply, before investing pack delivery time.

Validation experiment

Ask each trialist whether they already accept card payments online and on which provider.

Kill criteria

If more than half the metro cannot accept Stripe links, switch to the metro where they can rather than building new payment rails.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the repo, Vercel project and Supabase instance.
  • Draft the extraction JSON schema with every event field pinned.

Output: Deployed skeleton and a written extraction schema.

Hours 3-5

  • Build the paste screen and the OpenAI structured-extraction route.
  • Test against three hand-written messy threads.

Output: Working thread-to-JSON extraction on three samples.

Hours 6-9

  • Build the editable line-item table and event totals.
  • Persist events per merchant behind magic-link auth.

Output: A corrected order saved and reopened from the dashboard.

Hours 10-13

  • Render the three PDF documents from a validated event.
  • Add logo and brand colour settings.

Output: A downloadable three-page Event Order Pack PDF.

Hours 14-18

  • Create the per-event Stripe Payment Link and copyable message.
  • Connect TrustMRR test mode and confirm the event flow end to end.

Output: Complete demo flow from paste to deposit link.

Hours 19-24

  • Build the first 30-row caterer prospect sheet in one metro.
  • Send the first 10 DMs with the free pack offer.

Output: 30-row prospect sheet and 10 DMs sent with logged handles.

Complete report

Full 30-day launch report

Read the full generated report

Cater Order Pack — 30-Day Launch Report

1. Product opportunity and positioning

Small caterers run their business inside a chat window. An order arrives as a WhatsApp thread or Instagram DM: a menu typed in fragments, one guest is vegan, a headcount that changes twice, an address buried in the scroll. The owner retypes that into a quote, retypes it again into a prep sheet, then spends the week chasing a deposit. Every retype is where mistakes enter.

Cater Order Pack does not ask the caterer to leave that channel. The merchant pastes the thread; the product extracts client, event date, guest count, line items with quantity and unit price, dietary notes and delivery details into a strict schema; the merchant corrects an editable table; the product emits a branded quote/invoice PDF, a kitchen prep sheet, a packing checklist and a Stripe deposit link with a copyable payment message.

JEV scored this exact concept 63.5/100 (band C, confidence 0.75). Speed to first revenue (8.3) and solo build feasibility (7.39) are its strengths. Market demand (4.61) is its weakest criterion, and that sets the operating rule for the next 30 days: never sell a tool for caterers, always sell the resolution of one already-booked event waiting on a quote or a deposit. A caterer with a date on the calendar and no deposit in the bank has an urgent, budgeted problem. A caterer browsing software does not.

Against the alternatives: spreadsheet templates still require the retype; storefront and e-commerce builders require a migration and a customer-facing change; generic AI assistants return prose that cannot be validated field by field or printed for a kitchen. This product keeps the existing channel and returns a finished, printable pack.

The wedge stays narrow on purpose. No storefront, no POS, no inventory, no QR menus, no delivery logistics. One event conversation in, one complete Event Order Pack out, plus a deposit link the client can actually pay.

2. Smallest sellable MVP

The smallest sellable thing is a paste box that returns an editable, validated order and a three-page branded PDF plus a working deposit link. Nothing else earns the $99.

Required: paste area for WhatsApp or Instagram threads; LLM extraction into a strict schema covering client, date, guest count, line items with quantity and unit price, dietary notes and delivery address; a human validation table before any document renders; the branded PDF pack (quote/invoice, kitchen prep sheet, packing checklist); a Stripe deposit link per event with a copyable message; a dashboard with event list, deposit status and totals; CSV export; magic-link auth and Stripe Checkout subscription billing.

Explicitly out of scope for the full 30 days: storefront builder, POS, inventory, loyalty, QR menus, WhatsApp Business API sync, inbox sync, route optimisation, rider dispatch, multi-staff roles, CRM, kitchen display hardware and automated chasing. Every one of those is a distraction from closing the first ten subscriptions.

3. Technical implementation plan

Next.js on Vercel serves the dashboard, the paste workflow and a PDF route. Supabase holds merchants, events, line items and documents behind row-level security keyed to the merchant id. A serverless route posts the raw thread to the OpenAI API with a strict JSON schema and stores both the raw text and the parsed result, so every correction is auditable. A validated event row drives React-PDF rendering and creates a Stripe Payment Link for the deposit; subscription billing is a separate Stripe Checkout price at $99 per month, and pack generation is gated on an active subscription.

Build order: scaffold and auth, schema and RLS, extraction route, persistence plus confidence flags, editable table, PDF pack, deposit links, subscription checkout, dashboard and CSV, then hardening with three synthetic end-to-end runs.

The hardest technical risk is extraction on genuinely messy threads: voice-note transcripts, trays versus portions, ambiguous headcounts. The mitigation is non-negotiable: a validation table, per-field confidence highlighting and an explicit assumed marker so the merchant never ships an unchecked number.

4. Pricing and monetization

One plan: Founding Caterer at $99 per month, including 20 Event Order Packs, branded PDFs, deposit links, CSV export and the dashboard. Beyond 20 packs, $15 per pack. No free tier; the first pack is built free as a sales motion, not as a plan. Payment processing is assumed at roughly 4.5% of collected revenue, blending card fees with Stripe Billing and some non-US cards. Expansion comes from pack overage first, then a higher tier for caterers running more than 30 events a month.

5. First-customer acquisition

One channel: Instagram DM to caterers who advertise DM or WhatsApp ordering, starting in a single metro. Build a 50-row prospect sheet before sending anything. Open with the free pack, not the software. Ask for one redacted thread, return the pack within two hours, and only then send the $99 start link. Follow up at 48 hours with one line about reuse across events. Week one target: 50 profiles, 40 DMs, at least 5 real threads delivered.

6. Detailed 30-day execution roadmap

Days 1-6 are build-and-launch, ending with a live payment-accepting product on day 6. Day 1 ships auth and schema; day 2 extraction; day 3 the validation table; day 4 the PDF pack; day 5 Stripe deposit links and subscription checkout; day 6 live mode, TrustMRR connection, a pricing page and a refund policy.

Days 7-14 are first revenue. Day 7 builds the 50-row prospect sheet and sends 20 DMs; days 8-9 deliver free packs from real threads; day 10 collects price signal; day 11 sends start links; day 12 targets the first $99; days 13-14 cut time-to-first-pack under five minutes and pick the winning DM variant.

Days 15-21 expand and prove. A second metro, referral asks, CSV and event filters, one anonymised before/after page, the $15 overage add-on, an FAQ with a data deletion control, and a midpoint go/no-go against the base case.

Days 22-30 push and verify. Fifty new DMs, a private-chef segment test, privacy handling, a second proof page, billing hygiene, a closing sweep to every unconverted trialist, referral conversion, then full Stripe and TrustMRR reconciliation on day 29 and a frozen verified result before 13:00 UTC on day 30.

7. Revenue and profit scenarios

All three scenarios are projections from stated assumptions, not verified revenue or existing customers.

Conservative: 3 customers at $99, gross $297, a $13 processing fee, no refunds, no ads, $25 operating cost. Hackathon profit $284; business profit $259.

Base: 10 customers at $99, gross $990, a $45 processing fee, no refunds, no ads, $60 operating cost. Hackathon profit $945; business profit $885.

Upside: 18 customers at $99, gross $1,782, one $99 refund, an $80 processing fee, no ads, $90 operating cost. Hackathon profit $1,603; business profit $1,513.

The definition that ranks is collected revenue minus refunds, chargebacks, processing fees and paid marketing. Hosting and AI delivery are excluded from that number but still real, which is why they appear in the business-profit line. Selling below delivery cost is never acceptable as a revenue tactic.

8. Main risks and validation experiments

DM response risk: if 60 DMs produce fewer than 3 pack requests by day 12, the opener or the channel is wrong and volume alone will not fix it. Test two openers on 20 DMs by day 7.

Extraction accuracy risk: if more than 20% of line items need manual correction on typical threads, switch from full auto-extraction to guided entry. Test on 10 synthetic messy threads before launch.

Privacy risk: if four of five caterers refuse to paste even a redacted thread, the input path is wrong. Ask five directly and record the objection wording.

Workflow inertia risk: if trialists receive a free pack and never run a second event through it, the product is not sticky. Watch repeat usage inside seven days.

Payment friction risk: if most of a metro cannot accept Stripe links, move metro rather than build new payment rails.

9. First 24-hour action plan

Hours 1-2: repo, Vercel, Supabase, and a pinned extraction schema. Hours 3-5: paste screen and extraction route, tested on three hand-written messy threads. Hours 6-9: editable line-item table, totals and persistence behind magic-link auth. Hours 10-13: three PDF documents rendered from a validated event, with logo and brand colour settings. Hours 14-18: per-event Stripe Payment Link, copyable message, and an end-to-end demo from paste to deposit link. Hours 19-24: a 30-row caterer prospect sheet in one metro and the first 10 DMs sent with logged handles.

Every figure above is a projection. No customers, partnerships or revenue exist at the start of day 1, and none should be claimed until a Stripe payment for that exact amount has settled.

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 →