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

ChatQuote Card

Paste a customer's Instagram or WhatsApp chat and get a branded, deposit-ready event rental quote card in under a minute.

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.

Promising6.57/10
MVP build (solo)
4 days
Launch price
$99 · monthly
Sales to $1,000 revenue
11 customers
First paying customer
Instagram DM to party rental companies found via Google Maps and hashtags.
Who pays

Owner of a small party and event rental company with 1-10 employees in the US or UK who receives 20+ Instagram or WhatsApp inquiries per week.

Biggest execution risk

Operational simplicity 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 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/10.

Score and projections come from the generated report and are not guarantees. The $100K Hackathon is run by Ship or Die — read the official rules before you build.

Your first 24 hours

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

0/13
Entry price
$99
Solo build
4 days
30d base revenue
$990
30d hackathon profit
$950
Section 1 of 8

Product opportunity and positioning

Target customer

Owner of a small party and event rental company with 1-10 employees in the US or UK who receives 20+ Instagram or WhatsApp inquiries per week.

Why now

Owners already run sales in DMs, Stripe links are familiar, and an LLM can extract messy chat text accurately enough for an owner-approved draft.

Problem

Owners lose hours retyping event dates, item lists, quantities, and delivery addresses from DMs into quotes; slow replies let leads go cold.

Solution

Paste the chat; the app extracts the event date, items, quantities, address, and budget into an editable branded quote card with a Stripe deposit link and a draft reply.

Differentiation · Not a chatbot builder or CRM. The output is one quote card and deposit link, tested on the owner's last real inquiry, so the value is visible before purchase.

Product opportunity and positioning

Small party and event rental owners sell through Instagram and WhatsApp. An inquiry arrives as messy text: event date, item list, quantities, delivery address, budget. The owner retypes it into a spreadsheet, builds a PDF, and writes a reply. That takes 15-40 minutes, and slow replies let leads go cold. ChatQuote Card collapses that back-office step into one paste. The buyer is not a chatbot operator; they are an owner with 20+ weekly inquiries and no patience for flow builders. The wedge is narrow: turn one chat into one sendable quote card with a deposit link. This is a B-band concept: fast to first revenue and solo-buildable, with weaker defensibility. The sell is visible in 30 seconds because the output is the artifact the owner already sends. The competition is not a chatbot platform or a CRM; it is copy-paste, Canva, and a PDF. Position against that manual work: paste the chat, edit the extracted line items, send a branded link with a Stripe deposit. Do not broaden into inventory, calendar, or DM automation in the first 30 days. The product wins if an owner can test it on their last real inquiry and immediately see a usable quote. Distribution is direct: Instagram DM to rental companies with public business profiles. The first message offers a free quote card on a real inquiry, not a generic demo. Pricing is $99 per month, sold after the free output proves time saved. The 30-day goal is not a platform; it is a repeatable path from pasted chat to paid subscription. Keep the promise concrete: under a minute to a deposit-ready quote card.

Section 2 of 8

Smallest sellable MVP

A paste-in chat box that outputs an editable branded quote card with a Stripe deposit link and a copyable reply.

Must-have features

  • Paste-in chat textarea with a sample conversation preloaded
  • LLM extraction to structured JSON: event date, items, quantities, address, budget
  • Editable line-item quote table with price fields and totals
  • Branded quote card template with logo and colors rendered as PDF and shareable link
  • Stripe Payment Link generation for a 30% deposit
  • Draft reply copy button
  • Quote history list stored in Supabase

Explicitly out of scope

  • No WhatsApp or Instagram API integration; paste-in only
  • No inventory or availability calendar
  • No CRM, pipeline, or automated follow-ups
  • No multi-user accounts or roles
  • No automated pricing engine
  • No mobile app
  • No white-label client portal

Demo flow (what the buyer sees)

  1. Founder opens a real rental inquiry and pastes the chat text.
  2. App extracts date, items, quantities, address, and budget into a draft quote.
  3. Owner edits one price and confirms the line items.
  4. App renders a branded PDF and shareable quote page.
  5. App creates a Stripe Payment Link for a 30% deposit.
  6. Owner copies the drafted reply and sends the quote link.
Build plan

Technical implementation plan

Stack

Next.jsOpenAI APIStripe Payment LinksSupabaseVercelReact-PDF

Architecture

A Next.js app on Vercel handles the paste form, quote editor, public quote page, and PDF rendering. Server routes call OpenAI with a strict JSON schema for extraction, validate the result, and store quotes in Supabase. Stripe creates a deposit Payment Link from the quote total. The owner approves every quote before sending; nothing auto-sends.

Build steps

  1. Create Supabase tables for profiles, quotes, and line items.
  2. Add auth and a single-brand settings page.
  3. Build the paste-in form with a sample chat.
  4. Write the OpenAI extraction prompt and JSON validation.
  5. Build the editable line-item table with totals.
  6. Render the branded quote as PDF and a public share page.
  7. Create Stripe Payment Links for a 30% deposit.
  8. Add draft reply generation and copy button.
  9. Add quote history and error states.
  10. Deploy to Vercel and test with 5 sample chats.

AI components

  • LLM extraction of event date, items, quantities, address, and budget from pasted chat text
  • LLM drafting of a short reply message for owner approval
Hardest technical risk: Messy real-world chats produce incorrect extraction, so owners must review several fields before sending.
Section 3 of 8

Pricing and monetization

Solo

Entry offer
$99 / month

For Small party rental owner

  • 50 quote cards per month
  • Stripe deposit links
  • Branded PDF and shareable link
  • Quote history

Model: Single monthly subscription at $99 per month with no permanent free tier.

First revenue offer: Send me your last inquiry; I will turn it into a branded quote card with a Stripe deposit link free. If it saves you time, start at $99 per month.

Expected ACV: $99

Upsell path: Add extra quote packs, a second brand, a custom domain, and team seats after the first 10 customers.

Target customers
30
Revenue model
$2,970
Costs
$150
Profit model
$2,820
Section 4 of 8

First-customer acquisition

Primary channel

Instagram DM to party rental companies found via Google Maps and hashtags.

Where to find them

  • Google Maps searches for party rental in Austin, Dallas, Houston, Phoenix, Tampa, Orlando, Atlanta, Charlotte, San Diego, and Denver
  • Instagram hashtags such as #partyrental, #eventrental, #tentrental, and #weddingrentals
  • Local wedding vendor directories with Instagram handles
  • Facebook event vendor groups where rental owners post setups
  • Public Instagram profiles showing tents, chairs, tables, and event setups

Exact outreach motions

  • Send 20 DMs daily with a specific observation about their recent setup and the free-quote offer.
  • Follow up after 48 hours with a Loom using their public listing info.
  • Deliver one free quote card on a real inquiry and ask for a paid start after they confirm it saved time.
  • Log every reply and objection in a spreadsheet by city, message angle, and outcome.
  • Ask paying owners for permission to use an anonymized before-and-after example.

Message template

Hi [Name] - I saw your [tent/chair] setup for [event]. I built a tool that turns a customer's Instagram or WhatsApp chat into a branded quote card with a Stripe deposit link in under a minute. Want me to run your last inquiry through it free?
Week-one goal: 100 DMs sent, 10 replies, 3 free quote cards delivered, 1 paid customer.
Section 5 of 8

30-day execution roadmap

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

Data model and extraction

  • Create Supabase quotes and profile tables.
  • Write OpenAI extraction prompt with JSON schema.
  • Test on 5 sample chats.

Deliverable: Working extraction route returns validated JSON.

Day 2Build quote editor

Editable line items and totals

  • Build editable line-item table.
  • Add price fields and total calculation.
  • Add validation for missing fields.

Deliverable: Owner can edit extracted quote and see totals.

Day 3Build output

PDF and share link

  • Create branded PDF template.
  • Build public quote page.
  • Add draft reply copy button.

Deliverable: Shareable quote link and PDF render correctly.

Day 4Build paymentsMVP shipped

Stripe and deploy

  • Create Stripe Payment Link for 30% deposit.
  • Add brand settings for logo and colors.
  • Deploy to production.

Deliverable: End-to-end demo from paste to deposit link.

Day 5Launch readiness

Landing page and checks

  • Publish landing page with demo video.
  • Switch Stripe to live keys.
  • Confirm TrustMRR payment connection.

Deliverable: Public launch page and live payment path.

Day 6List building

Instagram handles

  • Collect 100 party rental Instagram handles.
  • Record city, handle, and recent setup note.
  • Prioritize 20 warm-looking profiles.

Deliverable: Qualified list of 100 handles.

Day 7First outreach

Send first DMs

  • Send 20 personalized DMs.
  • Log replies and objections.
  • Deliver one free quote card if invited.

Deliverable: First outreach batch sent and tracked.

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

Daily DM cadence

  • Send 20 DMs.
  • Reply to all responses within 2 hours.
  • Log objections.

Deliverable: 20 DMs sent and follow-ups queued.

Day 9Free quote delivery

Concierge output

  • Process 3 real inquiries into quote cards.
  • Ask for feedback on extraction accuracy.
  • Fix one recurring extraction error.

Deliverable: 3 free quote cards delivered.

Day 10Outreach

Message refinement

  • Send 20 DMs with revised opener.
  • Test a deposit-focused angle.
  • Log reply rate by variant.

Deliverable: Two message variants measured.

Day 11Demo follow-up

Loom videos

  • Record 5 personalized Looms.
  • Send follow-ups to day 7-9 leads.
  • Book demo calls.

Deliverable: 5 Loom follow-ups sent.

Day 12First sale targetFirst sale target

Close first paying customer

  • Ask every free user for paid start.
  • Send Stripe checkout link.
  • Confirm payment through TrustMRR.

Deliverable: First paid customer target.

Day 13Product fix

Extraction quality

  • Review all failed extractions.
  • Improve prompt for dates and quantities.
  • Add manual override fields.

Deliverable: Extraction error rate reduced.

Day 14Trust and review

Confidence flags

  • Add low-confidence field flags.
  • Add review reminder before send.
  • Test with messy chats.

Deliverable: Review flow protects against bad quotes.

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

New city batch

  • Send 25 DMs in two new cities.
  • Log replies by city.
  • Deliver free quote cards.

Deliverable: 25 new DMs sent.

Day 16Proof assets

Before-and-after examples

  • Create 2 anonymized examples.
  • Add examples to landing page.
  • Use examples in follow-ups.

Deliverable: 2 proof examples published.

Day 17Follow-up

Paid asks

  • Follow up with all free users.
  • Ask directly for $99 monthly start.
  • Log yes, no, and objection.

Deliverable: Paid ask completed for every free user.

Day 18Product

Second brand template

  • Add second brand preset.
  • Test color and logo swap.
  • Ship to one user if requested.

Deliverable: Second brand template live.

Day 19Outreach

Expansion

  • Send 25 DMs.
  • Target holiday and winter event rentals.
  • Track seasonal objections.

Deliverable: 25 DMs sent with seasonal angle.

Day 20Objection log

Message-market fit

  • Group objections into 3 themes.
  • Revise offer for top objection.
  • Update DM template.

Deliverable: Objection-driven message update.

Day 21Review

Conversion analysis

  • Review conversion by city and variant.
  • Double down on best segment.
  • Pause weak message angles.

Deliverable: Best segment and message chosen.

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

Best segment

  • Send 25 DMs to best segment.
  • Ask for referrals in replies.
  • Log paid conversion.

Deliverable: 25 targeted DMs sent.

Day 23Product

Reliability

  • Add retry handling for OpenAI timeouts.
  • Cap input length.
  • Test 10 varied chats.

Deliverable: More reliable extraction route.

Day 24Follow-up

Daily discipline

  • Send 20 follow-ups.
  • Deliver pending free quotes.
  • Book next demos.

Deliverable: Follow-up queue cleared.

Day 25Product

Repeat use

  • Add quote duplication.
  • Pre-fill repeat customer details.
  • Test with one owner.

Deliverable: Repeat quote flow live.

Day 26Outreach

Final push

  • Send 25 DMs.
  • Offer free quote card only.
  • Log all replies.

Deliverable: Final DM batch sent.

Day 27Referrals

Warm introductions

  • Ask paying users for one intro.
  • Send referral message template.
  • Track intro source.

Deliverable: Referral requests sent.

Day 28Proof

Testimonials

  • Ask paying users for testimonial permission.
  • Publish only approved text.
  • Do not use fake logos.

Deliverable: Approved testimonial assets.

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

Payments and refunds

  • Reconcile Stripe and TrustMRR.
  • Respond to refund requests.
  • Document support macros.

Deliverable: Clean payment and support log.

Day 30Handoff

30-day review

  • Summarize conversion and objections.
  • Document next 30-day priorities.
  • Archive outreach data.

Deliverable: Launch review and next-step brief.

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: 3 paying customers by day 30 from 100 targeted DMs.
  • Base: 10 paying customers by day 30 from 200 targeted DMs.
  • Upside: 30 paying customers by day 30 from 300 targeted DMs at 10% conversion, matching the concept target.
  • All scenarios use $99 monthly ARPU and no annual prepay.
  • Payment fees assume Stripe at roughly 4% blended, including international cards.
  • No paid marketing in conservative or base; upside keeps ad spend at 0 because the channel is organic DMs.
  • Operating costs cover Vercel, Supabase, OpenAI, domain, and email; they do not include founder time.
  • Refunds and chargebacks are assumed minimal because the first offer is a free quote card before payment.
  • These are projections from stated assumptions, not verified revenue or customer commitments.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$25
Business profit
$260

Base case

10 customers
$990
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$40
Paid marketing
$0
Hackathon profit
$950
Operating costs
$45
Business profit
$905

Optimistic

30 customers
$2,970
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$119
Paid marketing
$0
Hackathon profit
$2,851
Operating costs
$110
Business profit
$2,741

Model your own numbers

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

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 1Party rental owners ignore cold Instagram DMs.

Mitigation

Use specific observations from their recent setups and offer a free quote on a real inquiry.

Validation experiment

Send 30 DMs in two message variants and compare reply rate.

Kill criteria

After 100 qualified sends, reply rate below 5% and no paid customer from 10 demos.

Risk 2Owners do not trust AI extraction with quote details.

Mitigation

Require owner review, add low-confidence flags, and never auto-send.

Validation experiment

Manually process 10 real inquiries and count how many fields owners edit.

Kill criteria

If owners must edit more than 3 fields on most quotes and will not pay after a free test.

Risk 3The product is seen as a one-off feature, not a subscription.

Mitigation

Sell the repeat workflow and quote history; ask every free user for a monthly paid start.

Validation experiment

Ask 10 owners whether they would pay $99 per month after one free quote card.

Kill criteria

Fewer than 2 of 10 say yes and objections show no repeat need.

Risk 4December seasonality reduces rental inquiries.

Mitigation

Target holiday parties, winter events, and warmer-climate cities.

Validation experiment

Compare reply and demo rates across two city batches and two event angles.

Kill criteria

No paid customer after 150 sends and no clear objection that product changes can fix.

Risk 5Stripe deposit links fail or fees surprise owners.

Mitigation

Test live links before outreach and state the 30% deposit clearly in the quote.

Validation experiment

Run a $1 internal live charge and confirm payout and fee reporting.

Kill criteria

Payment failure rate above 10% in the first 10 attempts without a fix.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create repo and Next.js app.
  • Create Supabase project and tables.
  • Add Stripe test keys and env vars.

Output: Running skeleton with database and test payment config.

Hours 3-4

  • Write extraction JSON schema.
  • Write OpenAI prompt.
  • Test on 5 sample chats.

Output: 5 validated extraction samples.

Hours 5-6

  • Build editable line-item table.
  • Add totals and missing-field validation.

Output: Working quote draft screen.

Hours 7-8

  • Render PDF template.
  • Build public share page.

Output: Shareable test quote link and PDF.

Hours 9-10

  • Create Stripe Payment Link for 30% deposit.
  • Add draft reply copy.
  • Record 60-second Loom.

Output: End-to-end demo and outreach kit.

Complete report

Full 30-day launch report

Read the full generated report

ChatQuote Card: 30-Day Launch Report

1. Product opportunity and positioning

Small party and event rental owners sell through Instagram and WhatsApp. An inquiry arrives as messy text: date, item list, quantities, delivery address, budget. The owner retypes it into a spreadsheet, builds a PDF, and writes a reply. That takes 15-40 minutes, and slow replies lose bookings. ChatQuote Card collapses that back-office step into one paste. The buyer is not a chatbot operator; they are an owner with 20+ weekly inquiries and no patience for flow builders. The wedge is narrow: turn one chat into one sendable quote card with a deposit link. This is a B-band concept (JEV 65.7/100): fast to first revenue and solo-buildable, with weaker defensibility. The sell is visible in 30 seconds because the output is the artifact the owner already sends. The competition is not a chatbot platform or a CRM; it is copy-paste, Canva, and a PDF. Position against that manual work: paste the chat, edit the extracted line items, send a branded link with a Stripe deposit. Do not broaden into inventory, calendar, or DM automation in the first 30 days. The product wins if an owner can test it on their last real inquiry and immediately see a usable quote.

2. Smallest sellable MVP

Sell a single workflow: paste text, get an editable quote, send a deposit link. Required: textarea with a sample chat; LLM extraction to JSON; editable line-item table; branded PDF and shareable link; Stripe Payment Link for a 30% deposit; draft reply copy; quote history. Out of scope: WhatsApp or Instagram API, inventory, availability, CRM, automated follow-up, multi-user roles, and a pricing engine. Demo: founder opens a real inquiry, pastes it, reviews extracted date, items, address, and budget, fixes one price, clicks generate, sends the link. The build is four days. The MVP is sold monthly, not as a one-off PDF generator, because the owner repeats this workflow weekly. Keep the first version single-user and single-brand.

3. Technical implementation plan

Use Next.js on Vercel, OpenAI for extraction, Supabase for auth and quotes, Stripe Payment Links, and React-PDF. Flow: browser posts pasted chat to a server route; the route calls OpenAI with a strict JSON schema; server validates and stores a draft quote; owner edits line items; server renders PDF and public quote page; server creates a Stripe Payment Link for 30% of total; owner copies reply. Architecture: serverless routes, one Postgres table for quotes, one for profiles and branding, and JSONB line items. Build order: schema and sample data; extraction prompt with validation; editable table; PDF template; public share page; Stripe link creation; brand settings; history; error states; deploy. Hardest risk: messy chats produce bad extraction. Mitigate with a review step, confidence flags, and editable fields. Never auto-send. AI only drafts; owner approves. Keep prompts small, cap input length, and handle OpenAI timeouts with retry. Use Stripe test mode until launch, then live keys in Vercel env.

4. Pricing and monetization

Solo plan at $99 per month. Includes 50 quote cards, deposit links, branded PDF and link, and history. No permanent free tier; offer one free quote card during DM outreach as a sales demo. First revenue offer: send me your last inquiry; I will turn it into a quote card and deposit link free. If it saves you time, start at $99 per month. Expected first-month ACV is $99. Upsell later: extra quote packs, second brand, custom domain, team seats. Do not add usage-based pricing before 10 customers. The price is low enough for an owner to approve without procurement and high enough to cover OpenAI, Stripe, and hosting. Every sale must cover delivery cost; no below-cost promotions.

5. First-customer acquisition

Primary channel: Instagram DM to party rental companies found via Google Maps and hashtags. Build a list of 100 handles in 10 US cities. Qualify by recent posts showing tents, chairs, tables, and event setups. Send a short DM with a specific observation and the free-quote offer. Follow up after 48 hours with a Loom using their public listing info. No ads. No scraped email blasts. Track handle, city, sent date, reply, demo, and paid. Week-one goal: 100 DMs sent, 10 replies, 3 free quote cards delivered, 1 paid customer. Message template: Hi [Name] - I saw your [tent/chair] setup for [event]. I built a tool that turns a customer's Instagram or WhatsApp chat into a branded quote card with a Stripe deposit link in under a minute. Want me to run your last inquiry through it free? Keep it plain. Answer questions; do not argue.

6. Detailed 30-day execution roadmap

Days 1-4: build. Day 1 schema, extraction prompt, sample chat. Day 2 editable table and PDF. Day 3 share link and Stripe deposit. Day 4 branding, history, deploy, test with 3 sample chats. Day 5: launch page, demo video, Stripe live, TrustMRR payment connection check. Day 6: build list of 100 Instagram handles in 10 cities. Day 7: send first 20 DMs. Week 2: send 20 DMs daily, deliver free quote cards, log objections. Day 12 target first paid sale. Days 13-14: fix top extraction error and add confidence flags. Week 3: 100 more DMs, ask every free user for a paid start, publish 2 before-and-after examples. Day 18: add second brand template if requested. Day 21: review conversion by city and message angle. Week 4: double down on the best segment, send 20 follow-ups daily, offer annual prepay only if asked. Day 25: add quote duplication for repeat customers. Day 28: collect testimonial permission from paying users; no fake logos. Days 29-30: reconcile Stripe, respond to refunds, document support macros, prepare handoff notes. The daily rule: 20 DMs before noon, product fixes after.

7. Revenue and profit scenarios

These are projections from stated assumptions, not verified revenue. Conservative: 3 customers at $99 = $297 gross; refunds $0; chargebacks $0; payment fees $12; ad spend $0; operating costs $25. Base: 10 customers at $99 = $990 gross; fees $40; operating $45. Upside: 30 customers at $99 = $2,970 gross; refunds $0; chargebacks $0; fees $119; ad spend $0; operating $110. Hackathon profit deducts refunds, chargebacks, fees, and paid marketing only. Business profit also deducts hosting, domain, tooling, and AI/API delivery. Payment fees assume Stripe at roughly 4% blended. Operating costs cover Vercel, Supabase, OpenAI, domain, and email. The model does not assume existing customers or real traction. If conversion is below 3%, the problem is message or list quality, not price.

8. Main risks and validation experiments

Risk 1: owners ignore cold DMs. Experiment: send 30 DMs in two message variants; kill variant below 5% reply after 100 sends. Risk 2: owners do not trust AI extraction. Experiment: manually process 10 real inquiries and measure edit time; add confidence flags if edits exceed 3 fields. Risk 3: the product is seen as a feature. Experiment: ask 10 owners whether they would pay $99 per month after one free quote; if fewer than 2 say yes, narrow the promise to deposit collection. Risk 4: December seasonality. Experiment: target holiday party and winter event rentals; if replies stall, shift to warmer-climate cities. Risk 5: Stripe deposit link fails or fees surprise. Experiment: test a live link with a $1 internal charge before outreach. Kill criteria: after 100 qualified DMs and 10 demos, zero paid customers and no clear objection to fix. Do not buy ads to rescue a weak message.

9. First 24-hour action plan

Hours 1-2: create repo, env vars, Supabase project, Stripe test keys; output running skeleton. Hours 3-4: write extraction schema and prompt; test on 5 sample chats; output JSON samples. Hours 5-6: build editable line-item table and total calculation; output working draft screen. Hours 7-8: render PDF and public quote page; output shareable test link. Hours 9-10: create Stripe Payment Link for 30% deposit and draft reply copy; output end-to-end demo. Hours 11-12: record a 60-second Loom and write the DM list template; output outreach kit. Do not spend day one on branding, logo, or a landing page.

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 →