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

ChangeOrder Voice

Turns a 30-second job-site voice memo into a signed, priced change order with a deposit link, so remodelers get paid for extra work before they do it.

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.48/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach in US remodeler Facebook groups and local Craigslist services listings.
Who pays

Owner-operator remodelers and 1-5 person residential construction crews in the US running 2-10 active kitchen, bath or addition jobs with frequent mid-job client requests.

Biggest execution risk

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

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

0/15
Entry price
$99
Solo build
5 days
30d base revenue
$1,490
30d hackathon profit
$1,442
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator remodelers and 1-5 person residential construction crews in the US running 2-10 active kitchen, bath or addition jobs with frequent mid-job client requests.

Why now

Whisper-grade transcription plus cheap structured extraction makes a 30-second memo a reliable priced document, so the tool costs cents per use and ships in days rather than quarters.

Problem

Mid-job client requests get done on a handshake, then either go unbilled or cost the contractor an evening of paperwork while payment slips.

Solution

A mobile web recorder transcribes the change, maps it to a saved price book, and generates a branded PDF change order with client e-signature and a Stripe deposit link, sent by SMS or email and tracked on a status dashboard.

Differentiation · Generic invoicing apps bill after the fact; project suites need a full job setup. ChangeOrder Voice produces one legal artifact — the signed change order — in under two minutes from a voice memo.

1. Product opportunity and positioning

Owner-operator remodelers run two to ten jobs at once and get asked for extras constantly: an extra outlet, a soffit change, a tile upgrade, a moved vanity. The work gets done on a handshake. The paperwork gets written at 9pm, or never. Every unbilled change is margin lost, and every undocumented one becomes a collections argument three weeks later.

ChangeOrder Voice attacks the moment of the request, not the invoice. The contractor talks for thirty seconds into their phone. The app transcribes it, maps it against a saved price book, and produces a branded change order PDF with line items, terms, a client signature pad, and a Stripe deposit link. The contractor sends it by SMS from the truck.

Positioning: get paid for the extra work before you do it. This is deliberately not project management, not invoicing software, and not a payment rail. It is a single-document tool whose output is a signed financial artifact. The buyer already believes change orders matter; the product removes the friction that stops them writing one.

Why this customer. Independent remodelers are reachable directly — Facebook groups, Craigslist services, public Instagram job photos — with no procurement cycle. They can approve $99 or $199 in a single text exchange. And the ROI is arithmetic, not a promise: one recovered $800 change order pays for the product eight times over on the first job.

Why the wedge holds. JEV scored this concept 64.8/100, with speed to first revenue as the strongest criterion (8.58). That reflects a concrete pitch, an identifiable buyer, and a free sample the founder can deliver manually in minutes before the software is even finished. The weakest criterion is operational simplicity (4.69). The response is architectural discipline: no human review queue, no custom infrastructure, no regulated data, no credit exposure. Every step runs on managed services and costs cents per change order.

What it refuses to be. No vision-based progress verification, no lending, no stored payment credentials, no accounting sync in v1. The product stores a transcript, a PDF, and a signature. That keeps the operational surface small enough for one person to run alone for thirty days.

Section 2 of 8

Smallest sellable MVP

A mobile web app that converts one voice memo into one branded, priced, signable change order PDF with a Stripe deposit link the contractor can text to a client.

Must-have features

  • Mobile-first voice recorder using MediaRecorder with optional photo attachment
  • Whisper transcription of the memo
  • GPT-4o-mini extraction into editable line items (description, quantity, unit, price)
  • Price book CRUD seeded with 20 common remodel tasks
  • React-PDF change order with logo, line items, total, terms and signature line
  • Public signing page with canvas signature, timestamp and IP capture
  • Stripe Checkout deposit link at a configurable percentage
  • Send by Resend email and Twilio SMS with a unique link
  • Dashboard listing drafts, sent, signed and paid change orders

Explicitly out of scope

  • No project management, scheduling or full invoicing
  • No QuickBooks or Xero integration
  • No photo or vision verification of work progress
  • No lending, credit or stored payment credentials
  • No multi-user roles or team accounts
  • No native iOS or Android app

Demo flow (what the buyer sees)

  1. Contractor taps record and says: 'Add two recessed lights in the hallway ceiling, drywall patch, about four hours.'
  2. App transcribes and returns three editable line items priced from the saved price book.
  3. Contractor adjusts one price and taps generate.
  4. PDF change order renders with logo, items, total, 30% deposit and terms.
  5. Contractor enters client mobile number and sends.
  6. Client opens link, reviews, signs with a finger, and pays the deposit via Stripe.
  7. Dashboard flips the job to signed and paid.
Build plan

Technical implementation plan

Stack

Next.js App Router on VercelSupabase Postgres, Auth and StorageOpenAI Whisper APIOpenAI GPT-4o-miniStripe CheckoutResend emailTwilio SMSReact-PDF

Architecture

A single Next.js app serves both the contractor dashboard and the public signing pages. Audio is recorded in the browser, uploaded to Supabase Storage, transcribed by Whisper, then passed to GPT-4o-mini which returns strict JSON line items that the contractor edits. A React-PDF route renders the document from stored rows and writes the PDF back to Storage. The signing page is public, keyed by an unguessable token, writes a signature record with timestamp and IP, and creates a Stripe Checkout session for the deposit. Stripe webhooks update payment status.

Build steps

  1. Scaffold Next.js on Vercel, create Supabase project, enable email auth and RLS.
  2. Create tables: accounts, price_book, change_orders, change_order_items, signatures, payments.
  3. Build the recorder and upload path to Supabase Storage.
  4. Wire Whisper transcription and display the transcript with a retry control.
  5. Prompt GPT-4o-mini for strict JSON line items and build the editable table.
  6. Ship price book CRUD with 20 seeded remodel tasks.
  7. Render the React-PDF change order template with logo and terms.
  8. Build the public signing page with canvas signature, timestamp and IP.
  9. Create Stripe Checkout deposit sessions and handle the webhook.
  10. Add Resend email and Twilio SMS send actions with unique tokens.
  11. Build the status dashboard and run five end-to-end tests on a real phone.

AI components

  • Whisper for audio transcription
  • GPT-4o-mini for structured line-item extraction and price-book matching
  • Optional GPT-4o-mini pass to draft plain-language scope language for the PDF terms
Hardest technical risk: Voice extraction producing plausible but wrong prices; the editable confirmation screen and price-book-first matching are the guardrails.
Section 3 of 8

Pricing and monetization

Solo Launch

Entry offer
$99 one-time

For Solo remodeler testing on one job

  • 20 change orders
  • E-signature
  • Stripe deposit link
  • Email support

Pro Launch

$199 one-time

For Active remodeler with 2-10 jobs

  • Unlimited change orders for 12 months
  • Custom branding
  • Price book import
  • SMS sending

Model: One-time launch pricing with a volume tier, sold directly through Stripe payment links, with an optional monthly conversion later.

First revenue offer: I'll turn your last verbal change order into a signed, priced PDF with a deposit link, free, today. If it saves you an evening, Solo is $99 and Pro is $199 for unlimited change orders.

Expected ACV: $149

Upsell path: Move Pro Launch buyers to $49/month at month 12, add a $29 branded price-book import service, and take $50 referral credit on each contractor they introduce.

Target customers
30
Revenue model
$5,970
Costs
$230
Profit model
$5,740
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach in US remodeler Facebook groups and local Craigslist services listings.

Where to find them

  • Five active US kitchen and bath remodeler Facebook groups
  • Craigslist services > skilled trade > general contractor listings by metro
  • Public Instagram and TikTok remodelers already posting daily progress photos
  • Local contractor subreddits and trade-specific Facebook groups
  • Referrals from each buyer to one contractor friend

Exact outreach motions

  • Search group posts for 'change order' and 'scope creep', then DM the poster with a single question, not a pitch.
  • Send a 60-second Loom that turns their publicly posted project photo into a sample change order PDF.
  • Offer the free conversion of their last verbal change to open the conversation.
  • Follow up at 48 hours with the finished sample PDF and a Stripe link.
  • Post one value post per group: three sentences on how to word a change order so clients sign.

Message template

Hey — saw your post about the client adding work mid-job. I built a tool that turns a 30-second voice memo into a signed change order with a deposit link. Want me to convert your last verbal change into a sample PDF for free? No signup.
Week-one goal: 60 qualified leads logged, 45 DMs sent, 3 sample PDFs delivered, 5 replies asking for more.
Section 5 of 8

30-day execution roadmap

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

Ship the skeleton

  • Create Next.js repo on Vercel and a Supabase project
  • Write tables for accounts, price_book, change_orders, items, signatures, payments
  • Enable email auth with row-level security on user_id
  • Deploy the empty app to a production URL

Deliverable: Live URL with working login.

Day 2Record

Capture voice

  • Build the mobile recorder with MediaRecorder
  • Upload audio to Supabase Storage
  • Send to Whisper and store the transcript
  • Add retry and error states

Deliverable: Voice memo to transcript in under 15 seconds.

Day 3Extract

Priced line items

  • Prompt GPT-4o-mini for strict JSON line items
  • Build editable line-item table with quantity, unit and price
  • Ship price book CRUD with 20 seeded remodel tasks
  • Match spoken items to price book entries first

Deliverable: Editable priced line items from one memo.

Day 4Document

PDF and signature

  • Render the React-PDF change order with logo, items, total and terms
  • Build the public signing page with canvas signature, timestamp and IP
  • Create the Stripe Checkout deposit session at 30%
  • Store the signed PDF back to Storage

Deliverable: Signed PDF with a working deposit link.

Day 5DeliverMVP shipped

Send and track

  • Send the link via Resend email and Twilio SMS
  • Build the dashboard for draft, sent, signed, paid
  • Run five end-to-end tests on a real phone
  • Fix blockers and freeze the MVP

Deliverable: MVP live and end-to-end verified.

Day 6Proof

Sample assets

  • Create three sample change orders from publicly posted remodel photos
  • Record a 60-second Loom of the real workflow
  • Publish the landing page with both prices and the demo
  • Attach live Stripe payment links

Deliverable: Landing page, three sample PDFs, one Loom.

Day 7List

Lead sourcing

  • Join five US remodeler Facebook groups
  • Log 60 leads with name, group, city and recent post
  • Write three outreach message variants
  • Set up a simple outreach tracker sheet

Deliverable: 60-lead list and a tracker.

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

First DMs

  • Send 15 personalized DMs asking one question
  • Offer a free conversion of their last verbal change
  • Log every reply and objection verbatim
  • Queue a 48-hour follow-up with a sample PDF

Deliverable: 15 DMs sent, replies logged.

Day 9Outreach

Volume and proof

  • Send 15 more DMs
  • Post one value post in the largest group
  • Deliver the first free sample PDF
  • Follow up on day-8 non-replies

Deliverable: 30 cumulative DMs, one group post, one sample delivered.

Day 10Demo

Book live conversions

  • Offer five free 15-minute live conversions
  • Answer Craigslist services listings with the same offer
  • Publish the sample PDF as a group comment
  • Follow up on every warm reply

Deliverable: 5 live conversion slots booked.

Day 11Demo

Run the calls

  • Run the booked live conversions and build the change order on the call
  • Send each finished PDF within 10 minutes of hanging up
  • Note which objections repeat
  • Send Stripe links to the two strongest fits

Deliverable: 5 change orders built live, 2 payment links sent.

Day 12RevenueFirst sale target

First sale

  • Push the payment link to the warmest three prospects
  • Offer Solo at $99 as the low-friction entry
  • Follow up by SMS within four hours of the link
  • Log the payment and onboard manually

Deliverable: First paying customer.

Day 13Onboard

Make the first buyer succeed

  • Set up the buyer's price book from their own rates
  • Build their next change order together
  • Ask for one contractor referral
  • Capture a two-sentence quote if they are willing

Deliverable: One activated customer and one referral target.

Day 14Review

Fix the funnel

  • Count replies, samples and conversions by channel
  • Rewrite the message that got the most replies
  • Cut the group that produced nothing
  • Set the day-15 to day-21 target

Deliverable: Revised outreach script and channel mix.

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

Volume

  • Send 25 DMs with the rewritten script
  • Reply to 5 Craigslist services ads
  • Log every new lead in the tracker
  • Queue follow-ups for 48 hours later

Deliverable: 25 DMs and 5 listing replies sent.

Day 16Scale

Social proof

  • Post the first customer's before-and-after in two groups with permission
  • Publish a short case note on time saved
  • Send 25 DMs
  • Ask the first buyer for the referral introduction

Deliverable: Two proof posts live, 25 DMs sent.

Day 17Referral

Build the loop

  • Set up a referral credit: $50 off for both sides
  • Message every buyer and every sample recipient with the offer
  • Send 20 new DMs
  • Follow up on day-15 replies

Deliverable: Referral offer live and delivered to all contacts.

Day 18Referral

Warm intros

  • Ask three buyers for one named introduction each
  • Send introduction-ready forwarding text
  • Run two live conversions
  • Send resulting PDFs the same day

Deliverable: Three warm introductions requested, two PDFs delivered.

Day 19Cold

Instagram remodelers

  • Collect 40 remodeler handles posting progress photos
  • Send 20 DMs referencing their specific post
  • Offer the free conversion
  • Log reply rate by city

Deliverable: 20 Instagram DMs sent with reply tracking.

Day 20Event

Group demo

  • Host a free 20-minute live conversion in the largest group
  • Build two change orders on camera
  • Post the recording and the offer
  • Send payment links to attendees who asked

Deliverable: One live session delivered and archived.

Day 21Review

Midpoint decision

  • Tally customers, revenue, refunds and objections
  • Decide whether to keep $99 or lead with $199
  • Cut one channel and double the other
  • Set the day-22 to day-30 target

Deliverable: Written midpoint decision.

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

Push Pro

  • Offer existing Solo buyers an upgrade to Pro for the difference
  • Lead new DMs with Pro and the 12-month framing
  • Send 25 DMs
  • Follow up every unpaid link

Deliverable: Upgrade offer sent to all Solo buyers.

Day 23Convert

Follow the money

  • Call or SMS every warm prospect who has not paid
  • Remove one friction step from checkout if any abandoned
  • Send 20 new DMs
  • Log conversion rate by script version

Deliverable: All warm prospects contacted within 24 hours.

Day 24Polish

Remove delivery risk

  • Fix the top two extraction errors reported by buyers
  • Add SMS fallback if email bounces
  • Test the signing page on three phone models
  • Ship the fixes

Deliverable: Two bug fixes deployed.

Day 25Support

Keep buyers active

  • Check every buyer's account for unused credits
  • Send a one-line nudge to each with an unused price book
  • Build one change order for a stalled buyer
  • Ask for a referral from anyone who used it twice

Deliverable: Every buyer contacted and at least two reactivated.

Day 26Expand

New groups

  • Join three new regional contractor groups
  • Post the case note in each
  • Send 25 DMs to new-group members
  • Reply to 5 more Craigslist listings

Deliverable: Three new groups entered, 25 DMs sent.

Day 27Scale

Volume sprint

  • Send 30 DMs with the best-performing script
  • Run every free conversion requested within 24 hours
  • Send Stripe links immediately after each PDF
  • Log all objections

Deliverable: 30 DMs and all conversions cleared.

Day 28Review

Final pipeline

  • List every prospect still unpaid and rank by warmth
  • Send a final direct offer to the top ten
  • Confirm all payments settled in Stripe
  • Reconcile revenue against the tracker

Deliverable: Ranked final pipeline and reconciled numbers.

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

Last conversions

  • Send the closing-day offer to all remaining warm leads
  • Run two live conversions
  • Handle any refund requests immediately
  • Confirm all signed PDFs stored correctly

Deliverable: All remaining offers sent, refunds handled.

Day 30Wrap

Lock the result

  • Export the final revenue, refund and fee report from Stripe
  • Write a one-page postmortem on which message converted
  • Send every buyer a thank-you and the referral offer
  • Set the first post-hackathon retention action

Deliverable: Final numbers exported and postmortem written.

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 buyers, mostly the $99 Solo tier, conversion from unpaid direct outreach only.
  • Base: 10 buyers at a blended $149 from a $99/$199 mix, no paid marketing.
  • Upside: 25 buyers at a blended $169 with one Pro-heavy cohort and one refunded Solo purchase.
  • Payment fees assume Stripe at roughly 2.9% plus $0.30 per transaction, giving 3-4% of collected revenue.
  • No paid marketing is planned; ad_spend_usd is 0 in Conservative and Base and 150 in Upside for one boosted post test.
  • Operating costs cover Vercel, Supabase, OpenAI transcription and extraction, Resend, Twilio and Stripe-adjacent tooling.
  • Operating cost scales with change orders created, not with user count, so it stays low even in the Upside case.
  • Refunds assume a 30-day money-back expectation on a small share of buyers.
  • All figures are projections from these assumptions, not verified revenue or existing customers.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$11
Paid marketing
$0
Hackathon profit
$286
Operating costs
$25
Business profit
$261

Base case

10 customers
$1,490
collected revenue · avg payment $149
Refunds
$0
Chargebacks
$0
Payment fees
$48
Paid marketing
$0
Hackathon profit
$1,442
Operating costs
$65
Business profit
$1,377

Optimistic

25 customers
$4,225
collected revenue · avg payment $169
Refunds
$99
Chargebacks
$0
Payment fees
$135
Paid marketing
$150
Hackathon profit
$3,841
Operating costs
$180
Business profit
$3,661

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
$886

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 are scenario projections built from the stated assumptions, not verified revenue, existing customers or real traction. Actual results will differ.

Section 7 of 8

Main risks and validation experiments

Risk 1Contractors do not trust AI transcription for a document with legal weight.

Mitigation

Every extracted line item is editable before generation, and the PDF names the contractor as the author, not the software.

Validation experiment

Build three sample change orders by hand for three contractors and watch whether they correct prices or refuse the format.

Kill criteria

If fewer than 3 of 10 sample recipients would send the PDF to a real client, the output format is wrong.

Risk 2Wrong extracted prices create a financial mistake and a refund.

Mitigation

Price-book-first matching, unit and quantity shown separately, and a mandatory confirmation screen before the PDF renders.

Validation experiment

Run 20 recorded memos through extraction and measure line-item accuracy against hand-entered prices.

Kill criteria

If line-item accuracy stays below 80% after prompt tuning, transcription-only pricing is not sellable.

Risk 3Manual outreach cannot reach the customer count needed in 30 days.

Mitigation

Free conversion offer lowers the ask, and every buyer is asked for one named introduction.

Validation experiment

Send 45 DMs in week one and measure reply rate and sample-PDF requests.

Kill criteria

If reply rate stays under 5% after two script rewrites, switch the channel before day 15.

Risk 4Buyers prefer existing paper or QuickBooks workflows.

Mitigation

Pitch the artifact, not the software: one PDF per change, no workflow migration required.

Validation experiment

Ask every prospect what they use today and record whether a signed PDF alone changes their behaviour.

Kill criteria

If more than half of qualified prospects say they need QuickBooks sync before buying, the wedge is too narrow to sell.

Risk 5SMS link delivery is filtered by carriers and the client never sees the change order.

Mitigation

Email is always sent alongside SMS, and the signing link is copy-pasteable by the contractor.

Validation experiment

Send 10 test change orders across three carriers and confirm delivery and link open rates.

Kill criteria

If SMS delivery fails on more than 2 of 10 tests, launch email-first and drop the SMS claim from pricing.

Risk 6One-time pricing collects once and leaves no retention.

Mitigation

Pro Launch is framed as 12 months of access, creating a natural monthly conversation at renewal.

Validation experiment

Offer both tiers in the first week and record which one buyers choose without prompting.

Kill criteria

If more than 80% choose Solo, collapse to a single tier and test $49 per month instead.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and Vercel project
  • Create the Supabase project and enable email auth
  • Write the six core tables with row-level security

Output: Deployed skeleton app with a working login.

Hours 3-5

  • Build the MediaRecorder capture screen
  • Wire the Supabase Storage upload
  • Connect Whisper and render the transcript

Output: A spoken memo producing readable text in the app.

Hours 6-8

  • Write the GPT-4o-mini extraction prompt returning strict JSON
  • Build the editable line-item table
  • Seed ten starter price book items

Output: A memo producing editable priced line items.

Hours 9-11

  • Set up the Stripe account and connect it to TrustMRR before any customer exists
  • Create the $99 and $199 payment links
  • Draft the landing page headline and the free-conversion offer

Output: Live payment links and a draft landing page.

Hours 12-14

  • Join three remodeler Facebook groups
  • Log the first 20 leads with links to their posts
  • Send the first 5 DMs asking one question

Output: 20-lead list and 5 DMs sent on day one.

Complete report

Full 30-day launch report

Read the full generated report

ChangeOrder Voice — 30-Day Solo Launch Report

1. Product opportunity and positioning

Owner-operator remodelers run two to ten jobs at once and get asked for extras constantly: an extra outlet, a soffit change, a tile upgrade, a moved vanity. The work gets done on a handshake. The paperwork gets written at 9pm, or never. Every unbilled change is margin lost, and every undocumented one becomes a collections argument three weeks later.

ChangeOrder Voice attacks the moment of the request, not the invoice. The contractor talks for thirty seconds into their phone. The app transcribes it, maps it against a saved price book, and produces a branded change order PDF with line items, terms, a client signature pad and a Stripe deposit link. The contractor sends it by SMS from the truck.

Positioning: get paid for the extra work before you do it. This is deliberately not project management, not invoicing software, and not a payment rail. It is a single-document tool whose output is a signed financial artifact. The buyer already believes change orders matter; the product removes the friction that stops them writing one.

The customer is reachable directly — Facebook groups, Craigslist services listings, public Instagram job photos — with no procurement cycle, and can approve $99 or $199 in one text exchange. JEV scored this concept 64.8/100 with speed to first revenue as its strongest criterion (8.58); the weakest is operational simplicity (4.69). The plan below keeps every step self-serve and stateless to defend that weakness: no human review queue, no regulated data, no credit exposure.

2. Smallest sellable MVP

One voice memo in, one signable priced PDF out. The MVP is a mobile web app with a recorder, Whisper transcription, a GPT-4o-mini extraction step returning editable line items, a price book of twenty common remodel tasks, a React-PDF change order template, a public signing page with canvas signature and timestamp, and a Stripe Checkout deposit link at 30%. Sending happens through Resend email and Twilio SMS. A dashboard lists drafts, sent, signed and paid.

Explicitly absent: project management, accounting sync, photo verification of progress, stored card credentials, team roles, native apps. Every one of those adds operational surface a solo founder cannot carry in thirty days.

3. Technical implementation plan

Next.js on Vercel serves the dashboard and the public signing pages from one codebase. Supabase provides Postgres, auth, storage and row-level security. Audio is recorded with MediaRecorder, uploaded to Storage, transcribed by Whisper, then passed to GPT-4o-mini with a strict JSON schema. The contractor confirms or edits line items. A React-PDF route renders the document and writes it back to Storage. The signing page is keyed by an unguessable token, records signature, timestamp and IP, and opens a Stripe Checkout session. A Stripe webhook flips status to paid.

The hardest technical risk is extraction producing plausible but wrong prices. Mitigations are price-book-first matching, separated unit and quantity columns, and a mandatory confirmation screen. Build order runs scaffold, schema, recorder, transcription, extraction, price book, PDF, signing, Stripe, sending, dashboard — five working days.

4. Pricing and monetization

Two one-time tiers sold through Stripe links: Solo Launch at $99 for 20 change orders, and Pro Launch at $199 for unlimited change orders for 12 months plus custom branding and SMS sending. Blended expected order value is $149. One-time pricing matches how contractors buy tools, avoids a subscription objection in a cold DM, and the 12-month Pro framing creates a natural renewal conversation later. The upsell path is Pro to $49 per month at month 12, a $29 branded price-book import, and $50 referral credit for both sides.

5. First-customer acquisition

One channel: direct outreach in US remodeler Facebook groups and Craigslist services listings. The founder joins five groups, searches posts for "change order" and "scope creep", and DMs the poster with one question rather than a pitch. The offer is a free conversion of their last verbal change order into a signed priced PDF. That artifact is produced manually if necessary, then followed up at 48 hours with a Stripe link.

Week one target: 60 qualified leads logged, 45 DMs sent, 3 sample PDFs delivered, 5 replies asking for more. Every buyer is asked for one named introduction, and referral credit is live by day 17.

6. 30-day execution roadmap

Days 1-5 build the MVP in production, one vertical slice per day, ending with five end-to-end tests on a real phone. Day 6 turns the product into sales assets: three sample PDFs from public project photos, a 60-second Loom, a landing page, live payment links. Day 7 builds a 60-lead list.

Days 8-14 are the first outreach wave: 15 DMs per day, a value post, five free live conversions, and payment links pushed to the warmest prospects on day 12. Day 13 is manual onboarding of the first buyer, including building their price book. Day 14 rewrites the script based on reply data.

Days 15-21 scale volume to 25 DMs per day, add Instagram and Craigslist, publish the first customer proof post, launch the referral credit, and run one live group demo. Day 21 is a written midpoint decision on price and channel mix.

Days 22-28 push Pro upgrades, chase every unpaid link, fix the top two reported extraction errors, nudge inactive buyers, and enter three new regional groups. Day 29 is the closing-day offer to all warm leads. Day 30 exports final Stripe numbers and writes the postmortem. Milestone deadline: day 5. First sale target: day 12.

7. Revenue and profit scenarios

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

Conservative: 3 buyers at $99, $297 gross, $11 in payment fees, $0 ad spend, $25 operating cost.

Base: 10 buyers at a blended $149, $1,490 gross, $48 in payment fees, $0 ad spend, $65 operating cost.

Upside: 25 buyers at a blended $169, $4,225 gross, one $99 refund, $135 in payment fees, $150 of paid marketing for one boosted post test, $180 operating cost.

Hackathon profit counts collected revenue minus refunds, chargebacks, payment fees and paid marketing. Operating costs for hosting, domains, tooling and AI delivery are excluded from hackathon profit but reduce business profit. Stripe fees are assumed at roughly 2.9% plus $0.30 per transaction.

8. Main risks and validation experiments

The first risk is trust: contractors may not accept AI transcription on a document with legal weight. Test by hand-building three sample change orders and watching whether recipients correct or reject them; if fewer than 3 of 10 would send it to a real client, the format is wrong.

The second is pricing accuracy. Run 20 recorded memos through extraction and measure line-item accuracy against hand-entered prices. Below 80% after prompt tuning, transcription-only pricing is not sellable and the price book must lead every line.

The third is channel capacity. If DM reply rate stays under 5% after two script rewrites, switch channel before day 15 rather than grinding.

The fourth is delivery: SMS filtering can hide the signing link. Send 10 test change orders across three carriers; if more than 2 fail, launch email-first and remove SMS from the Pro tier claim.

The fifth is retention: if more than 80% of buyers choose Solo, collapse to one tier and test $49 per month instead.

9. First 24-hour action plan

Hours 1-2: repo, Vercel, Supabase, six tables with row-level security. Output: deployed skeleton with login.

Hours 3-5: recorder, storage upload, Whisper transcription. Output: a spoken memo producing readable text.

Hours 6-8: GPT-4o-mini extraction prompt, editable line-item table, ten seeded price book items. Output: editable priced line items.

Hours 9-11: Stripe account connected to TrustMRR before any customer exists, $99 and $199 payment links, landing page draft. Output: live payment links.

Hours 12-14: join three groups, log 20 leads, send the first 5 DMs. Output: 20-lead list and 5 DMs sent on day one. Every sale must cover what it costs to deliver it; at roughly $0.10 of AI cost per change order, a $99 Solo purchase covers roughly 990 change orders of delivery cost before it stops being profitable.

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 →