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

MissedCall Quote Card

Turns a missed call plus a customer photo into a ready-to-send SMS quote card for solo home-service pros.

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.65/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct SMS and calls to solo plumbers and HVAC pros in one metro, sourced from Google Maps listings with reviews that explicitly mention unanswered calls.
Who pays

Solo or 2-person plumbers, HVAC techs and electricians in the US who answer their own phones and lose jobs when on-site or asleep.

Biggest execution risk

Operational simplicity 5.1/10

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

Product opportunity and positioning

Target customer

Solo or 2-person plumbers, HVAC techs and electricians in the US who answer their own phones and lose jobs when on-site or asleep.

Why now

Vision models are now accurate enough on plumbing and HVAC photos, and Twilio missed-call webhooks plus Stripe Checkout let one person ship and charge for this in under a week.

Problem

When the pro is under a sink or asleep, the call rolls to voicemail and the homeowner dials the next Google Maps listing; no quote is ever sent.

Solution

A missed call triggers an SMS with a no-login photo upload link; a vision model classifies the job, matches it to the pro's CSV price sheet, and returns a one-tap-approvable quote card the pro texts back.

Differentiation · Not a receptionist, not a voice AI, not a CRM: it produces exactly one artifact — a priced quote card — that a pro can judge in a single missed call.

1. Product opportunity and positioning

A solo plumber under a sink cannot answer the phone. The call goes to voicemail, the homeowner scrolls to the next listing on Google Maps, and the job is gone before the pro ever knew it existed. Every existing fix is too big: a human answering service costs more than the marginal job, a general virtual receptionist sells a monthly subscription to a suspicious buyer, and a full field-service platform asks the pro to change how they run the business before they get one dollar of value.

MissedCall Quote Card sells a single artifact instead. When a call is missed on the pro's Twilio number, the homeowner instantly receives an SMS with a no-login photo upload link. They snap the leak, the panel or the unit. A vision model classifies the job against a small taxonomy, the tool looks up the pro's own CSV price sheet, and the pro gets an SMS quote card with one-tap approve-and-send. The homeowner receives a priced, professional reply minutes after hanging up, while the pro is still under the sink.

Positioning: quote card, not receptionist. The product never answers a call and never books a job. That restraint is the pitch — it is why a one-person founder can build it in days, why the pro can evaluate it on their next real missed call, and why the price can be a flat $99 instead of a monthly platform commitment. The buyer is a solo or two-person operator in plumbing, HVAC or electrical who already pays for a Google Business Profile presence and already knows exactly how many calls they miss. The pain is self-evident to them, which shortens the sales conversation to one live test.

The commercial wedge is speed. Because the deliverable is a card the pro can read on their phone in ten seconds, the trial is the demo and the demo is the trial. JEV scored this concept 66.5 (band B), strongest on speed to first revenue (8.71 normalized) and solo build feasibility (7.37), weakest on operational simplicity and defensibility. The plan below leans into the strength — fast, direct, one-metro outreach — and deliberately does not try to fix the weaknesses with scope.

2. Smallest sellable MVP

The sellable unit is: one Twilio number wired to a missed-call webhook, an SMS with a photo upload link, a vision classification against a five-to-eight category taxonomy, a CSV price sheet the founder imports on the pro's behalf, and a generated quote card the pro approves by replying or tapping. Stripe Checkout closes the $99.

Everything else is out. No voice answering, no scheduling, no deposits from homeowners, no team accounts, no marketplace. Classification does not need to be perfect — it needs to pick the right category and price band on obvious photos, and the card always shows a range plus "confirm on site" so a wrong AI guess stays a starting point rather than a commitment. The founder imports the first price sheet manually; self-serve editing is a day-two feature.

3. Technical implementation plan

Next.js on Vercel for the upload page, the pro's price sheet form and the quote card page. Twilio provides the number and the missed-call webhook. Supabase stores pros, price sheets and job records. OpenAI vision classifies the photo. Stripe Checkout takes the $99.

Flow: Twilio webhook → create job row → send SMS with a signed upload link → homeowner uploads photo → vision call returns category plus confidence plus visible damage notes → lookup price band in the pro's CSV → render quote card HTML plus a short SMS body → notify pro with approve/edit links → pro taps approve → homeowner receives the text. The hardest technical risk is vision misclassification on poor photos; mitigate with a low-confidence fallback that sends a generic "need to see it in person, here's my diagnostic range" card instead of guessing.

4. Pricing and monetization

Two prices only. Founding Pro: $99 one-time, includes number setup, price sheet import, the first 30 days of cards and a sample card built for their business. Pro Monthly: $79/month for unlimited cards after the founding month. The one-time price exists because the hackathon rewards collected money inside the window, and a pro will pay $99 to test something on their own real missed call far more readily than they will start a subscription.

5. First-customer acquisition

One channel: direct SMS and calls to solo pros in a single metro, sourced from Google Maps listings whose reviews explicitly complain that nobody answered. The list is the product. Sixty entries with name, trade, phone and the review quote. The outreach message references their own review, offers a free test on their next missed call, and asks for five minutes. Conversion happens on a live test, not on a pitch deck.

6. 30-day execution

Days 1-5 are build and dry-run; the MVP must fire a real card end to end on the founder's own phone by day 5. Days 6-9 are list-building and the first live test, with the first $99 targeted for day 9 and accepted any time after. Days 10-21 are outreach volume — batches of 40 SMS plus 10-15 calls per cycle, with the 48-hour sample-card follow-up as the main second touch. Days 22-30 add a second metro, referrals from paying pros, reliability hardening and the final close push. Weekly gates: 60 SMS sent by day 7, one paying pro by day 12, five by day 21, ten by day 30.

7. Revenue scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 customers × $99 = $297. Base: 10 × $99 = $990. Upside: 25 × $99 = $2,475 with $150 of paid spend and $50 of refunds. Payment processing is assumed at roughly 4% (Stripe Checkout, 2.9% + $0.30 blended). Operating costs are $25-$90 across scenarios for Twilio, OpenAI vision calls, Supabase and the domain. Hackathon profit excludes those operating costs; business profit deducts them. None of these numbers represent existing customers.

8. Main risks

Cold SMS gets ignored or reported — the deliberate fix is a one-metro, review-referenced message and a hard cap on daily sends. Vision misclassifies and the pro loses trust — fixed with a confidence threshold and a generic fallback card. Twilio A2P registration or deliverability delays — start registration on day 1, before writing product code. A pro's price sheet is too custom to automate — validated by manually importing the first five sheets and counting the exceptions.

9. First 24 hours

Register the Twilio number and start A2P 10DLC registration. Stand up the Next.js repo, Supabase schema and Vercel deploy. Build the missed-call webhook and the SMS with the upload link, and prove it on the founder's own phone. Build the 60-row prospect list for one metro and send the first ten messages the same day.

Section 2 of 8

Smallest sellable MVP

A Twilio missed-call webhook that texts the homeowner a photo upload link, a vision-classified job matched to an imported CSV price sheet, and a quote card the pro approves in one tap — charged at $99 via Stripe Checkout.

Must-have features

  • Twilio number with missed-call webhook that fires within 10 seconds
  • No-login mobile photo upload page with a signed link
  • Vision classification into 6-8 job categories with a confidence score
  • Per-pro price sheet imported from CSV and editable in a web form
  • Quote card generator: short SMS body plus hosted card page
  • Pro notification with one-tap approve and edit-then-send
  • Stripe Checkout for the $99 Founding Pro plan
  • Low-confidence fallback card when the photo is ambiguous

Explicitly out of scope

  • Inbound voice AI or call answering
  • Calendar, booking or dispatch scheduling
  • Homeowner deposit collection
  • Multi-user team accounts
  • Marketplace or lead generation
  • Automated Stripe subscription billing on day one
  • Native mobile app

Demo flow (what the buyer sees)

  1. Pro's Twilio number misses an inbound call
  2. Homeowner receives SMS with a photo upload link
  3. Homeowner uploads one photo of the leak or unit
  4. Vision model returns category, confidence and visible notes
  5. Tool matches category to the pro's CSV price band
  6. Quote card generated with range, scope line and 'confirm on site' note
  7. Pro gets an SMS with approve/edit links and taps approve
  8. Homeowner receives the priced quote card text
Build plan

Technical implementation plan

Stack

Next.js on VercelTwilio Programmable SMS and Voice webhooksOpenAI vision API (GPT-4o class model)Supabase Postgres and storageStripe CheckoutResend or Twilio for pro notificationsVercel Cron for retry and follow-up jobs

Architecture

Twilio owns the phone number and posts a missed-call webhook to a Next.js API route. That route writes a job row in Supabase, mints a signed upload token, and sends the homeowner an SMS with the upload URL. The upload page stores the photo in Supabase storage and calls the vision API. The response plus the pro's CSV price sheet produce a rendered quote card page and a short SMS body. The pro is notified with approve and edit links; approving sends the card text to the homeowner through Twilio and marks the job complete. Stripe Checkout sits on the marketing page and gates the pro's dashboard.

Build steps

  1. Register Twilio number and start A2P 10DLC registration
  2. Create Supabase schema: pros, price_sheets, jobs, cards, payments
  3. Build missed-call webhook route with idempotency key and job row creation
  4. Build signed photo upload page and storage write
  5. Wire OpenAI vision call with a fixed JSON schema and confidence field
  6. Build price band lookup against per-pro CSV with a default fallback row
  7. Build quote card renderer and hosted card page
  8. Add pro SMS notification with approve and edit tokens
  9. Implement approve route that texts the card to the homeowner
  10. Add Stripe Checkout and a paid flag on the pro record
  11. Add pro dashboard for price sheet editing and recent cards
  12. Dry run end to end on the founder's own phone and fix latency
  13. Add retry and duplicate-suppression cron for webhook failures

AI components

  • OpenAI vision model classifies the uploaded photo into a fixed job taxonomy with a confidence score
  • Same model extracts visible damage notes and a suggested scope line
  • LLM drafts the short SMS quote card copy from category, price band and extracted notes
Hardest technical risk: Vision misclassification on low-quality or ambiguous photos, which produces a wrong price band and destroys pro trust on the very first test.
Section 3 of 8

Pricing and monetization

Founding Pro

Entry offer
$99 one-time

For Solo pros testing on real missed calls

  • Twilio number setup and missed-call webhook
  • Price sheet import and cleanup
  • First 30 days of quote cards
  • One sample quote card built for their business

Pro Monthly

$79 / month

For Pros who saw a quote card convert

  • Unlimited missed-call quote cards
  • Editable price sheet
  • SMS approve and send

Model: One $99 one-time Founding Pro package to convert a live test into cash, then a $79/month plan for pros who keep using it.

First revenue offer: Founding Pro, $99 one-time: I set up the number, import your price sheet and run the first quote card on your next real missed call. If the card isn't something you'd actually send, I refund it.

Expected ACV: $99

Upsell path: Founding Pros roll into $79/month after their 30 days; monthly customers who ask for second numbers or a second tech add a $49 per-number add-on.

Target customers
40
Revenue model
$3,960
Costs
$180
Profit model
$3,780
Section 4 of 8

First-customer acquisition

Primary channel

Direct SMS and calls to solo plumbers and HVAC pros in one metro, sourced from Google Maps listings with reviews that explicitly mention unanswered calls.

Where to find them

  • Google Maps listings for plumbers in one metro, sorted by review count
  • Reviews containing phrases like 'never answered', 'no one picked up', 'called three times'
  • HVAC and electrical listings on the same map search
  • Yelp business pages for the same trades in the same metro
  • Nextdoor neighborhood threads asking 'who is a plumber that actually picks up'
  • Local trade Facebook groups and subreddits for that metro

Exact outreach motions

  • SMS referencing their own review quote and offering a free test on the next missed call
  • Follow-up SMS at 48 hours with a screenshot of a sample quote card
  • Callback to pros who reply, walking through the missed-call flow in five minutes
  • In-person or phone offer of the $99 Founding Pro package immediately after a live test
  • Referral ask to every paying pro: name two other pros in the metro
  • Post the same sample card in one local trade group thread per week

Message template

Hey [Name] — saw the review that said 'called twice, no answer.' I built a tool that texts the customer a photo link when you miss a call, then sends you a priced quote card to approve in one tap. Want a free test on your next missed call? — [Founder], [phone]
Week-one goal: 60 qualified pros listed, 60 SMS sent, 8 replies, 3 live tests run and 1 paid $99 Founding Pro.
Section 5 of 8

30-day execution roadmap

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

Twilio and repo

  • Register Twilio number and start A2P 10DLC registration
  • Scaffold Next.js repo, Supabase schema and Vercel deploy

Deliverable: Live deploy with Twilio number approved-pending and schema migrated

Day 2Missed-call capture

Webhook to SMS

  • Build missed-call webhook with idempotency key
  • Send homeowner SMS with signed upload link
  • Prove it on the founder's own phone

Deliverable: Missed call produces an SMS with a working upload link

Day 3Vision

Classification

  • Build no-login photo upload page
  • Wire OpenAI vision call with fixed JSON schema and confidence
  • Add low-confidence fallback branch

Deliverable: Photo in, category plus confidence out

Day 4Quote card

Card generation

  • Build CSV price sheet import and price band lookup
  • Render quote card page and short SMS body
  • Add pro approve/edit links

Deliverable: Full card generated and approvable from a link

Day 5MVP closeMVP shipped

End-to-end plus payment

  • Add Stripe Checkout and paid flag
  • Run three full dry runs on real photos
  • Publish one-page site with the $99 offer

Deliverable: MVP live and payable, mvp deadline met

Day 6Prospecting

Build the list

  • Build 60-row prospect list in one metro with review quotes
  • Send first 20 SMS using the review-referenced template

Deliverable: Prospect sheet plus 20 messages sent

Day 7Prospecting

Volume

  • Send 40 more SMS
  • Log replies and objections in the sheet
  • Book first live test

Deliverable: 60 SMS sent, first live test scheduled

Week 2 · Launch & first sale · 7 days
Day 8Live test

First real card

  • Run the live test on the pro's next missed call
  • Send them the generated sample card
  • Fix any break in under an hour

Deliverable: One real quote card delivered to a real homeowner

Day 9First saleFirst sale target

Close $99

  • Ask for the $99 Founding Pro on the follow-up call
  • Send Stripe Checkout link while on the phone
  • Log the objection if declined

Deliverable: First paying Founding Pro or a documented blocker

Day 10Outreach

Calls

  • Call 20 pros from the list
  • Tighten the message template using the day 8-9 feedback

Deliverable: 20 calls, revised template

Day 11Onboarding

Time to value

  • Write the 15-minute onboarding checklist
  • Import a second pro's price sheet manually
  • Time the setup end to end

Deliverable: Onboarding under 15 minutes, documented

Day 12Sales

Second and third close

  • Run two more live tests
  • Offer $99 Founding Pro to both
  • Collect the top three objections verbatim

Deliverable: Two more checkout links sent

Day 13Product fix

Top objection

  • Fix the single most common objection
  • Add a second sample photo set per trade
  • Re-run one failed test

Deliverable: Objection fix shipped and retested

Day 14Review

Week two audit

  • Audit revenue collected versus messages sent
  • Kill the worst-performing message angle
  • Set week three targets

Deliverable: Conversion stats and revised targets

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

Batch two

  • Build a second 40-row list in the same metro
  • Send 40 SMS
  • Make 10 calls

Deliverable: 40 SMS and 10 calls logged

Day 16Follow-up

48-hour touch

  • Send sample card screenshots to all non-responders
  • Call every reply that went cold

Deliverable: All warm leads touched twice

Day 17Quality

Vision accuracy

  • Collect every real photo processed so far
  • Label misclassifications and adjust the taxonomy
  • Retest against the corrections

Deliverable: Measured accuracy on real photos

Day 18Discovery

Price sheets

  • Run 10 short calls on how pros price jobs
  • Collect the most common sheet structures
  • Add one default template per trade

Deliverable: Three default price sheet templates

Day 19Assets

Demo video

  • Record a 45-second screen capture of the missed-call flow
  • Add it to the outreach link
  • Update the landing page with it

Deliverable: Demo video live and in use

Day 20Outreach

Batch three

  • Send 40 SMS
  • Make 15 calls
  • Push outstanding checkout links

Deliverable: 40 SMS and 15 calls logged

Day 21Review

Midpoint

  • Reconcile Stripe revenue to date
  • Cut any outreach motion with zero replies
  • Set final nine-day revenue target

Deliverable: Midpoint P&L and final target

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

Second metro

  • Build a 60-row list in a second metro
  • Send the first 20 SMS there

Deliverable: Second market opened

Day 23Outreach

Batch four

  • Send 40 SMS in metro two
  • Call 10 pros in metro one

Deliverable: 50 touches logged

Day 24Referrals

Paying pros

  • Ask every paying pro for two names
  • Offer a free second month per referral that pays

Deliverable: Referral pipeline started

Day 25Revenue mix

Monthly plan

  • Offer $79 Pro Monthly to new signups alongside $99
  • Compare take rate on both offers

Deliverable: Two live price points with take-rate data

Day 26Outreach

Batch five

  • Send 40 SMS
  • Make 15 calls
  • Follow up every unopened checkout link

Deliverable: 40 SMS and 15 calls logged

Day 27Reliability

Harden

  • Add retry and duplicate suppression to the webhook
  • Monitor error rate on vision calls
  • Write the one-page runbook

Deliverable: Error rate under 5% with a runbook

Day 28Pipeline

Close pending

  • Call every unclosed live test
  • Remove friction from the last onboarding step
  • Send a deadline note to warm leads

Deliverable: All warm leads with a clear yes or no

Days 29-30 · Consolidate · 2 days
Day 29Final push

Collect

  • Close outstanding checkout links
  • Process any refund requests immediately
  • Reconcile Stripe against the job log

Deliverable: Clean collected-revenue number

Day 30Freeze

Reconcile and submit

  • Freeze code and stop new onboarding
  • Export the final revenue and payment record
  • Submit the hackathon entry

Deliverable: Final reconciled submission

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/Base/Upside: every counted customer buys the $99 Founding Pro one-time package; no monthly revenue is counted inside the 30-day window.
  • Conservative: 3 customers, ~1% conversion on roughly 300 outbound SMS and calls.
  • Base: 10 customers, ~3.3% conversion on the same outreach volume, plus three referrals.
  • Upside: 25 customers, ~8% conversion with $150 of paid placement boosting the same message, and $50 of refunds on two cards the pros judged generic.
  • Payment processing assumed at Stripe Checkout rates, roughly 4% blended after the fixed per-transaction fee.
  • Ad spend is paid placement only; all direct SMS and calls are organic and cost $0 in this line.
  • Operating costs cover Twilio number and SMS, OpenAI vision calls, Supabase and domain, scaled by customer count.
  • No customer, revenue or partnership in this report is verified; all figures are projections.

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
$39
Paid marketing
$0
Hackathon profit
$951
Operating costs
$45
Business profit
$906

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$50
Chargebacks
$0
Payment fees
$97
Paid marketing
$150
Hackathon profit
$2,178
Operating costs
$90
Business profit
$2,088

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. No customers, payments or traction exist at the time of writing; these are projections for planning only.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold SMS and calls get ignored or reported as spam, so no pro ever runs a test.

Mitigation

Keep every message review-referenced and personal, cap sends at 40 per day per number, and use a second Twilio number if a report rate appears.

Validation experiment

Send 20 review-referenced SMS to one metro on day 6 and count replies within 24 hours.

Kill criteria

Fewer than 2 replies from 60 SMS by day 10 — rewrite the message and channel before spending more days.

Risk 2Vision misclassifies the job and the pro sees a wrong price band on their first real card.

Mitigation

Confidence threshold with a generic diagnostic-range fallback card, plus a mandatory 'confirm on site' line on every card.

Validation experiment

Label 30 real photos from live tests and measure category accuracy before claiming accuracy in outreach.

Kill criteria

Category accuracy below 70% on real photos after two taxonomy passes.

Risk 3Twilio A2P 10DLC registration or SMS deliverability delays block missed-call capture entirely.

Mitigation

Start registration on day 1, use a toll-free number as a backup, and test delivery to three carriers before day 5.

Validation experiment

Send a test SMS to one phone on each of AT&T, Verizon and T-Mobile on day 3.

Kill criteria

Registration still unresolved by day 8 with no working fallback number.

Risk 4A pro's price sheet is too custom to import in 15 minutes, making onboarding unprofitable.

Mitigation

Three default price sheet templates per trade and a manual import done by the founder for the first ten pros.

Validation experiment

Time the import of five real price sheets and log every exception.

Kill criteria

Median import time above 30 minutes after five sheets.

Risk 5Quote cards feel generic, driving refunds and negative word of mouth in a small metro.

Mitigation

Include the pro's business name, a scope line drawn from the photo, and an explicit range rather than a single number.

Validation experiment

Ask each paying pro to rate the first card 1-5 and explain any score below 4.

Kill criteria

Two or more refund requests from the first ten sales.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register Twilio number
  • Start A2P 10DLC registration
  • Create Supabase project and Stripe account in test mode

Output: Twilio number pending registration, Supabase and Stripe accounts live

Hours 2-5

  • Scaffold Next.js repo
  • Define pros, price_sheets, jobs, cards, payments tables
  • Deploy to Vercel

Output: Deployed app skeleton with migrated schema

Hours 5-8

  • Build missed-call webhook route with idempotency
  • Send SMS with signed upload link
  • Test with a call to the founder's own number

Output: Working missed-call to SMS path

Hours 8-11

  • Build no-login upload page
  • Wire OpenAI vision call with JSON schema
  • Store result on the job row

Output: Photo upload returns category and confidence

Hours 11-14

  • Build the 60-row prospect list for one metro with review quotes
  • Send the first 10 SMS using the review-referenced template
  • Log sends and replies in the sheet

Output: Prospect sheet plus 10 messages sent on day one

Complete report

Full 30-day launch report

Read the full generated report

MissedCall Quote Card — 30-Day Launch Report

1. Product opportunity and positioning

A solo plumber under a sink cannot answer the phone. The call rolls to voicemail, the homeowner scrolls to the next Google Maps listing, and the job is gone before the pro knew it existed. Every existing fix is too large: a human answering service costs more than the marginal job, a general virtual receptionist sells a monthly subscription to a suspicious buyer, and a field-service platform demands the pro change how they run the business before seeing a dollar of value.

MissedCall Quote Card sells one artifact instead. A call missed on the pro's Twilio number instantly triggers an SMS to the homeowner with a no-login photo upload link. They snap the leak, the panel or the unit. A vision model classifies the job against a small taxonomy, the tool looks up the pro's own CSV price sheet, and the pro receives an SMS quote card with one-tap approve and send. The homeowner gets a priced, professional reply minutes after hanging up, while the pro is still under the sink.

The positioning is deliberate: quote card, not receptionist. The product never answers a call and never books a job. That restraint is the pitch — it is why one person can build it in days, why the pro can evaluate it on their next real missed call, and why the price is a flat $99 rather than a platform commitment. The buyer is a solo or two-person operator in plumbing, HVAC or electrical who already maintains a Google Business Profile and already knows how many calls they miss. The pain is self-evident, which collapses the sales conversation into one live test.

JEV scored this concept 66.5 (band B), strongest on speed to first revenue and solo build feasibility, weakest on operational simplicity and defensibility. This plan leans into the strength: fast, direct, single-metro outreach. It does not attempt to fix defensibility with scope.

2. Smallest sellable MVP

The sellable unit is a Twilio number wired to a missed-call webhook, an SMS with a photo upload link, a vision classification into six to eight categories, a CSV price sheet imported by the founder on the pro's behalf, and a generated quote card the pro approves by tapping a link. Stripe Checkout takes the $99.

Everything else is cut: no voice answering, no scheduling, no homeowner deposits, no team accounts, no marketplace. Classification does not need to be perfect. It needs to pick the right category and price band on obvious photos, and every card shows a range plus a 'confirm on site' line so an AI guess stays a starting point rather than a commitment.

3. Technical implementation plan

Next.js on Vercel serves the upload page, the price sheet form and the hosted card. Twilio owns the number and posts the missed-call webhook. Supabase stores pros, sheets and jobs. OpenAI vision classifies the photo. Stripe Checkout collects payment.

The sequence is linear: webhook creates a job row, mints a signed upload token and texts the link; the homeowner uploads; vision returns category, confidence and visible notes; the lookup finds the price band in that pro's sheet; the card renders; the pro is notified with approve and edit links; approval sends the card to the homeowner. The hardest risk is misclassification on poor photos, handled by a confidence threshold that downgrades to a generic diagnostic-range card instead of guessing.

4. Pricing and monetization

Two prices. Founding Pro at $99 one-time covers number setup, price sheet import, one sample card and thirty days of cards. Pro Monthly at $79 follows for pros who keep using it. The one-time price exists because cash inside the window is what counts and because a pro will pay $99 to test on their own missed call far more readily than they will start a subscription.

5. First-customer acquisition

One channel: direct SMS and calls to solo pros in a single metro, sourced from Google Maps listings whose reviews explicitly complain that nobody answered. The list is the product — name, trade, phone and the review quote. Outreach references their own review, offers a free test on the next missed call, and asks for five minutes. Conversion happens on a live card, not a pitch.

6. 30-day execution

Days 1-5 are build and dry-run; the MVP must fire a card end to end on the founder's own phone by day 5. Days 6-9 are list building and the first live test, with the first $99 targeted for day 9. Days 10-21 are outreach volume: batches of 40 SMS plus 10-15 calls, with a 48-hour sample-card follow-up as the main second touch. Days 22-30 open a second metro, harvest referrals, harden reliability and close. Gates: 60 SMS by day 7, one paying pro by day 12, five by day 21, ten by day 30.

7. Revenue scenarios

All figures are projections from stated assumptions, not verified revenue. Conservative: 3 customers at $99 for $297. Base: 10 for $990. Upside: 25 for $2,475, with $150 of paid placement and $50 of refunds. Processing is assumed near 4% at Stripe Checkout rates. Operating costs run $25-$90 for Twilio, vision calls, Supabase and the domain. Hackathon profit excludes those operating costs; business profit deducts them. No customer or payment described here exists today.

8. Main risks

Cold SMS gets ignored — mitigated by one-metro, review-referenced messages and a 40-per-day cap. Vision misclassifies and erodes trust — mitigated by a confidence threshold and fallback card. Twilio A2P registration stalls — mitigated by starting on day 1 and testing three carriers before day 5. Price sheets resist import — mitigated by manual imports and three trade templates.

9. First 24 hours

Register the Twilio number and start A2P registration. Stand up the repo, Supabase schema and Vercel deploy. Build the webhook and prove the SMS with upload link on the founder's own phone. Then build the 60-row prospect list and send the first ten messages the same day.

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 →