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

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.

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.49/10
MVP build (solo)
4 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Instagram direct messages to personal chefs and meal-prep operators who publicly post weekly menus.
Who pays

Owner-operator personal chefs and meal-prep businesses of 1-3 people serving 5-40 local households per week, English-speaking in the US, Canada, UK and Australia.

Biggest execution risk

Monetization potential 5.2/10

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

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

0/18
Entry price
$99
Solo build
4 days
30d base revenue
$1,782
30d hackathon profit
$1,724
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator personal chefs and meal-prep businesses of 1-3 people serving 5-40 local households per week, English-speaking in the US, Canada, UK and Australia.

Why now

Chefs publicly post weekly menus under findable hashtags and buy from a DM when shown their own menu as a packet; December menu changes make manual packets painful now.

Problem

For every client, every week, the chef hand-builds a menu, shopping list, prep timeline and reheating notes; merging 8 recipes means unit conversion, duplicate ingredients, pack-size rounding and mid-week re-shops.

Solution

The chef pastes or imports recipes, selects a weekly menu, attaches a client intake profile, and Mise Packet generates one branded PDF: menu grid, aisle-sorted consolidated shopping list with pack-size rounding, batch-cook run sheet, container labels and reheating notes.

Differentiation · Not a recipe library, grocery delivery or Canva template: deterministic consolidation, pack rounding and prep sequencing on the chef's own recipes.

Product opportunity and positioning

Mise Packet is a narrow SaaS wedge for owner-operator personal chefs and 1-3 person meal-prep businesses serving 5-40 local households per week. The buyer already sells weekly menus and already builds a client packet by hand in Google Docs and Canva. The painful work is not creativity; it is the arithmetic and sequencing: converting units, merging duplicate ingredients across eight recipes, rounding to store pack sizes, and turning shared prep into a batch-cook run sheet. Mise Packet turns the chef's own recipes and a client intake profile into one branded PDF containing a 7-day menu grid, a single aisle-sorted shopping list, a time-ordered run sheet, container labels and reheating notes. One menu edit regenerates the packet in minutes.

The positioning is deliberately not meal planning software and not recipe content. The chef's recipes are the input. Mise Packet owns the deterministic consolidation layer: unit normalization, cross-recipe merge, pack-size rounding and prep-step sequencing. The LLM parses loosely written recipes and estimates macros; the math path is custom TypeScript, so output is repeatable enough to review. That matters because a visibly wrong shopping list destroys trust immediately.

Why now: personal chefs publicly post weekly menus under hashtags such as #personalchef, #mealprepchef and #privatechef, and they buy from a direct message when shown their own menu as a client-ready packet. There is no procurement cycle, integration or marketplace cold-start. A $99 one-time founding license is below a typical weekly client billing and can be approved same-day. The demo is the deliverable: generate a sample from a menu the chef already posted, then offer the PDF free.

The JEV score is 64.9/100 (C band), with speed to first revenue as the strongest signal and monetization potential as the weakest. The plan therefore stays narrow: one buyer, one workflow, one acquisition channel, two one-time prices. It does not build grocery delivery, retailer integrations, recipe generation, client invoicing or a mobile app. Success in 30 days means collecting a small number of real licenses from chefs who have seen their own menu turned into a packet; every financial figure in this report is a projection, not verified traction.

Section 2 of 8

Smallest sellable MVP

A branded PDF client packet generated from the chef's own recipes plus a client intake profile, with Stripe checkout gating packet generation.

Must-have features

  • Chef account with one brand profile: business name, logo, two colors and footer contact line
  • Recipe library with paste/import recipe text and structured ingredient extraction
  • Shareable client intake link for allergens, dislikes, household size, macros, budget, equipment and prep day
  • Weekly menu composer that selects recipes and a client profile to generate the packet
  • Deterministic consolidation module for unit normalization, duplicate merge, pack-size rounding and aisle grouping
  • Batch-prep run sheet that collapses shared prep steps into one time-ordered cook plan with container counts
  • Branded PDF export with menu grid, shopping list, run sheet, container labels and reheating notes
  • Stripe Checkout with license gating on packet generation

Explicitly out of scope

  • No recipe content library or recipe generation
  • No grocery delivery, store price lookup or retailer integration
  • No medical, therapeutic or allergen-safety certification claims
  • No invoicing or payments between the chef and their clients
  • No native mobile app; responsive web only
  • No multi-seat team roles or team permissions

Demo flow (what the buyer sees)

  1. Chef pastes or imports 6-8 of their own recipes into the recipe library.
  2. Chef sends a client intake link; client fills allergens, household size, macros, budget, equipment and prep day.
  3. Chef selects the week's recipes and the client profile, then clicks generate.
  4. Mise Packet normalizes units and merges duplicate ingredients across recipes.
  5. It rounds quantities to purchasable pack sizes and groups the list by aisle.
  6. It sequences shared prep steps into a batch-cook run sheet and prints container labels.
  7. Chef downloads a branded PDF packet with menu grid, shopping list, run sheet, labels and reheating notes.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, auth and file storage for logosLLM API with structured JSON output for recipe parsing and macro estimationCustom TypeScript unit-conversion and ingredient-consolidation moduleReact-PDF for branded packet exportStripe CheckoutResend for intake-link and packet delivery emails

Architecture

Chef auth and data live in Supabase. A recipe paste goes to an LLM JSON extraction endpoint for quantities, units, prep state and steps; normalized ingredients and the client intake profile enter a deterministic TypeScript consolidation module. React-PDF renders the packet, Stripe gates generation, and Resend sends intake and packet links. The LLM never does the shopping-list math.

Build steps

  1. Create Next.js app, Supabase schema, Vercel deployment and Stripe payment account.
  2. Build auth, brand profile and logo storage.
  3. Add recipe paste/import form and LLM JSON extraction with a correction UI.
  4. Implement unit normalization, duplicate merge, aisle grouping and pack-size rounding.
  5. Add client intake link and stored client profile.
  6. Generate batch-prep run sheet and React-PDF packet template.
  7. Gate packet generation behind Stripe Checkout and license check.
  8. QA on 20 public chef menus and fix the highest-frequency errors.

AI components

  • LLM structured JSON extraction for recipe ingredients and ordered steps
  • LLM macro estimation per meal with a visible review step
Hardest technical risk: LLM ingredient parsing on loosely written chef recipes producing a visibly wrong shopping list; deterministic math cannot fix missing or misread quantities.
Section 3 of 8

Pricing and monetization

Founding Chef

Entry offer
$99 one-time

For Solo personal chef or meal-prep operator with 5-40 clients

  • 12 months of unlimited client packets
  • One branded profile with logo, colors and footer
  • Recipe library and client intake links
  • PDF export with shopping list, run sheet and container labels

Studio

$249 one-time

For Two-to-three-chef meal-prep studio or private-chef pair running multiple brands

  • Everything in Founding Chef
  • Three separate brand profiles
  • Shared recipe library across the studio

Model: One-time founding license with 12 months of unlimited packets, plus a one-time Studio license for multi-brand studios.

First revenue offer: Reply 'send it' and I will generate your first client packet free from a menu you already posted; a $99 Founding Chef license unlocks unlimited packets for 12 months.

Expected ACV: $99

Upsell path: After the first packet, offer Studio at $249 to chefs with a partner or a second brand; do not count Studio revenue in base.

Target customers
40
Revenue model
$3,960
Costs
$220
Profit model
$3,740
Section 4 of 8

First-customer acquisition

Primary channel

Instagram direct messages to personal chefs and meal-prep operators who publicly post weekly menus.

Where to find them

  • Instagram hashtags #personalchef, #mealprepchef and #privatechef
  • Location searches for personal chef and meal-prep businesses in US, Canada, UK and Australia
  • Public personal-chef directory listings
  • Personal-chef and meal-prep Facebook groups where promotion is allowed
  • Weekly-menu posts from meal-prep studios with 1-3 chefs

Exact outreach motions

  • Build 200 handles with city and weekly-menu posting status.
  • Generate 30 sample packets from menus already posted and attach the PDF in the first DM.
  • Send 40-60 personalised DMs per day with the free-first-packet offer.
  • Reply to every 'send it' with a Stripe checkout link and the $99 framing.
  • Post messy-doc vs packet before/after in allowed groups and link a one-menu free trial.
  • Follow up once at 72 hours on non-replies with a second free packet for another client.

Message template

Saw your weekly menu post. I built a sample client packet from it: branded menu, merged shopping list with pack-size rounding, batch-cook run sheet, container labels. Want the PDF free? If useful, a $99 founding license unlocks unlimited packets for 12 months.
Week-one goal: 200 qualified handles listed, 30 sample packets sent, 150 DMs sent, 3 checkout links opened by day 7, first paid license targeted by day 9.
Section 5 of 8

30-day execution roadmap

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

Set contest start, deploy skeleton, build chef list

  • Create Next.js and Supabase repo and deploy placeholder on Vercel.
  • Create Stripe account and connect TrustMRR payment flow.
  • Build 50-handle Instagram chef list from hashtag and directory searches.
  • Draft sample-packet DM and intake-link copy.

Deliverable: Live placeholder, payment account and 50 qualified chef handles.

Day 2Recipe parsing

Build recipe library and structured ingredient extraction

  • Implement Supabase schema for chefs, recipes, ingredients, clients and packets.
  • Add paste/import recipe form and LLM JSON extraction prompt.
  • Validate extraction on 10 public chef recipes.
  • Add correction UI for quantity, unit and prep state.

Deliverable: Working recipe library with review screen on 10 recipes.

Day 3Consolidation engine

Unit conversion, duplicate merge, pack rounding and aisle grouping

  • Write TypeScript normalization for common units and densities.
  • Merge duplicate ingredients across selected recipes.
  • Round to purchasable pack sizes per aisle category.
  • Unit-test 20 multi-recipe menus against hand totals.

Deliverable: Deterministic shopping-list module with test fixtures.

Day 4Packet export and checkout

PDF generation, branding and Stripe gating

  • Build branded PDF template with menu grid, list, run sheet and labels.
  • Add batch-prep run sheet sequencing and container counts.
  • Add Stripe Checkout and license gate on packet generation.
  • Send test packet to own email.

Deliverable: End-to-end packet PDF behind $99 checkout.

Day 5MVP QA and sample batchMVP shipped

Fix blockers and generate 30 personalised samples

  • Run 5 chef menus through full flow and fix visible errors.
  • Generate 30 sample packets from posted menus.
  • Write disclaimer for macros and allergens.
  • Publish one-menu free trial landing page.

Deliverable: MVP live at day 5 with 30 sample PDFs and trial page.

Day 6DM launch

Send first 40 personalised DMs with samples

  • Warm Instagram account with profile and link.
  • Send 40 DMs attaching sample PDF and free-file offer.
  • Log handle, menu source, reply and next follow-up.
  • Respond to all replies within 2 hours.

Deliverable: 40 DMs sent and tracker live.

Day 7Volume and replies

Send 50 more DMs and handle objections

  • Send 50 DMs to next chef cohort.
  • Follow up with day-6 non-replies at 24 hours.
  • Collect top three objections verbatim.
  • Tweak message template only for clarity.

Deliverable: 90 total DMs and objection list.

Week 2 · Launch & first sale · 7 days
Day 8First checkout links

Convert interested chefs to $99 founding license

  • Send checkout links to every 'send it' reply.
  • Offer a 10-minute packet walkthrough only if asked.
  • Fix one packet-quality bug reported by a chef.
  • Post before/after in one allowed chef group.

Deliverable: Checkout links sent and first group post live.

Day 9First sale targetFirst sale target

Close first paying chef and document proof

  • Follow up all checkout links at 24 hours.
  • Ask first buyer for permission to use anonymised testimonial.
  • Record exact DM-to-checkout path.
  • Send 30 new DMs.

Deliverable: First sale target day with documented conversion path.

Day 10Repeatable sample engine

Reduce sample generation time to under 10 minutes

  • Create sample-generation checklist and folder structure.
  • Generate 20 new samples from recent posts.
  • Send 40 DMs with samples.
  • Track reply rate by hashtag source.

Deliverable: Sample workflow under 10 minutes and 40 DMs sent.

Day 11Packet quality

Fix parser and list edge cases from real menus

  • Review all chef corrections from week one.
  • Add handling for 'to taste', garnishes and split units.
  • Add manual override on shopping list before export.
  • Re-export two flagged packets.

Deliverable: Correction rate measured and edge-case backlog cleared.

Day 12Second cohort

Scale DMs and test different angle

  • Send 50 DMs to meal-prep chefs with weekly menu posts.
  • Test angle: 'your shopping list merged and rounded'.
  • Follow up day-8 to day-10 checkout links.
  • Log replies by segment: personal chef vs meal-prep.

Deliverable: Segment reply data and 50 DMs sent.

Day 13Free-to-paid

Convert free sample users with second client packet

  • Email every sample recipient with second free packet offer.
  • Add one-click checkout to that email.
  • Send 30 DMs.
  • Answer pricing objections with $99 for 12 months framing.

Deliverable: Second-packet email sent and checkout clicks tracked.

Day 14Week 2 review

Decide what to double down on

  • Calculate DMs sent, replies, samples, checkout links and sales.
  • Kill any message angle below 3% reply.
  • Plan week 3 list of 200 new handles.
  • Fix highest-friction onboarding step.

Deliverable: Week-2 metrics memo and week-3 list.

Week 3 · Repeat & systematize · 7 days
Day 15Group distribution

Post before/after in allowed communities

  • Post messy-doc vs packet comparison in two chef groups.
  • Answer comments with free one-menu trial link.
  • Send 40 DMs.
  • Collect screenshots for landing page.

Deliverable: Two community posts and landing-page proof assets.

Day 16Studio tier

Test $249 Studio offer to multi-chef operators

  • Identify 30 two-to-three-chef studios from Instagram bios.
  • Send Studio-specific DM with multi-brand angle.
  • Add Studio checkout link.
  • Ask two solo chefs if they share prep with a partner.

Deliverable: Studio outreach live and first Studio conversations.

Day 17Onboarding

Make first packet self-serve

  • Add 3-step onboarding checklist in app.
  • Add sample recipe import and sample client profile.
  • Record 3-minute Loom walkthrough.
  • Send walkthrough to all free users.

Deliverable: Self-serve onboarding and walkthrough live.

Day 18Objection handling

Convert think-about-it chefs

  • Send second free packet for another client to 10 warm leads.
  • Offer 30-day refund promise only if it protects trust.
  • Follow up all week-1 checkout links.
  • Send 50 new DMs.

Deliverable: Warm-lead reactivation and 50 DMs sent.

Day 19Proof and testimonials

Turn buyers into referrers

  • Ask each buyer for one chef referral.
  • Request anonymised quote about time saved.
  • Add quote to landing page if permitted.
  • Send referral DM to named chefs.

Deliverable: Referral requests sent and testimonials collected.

Day 20Content pull

Publish one useful teardown

  • Write post: what 8 recipes actually need at the store.
  • Include packet before/after without customer data.
  • Share in two allowed communities.
  • Send 40 DMs.

Deliverable: Published teardown and 40 DMs sent.

Day 21Week 3 review

Double down on best segment

  • Compare reply and close rates by segment and hashtag.
  • Rebuild DM script around top objection.
  • Set week-4 target of 15 new checkout links.
  • Fix any PDF branding issue.

Deliverable: Segment scorecard and revised script.

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

Use December menus as urgency

  • Send holiday-menu sample to chefs posting festive menus.
  • Angle: holiday client packets without the spreadsheet.
  • Send 50 DMs.
  • Follow up day-15 group comments.

Deliverable: Holiday cohort DMs and 50 sends.

Day 23Packet breadth

Support more menu shapes without broadening product

  • Add support for 5-day and 7-day menus only.
  • Add equipment-aware prep notes.
  • Test 10 new menus for pack rounding.
  • Update free-trial page examples.

Deliverable: Menu-shape coverage and updated examples.

Day 24Checkout recovery

Recover abandoned checkout links

  • Email chefs who opened checkout but did not buy.
  • Offer one live packet review, not a discount.
  • Send 40 new DMs.
  • Log reasons for abandonment.

Deliverable: Recovery email sent and abandonment reasons logged.

Day 25Referral loop

Make referrals explicit

  • Add refer-a-chef line to buyer email.
  • Offer one extra free month for a referral that buys if needed.
  • DM referred chefs with sample.
  • Send 40 DMs.

Deliverable: Referral loop live and referred-chef DMs sent.

Day 26Quality sweep

Reduce refund risk

  • Audit 10 recent packets for allergen and macro disclaimer placement.
  • Add visible review-before-sending checklist.
  • Fix top 3 parser errors.
  • Re-send corrected packets where needed.

Deliverable: Refund-risk checklist and corrected packets.

Day 27Pipeline push

Fill final week with warm leads

  • Send 50 DMs to new handles.
  • Follow up every non-reply once at 72 hours.
  • Offer free first packet to all group commenters.
  • Post one before/after in an allowed group.

Deliverable: Final-week pipeline and 50 DMs sent.

Day 28Week 4 review

Forecast final two days

  • Count collected revenue, refunds, fees and sales.
  • List every warm lead with next action.
  • Prepare final 48-hour follow-up sequence.
  • Freeze feature work except blockers.

Deliverable: Final forecast and 48-hour sequence.

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

Convert all remaining interested chefs

  • Send personal follow-up to every checkout-link lead.
  • Call any chef who asked for a call.
  • Send 30 final DMs.
  • Fix only blocking packet bugs.

Deliverable: Warm-lead closeout and 30 DMs sent.

Day 30Final collection and handoff

Collect payments before deadline and document learning

  • Send final checkout reminders before 13:00 UTC.
  • Reconcile Stripe payouts and refunds.
  • Export metrics and customer feedback.
  • Write next-30-day plan from evidence.

Deliverable: Final revenue reconciliation and next-step memo.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Conservative: 5 Founding Chef licenses at $99; organic Instagram DMs only; no paid ads.
  • Base: 18 Founding Chef licenses at $99; same channel; 300-500 packets including free samples.
  • Upside: 40 Founding Chef licenses at $99; one refund modeled; Studio conversations not counted as revenue.
  • Payment processing modelled with Stripe at roughly 3.2-3.5% effective on collected revenue including fixed fee.
  • Refunds: 0 in conservative and base, one $99 refund in upside.
  • Chargebacks: 0 in all scenarios; any chargeback would reduce hackathon profit.
  • Ad spend: $0 in all scenarios because acquisition is organic Instagram DMs and allowed group posts.
  • Operating costs cover Vercel, Supabase, Resend, domain and LLM/API delivery: $30/$65/$140 across scenarios.
  • All figures are 30-day projections, not verified revenue, customers or traction.

Conservative

5 customers
$495
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$16
Paid marketing
$0
Hackathon profit
$479
Operating costs
$30
Business profit
$449

Base case

18 customers
$1,782
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$58
Paid marketing
$0
Hackathon profit
$1,724
Operating costs
$65
Business profit
$1,659

Optimistic

40 customers
$3,960
collected revenue · avg payment $99
Refunds
$99
Chargebacks
$0
Payment fees
$128
Paid marketing
$0
Hackathon profit
$3,733
Operating costs
$140
Business profit
$3,593

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,782
Payment fees (3.9%)
$70
Paid marketing
$0
Hackathon profit
$1,713
Business profit
$1,648

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.

Section 7 of 8

Main risks and validation experiments

Risk 1Instagram DM volume of 40-60 per day may trigger rate limits or spam flags, throttling the only acquisition channel.

Mitigation

Send manually in spaced batches, vary message text, and prioritise warm replies over raw volume.

Validation experiment

Send 20 DMs to a test cohort and measure delivery, reply rate and any account warnings.

Kill criteria

If 100 sent DMs produce under 5% replies and account limits appear, switch to email and group comments before abandoning the concept.

Risk 2LLM ingredient parsing on loosely written recipes produces a visibly wrong shopping list in the demo.

Mitigation

Keep math deterministic, show a correction screen, and QA every sample before sending.

Validation experiment

Parse 20 public chef menus and count ingredient lines needing manual correction.

Kill criteria

If more than 20% of ingredient lines need correction after two parser iterations, narrow to structured recipe input only.

Risk 3Willingness to pay $99 one-time is unverified and the real ceiling may be $29-$49.

Mitigation

Use a founding-license frame and ask for a same-day yes after the free sample.

Validation experiment

Track checkout-link opens and purchases from the first 200 DMs.

Kill criteria

If 100 targeted DMs produce fewer than 2 checkout-link opens, test $49 before spending more on outreach.

Risk 4December timing means chefs are in their busiest holiday period and defer purchases to January.

Mitigation

Lead with holiday-menu packets and offer to generate the first packet so they save time this week.

Validation experiment

Compare reply rates on holiday-angle versus standard DM in the same week.

Kill criteria

If holiday-angle replies are below standard replies after 50 sends, revert to the standard weekly-menu angle.

Risk 5The product is copyable in a week, so differentiation depends on packet quality and chef-specific templates.

Mitigation

Focus on consolidation accuracy, pack rounding and prep sequencing rather than broad features.

Validation experiment

Ask five chefs which part of the packet they would miss most if removed.

Kill criteria

If chefs say the branded menu is the only valued part, reposition around menu packaging or stop.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Next.js and Supabase repo.
  • Deploy placeholder to Vercel.
  • Create Stripe account and connect TrustMRR flow.

Output: Live placeholder and payment account.

Hours 3-5

  • Search #personalchef, #mealprepchef and #privatechef.
  • Log 50 handles with city and weekly-menu status.
  • Draft the sample-packet DM.

Output: 50-handle chef list and DM draft.

Hours 6-9

  • Create Supabase tables for chefs, recipes, ingredients, clients and packets.
  • Build recipe paste form.
  • Add LLM JSON extraction endpoint.

Output: Recipe library skeleton with parsing.

Hours 10-14

  • Write unit normalization and duplicate merge.
  • Add aisle grouping and pack-size rounding.
  • Create fixtures from two public menus.

Output: Deterministic consolidation module v1.

Hours 15-20

  • Build React-PDF packet template.
  • Add menu grid, shopping list, run sheet and labels.
  • Generate one sample from a public menu.

Output: First branded sample PDF.

Hours 21-24

  • QA sample for visible errors.
  • Publish one-menu free trial page.
  • Send five test DMs with the sample attached.

Output: Trial page live and first five DMs sent.

Complete report

Full 30-day launch report

Read the full generated report

Mise Packet — public 30-day launch report

1. Product opportunity and positioning

Mise Packet is a narrow tool for owner-operator personal chefs and 1-3 person meal-prep businesses serving 5-40 local households per week. The buyer already sells weekly menus and already builds client packets by hand. The unpaid work is arithmetic and sequencing: unit conversion, merging duplicate ingredients across recipes, rounding to store pack sizes, and collapsing shared prep into one run sheet. Mise Packet turns the chef's own recipes and one client intake profile into a branded PDF with menu grid, aisle-sorted shopping list, batch-cook run sheet, container labels and reheating notes. The wedge is narrow on purpose: one buyer, one workflow, one channel, two one-time prices. The JEV score is 64.9/100 in the C band; speed to first revenue is the strongest signal, monetization potential the weakest. This plan therefore prioritises a sellable packet and DM-led distribution over platform breadth.

2. Smallest sellable MVP

The sellable MVP is one branded PDF packet generated from the chef's own recipes and one client intake profile, behind a Stripe license gate. Must-haves: brand profile, recipe paste/import with structured ingredients, shareable intake link, weekly menu composer, deterministic consolidation with pack-size rounding, batch-prep run sheet, PDF export and checkout gating. Explicitly out of scope: recipe content, grocery delivery, retailer integration, allergen or medical certification, client invoicing, native mobile app and team roles. The demo flow is the deliverable: paste recipes, capture client constraints, generate a packet, download a PDF that looks ready to send.

3. Technical implementation plan

Stack: Next.js on Vercel, Supabase for Postgres, auth and logo storage, an LLM API with structured JSON output for recipe parsing and macro estimates, custom TypeScript for unit conversion and consolidation, React-PDF for the packet, Stripe Checkout and Resend for links and delivery. The LLM never does the shopping-list math. Recipe paste goes to extraction, then normalized ingredients enter a deterministic module that merges duplicates, rounds to purchasable packs and groups by aisle. The packet builder sequences shared prep and renders the PDF. Hardest technical risk: loosely written chef recipes produce missing or misread quantities, creating a visibly wrong list. The correction screen and sample QA are mandatory before any DM sends a PDF.

4. Pricing and monetization

Founding Chef is $99 one-time for 12 months of unlimited client packets, one brand profile, recipe library, intake links and PDF export. Studio is $249 one-time for two-to-three-chef studios with three brand profiles and a shared recipe library. The first-revenue offer is simple: reply 'send it' and the founder generates the first client packet free from a menu the chef already posted; $99 unlocks unlimited packets for 12 months. The upsell path is Studio after the first packet, but base projections count only Founding Chef licenses.

5. First-customer acquisition

Primary channel is Instagram DMs to personal chefs and meal-prep operators who publicly post weekly menus. Build a 200-handle list from hashtags, location searches and directory listings. Generate 30 real sample packets from posted menus and attach the PDF in the first DM. Send 40-60 personalised DMs per day, reply to every 'send it' with a checkout link, and follow up once at 72 hours with a second free packet for another client. Post messy-doc versus packet before/after in allowed chef groups and link a one-menu free trial. Week-one goal: 200 handles, 30 samples, 150 DMs, 3 checkout links opened by day 7 and first paid license targeted by day 9.

6. 30-day execution roadmap

Days 1-5 build the MVP: deploy Next.js and Supabase, add recipe parsing, build the consolidation engine, render the branded PDF, gate with Stripe and publish the trial page. Day 6 launches 40 DMs with samples; day 7 adds 50 more and collects objections; day 8 sends checkout links; day 9 targets the first sale. Week 2 scales samples, fixes parser edge cases, tests meal-prep chefs and converts free users with a second client packet. Week 3 adds allowed group posts, tests the Studio tier, improves self-serve onboarding and asks buyers for referrals. Week 4 uses holiday menus as urgency, recovers abandoned checkout links, runs a referral loop, audits refund risk and fills the pipeline. Days 29-30 close warm leads, send final checkout reminders before the deadline, reconcile Stripe and write the next-30-day memo. Day-level tasks sit in the structured roadmap.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue or traction. Customers are Founding Chef licenses at $99 ARPU. Payment fees assume Stripe at roughly 3.2-3.5% effective. Ad spend is zero because acquisition is organic DMs and allowed group posts. Operating costs cover Vercel, Supabase, Resend, domain and LLM/API delivery. Hackathon profit equals gross revenue minus refunds, chargebacks, payment fees and ad spend; business profit subtracts operating costs. The pipeline derives both from the supplied inputs.

ScenarioCustomersARPUGrossRefundsChargebacksFeesAd spendOperating
Conservative5$99$495$0$0$16$0$30
Base18$99$1,782$0$0$58$0$65
Upside40$99$3,960$99$0$128$0$140

8. Main risks and validation experiments

DM rate limits are the top channel risk. Send manually in spaced batches and test 20 DMs before scaling; if 100 sends produce under 5% replies and warnings appear, move to email and group comments. Parsing errors are the top trust risk. Parse 20 public menus and count corrections; if over 20% of ingredient lines need manual fixes after two iterations, restrict input to structured recipes. Price ceiling is unverified. If 100 targeted DMs produce fewer than 2 checkout-link opens, test $49 before spending more outreach. December timing may defer purchases; compare holiday-angle and standard DM replies after 50 sends. Copyability is real, so validate which packet part chefs would miss most; if only the branded menu matters, stop or reposition.

9. First 24-hour action plan

Hours 1-2: create Next.js and Supabase repo, deploy to Vercel, create Stripe and connect TrustMRR. Hours 3-5: build a 50-handle chef list from hashtags and directory searches, draft the sample DM. Hours 6-9: create schema, recipe paste form and LLM JSON extraction endpoint. Hours 10-14: write unit normalization, duplicate merge, aisle grouping and pack rounding with two public-menu fixtures. Hours 15-20: build the React-PDF packet and generate one sample from a public menu. Hours 21-24: QA the sample, publish the one-menu free trial page, send five test DMs with the PDF attached.

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 →