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

JobPing Rescue

When a home-service owner misses a call, JobPing texts the caller back in 10 seconds, qualifies the job by SMS, and delivers a one-screen Job Brief to the owner so the job gets booked instead of lost.

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.79/10
MVP build (solo)
4 days
Launch price
$99 · monthly
Sales to $1,000 revenue
11 customers
First paying customer
The missed-call audit: call solo home-service businesses from Google Maps after 6pm, log who hits voicemail, then send each one the exact timestamp of their own missed call plus a sample Job Brief.
Who pays

Owner-operator of a 1-5 person home-service business (plumber, electrician, roofer, mobile mechanic, garage-door tech) in the US, Canada, UK or Australia who is on tools most of the day and misses inbound calls.

Biggest execution risk

Operational simplicity 4.3/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 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

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

0/18
Entry price
$99
Solo build
4 days
30d base revenue
$1,620
30d hackathon profit
$1,569
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a 1-5 person home-service business (plumber, electrician, roofer, mobile mechanic, garage-door tech) in the US, Canada, UK or Australia who is on tools most of the day and misses inbound calls.

Why now

Qualification-grade AI SMS is now cheap enough to sit inside a $99/month product, and Twilio, Stripe, Supabase and Resend are all self-serve, so one person can ship a working missed-call rescue in four days.

Problem

A missed call is a lost job, and the voicemail that replaces it has no address, no job type, no urgency and no photos, so the callback becomes phone tag the owner never runs.

Solution

Calls forward on no-answer to a JobPing number, the caller gets an instant SMS, an AI SMS flow extracts job type, ZIP, urgency, photos and preferred time, and the owner receives a Job Brief by SMS and email with a one-tap call button, booking link and suggested price range.

Differentiation · Not a voicemail box, not a staffed answering service, not a CRM: one artifact, the Job Brief, delivered in under two minutes, priced below a single recovered job.

1. Product opportunity and positioning

A one-person plumbing, electrical or roofing shop lives on its phone, and the phone rings while its owner is under a sink, on a roof or elbow-deep in a panel. The caller is not patient. They dial the next name on Google. What replaces the missed call today is a voicemail with no address, no job type, no urgency and no photo, so the callback turns into three rounds of phone tag the owner never has time to run.

JobPing Rescue sells the moment of the missed call, not a platform. A forwarding rule sends unanswered calls to a JobPing number. Ten seconds later the caller gets a text: "Sorry we missed you - what's the job?" An SMS conversation collects job type, ZIP, urgency, photos and preferred time. The owner receives a Job Brief, one screen, by text and email, with a one-tap call button, a booking link and a suggested price range.

The buyer is the owner-operator of a 1-5 person home-service business in the US, Canada, UK or Australia who has just paid for a lead or has just missed a homeowner's call. Price sits below one recovered job. Setup is a forwarding rule, five minutes of work, not a procurement project. There is no IT department, no security review and no integration ask.

Positioning against the alternatives: a voicemail box stores the loss; a staffed answering service costs more per month and still cannot quote; a CRM assumes the owner already has the caller's details. JobPing's only output is the artifact the owner actually needs at 7:42pm, a quote-ready job.

The JEV score of 67.9 (band B) is carried by speed to first revenue (8.34) and solo build feasibility (7.58). The weak leg is operational simplicity (4.28), so this plan deliberately keeps the system stateless on managed services, stores no regulated data, removes human review steps and ships nothing that needs a support rota. Compliance surface is limited to STOP handling and a do-not-call flag.

The wedge is deliberately narrow: one buyer, one trigger event (a missed call), one output artifact (the Job Brief), two prices, one acquisition motion. Every hour not spent on that is an hour not spent collecting revenue inside the 30-day window.

Section 2 of 8

Smallest sellable MVP

A jobping.app account where the owner forwards their unanswered calls to a provisioned number and receives a Job Brief by SMS and email within two minutes of a missed call, billed by Stripe.

Must-have features

  • Twilio number provisioning with call-forward-on-no-answer and a 10-second auto text-back
  • AI SMS qualification flow extracting job type, ZIP, urgency, photos and preferred time
  • Job Brief rendered three ways: SMS summary, Resend email, shareable /b/[id] page
  • One-tap call button, booking link and suggested price band inside the brief
  • Owner dashboard listing recovered calls, briefs and marked-won jobs
  • Five-minute forwarding wizard with carrier-specific steps
  • Stripe Checkout for $99 and $199 monthly, self-serve cancel
  • STOP keyword handling and a per-account do-not-call flag

Explicitly out of scope

  • No outbound cold-calling or lead-list dialing
  • No CRM, invoicing or dispatch scheduling
  • No human answering service or staffed 24/7 support
  • No mobile app, no multi-language, no franchise accounts
  • No voice AI in the $99 tier, and no voice at all until day 18
  • No marketplace or third-party app-store listing

Demo flow (what the buyer sees)

  1. Founder calls the JobPing number and hangs up at the voicemail prompt
  2. Caller handset receives 'Sorry we missed you - what's the job?' in about 10 seconds
  3. Caller answers job type, ZIP, urgency and preferred time over four SMS turns and texts one photo
  4. Structured record is written to Supabase with all fields populated
  5. Job Brief is delivered to the owner by SMS and email with call button, booking link and price band
  6. Shareable /b/[id] page opens in a browser and shows the same brief
Build plan

Technical implementation plan

Stack

Twilio Programmable Voice and SMS (US local numbers plus toll-free)Next.js 15 on Vercel with route handlers as webhooksSupabase Postgres for accounts, jobs and briefsOpenAI API with function calling for SMS qualification and brief summarizationStripe Checkout and Billing PortalResend for Job Brief emailCal.com booking linksUpstash Redis for simple per-account rate limits

Architecture

Each customer gets a Twilio number. Twilio's voice webhook points at /api/voice, which records the call as missed when no answer occurs and immediately enqueues the opening SMS. Twilio's SMS webhook points at /api/sms, which loads the job thread from Supabase, calls OpenAI with a JSON schema for the missing fields, saves new values and returns the next question. When all required fields are present or the sixth message arrives, the Job Brief service renders the SMS summary, the Resend email and the /b/[id] page from the same record. Stripe Checkout creates the account and provisions the number via a Twilio API call in the same webhook.

Build steps

  1. Create Twilio, Stripe, Supabase, Vercel, Resend and OpenAI accounts; connect Stripe to TrustMRR; buy five numbers and submit toll-free verification
  2. Deploy a Next.js skeleton and point the Twilio voice and SMS webhooks at it
  3. Implement the missed-call detector and the 10-second text-back with the caller's timestamp
  4. Define the Supabase schema: accounts, numbers, jobs, messages, briefs, won_at
  5. Build the OpenAI qualification call with a strict JSON schema and a six-message cap
  6. Build the Job Brief renderer for SMS, Resend email and the shareable page
  7. Add the forwarding wizard with carrier steps for Verizon, AT&T, T-Mobile and major VoIP providers
  8. Wire Stripe Checkout, the Billing Portal and number provisioning into the checkout webhook
  9. Add STOP handling, a do-not-call flag and per-account SMS caps
  10. Run ten real missed calls end to end and fix every failure before any outreach

AI components

  • OpenAI function calling to extract job type, ZIP, urgency, preferred time and contact name from free-text SMS replies
  • OpenAI summarization to write the one-paragraph Job Brief and a suggested price band from job type plus urgency
  • Short follow-up phrasing generation so the flow does not read as a scripted bot
Hardest technical risk: Toll-free or A2P 10DLC verification not clearing before outreach starts, which blocks the text-back that the entire product depends on.
Section 3 of 8

Pricing and monetization

Text-Back

Entry offer
$99 / month

For Solo operators who mainly want the caller acknowledged fast

  • Instant missed-call text-back within 10 seconds
  • AI SMS qualification into structured fields
  • Job Brief by SMS and email
  • Booking link in the brief
  • Self-serve onboarding

Text-Back + Voice

$199 / month

For Shops with real after-hours and weekend call volume

  • Everything in Text-Back
  • AI voice answer for after-hours calls with the same brief
  • Weekly recovered-revenue email
  • Photo and ZIP collection in the brief
  • Priority setup help

Model: Two flat monthly subscriptions, self-serve via Stripe, no setup fee and no usage metering inside fair-use SMS caps.

First revenue offer: First 10 shops get month one of Text-Back + Voice at $99 instead of $199, live in 5 minutes on a 10-minute screen-share, cancel anytime - sent as a two-line SMS quoting their own missed-call timestamp and a sample Job Brief.

Expected ACV: $135

Upsell path: Move $99 Text-Back accounts to $199 once a shop logs three or more after-hours calls in a month, then add a second number for a second crew at $99.

Target customers
50
Revenue model
$9,950
Costs
$280
Profit model
$9,670
Section 4 of 8

First-customer acquisition

Primary channel

The missed-call audit: call solo home-service businesses from Google Maps after 6pm, log who hits voicemail, then send each one the exact timestamp of their own missed call plus a sample Job Brief.

Where to find them

  • Google Maps listings for plumbers, electricians, roofers and garage-door techs in three metros, one of them the founder's home city
  • Local Services Ads and Google Ads results for 'emergency plumber [city]', which reveal who is paying for calls
  • Trade Facebook groups for plumbers and electricians, where owners post about missed calls and slow seasons
  • Supply houses and trade counters the founder can visit in person in week three
  • Nextdoor and local Facebook community groups where homeowners recommend solo trades

Exact outreach motions

  • Call 40 listings after 6pm and log every number that reaches voicemail, plus the exact local time
  • Text each voicemail number: 'I called your shop at 7:42pm and got voicemail - here's the Job Brief your caller would have sent you' plus a sample link
  • Email the same list 24 hours later with the missed-call timestamp in the subject line and a 40-second screen recording of the brief
  • Follow up at 48 hours with the arithmetic of one missed $450 job against a $199 month
  • Offer a 10-minute screen-share where the founder sets up forwarding live and triggers a real test call
  • Ask each paying shop for one introduction inside their trade group or at the supply counter

Message template

Hi [Name] - I called [Business] at 7:42pm tonight and got voicemail instead of you. That caller just dialled the next plumber on Google. Here's the Job Brief you'd have had 60 seconds later: [link]. Want me to switch it on for your line this week? First 10 shops get month one at $99.
Week-one goal: 300 businesses listed with phone and city, 80 after-hours calls logged, and 80 audit messages sent with at least 8 replies.
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 1Accounts

Unblock SMS and payments on day one

  • Open Twilio, Stripe (connected to TrustMRR), Supabase, Vercel, Resend and OpenAI accounts.
  • Buy five US local numbers and submit toll-free verification for SMS.
  • Scaffold the Next.js repo and deploy an empty app to Vercel.

Deliverable: Live accounts, five numbers and a deploying skeleton app.

Day 2Call capture

Missed call in, text out

  • Point each number's voice webhook at /api/voice.
  • Fire the 10-second text-back on no-answer or busy, stamping the local time.
  • Write accounts, numbers and jobs tables in Supabase.

Deliverable: A real missed call produces an SMS within 10 seconds.

Day 3Qualification

Turn SMS into structured fields

  • Build the AI SMS state machine asking job type, ZIP, urgency and preferred time.
  • Use OpenAI function calling to write each field as the thread progresses.
  • Add the six-message cap plus STOP and do-not-call handling.

Deliverable: A test caller finishes a thread and produces a complete JSON job record.

Day 4Brief and billing

Deliver the artifact, take the money

  • Render the Job Brief as SMS, Resend email and a public /b/[id] page.
  • Add the one-tap call button, Cal.com link and a price band by job type.
  • Wire Stripe Checkout for $99 and $199 with self-serve cancellation.

Deliverable: Stripe test checkout provisions an account with a working number.

Day 5MVP gateMVP shipped

Ship and stop building

  • Build the forwarding wizard with Verizon, AT&T, T-Mobile and VoIP steps.
  • Run ten end-to-end missed calls on the founder's own phone.
  • Freeze scope: no new features until the first payment clears.

Deliverable: Public signup live; MVP shipped on day 5.

Day 6List

Build the audit list

  • Collect 300 solo trades across three metros from Google Maps: name, phone, website, city.
  • Tag the 60 who are running Local Services Ads or Google Ads.
  • Draft the audit SMS and email and the sample Job Brief link.

Deliverable: A 300-row spreadsheet with 60 paid-lead prospects tagged.

Day 7Audit

Prove the pain with their own evidence

  • Call 40 listings after 6pm and log every voicemail with the exact time.
  • Call 20 more at midday to catch the on-tools gap.
  • Send the first 25 audit messages with their own timestamp and the sample brief.

Deliverable: 60 logged missed calls and 25 audit messages sent.

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

Volume on the audit motion

  • Call and log 60 more numbers, staggered across lunch and after 6pm.
  • Send 60 audit messages using the exact missed-call timestamp.
  • Reply to every response within 15 minutes during business hours.

Deliverable: 85 audit messages out, first replies in hand.

Day 9Follow-up

Convert repliers into screen-shares

  • Send the 48-hour follow-up with the one-job-versus-one-month arithmetic.
  • Book screen-shares for five interested owners.
  • Fix any onboarding step that blocks a live test call.

Deliverable: Five booked setup calls and a fixed onboarding funnel.

Day 10Setups

Run live setups on the call

  • Run the booked screen-shares and set up forwarding live.
  • Trigger a real test call on every new account during the call.
  • Send each owner their first real Job Brief within an hour of setup.

Deliverable: Three to five accounts forwarding calls to JobPing.

Day 11Close

Turn trials into payments

  • Ask every live account for the card and the $99 launch price.
  • Send the Stripe link while still on the call, never after.
  • Follow up with the remaining audit repliers who went quiet.

Deliverable: First Stripe payment received.

Day 12First saleFirst sale target

Lock the first paying shop

  • Close the first paying customer and confirm money landed in Stripe.
  • Verify the payment is visible in TrustMRR and the number is live.
  • Log the exact message and call that produced the sale.

Deliverable: FirstSale: one paying shop inside the hackathon window.

Day 13Delivery

Make the first account undeniably work

  • Review every brief from the first account by hand and fix errors.
  • Call the owner and walk through their recovered jobs.
  • Add the missed-call counter to the dashboard.

Deliverable: First account producing clean briefs daily.

Day 14Review

Double down on what converted

  • Measure reply rate, setup-completion rate and close rate from week two.
  • Rewrite the audit message using the phrasing that got replies.
  • Cut any feature that did not appear in a closing conversation.

Deliverable: A one-page funnel table with real week-two numbers.

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

Scale the audit to 300 businesses

  • Log the remaining 180 calls across the three metros.
  • Send 100 audit messages on the proven template.
  • Run a second wave of follow-ups at 48 hours.

Deliverable: All 300 businesses audited and messaged.

Day 16Second metro

Prove the motion travels

  • Repeat the audit in a metro the founder has never visited.
  • Compare reply rates between metros before adding a third.
  • Collect three more setup calls from the new metro.

Deliverable: Second-metro reply rate measured.

Day 17Referrals

Get introduced inside the trade

  • Ask each paying shop for one introduction in their trade group.
  • Post the missed-call math into two plumber or electrician Facebook groups.
  • Offer the $99 launch price only for introductions that convert.

Deliverable: Three introductions and two group posts live.

Day 18Voice tier

Ship the $199 upgrade

  • Add AI voice answering for after-hours calls using the same brief pipeline.
  • Keep the $99 tier text-only so the upgrade has a reason to exist.
  • Test ten after-hours calls on the founder's own number.

Deliverable: Text-Back + Voice live and billable at $199.

Day 19Upgrades

Move $99 accounts to $199

  • Pull every account with three or more after-hours calls in a week.
  • Send each one their own after-hours call count and the upgrade link.
  • Close at least one upgrade.

Deliverable: First $199 upgrade billed.

Day 20Onboarding

Remove the forwarding drop-off

  • Measure how many signups complete forwarding within 24 hours.
  • Add a founder-managed setup option for anyone who stalls.
  • Ship the carrier detection step so steps match the owner's provider.

Deliverable: Onboarding completion rate above 60%.

Day 21Review

Decide the week-four push

  • Recount customers, MRR and TrustMRR-visible payments.
  • Kill the weakest outreach angle and keep the best one.
  • Set the week-four target number explicitly.

Deliverable: Week-three scorecard and a week-four target.

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

Run the proven script daily

  • Audit 40 new numbers before 9am and after 6pm.
  • Send 40 audit messages and all 48-hour follow-ups.
  • Book every replier into a screen-share slot the same week.

Deliverable: Daily audit cadence locked at 40 calls and 40 messages.

Day 23Proof

Turn recovered jobs into evidence

  • Ask two paying shops for permission to quote a recovered job anonymously.
  • Add a recovered-jobs count and value estimate to the weekly email.
  • Send the weekly recovered-revenue email to every account.

Deliverable: Two permissioned proof points and one weekly email sent.

Day 24Retention

Make month two obvious

  • Review each account's brief volume and flag any with no activity.
  • Call the flagged accounts and fix their forwarding.
  • Add a one-click 'mark won' so recovered value is recorded.

Deliverable: Zero accounts with broken forwarding.

Day 25Outreach

Second offer wave

  • Send a shorter audit message to the non-repliers with a fresh timestamp.
  • Call the supply-house contacts the founder can reach in person.
  • Close any warm replier who has gone quiet twice.

Deliverable: 20 fresh replies and 2 new setups booked.

Day 26Close

Push to the target customer count

  • Close every outstanding setup call before the weekend.
  • Take payment on the call via Stripe Checkout.
  • Confirm each new payment appears in TrustMRR.

Deliverable: Customer count at or above the base case pace.

Day 27Quality

Protect against refunds

  • Read 30 briefs for extraction errors and tighten the schema prompt.
  • Check the six-message cap is not cutting off good leads.
  • Verify STOP handling works on a live test number.

Deliverable: Brief accuracy spot-checked at 30 samples.

Day 28Referrals

Second-degree reach

  • Collect every introduction promised so far.
  • Message each introduction with their referrer's shop name.
  • Ask two shops to post the recovered-job screenshot in their trade group.

Deliverable: Five warm introductions messaged.

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

Last calls and closes

  • Audit and message 50 more numbers with a hard 24-hour offer.
  • Close any pending screen-share the same day.
  • Reconcile every payment against TrustMRR before the deadline.

Deliverable: All payments reconciled and visible.

Day 30Wrap

Lock the number and the next 30 days

  • Take the final count of paying shops, MRR and verified profit inputs.
  • Send every customer their week-one recovered-jobs summary.
  • Publish the honest scorecard and the week-five to week-eight plan.

Deliverable: Final hackathon scorecard and a retention plan for month two.

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

  • Blended ARPU of $135 assumes a 60/40 mix between the $99 Text-Back plan and the $199 Text-Back + Voice plan (Base).
  • Conservative: 4 paying shops by day 30 from roughly 300 audited businesses, below the stated 15% reply and 10% close hypotheses.
  • Base: 12 paying shops, consistent with 15% reply, 10% close and one upgrade to $199.
  • Upside: 26 paying shops driven by two trade Facebook groups, the $99 launch offer and supply-counter introductions.
  • Payment fees assume Stripe at 2.9% plus $0.30 on one monthly charge per customer, about 3.1% effective on a $135 average charge.
  • Ad spend is zero in Conservative and Base because the acquisition channel is organic missed-call audits; Upside carries $250 of paid trade-newsletter and Facebook group placements.
  • Operating cost per customer is roughly $6-9 per month: Twilio numbers at about $1.15 each, SMS near $0.008 per segment, one OpenAI qualification thread per recovered call, Resend and Vercel.
  • Refunds are zero in Conservative and Base because the plan is cancel-anytime with no refund promise; Upside carries one refunded month.
  • Chargebacks are zero in all three scenarios and are treated as an unmodelled risk.
  • No customer pays before launch; all counted revenue is received between 16 November and 16 December 2026.
  • Every sale is priced above delivery cost, so no scenario sells below cost.

Conservative

4 customers
$540
collected revenue · avg payment $135
Refunds
$0
Chargebacks
$0
Payment fees
$17
Paid marketing
$0
Hackathon profit
$523
Operating costs
$40
Business profit
$483

Base case

12 customers
$1,620
collected revenue · avg payment $135
Refunds
$0
Chargebacks
$0
Payment fees
$51
Paid marketing
$0
Hackathon profit
$1,569
Operating costs
$95
Business profit
$1,474

Optimistic

26 customers
$3,510
collected revenue · avg payment $135
Refunds
$199
Chargebacks
$0
Payment fees
$110
Paid marketing
$250
Hackathon profit
$2,951
Operating costs
$220
Business profit
$2,731

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,188
Payment fees (3.9%)
$46
Paid marketing
$0
Hackathon profit
$1,142
Business profit
$1,047

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.

All figures are projections built from stated assumptions, not verified revenue, customers or traction. Hackathon profit is gross revenue minus refunds, chargebacks, payment fees and ad spend; business profit additionally subtracts operating costs.

Section 7 of 8

Main risks and validation experiments

Risk 1Toll-free or A2P 10DLC verification does not clear, so the text-back that the whole product depends on never fires.

Mitigation

Submit verification on day 1 before writing any product code, buy toll-free numbers because they verify faster, and keep a voice-only fallback number ready.

Validation experiment

Submit registration on day 1 and check approval status every morning; test a live text-back on day 3 with a real handset.

Kill criteria

If no SMS can be delivered to US handsets by day 6, switch the brief to email plus a voice message and re-scope before any outreach.

Risk 2Cold SMS and email from an unknown number get ignored, so reply rates land far below the 15% hypothesis.

Mitigation

Always quote the prospect's own missed-call timestamp, link a sample Job Brief built from a real call, and add an email with a screen recording as a second channel.

Validation experiment

Send 40 audits on day 8 and count replies within 48 hours; send 60 more on day 9 with the follow-up template.

Kill criteria

If fewer than 5 replies come from 100 audit messages, rewrite the message once; if it still fails at 200, change the channel.

Risk 3Call forwarding setup friction means trials stall before the first real recovered call.

Mitigation

Build carrier-specific wizard steps, offer a 10-minute screen-share, and let the founder set forwarding on the customer's behalf during the call.

Validation experiment

Track what percentage of signups complete forwarding within 24 hours across the first 15 accounts.

Kill criteria

If under 50% complete forwarding within 24 hours, replace the wizard with founder-managed setup and a number-swap model.

Risk 4Owners already pay a human answering service and see JobPing as redundant.

Mitigation

Position only as the after-hours and on-tools overflow that produces a written brief, not as a replacement for their daytime receptionist.

Validation experiment

Ask every audit replier whether they use an answering service and what it costs them per month.

Kill criteria

If more than half of repliers already have a service and refuse to run both, narrow to shops with no existing service.

Risk 5Churn after month one because the owner cannot see recovered revenue.

Mitigation

Ship the weekly recovered-revenue email and the mark-won button before day 25 so value is visible without the owner doing work.

Validation experiment

Count how many accounts mark at least one job won in their first 21 days.

Kill criteria

If fewer than 40% of accounts record a won job by day 30, the brief is not converting and the pricing or qualification flow must change.

Risk 6Twilio and OpenAI costs spike on an unusually high-volume account and a sale ends up below cost.

Mitigation

Cap the SMS qualification at six messages per call, add per-account monthly SMS limits and a fair-use clause in the plan description.

Validation experiment

Log per-account message and call counts daily and compute delivery cost per customer every Friday.

Kill criteria

If any account's monthly delivery cost exceeds $20, cap the plan and re-price before taking more customers.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create Twilio, Stripe (connected to TrustMRR), Supabase, Vercel, Resend and OpenAI accounts.
  • Confirm no customers or payments exist anywhere before launch.
  • Write the one-line scope freeze: text-back, brief, booking link, Stripe.

Output: Live accounts and a written scope freeze.

Hours 3-5

  • Buy five US local numbers and submit toll-free verification.
  • Scaffold the Next.js repo and deploy an empty app to Vercel.
  • Create the Supabase project and push the initial schema.

Output: Five provisioned numbers, a deploying app and a schema.

Hours 6-9

  • Build the /api/voice webhook with the no-answer detector.
  • Fire the 10-second text-back with the caller's local timestamp.
  • Test with the founder's own phone on a live number.

Output: A real missed call producing an SMS in under 15 seconds.

Hours 10-14

  • Build the AI SMS qualification call with a strict JSON schema.
  • Store extracted fields on the job record after every turn.
  • Add the six-message cap and STOP handling.

Output: A completed test thread writing a full job record.

Hours 15-19

  • Render the Job Brief as SMS, Resend email and the /b/[id] page.
  • Add the one-tap call button, Cal.com link and price band.
  • Wire Stripe Checkout for $99 and $199 in test mode.

Output: End-to-end brief delivered and a working test checkout.

Hours 20-24

  • Build a 40-row Google Maps list of local plumbers and electricians.
  • Call 12 of them after 6pm and log every voicemail with the exact time.
  • Draft the audit SMS and the sample Job Brief link.

Output: 40-row prospect list, 12 logged missed calls and the audit message ready to send.

Complete report

Full 30-day launch report

Read the full generated report

JobPing Rescue: build, launch and collect in 30 days

1. Product opportunity and positioning

A one-person plumbing, electrical or roofing shop lives on its phone, and the phone rings while the owner is under a sink, on a roof or inside a panel. The caller is not patient; they dial the next name on Google. What replaces the missed call today is a voicemail with no address, no job type, no urgency and no photo, so the callback becomes three rounds of phone tag the owner never has time to run.

JobPing Rescue sells the moment of the missed call, not a platform. A forwarding rule sends unanswered calls to a JobPing number. Ten seconds later the caller gets a text: "Sorry we missed you - what's the job?" An SMS conversation collects job type, ZIP, urgency, photos and preferred time. The owner receives a Job Brief, one screen, by text and email, with a one-tap call button, a booking link and a suggested price range.

The buyer is the owner-operator of a 1-5 person home-service business in the US, Canada, UK or Australia who has just paid for a lead or just missed a homeowner's call. Price sits below one recovered job. Setup is a forwarding rule, five minutes of work, not a procurement project. There is no IT department, no security review and no integration ask.

Against the alternatives: a voicemail box stores the loss; a staffed answering service costs more per month and still cannot quote; a CRM assumes the owner already has the caller's details. JobPing's only output is the artifact the owner actually needs at 7:42pm, a quote-ready job.

The JEV score of 67.9 (band B) is carried by speed to first revenue (8.34) and solo build feasibility (7.58). The weak leg is operational simplicity (4.28), so this plan keeps the system stateless on managed services, stores no regulated data, removes human review steps and ships nothing that needs a support rota. Compliance surface is limited to STOP handling and a do-not-call flag.

2. Smallest sellable MVP

One number, one forwarding rule, one brief, one Stripe price. The sellable unit is an account where unanswered calls go to a JobPing number and a Job Brief arrives by SMS and email within two minutes, containing job type, ZIP, urgency, photo, preferred time, a call button, a booking link and a price band. Everything else, including the dashboard, exists only to make that artifact believable and to prove recovery later.

The build is four days: call capture on day 2, SMS qualification on day 3, brief and billing on day 4, forwarding wizard on day 5. Voice AI is deliberately held back to day 18 so the $199 upgrade has a reason to exist and day-5 launch is not delayed.

3. Technical implementation plan

Twilio carries voice and SMS; Next.js on Vercel hosts two webhooks; Supabase holds accounts, numbers, jobs, messages and briefs; OpenAI extracts fields with function calling; Resend sends the email; Cal.com supplies the booking link; Stripe Checkout provisions accounts.

The qualification prompt is the product. It gets a strict JSON schema, a six-message cap and an explicit instruction to ask one question per turn. When required fields are complete, or the cap is hit, the brief service renders three outputs from one record, which keeps SMS, email and the shareable page permanently in sync.

The hardest technical risk is not code. It is toll-free or A2P 10DLC verification. Submit it in hour three of day 1, before any feature work, because a blocked SMS channel turns the product into nothing.

4. Pricing and monetization

Two flat monthly plans. Text-Back at $99 covers the instant text-back, AI qualification, the brief and the booking link. Text-Back + Voice at $199 adds after-hours AI voice answering, photo and ZIP collection and a weekly recovered-revenue email. Both are self-serve through Stripe with no setup fee and no usage metering inside fair-use caps.

The launch offer is deliberately simple: the first 10 shops get month one of the $199 plan at $99. Blended ARPU in the scenarios is $135, assuming a 60/40 split. The upgrade path is mechanical: any $99 account logging three or more after-hours calls in a month gets its own call count and a $199 link. A second crew means a second number at $99.

5. First-customer acquisition

The only channel is the missed-call audit. Call 300 solo trades from Google Maps in three metros, staggered across midday and after 6pm, and log every number that reaches voicemail with the exact local time. Then send each one their own timestamp and a sample Job Brief: "I called your shop at 7:42pm and got voicemail. Here is the brief your caller would have sent you."

This works because the founder is not claiming a problem, he is showing the prospect a recording of their own lost job. A 48-hour follow-up adds the arithmetic: one missed $450 job against a $199 month. Everything closes on a 10-minute screen-share where forwarding is set live and a real test call is triggered on the call. Each paying shop is asked for one introduction inside their trade group or at the supply counter.

6. 30-day execution roadmap

Days 1-5 are build and they end at a hard gate: signup live, ten end-to-end test calls passed, scope frozen. Day 1 is spent on accounts and SMS verification before any product code, because verification is the schedule risk.

Days 6-11 are the audit engine: a 300-row list, 120 after-hours calls logged, 85 audit messages out, five booked screen-shares, live setups on the call. Day 12 is the first-sale target, with the card taken during the screen-share rather than emailed afterwards.

Days 13-21 turn one customer into proof. Brief quality is hand-checked, reply and setup-completion rates are measured, the audit message is rewritten around the phrasing that actually got replies, the list is extended to all 300, a second metro is tested and referrals start. Day 18 ships the $199 voice tier; day 19 sells the first upgrade.

Days 22-28 run the proven script at 40 calls and 40 audit messages a day, add permissioned proof points, fix any broken forwarding and push onboarding completion above 60%. Days 29-30 reconcile every payment against TrustMRR and publish an honest scorecard.

7. Revenue and profit scenarios

These are projections, not traction. Conservative: 4 customers at a $135 blended ARPU, $540 gross, $17 in Stripe fees, no ad spend, $40 operating cost. Base: 12 customers, $1,620 gross, $51 fees, $95 operating cost. Upside: 26 customers, $3,510 gross, one $199 refund, $110 fees, $250 of paid placements and $220 operating cost.

Hackathon profit deducts refunds, chargebacks, payment fees and ad spend only; business profit additionally deducts hosting, numbers, SMS and inference. At $6-9 of delivery cost per customer per month against a $99 floor, no sale is below cost.

8. Main risks and validation experiments

SMS verification delay is the top risk and is mitigated by submitting on day 1 with a voice-only fallback. Cold outreach reply rate is tested at 40 messages on day 8 with a rewrite trigger at 100. Forwarding friction is measured by 24-hour completion rate, with a founder-managed setup fallback below 50%. Redundancy against answering services is tested by asking directly in every reply. Churn is tested by counting how many accounts mark a won job in 21 days. Cost blowout is capped by six messages per call and per-account SMS limits.

9. First 24-hour action plan

Hours 1-2: accounts and scope freeze. Hours 3-5: buy numbers, submit toll-free verification, deploy the skeleton. Hours 6-9: voice webhook and the 10-second text-back, tested on a real handset. Hours 10-14: OpenAI qualification and the job record. Hours 15-19: Job Brief in three formats plus Stripe test checkout. Hours 20-24: a 40-row prospect list, 12 logged missed calls after 6pm and the audit message drafted and ready to send.

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 →