ArtisanQuote
ArtisanQuote turns a messy corporate event email into a branded, allergen-tagged, margin-checked catering quote PDF in under two minutes.
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.
Independent artisanal caterers and food craftsmen with 1-10 employees who receive corporate lunch and event inquiries by email and currently quote in Word or Excel, in France, the UK and the US.
Operational simplicity 4.9/10
Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.
Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 11; 4 sales at $299 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
14 concrete actions. Tick them off as you go — nothing is saved or sent.
Product opportunity and positioning
Target customer
Independent artisanal caterers and food craftsmen with 1-10 employees who receive corporate lunch and event inquiries by email and currently quote in Word or Excel, in France, the UK and the US.
Why now
Cheap structured-output LLM calls make messy-email parsing reliable at roughly a cent per quote, and a $299 one-time tool sits inside a small caterer's discretionary spend with no procurement cycle.
Problem
Corporate event inquiries arrive as unstructured emails with headcount, budget, dietary needs and venue constraints; caterers spend 1-2 hours rebuilding a quote manually, often underprice, and risk missing an allergen.
Solution
Load the menu once as CSV or pasted text, paste the client email, and the tool extracts constraints, matches menu items, flags missing dietary coverage, applies margin guardrails and renders a branded PDF quote with an allergen matrix and a Stripe deposit link.
1. Product opportunity and positioning
Independent artisanal caterers with 1-10 employees live on inbound email. A corporate event inquiry lands with a headcount, a date, a budget ceiling, three dietary restrictions and a venue constraint - and the caterer spends 60 to 120 minutes rebuilding a quote in Word, guessing at margins and hand-checking allergens. Two failure modes follow: underpricing a job that then eats the week, or missing a nut-free requirement and losing the client or carrying liability.
ArtisanQuote collapses that into one workflow. The caterer uploads a menu once as CSV or pasted text. They paste the client email. The tool extracts the event constraints, matches them against the menu, flags missing dietary coverage, applies margin guardrails, and emits a branded PDF quote with an allergen matrix and a Stripe deposit link.
Positioning is deliberately narrow: a single-player quoting tool on the supply side of corporate catering, not a marketplace. The original Monbanquet.fr connected corporate buyers to artisans through a two-sided network that needed supply density, demand density and a working commission take rate before it delivered value. ArtisanQuote needs one caterer and one email. No cold-start, no commission, no logistics, no photographer, no courier.
The wedge is the artifact. Caterers already have the pain weekly and already have a menu they can paste. The product's output is something they send to a paying client within minutes of buying, which makes the ROI argument concrete rather than theoretical: one won event above $1,000 pays for the license three times over.
Why now: structured-output LLM calls are cheap and accurate enough to parse a messy email and a pasted menu at roughly a cent per quote, and a $299 one-time purchase sits inside a small caterer's discretionary spend without procurement, IT review or approval chains.
Differentiation against the generic alternative matters here. ChatGPT or a Word template produces prose the caterer still has to verify. ArtisanQuote runs a deterministic matcher against the caterer's own allergen-tagged menu and enforces a per-item margin floor, so the deliverable is a checked artifact with a visible allergen matrix, not a draft that quietly invents a gluten-free option.
JEV scored this concept 63.5/100, band C. The strongest dimension is speed to first revenue (8.28); the weakest is operational simplicity (4.94). The plan below is shaped by both: keep the system stateless on managed services and get a paid transaction inside week two rather than polishing the generator.
Smallest sellable MVP
A single-page web app where a caterer pastes a menu and a client email and downloads one correct branded quote PDF, sold through a Stripe checkout that is live on day 5.
Must-have features
- Menu import from CSV paste or pasted text: item name, ingredients, cost, price, allergen tags.
- Brief parser that extracts event date, headcount, budget ceiling, dietary restrictions and service style from a pasted email.
- Constraint matcher that flags uncovered dietary restrictions and proposes menu substitutions.
- Margin guardrail that blocks or warns when a line item prices below a configurable floor.
- Server-rendered branded quote PDF with itemized pricing, allergen matrix and terms.
- Stripe Checkout for the founding license plus a reusable Stripe deposit link inside the quote.
- History dashboard listing past quotes and reusing stored menu data.
Explicitly out of scope
- Two-sided marketplace, client-facing portal, or caterer discovery.
- Invoicing, accounting, payroll or inventory management.
- Multi-user team accounts and role permissions.
- Native mobile app.
- POS, calendar or CRM integrations.
- Automated follow-up emails to the caterer's own clients outside 30 days.
Demo flow (what the buyer sees)
- Caterer buys the founding license on Stripe Checkout and lands in the app.
- Caterer pastes 12 menu items with prices and allergen tags.
- Caterer pastes a sample corporate brief: 60 guests, 14 November, nut-free and two vegetarian.
- App shows extracted constraints and flags one missing vegetarian main.
- Caterer accepts a substitution and confirms the 32% margin floor.
- App renders the branded PDF with allergen matrix and deposit link; caterer downloads it.
Technical implementation plan
Stack
Architecture
A Next.js app on Vercel holds auth via Supabase magic links. Menus and quotes live in two Supabase tables scoped by user id through row-level security. Two LLM calls do parsing only: one normalizes the pasted menu into a typed item list, one extracts the event brief into a typed constraint object. Neither call is allowed to invent allergen tags - unknown values are stored as 'unverified' and surfaced as warnings. A deterministic TypeScript matcher joins brief constraints to menu items, applies the margin floor and produces a quote model. That model is rendered to PDF by @react-pdf/renderer inside a serverless route and stored in Vercel Blob; the download link is emailed via Resend. Stripe Checkout gates the license and a separate Payment Link is generated per quote as a client deposit.
Build steps
- Scaffold Next.js repo, Supabase project, and Vercel deployment with a placeholder landing page.
- Create schemas: caterers, menus, menu_items, quotes, quote_line_items.
- Build menu paste and CSV importer with the normalization LLM call and a manual edit table.
- Build brief parser with structured output and a visible extracted-constraints panel.
- Implement the deterministic constraint matcher with dietary coverage flags and substitution suggestions.
- Implement margin guardrail rules with configurable floor percentage per caterer.
- Build the PDF template: header, itemization, allergen matrix, terms, deposit link.
- Wire Stripe Checkout for the founding license and a per-quote deposit Payment Link.
- Add a dashboard listing quotes with re-download and menu reuse.
- Run 10 real caterer menus end to end, fix parsing failures, deploy to production domain.
AI components
- OpenAI structured-output call to normalize a pasted menu into typed items with ingredients, cost, price and stated allergens.
- OpenAI structured-output call to extract event date, headcount, budget ceiling, dietary restrictions and service style from the client email.
- Optional constrained call to suggest a substitution from existing menu items only - never to invent a dish.
Pricing and monetization
Founding Solo
Entry offerFor Solo artisanal caterer
- Unlimited quote PDFs for 6 months
- Branded PDF with allergen matrix
- Margin guardrails
Founding Studio
For Small catering team
- Everything in Solo
- Custom logo on PDF
- Stripe deposit links
- 12 months access
Founding Company
For Catering company with multiple event managers
- 3 users
- 12 months access
- Priority email support
Model: One-time founding license with three tiers, sold through Stripe Checkout, with a 14-day money-back guarantee.
First revenue offer: Founding Solo at $299 one-time for the first 20 caterers, including a sample quote built from their own menu before they pay, and a 14-day money-back guarantee.
Expected ACV: $324
Upsell path: Tier upgrades at purchase (Studio, Company), then a $149/year renewal after the included access period, then paid add-ons for extra seats and custom PDF branding.
First-customer acquisition
Personalized cold email with a 90-second Loom demo built from the caterer's own menu, to 300 independent caterers in Paris and London.
Where to find them
- Google Maps listings for 'traiteur artisanal' in Paris arrondissements 1-20.
- Google Maps listings for 'artisan caterer' and 'event caterer' in London boroughs.
- Caterer websites with a public menu page and a contact@ or info@ address.
- Instagram and LinkedIn profiles of independent caterers posting corporate lunch photos.
- Directory listings for organic and specialty caterers with a published email.
Exact outreach motions
- Send email 1 with a Loom built from one real menu item and one sample corporate brief.
- Send one follow-up 3 days later with the Stripe checkout link and the money-back guarantee.
- Comment meaningfully on a recent Instagram or LinkedIn post before emailing.
- Call the caterer's public number if a follow-up goes unanswered for 5 days.
- Offer to build the first quote live on a 15-minute call for anyone who replies with interest.
Message template
Hi [Name] - I built a tool that turns a corporate event email into a branded catering quote PDF with an allergen matrix, in about two minutes. Here is a 90-second demo using three items from your [menu page / site]: [Loom link]. Founding license is $299 one-time with a 14-day refund. Want the link?
30-day execution roadmap
Week 1 · Build & validate · 7 days
Accounts and skeleton
- Create GitHub repo, Supabase project and Vercel deployment.
- Connect Stripe to TrustMRR before any payment is taken.
- Ship a landing page with the offer and an email capture form.
Deliverable: Live landing page and connected Stripe account.
Menu data model
- Create tables for caterers, menus, menu_items, quotes and line items.
- Build menu paste importer with the normalization LLM call.
- Add an editable table so caterers can fix parsed items.
Deliverable: Working menu import with manual correction.
Brief parsing and matching
- Build brief parser with structured output.
- Ship the extracted-constraints review panel.
- Implement the deterministic dietary matcher with substitution suggestions.
Deliverable: Brief in, constraint report out.
PDF and payments
- Build the PDF template with itemization, allergen matrix and terms.
- Add margin guardrail rules with a configurable floor.
- Wire Stripe Checkout for the three founding tiers.
Deliverable: End-to-end quote PDF and live checkout.
MVP live
- Run 10 real caterer menus end to end and fix the top three failures.
- Snapshot-test the PDF against fixed fixtures.
- Deploy to the production domain and open founding sales.
Deliverable: Public MVP accepting payments.
List building
- Build a 300-row list of Paris and London caterers with verified emails.
- Write the three-sentence email and the Loom script.
- Generate five sample quotes from real public menus.
Deliverable: 300-row outreach list and sample quote library.
First sends
- Record 80 personalized Looms.
- Send 80 first-touch emails.
- Log every send and reply in a single sheet.
Deliverable: 80 emails sent.
Week 2 · Launch & first sale · 7 days
Volume plus follow-up
- Record and send 50 new Looms.
- Send follow-up 1 to day-7 recipients with the checkout link.
Deliverable: 130 total sends.
Second channel
- Send 50 new Looms.
- Send 30 LinkedIn messages to caterer owners with the same demo link.
Deliverable: 180 total touches.
Fix objections
- Run the first demo calls and note every objection verbatim.
- Add guarantee and sample-quote language to the landing page.
- Fix the top parsing failure seen in demos.
Deliverable: Revised offer copy and a parser fix.
First sale
- Send 40 new Looms.
- Offer the first 20 founders a pre-built sample quote before payment.
- Close the first paid license.
Deliverable: First Stripe payment received.
Repeat the close
- Run 5 demo calls.
- Send follow-up 2 to non-responders with the Stripe link.
- Ask the first buyer for one specific referral.
Deliverable: 2-4 paid licenses and one referral name.
Refill pipeline
- Send 50 new Looms.
- Add 50 US caterers to the list as a third geography.
Deliverable: 230 total sends.
Week two audit
- Compute open, reply and call rates per subject line.
- Process any refund immediately and log the reason.
- Rewrite the email around the best-performing angle.
Deliverable: Written week-two funnel audit.
Week 3 · Repeat & systematize · 7 days
Volume with the winning copy
- Send 60 emails using the rewritten angle.
- Shorten the Loom to 60 seconds.
Deliverable: 60 sends with the new script.
Message testing
- Split-test two subject lines across 60 sends.
- Track which reply rate wins by geography.
Deliverable: Winning subject line identified.
Publish samples, not claims
- Publish three anonymized sample quote PDFs built from public menus.
- Add a two-minute annotated walkthrough video to the landing page.
- State plainly that these are sample outputs, not customer results.
Deliverable: Public sample library page.
Calls and closes
- Run 6 demo calls.
- Send 50 new emails.
- Close at least one Studio tier upgrade.
Deliverable: Second and third paid licenses.
Reduce support load
- Add an in-app onboarding checklist for new buyers.
- Add a self-serve PDF failure report button.
- Write a five-question FAQ from real support emails.
Deliverable: Self-serve onboarding shipped.
Volume
- Send 60 new emails.
- Follow up with every open thread older than 4 days.
Deliverable: All threads actioned.
Mid-point decision
- Compare actual sales against the conservative scenario.
- Decide whether to change geography focus or message.
- Document the single biggest conversion blocker.
Deliverable: Written go/hold decision with reasons.
Week 4 · Scale what works · 7 days
Double down on the winning segment
- Send 60 emails to the best-converting segment only.
- Record 20 Looms for tier-two cities.
Deliverable: Segment-focused campaign live.
Deposit links
- Ship per-quote Stripe Payment Links so caterers can collect client deposits.
- Add the deposit URL into the PDF footer.
Deliverable: Deposit links live in the PDF.
Volume
- Send 60 new emails.
- Offer a live 15-minute quote build to every replier.
Deliverable: Pipeline refilled.
Referrals
- Email every existing buyer a one-line referral offer.
- Add a referral note to the PDF download confirmation email.
Deliverable: Referral loop live.
Volume
- Send 60 new emails.
- Send a final follow-up to the entire list.
Deliverable: Full list contacted at least twice.
Scarcity with a real limit
- Announce that 20 founding licenses remain at $299 and the price rises after December 16.
- Send the deadline email to warm replies only.
- Run 5 closing calls.
Deliverable: Deadline campaign sent.
Final push
- Call every warm lead with no reply.
- Send 40 last-chance emails.
- Upgrade two Solo buyers to Company where seats justify it.
Deliverable: Maximum closes attempted.
Days 29-30 · Consolidate · 2 days
Reconcile
- Reconcile Stripe gross against refunds and fees.
- Confirm every payment recorded in TrustMRR.
- Fix any buyer onboarding issue before the window closes.
Deliverable: Verified payment ledger.
Report and lock in
- Publish the final profit figure with the fee breakdown.
- Write the next-30-day plan for retention and renewals.
- Send a thank-you note to every buyer.
Deliverable: Final report and post-hackathon plan.
Revenue and profit scenarios
How the numbers are defined
Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.
Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).
The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.
Stated assumptions
- Conservative, Base and Upside all assume the primary channel is organic cold outreach, so ad_spend_usd is 0 in every scenario.
- Payment fees assume Stripe at 2.9% + $0.30 per transaction, blended across the three tiers.
- Blended ARPU reflects a mix of Founding Solo ($299), Studio ($399) and Company ($499).
- Conservative assumes 3 buyers from 300 contacted caterers, roughly a 1% close rate.
- Base assumes 12 buyers and a blended ARPU of $324.
- Upside assumes 30 buyers, one refund and a slightly richer tier mix.
- Operating costs cover Vercel, Supabase, OpenAI parsing at roughly $0.01-0.03 per quote, Resend and the domain.
- No existing customers, partnerships or verified revenue are claimed; every figure below is a projection.
Conservative
3 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $27
- Paid marketing
- $0
- Hackathon profit
- $870
- Operating costs
- $25
- Business profit
- $845
Base case
12 customers- Refunds
- $0
- Chargebacks
- $0
- Payment fees
- $116
- Paid marketing
- $0
- Hackathon profit
- $3,772
- Operating costs
- $70
- Business profit
- $3,702
Optimistic
30 customers- Refunds
- $299
- Chargebacks
- $0
- Payment fees
- $305
- Paid marketing
- $0
- Hackathon profit
- $9,566
- Operating costs
- $180
- Business profit
- $9,386
Model your own numbers
Runs in your browser · nothing is saved- Collected revenue
- $3,588
- Payment fees (3.9%)
- $140
- Paid marketing
- $0
- Hackathon profit
- $3,448
- Business profit
- $3,378
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.
These figures are projections modeled from the stated assumptions. They are not verified revenue, existing customers or real traction, and they carry no guarantee.
Main risks and validation experiments
Risk 1Cold outreach reply rate below 2%, leaving too few calls to close anything.
Lead with a Loom built from the caterer's actual menu so the email is not a generic pitch, and run three subject-line variants by day 16.
Send 50 emails on day 7 and measure replies per subject line before building anything else.
If 150 emails produce fewer than 3 replies and zero demo calls, change geography or offer before spending further days on outreach.
Risk 2The LLM misparses a menu or brief and the quote is wrong, causing refunds and lost trust.
Never let the model emit allergen tags it cannot trace to caterer-supplied text; surface every unverified field as a warning and keep a manual edit table.
Run 10 real public menus and 10 real-shaped briefs through the pipeline and count extraction errors by field.
If allergen or price extraction error rate stays above 10% after two fix cycles, narrow the product to a manual-verified quote builder without auto-extraction.
Risk 3Caterers prefer pen and paper or an existing Word template and see no reason to change.
Generate a finished sample quote from their own menu before they pay, so the comparison is artifact versus artifact, not software versus habit.
Offer 5 caterers a free sample quote and record whether they would send it to a client unedited.
If fewer than 2 of 5 say they would send the sample unedited, the output quality is the blocker, not the price.
Risk 4A Stripe account hold or payment freeze during the contest window kills collected revenue.
Complete Stripe verification on day 1, keep refunds processed promptly, and keep the offer and landing page consistent so disputes are unlikely.
Run a live $1 test charge through the same checkout on day 2 and confirm it settles.
If payment collection is blocked for more than 5 consecutive days, stop selling and resolve the account before further outreach.
Risk 5Founder time consumed by support, cutting outreach volume below what the funnel needs.
Ship an onboarding checklist, a five-question FAQ and a self-serve failure report by day 19 so support is answerable once a day.
Log every support message for a week and count how many are answered by the FAQ.
If support exceeds 45 minutes per day per buyer, stop adding buyers and fix onboarding first.
Hour-by-hour: the first 24 hours
Hours 1-2
- Create the GitHub repo, Supabase project and Vercel app.
- Draft the Supabase schema for menus, items, quotes and line items.
Output: Deployed skeleton app and written schema.
Hours 3-5
- Ship the landing page with the offer, sample PDF placeholder and email capture.
- Connect Stripe and confirm the account is linked to TrustMRR.
Output: Live landing page and verified Stripe connection.
Hours 6-9
- Build the menu paste importer and the OpenAI normalization call.
- Render the parsed items into an editable table.
Output: Working menu import from pasted text.
Hours 10-13
- Build the brief parser with structured output.
- Ship the extracted-constraints review panel.
Output: Brief in, structured constraints out.
Hours 14-17
- Build the deterministic dietary matcher with coverage flags.
- Test against three real public caterer menus and log failures.
Output: Constraint report on three real menus.
Hours 18-21
- Build the first PDF template with itemization and a placeholder allergen matrix.
- Generate one sample quote end to end.
Output: First generated ArtisanQuote PDF.
Hours 22-24
- Scaffold the 300-row outreach list starting with 40 Paris caterers.
- Write the three-sentence email and Loom script.
Output: First 40 list rows and final outreach copy.
Full 30-day launch report
Read the full generated report
ArtisanQuote - 30-Day Public Launch Report
Concept version 1. Built for The $100k Hackathon by Ship or Die, 16 November to 16 December 2026. Every financial figure in this report is a projection from stated assumptions, not verified revenue, and no customers or partnerships are claimed.
1. Product opportunity and positioning
Independent artisanal caterers with 1-10 employees live on inbound email. A corporate inquiry lands with a headcount, a date, a budget ceiling, three dietary restrictions and a venue constraint. The caterer then spends 60 to 120 minutes rebuilding a quote in Word, guessing at margins and hand-checking allergens. Two failures follow: underpricing a job that eats the week, or missing a nut-free requirement and losing the client or carrying liability.
ArtisanQuote collapses this into one workflow. Paste the menu once. Paste the client email. The tool extracts the constraints, matches them against the menu, flags missing dietary coverage, applies margin guardrails, and emits a branded PDF quote with an allergen matrix and a Stripe deposit link.
The positioning is deliberately narrow: a single-player quoting tool on the supply side of corporate catering, not a marketplace. Monbanquet.fr needed supply density, demand density and a working commission before it delivered value. ArtisanQuote needs one caterer and one email. No cold-start, no commission, no logistics.
The wedge is the artifact. Caterers already feel this pain weekly and already have a menu they can paste. The output is something they send to a paying client minutes after buying, which makes the ROI concrete: one won event above $1,000 pays for the license three times.
Why now: structured-output LLM calls are cheap and accurate enough to parse a messy email and a pasted menu at roughly a cent per quote, and $299 sits inside a small caterer's discretionary spend with no procurement.
Differentiation against the generic alternative matters. ChatGPT or a Word template produces prose the caterer must still verify. ArtisanQuote runs a deterministic matcher against the caterer's own allergen-tagged menu and enforces a margin floor, so the deliverable is a checked artifact with a visible allergen matrix.
JEV scored this concept 63.5/100, band C. Speed to first revenue is the strongest dimension at 8.28; operational simplicity is the weakest at 4.94. This plan is shaped by both: stay stateless on managed services, and get a paid transaction inside week two instead of polishing the generator.
2. Smallest sellable MVP
One page, one flow: paste menu, paste email, download a correct branded quote PDF, pay through Stripe. Six must-have capabilities ship by day 5 - menu import from CSV or pasted text, brief extraction, dietary constraint matching with flagged gaps, margin guardrails, the PDF with an allergen matrix and terms, and Stripe Checkout plus a reusable deposit link.
Explicitly not built: no marketplace, no client portal, no invoicing or inventory, no team accounts, no mobile app, no POS integration. Each of these would add a week and none of them is required for the first $299.
3. Technical implementation plan
Next.js on Vercel, Supabase Postgres with row-level security, OpenAI structured output for two parsing calls, @react-pdf/renderer for the document, Stripe Checkout for the license and Payment Links for deposits, Resend for delivery, Vercel Blob for stored PDFs.
The model parses only. It normalizes the pasted menu into typed items and extracts the brief into a constraint object. It never invents allergen tags: anything absent from the caterer's text is stored as unverified and shown as a warning. A deterministic TypeScript matcher joins constraints to items, applies the margin floor and produces a quote model that the PDF renderer consumes.
The hardest technical risk is PDF rendering plus allergen correctness on serverless infrastructure. Mitigation: pin fonts in the repo, snapshot-test the PDF against fixed fixtures, and treat every unverified allergen as a visible warning rather than a silent assumption.
4. Pricing and monetization
Three one-time founding tiers sold through Stripe: Founding Solo at $299 with six months of unlimited quotes, Founding Studio at $399 adding custom logo, deposit links and twelve months, Founding Company at $499 adding three users and priority email. A 14-day money-back guarantee removes the risk of a first purchase.
Blended ARPU is modeled at $324. After the included period the upgrade path is a $149 annual renewal, extra seats and branding add-ons. No commission, no per-quote fee, no usage metering in the first 30 days.
5. First-customer acquisition
One channel: personalized cold email with a 90-second Loom built from the caterer's own menu, sent to 300 independent caterers in Paris and London sourced from Google Maps listings for "traiteur artisanal" and "artisan caterer", plus their public menu pages and contact addresses.
The email is three sentences, names the caterer, links the Loom and states the $299 price with the guarantee. One follow-up goes out after three days with the Stripe link. Warm repliers get a live 15-minute quote build. LinkedIn and Instagram touches supplement but never replace email.
Week-one goal: 300 verified rows, 80 Looms recorded, 80 emails sent by day 7.
6. 30-day execution roadmap
Days 1-5 build and ship the MVP, with Stripe connected to TrustMRR before any payment is taken. Days 6-7 build the list and send the first 80 emails. Days 8-14 push volume to roughly 230 sends, run the first demo calls, close the first licenses around day 11 and audit the funnel. Days 15-21 scale the winning copy, publish anonymized sample quotes, cut support load with self-serve onboarding and make an explicit go/hold decision at the midpoint. Days 22-28 double down on the best-converting segment, ship deposit links, open a referral loop and run a real deadline campaign. Days 29-30 reconcile Stripe against TrustMRR and publish the result. The JSON roadmap carries all 30 day entries with tasks and deliverables.
7. Revenue and profit scenarios
All figures are projections, not verified revenue.
Conservative: 3 customers at $299 blended, $897 gross, $27 fees, no refunds, $25 operating cost. Base: 12 customers at $324 blended, $3,888 gross, $116 fees, $70 operating cost. Upside: 30 customers at $339 blended, $10,170 gross, $299 refunded, $305 fees, $180 operating cost.
Hackathon profit subtracts refunds, chargebacks and payment fees only. Business profit also subtracts operating cost. Ad spend is zero in every scenario because the channel is organic outreach. Fee assumption is Stripe at 2.9% plus $0.30 per transaction.
8. Main risks and validation experiments
Four risks dominate. First, reply rates below 2%: test 50 sends on day 7 and change geography or offer if 150 sends produce fewer than three replies. Second, parsing errors: run ten real menus and ten shaped briefs, and if allergen or price error rate stays above 10% after two fix cycles, drop auto-extraction. Third, adoption inertia: offer five caterers a free sample quote and if fewer than two would send it unedited, output quality is the blocker. Fourth, a Stripe hold: verify on day 1, test a $1 charge on day 2, and halt selling for more than five days if collection breaks. A fifth operational risk is support load; if it exceeds 45 minutes per buyer per day, stop adding buyers and fix onboarding.
9. First 24-hour action plan
Hours 1-2: repo, Supabase project, Vercel app, schema. Hours 3-5: landing page live, Stripe connected to TrustMRR. Hours 6-9: menu importer and normalization call. Hours 10-13: brief parser and constraints panel. Hours 14-17: deterministic matcher tested on three real menus. Hours 18-21: first PDF generated end to end. Hours 22-24: first 40 outreach rows plus the final email and Loom script.
The constraint is simple: a working PDF and a live checkout by day 5, then 300 emails. Everything else is optional.
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 →Kitchen Sheet
Kitchen Sheet turns a cloud kitchen's messy WhatsApp lunch orders into a print-ready kitchen prep sheet, one label per order, and a delivery run order in under 60 seconds.
FridgeDrop Prep
FridgeDrop Prep turns a small caterer's week of office meal orders into one print-ready Monday Prep & Drop Sheet: batch totals per recipe, container counts, per-office packing labels and a delivery sheet grouped by postcode.
DropCount Lunch Desk
DropCount turns a small caterer's daily single menu into a shareable order page with a hard cutoff, then produces one kitchen drop sheet with exact per-dish counts and per-building drop groupings.