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

MenuIcon Foundry

MenuIcon Foundry turns a cafe's menu text into a cohesive set of hand-drawn-style dish icons plus a print-ready A3 menu board, delivered as a download.

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.05/10
MVP build (solo)
5 days
Launch price
$149
Sales to $1,000 revenue
7 customers
First paying customer
Instagram DMs to independent cafes with a free 3-icon sample generated from their public menu.
Who pays

Owner/operator of an independent cafe or small restaurant with 1-3 locations, no in-house designer, changing a seasonal menu or opening a new site; France/UK/US, French or English menu.

Biggest execution risk

Market demand 4.2/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; 7 sales at $149 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

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

0/12
Entry price
$149
Solo build
5 days
30d base revenue
$1,788
30d hackathon profit
$1,582
Section 1 of 8

Product opportunity and positioning

Target customer

Owner/operator of an independent cafe or small restaurant with 1-3 locations, no in-house designer, changing a seasonal menu or opening a new site; France/UK/US, French or English menu.

Why now

Independent cafes are changing seasonal menus and opening sites now, publish menus publicly, and can be reached directly by DM with a free sample made from their own menu.

Problem

The cafe needs a distinctive illustrated menu, but custom studio work is too slow and costly for a small operator, and generic icon packs produce inconsistent styles that make the menu look amateur.

Solution

The owner uploads menu text, picks one of six locked illustration styles and brand colors, and the pipeline extracts dishes, generates 12 matching icons with one style seed and palette, removes backgrounds, and lays them into an A3/A4 PDF plus transparent PNGs and Instagram squares.

Differentiation · A custom illustrator is slow and expensive; stock and Canva packs mix styles. MenuIcon Foundry locks one style, palette and line weight across every dish and returns a print-ready board in a day for $149.

1. Product opportunity and positioning

MenuIcon Foundry is a narrow software artifact generator for independent cafes. The buyer is the owner/operator of one to three cafes with no in-house designer, changing a seasonal menu or opening a new site. The trigger is a menu change, a new opening, a holiday menu, or a public menu post that exposes mismatched icons. The buyer does not want a brand identity project. They want a coherent illustrated menu board this week.

The alternatives are specific and bad. A custom illustrator is slow and expensive. Stock or Canva icon packs mix line weights and palettes. Generic AI image tools produce 12 unrelated dishes. MenuIcon Foundry locks one style seed, palette and line weight across 12 dish icons, removes backgrounds, and lays them into an A3/A4 PDF plus transparent PNGs and Instagram squares. The output is a print-ready menu board for $149, delivered as a download within 24 hours of payment.

JEV scored this exact concept 60.5/100 (C band). Speed to first revenue is strong; market demand and monetization are the weak criteria. This plan is built around that split. Demand is attacked with a free 3-icon sample generated from the cafe's public menu, not with a broad pitch. Monetization is tied to a deadline event and a repeatable seasonal refresh, not a vague subscription. The wedge stays narrow: one buyer, one output, one channel. No marketplace, no SEO ramp, no ads budget, no human illustration service.

Section 2 of 8

Smallest sellable MVP

A Stripe-paid intake page that accepts menu text, a style preset and an optional logo, then returns 12 QA'd icons, transparent PNGs and an A3/A4 PDF menu board within 24 hours.

Must-have features

  • Public-menu text intake and editable dish/ingredient extraction
  • Six locked style presets with palette, line weight, prompt template and seed
  • Batch generation of 12 icons per order with re-roll and founder QA
  • Background removal and transparent PNG/WebP export
  • Print-ready A3/A4 PDF menu board with names, prices and optional logo
  • Stripe Checkout and private download page
  • Resend delivery email with zip
  • 3-icon free sample generator for DM outreach

Explicitly out of scope

  • Custom logo or full brand identity design
  • Human illustration revisions beyond automated re-rolls
  • Print fulfillment or shipping
  • Website builder, social scheduler or POS integration
  • Multi-user team accounts
  • Marketplace or public template store

Demo flow (what the buyer sees)

  1. Owner opens intake page and pastes menu text.
  2. Pipeline extracts dishes and ingredients into an editable list.
  3. Owner selects one of six locked styles and brand colors.
  4. Generation job creates 12 icons with one seed and palette.
  5. Founder QA console checks consistency and re-rolls weak icons.
  6. Backgrounds are removed and assets stored.
  7. react-pdf renders an A3/A4 menu board with names, prices and optional logo.
  8. Stripe payment unlocks a private download page and delivery email with zip.
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres and storageStripe CheckoutOpenAI Images or Recraft APIremove.bg or rembgreact-pdfResendTypeScriptZod for intake validationFounder QA admin console

Architecture

The intake form stores menu text and style choices in Supabase. A parser extracts dishes and ingredients into an editable list. A generation job calls the image API with the locked style prompt, palette and seed, then stores each asset. Background removal creates transparent PNG/WebP files. react-pdf renders the A3/A4 board, and Stripe webhooks unlock a private download page and Resend email. The founder QA console shows every icon, allows re-rolls and logs API cost per order.

Build steps

  1. Scaffold Next.js app and deploy to Vercel.
  2. Create Supabase tables for orders, menus, icons, styles and assets.
  3. Build intake form with menu text, style choice and optional logo upload.
  4. Wire LLM parser for editable dish and ingredient extraction.
  5. Create six locked style presets with prompt, palette and seed.
  6. Add batch icon generation with per-project seed and QA console.
  7. Add background removal, storage and zip export.
  8. Build react-pdf A3/A4 layout with icons, names, prices and logo slot.
  9. Connect Stripe Checkout, webhook and private delivery page.
  10. Add Resend delivery email and free 3-icon sample generator.

AI components

  • LLM extracts dishes and ingredients from menu text.
  • Image model generates 12 dish icons from locked prompt templates.
  • Optional logo-aware layout uses image processing, not a generative model.
Hardest technical risk: Style consistency across 12 icons with one seed and palette while keeping each dish recognizable; mitigation is locked prompt templates, founder QA and a two-re-roll limit.
Section 3 of 8

Pricing and monetization

Cafe Menu Kit

Entry offer
$149 one-time

For Independent cafe or small restaurant owner changing a menu

  • 12 custom dish icons in one locked style
  • A3/A4 print-ready PDF menu board
  • Transparent PNGs and Instagram square exports
  • One menu layout revision

Model: One-time $149 Cafe Menu Kit per cafe, sold through Stripe Checkout.

First revenue offer: I made these 3 icons from your public menu. Want the full 12-icon A3/A4 board for $149 this week? I deliver within 24 hours of payment.

Expected ACV: $149

Upsell path: After delivery, offer a second-location kit or seasonal refresh at $149 and ask for one referral to another cafe owner.

Target customers
20
Revenue model
$2,980
Costs
$180
Profit model
$2,800
Section 4 of 8

First-customer acquisition

Primary channel

Instagram DMs to independent cafes with a free 3-icon sample generated from their public menu.

Where to find them

  • Instagram search for Lyon and Paris specialty coffee hashtags
  • Public Google Maps listings of independent cafes
  • Cafe accounts posting recent seasonal menu changes
  • Cafe accounts announcing new openings
  • Local coffee guide lists and tagged cafes
  • English-language UK and US cafe accounts with public menus

Exact outreach motions

  • Collect 30 handles with a public menu and a clear trigger event.
  • Generate a 3-icon sample from each public menu.
  • Send the sample image with the exact $149 offer and 24-hour delivery promise.
  • Log send time, reply status and objection category.
  • Follow up once after 48 hours with one new icon or a print-size detail.
  • Ask every buyer for one referral after delivery.

Message template

I made these 3 icons from your public menu. Want the full 12-icon A3/A4 board for $149 this week? I deliver within 24 hours of payment.
Week-one goal: 60 handles collected, 30 samples generated, 30 DMs sent and at least 3 replies.
Section 5 of 8

30-day execution roadmap

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

Scaffold app and data model

  • Create Next.js app on Vercel.
  • Create Supabase tables for orders, menus, icons, styles.
  • Add Stripe test keys and env vars.
  • Build empty intake form.

Deliverable: Deployed scaffold with DB schema.

Day 2Menu intake

Extract dishes and ingredients

  • Wire LLM parser for menu text.
  • Build editable dish list with quantities.
  • Add optional logo upload.
  • Add six style preset records.

Deliverable: Working intake and editable extraction.

Day 3Icon generation

Batch 12 icons with locked style

  • Call image API with style seed and palette.
  • Store prompt, seed and asset per icon.
  • Build founder QA and regenerate console.
  • Log per-order API cost.

Deliverable: Internal batch generation console.

Day 4Asset export

Remove backgrounds and package files

  • Run remove.bg or rembg on generated icons.
  • Store transparent PNG and WebP in Supabase.
  • Zip assets per order.
  • Add retry and failed-icon handling.

Deliverable: Transparent asset pipeline and zip.

Day 5PDF menu

Render A3/A4 board

  • Build react-pdf A3/A4 layout.
  • Place icons, dish names and prices.
  • Add optional logo slot.
  • Test five public menus.

Deliverable: End-to-end PDF menu board.

Day 6QA

Harden sample and delivery

  • Build free 3-icon sample generator.
  • Run five test orders and log failures.
  • Fix icon consistency and PDF overflow.
  • Write delivery email via Resend.

Deliverable: Five QA'd test orders.

Day 7LaunchMVP shipped

Go live with checkout

  • Connect Stripe Checkout and webhook.
  • Publish pricing, terms and refund policy.
  • Test paid order in test mode.
  • Deploy production build.

Deliverable: Live product accepting payments.

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

Build first 30 cafe list

  • Search Instagram for Lyon and Paris cafes.
  • Collect handles with recent menu posts.
  • Record menu link and trigger event.
  • Prioritise seasonal or new openings.

Deliverable: 30-handle outreach sheet.

Day 9Samples

Generate 15 free samples

  • Pull public menu text for 15 cafes.
  • Generate 3 icons per cafe.
  • QA samples for dish recognition.
  • Name files by handle.

Deliverable: 15 sample images.

Day 10Outreach

Send first 15 DMs

  • Send sample with exact offer.
  • Log send time and reply status.
  • Ask one clarifying question.
  • Schedule 48-hour follow-up.

Deliverable: 15 DMs sent.

Day 11Outreach

Send next 15 DMs

  • Generate 15 more samples.
  • Send 15 DMs.
  • Update reply tracker.
  • Refine message if low opens.

Deliverable: 30 total DMs sent.

Day 12First saleFirst sale target

Close first paying cafe

  • Follow up all 48-hour non-replies.
  • Answer style and print questions.
  • Send Stripe checkout link.
  • Record first paid order.

Deliverable: First paid order or documented objection.

Day 13Delivery

Deliver first kit in 24 hours

  • Run full 12-icon generation.
  • QA icons and PDF print size.
  • Send private download page.
  • Ask for one referral.

Deliverable: Delivered first Cafe Menu Kit.

Day 14Pipeline

Measure and refill

  • Calculate reply and sample-to-sale rates.
  • Add 20 new cafe handles.
  • Send 10 follow-ups.
  • Generate 10 new samples.

Deliverable: Funnel stats and refilled pipeline.

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

Improve consistency from feedback

  • Review buyer corrections.
  • Tighten prompt templates and palette locks.
  • Add re-roll limits to delivery page.
  • Update QA checklist.

Deliverable: Revised prompt and QA checklist.

Day 16Offer

Add second-location and seasonal upsell

  • Add $149 second-location kit copy.
  • Add seasonal refresh request form.
  • Update delivery page.
  • Email previous buyers.

Deliverable: Upsell offer live.

Day 17Outreach

Send 20 new DMs

  • Generate 20 samples.
  • Send 20 DMs with deadline.
  • Log objections by category.
  • Follow up day-10 leads.

Deliverable: 20 new DMs and objection log.

Day 18Referral

Turn deliveries into referrals

  • Ask every buyer for one cafe name.
  • Send referral thank-you copy.
  • Post two anonymised sample boards.
  • Track referral source in Stripe metadata.

Deliverable: Referral asks and posts.

Day 19Delivery

Clear paid backlog

  • Generate and QA all open orders.
  • Fix PDF margin issues.
  • Send delivery emails.
  • Request print feedback.

Deliverable: Backlog delivered.

Day 20Print QA

Verify print-ready output

  • Print one A3 test at local shop.
  • Check colour and bleed.
  • Update PDF template.
  • Document print settings.

Deliverable: Print-checked PDF template.

Day 21Review

Cut weak segment

  • Compare Lyon vs Paris reply rates.
  • Cut lowest-converting segment.
  • Double down on best trigger event.
  • Set week-four targets.

Deliverable: Segment decision memo.

Week 4 · Scale what works · 7 days
Day 22Expansion

Add English-speaking cafes

  • Collect 30 UK and US cafe handles.
  • Prioritise new openings and menu changes.
  • Generate 15 English samples.
  • Send 15 DMs.

Deliverable: 30 English-market handles.

Day 23Outreach

Send 15 English DMs

  • Send sample and offer.
  • Log replies.
  • Follow up 48 hours later.
  • Test British spelling variant.

Deliverable: 15 English DMs sent.

Day 24Speed

Reduce delivery time

  • Automate failure retries.
  • Precompute style prompts.
  • Add one-click QA flags.
  • Target under 45 minutes per order.

Deliverable: Faster order console.

Day 25Upsell

Sell seasonal refresh

  • Email all buyers seasonal offer.
  • Offer second-location kit.
  • Add deadline for this week.
  • Track upsell revenue separately.

Deliverable: Upsell campaign sent.

Day 26Outreach

Send 20 deadline DMs

  • Generate 20 samples.
  • Send 20 DMs with this-week deadline.
  • Follow up all non-replies once.
  • Log closed-lost reasons.

Deliverable: 20 deadline DMs.

Day 27Conversion

Fix top objection

  • Group objections from tracker.
  • Rewrite message for top objection.
  • Test new opener on 10 DMs.
  • Update FAQ on site.

Deliverable: Revised message and FAQ.

Day 28Close

Convert warm leads

  • Send checkout links to warm leads.
  • Offer one revision to hesitators.
  • Confirm delivery dates.
  • Record payments.

Deliverable: Warm leads closed or marked lost.

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

Deliver and reconcile

  • Deliver all paid orders.
  • Process any refunds.
  • Reconcile Stripe vs TrustMRR.
  • Export revenue and fee report.

Deliverable: Clean delivery and payment ledger.

Day 30Wrap

Final report and next step

  • Calculate verified profit inputs.
  • Archive prompts, samples and PDFs.
  • Write post-hackathon offer for buyers.
  • Ask every buyer for referral.

Deliverable: Final reconciliation and referral list.

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 paid cafes from 60 targeted DMs; Base: 12 paid cafes from 180 targeted DMs; Upside: 22 paid cafes from 300 targeted DMs. These are projections, not validated demand.
  • Stripe is assumed at 3% + $0.30 per transaction for payment_fees_usd.
  • No paid marketing; ad_spend_usd is 0 because the channel is organic Instagram DMs.
  • Operating costs cover image API, remove.bg or rembg, Vercel, Supabase, Resend and domain, at roughly $5-$7 per order plus fixed tooling.
  • Refunds: Conservative 0; Base one $149 refund; Upside two $149 refunds. Chargebacks are 0 in all scenarios.
  • Every scenario is a projection, not verified revenue, customers or traction.

Conservative

5 customers
$745
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$24
Paid marketing
$0
Hackathon profit
$721
Operating costs
$35
Business profit
$686

Base case

12 customers
$1,788
collected revenue · avg payment $149
Refunds
$149
Chargebacks
$0
Payment fees
$57
Paid marketing
$0
Hackathon profit
$1,582
Operating costs
$70
Business profit
$1,512

Optimistic

22 customers
$3,278
collected revenue · avg payment $149
Refunds
$298
Chargebacks
$0
Payment fees
$105
Paid marketing
$0
Hackathon profit
$2,875
Operating costs
$120
Business profit
$2,755

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,788
Payment fees (3.9%)
$70
Paid marketing
$0
Hackathon profit
$1,718
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 limits or account restrictions reduce outreach volume.

Mitigation

Send 20-30 DMs per day, warm the account, log blocks and keep a backup direct channel.

Validation experiment

Send 10 DMs on day 8 and record delivery, replies and restrictions.

Kill criteria

If more than 40% of sends are blocked, switch to email or another direct channel before scaling.

Risk 2Generated icons do not match the cafe's expected style or dish accuracy.

Mitigation

Use locked prompt templates, one palette per order, founder QA and a two-re-roll limit.

Validation experiment

Run a blind five-menu QA and score 12-icon recognisability.

Kill criteria

If fewer than 7 of 12 icons are recognizable after two re-rolls, stop selling until prompts are fixed.

Risk 3Low conversion from free sample to paid order.

Mitigation

Track objections by category and rewrite the offer around the top objection.

Validation experiment

After 60 well-targeted DMs with samples, measure paid orders.

Kill criteria

If there are zero paid orders after 60 well-targeted DMs, test a $99 pilot for 10 cafes before spending more.

Risk 4PDF is not print-ready, causing refunds.

Mitigation

Print one A3 test locally and document bleed, colour and margin settings.

Validation experiment

Print an A3 test by day 20 and inspect colour and bleed.

Kill criteria

If print issues cannot be fixed by day 10, refund and pause sales until the template is corrected.

Risk 5Image API quality or pricing changes mid-build.

Mitigation

Pin the model version and keep a fallback image provider.

Validation experiment

Calculate delivery cost per test order during day 6 QA.

Kill criteria

If delivery cost exceeds $15 per order, rework the pipeline or raise price before launch.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-3

  • Lock scope to the cafe menu kit.
  • Create repo and Supabase project.
  • Set env vars for Stripe, image API and Resend.

Output: Deployed scaffold and schema.

Hours 4-6

  • Build intake form with menu text and style field.
  • Add parser stub and editable dish list.
  • Create six style preset records.

Output: Menu text accepted and dishes editable.

Hours 7-9

  • Generate a three-icon test sheet with one style seed.
  • Check dish recognition and palette.
  • Log API cost and latency.

Output: One visual style proof.

Hours 10-24

  • Build the free 3-icon sample generator.
  • Create a 30-handle outreach tracker template.
  • Generate one real sample from a public menu.

Output: One free sample and first prospect list.

Complete report

Full 30-day launch report

Read the full generated report

MenuIcon Foundry — 30-Day Launch Report

1. Product opportunity and positioning

MenuIcon Foundry is a narrow software artifact generator for independent cafes. The buyer is the owner/operator of one to three cafes with no in-house designer, changing a seasonal menu or opening a new site. The trigger is a menu change, a new opening, a holiday menu, or a public menu post that exposes mismatched icons. The buyer does not want a brand identity project. They want a coherent illustrated menu board this week.

The alternatives are specific and bad. A custom illustrator is slow and expensive. Stock or Canva icon packs mix line weights and palettes. Generic AI image tools produce 12 unrelated dishes. MenuIcon Foundry locks one style seed, palette and line weight across 12 dish icons, removes backgrounds, and lays them into an A3/A4 PDF plus transparent PNGs and Instagram squares. The output is a print-ready menu board for $149, delivered as a download within 24 hours of payment.

JEV scored this exact concept 60.5/100 (C band). Speed to first revenue is strong; market demand and monetization are the weak criteria. This plan is built around that split. Demand is attacked with a free 3-icon sample generated from the cafe's public menu, not with a broad pitch. Monetization is tied to a deadline event and a repeatable seasonal refresh, not a vague subscription. The wedge stays narrow: one buyer, one output, one channel. No marketplace, no SEO ramp, no ads budget, no human illustration service.

2. Smallest sellable MVP

The smallest sellable MVP is a Stripe-paid intake page that accepts menu text, a style preset and an optional logo, then returns 12 QA'd icons, transparent PNGs and an A3/A4 PDF menu board within 24 hours. It must include editable dish extraction, six locked style presets, batch generation with a single seed, background removal, PDF layout, a private download page and a delivery email. The free 3-icon sample generator is part of the MVP because it is the acquisition tool.

Out of scope: custom logo design, human illustration revisions beyond automated re-rolls, print fulfillment, website building, POS integration, team accounts, marketplace templates and a public template store. The founder does not promise unlimited revisions. One menu layout revision is included.

3. Technical implementation plan

Stack: Next.js on Vercel, Supabase Postgres and storage, Stripe Checkout, OpenAI Images or Recraft for icon generation, remove.bg or rembg for background removal, react-pdf for the menu board, Resend for delivery email, and a small admin console for QA.

The flow is linear. The intake form stores menu text and style choices. A parser extracts dishes and ingredients into an editable list. A generation job creates 12 icons using the locked style prompt, palette and seed. Assets are background-removed and stored. The PDF renderer places icons, dish names, prices and an optional logo into an A3/A4 template. The paid order unlocks a private download page with a zip and a delivery email. The founder QA console shows every icon, allows re-rolls and logs API cost per order.

Build steps: scaffold the app, create the schema, build intake and extraction, add style presets, wire image generation, add background removal, build the PDF, connect Stripe, add delivery email, then build the sample generator. The hardest technical risk is style consistency across 12 icons while keeping each dish recognizable. The mitigation is locked prompt templates, one palette per order, a founder QA step and a two-re-roll limit.

4. Pricing and monetization

One offer: Cafe Menu Kit at $149 one-time. It includes 12 custom dish icons in one locked style, an A3/A4 print-ready PDF menu board, transparent PNGs and Instagram square exports, and one menu layout revision. There is no subscription and no per-seat pricing. The first-revenue offer is the exact DM: 'I made these 3 icons from your public menu. Want the full 12-icon A3/A4 board for $149 this week? I deliver within 24 hours of payment.' The expected average order value is $149. Upsell after delivery is a second-location kit or a seasonal refresh at $149, plus one referral ask.

5. First-customer acquisition

The only primary channel is Instagram DMs to independent cafes with a free 3-icon sample generated from their public menu. The founder finds cafes through Instagram search for Lyon/Paris specialty coffee and cafe hashtags, public Google Maps listings, recent menu-change posts, new-opening announcements and local coffee guides. Outreach is manual and logged. For each cafe, generate three icons, send the image, state the $149 price and the 24-hour delivery promise, then follow up once after 48 hours. Week-one goal: 60 handles collected, 30 samples generated, 30 DMs sent and at least 3 replies. No paid ads.

6. Detailed 30-day execution roadmap

Days 1-5: build the order pipeline. Day 1 scaffolds Next.js, Supabase and Stripe. Day 2 ships menu extraction and six style presets. Day 3 adds batch icon generation and QA console. Day 4 adds background removal, storage and zip export. Day 5 renders the A3/A4 PDF and delivery page.

Days 6-7: harden and launch. Day 6 runs five test menus, fixes icon consistency and PDF overflow, and builds the sample generator. Day 7 connects Stripe Checkout, publishes terms and refund policy, tests a paid order and deploys production.

Days 8-14: first sales. Day 8 builds a 30-cafe list. Day 9 generates 15 free samples. Day 10 sends 15 DMs. Day 11 sends 15 more. Day 12 follows up and closes the first paid order. Day 13 delivers the first kit in 24 hours and asks for a referral. Day 14 measures reply and sample-to-sale rates, then refills the pipeline.

Days 15-21: quality and repeat. Day 15 tightens prompts from buyer feedback. Day 16 adds the second-location and seasonal upsell. Day 17 sends 20 new DMs. Day 18 asks every buyer for one referral. Day 19 clears paid backlog. Day 20 runs an A3 print test. Day 21 cuts the lowest-converting segment and sets week-four targets.

Days 22-30: expansion and close. Day 22 collects 30 English-market cafe handles. Day 23 sends 15 English DMs. Day 24 reduces delivery time. Day 25 emails buyers the seasonal refresh. Day 26 sends 20 deadline DMs. Day 27 fixes the top objection. Day 28 closes warm leads. Day 29 delivers and reconciles Stripe. Day 30 calculates verified profit inputs, archives assets and asks every buyer for a referral.

7. Revenue and profit scenarios

These are projections, not verified revenue. Conservative: 5 customers at $149 = $745 gross, $24 payment fees, $0 refunds, $0 chargebacks, $0 ad spend, $35 operating costs. Base: 12 customers = $1,788 gross, one $149 refund, $57 payment fees, $0 chargebacks, $0 ad spend, $70 operating costs. Upside: 22 customers = $3,278 gross, two $149 refunds, $105 payment fees, $0 chargebacks, $0 ad spend, $120 operating costs. Stripe is assumed at 3% + $0.30 per transaction. Operating costs cover image API, background removal, hosting, storage and email. The contest ranks hackathon profit before operating costs; business profit subtracts them. None of these numbers are customers or traction.

8. Main risks and validation experiments

DM limits: keep sends to 20-30 per day, warm the account, log blocks. Test 10 DMs on day 8. If more than 40% are blocked, switch to email or another direct channel before scaling.

Icon mismatch: run a five-menu blind QA. If fewer than 7 of 12 icons are recognizable after two re-rolls, stop selling until prompts are fixed.

Low conversion: after 60 well-targeted DMs with samples, if there are zero paid orders, rewrite the offer and test a $99 pilot for 10 cafes. Do not spend on ads.

Print failure: print one A3 test locally by day 20. If bleed, colour or margins fail and cannot be fixed by day 10, refund and pause sales until the template is corrected.

9. First 24-hour action plan

Hours 1-3: lock scope, create the repo, Supabase project and env vars. Output: deployed scaffold and schema.

Hours 4-6: build the intake form and parser stub. Output: menu text accepted and dishes editable.

Hours 7-9: create six style presets and generate a three-icon test sheet. Output: one visual style proof.

Hours 10-24: build the sample generator and a 30-handle outreach tracker. Output: one free sample and the first prospect list.

This brief was generated from public data about established startups, then narrowed and scored for a solo 30-day launch. Revenue and profit figures are scenario models, not verified results, guarantees or evidence of existing customers. Validate demand yourself before you spend a month on it — and check the contest rules for what counts toward your score.

Related ideas

All ideas →