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

SlotBack Text Rescue

A text-only agent that messages a clinic's waitlist the moment a slot cancels and books the first reply, filling the chair within the hour.

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.30/10
MVP build (solo)
4 days
Launch price
$99 · monthly
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach to clinics found via public online-booking pages that show same-day availability.
Who pays

Office manager or owner at a 2-10 staff dental, medspa or physio clinic that already uses online booking and keeps a waitlist.

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.2/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

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

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

Product opportunity and positioning

Target customer

Office manager or owner at a 2-10 staff dental, medspa or physio clinic that already uses online booking and keeps a waitlist.

Why now

Every clinic already has SMS on the front desk phone and a waitlist in a notebook or PMS note; the tool needs no integration, so the first rescue can happen in the same conversation as the sales pitch.

Problem

A patient cancels, staff are too busy at the front desk to call the waitlist, and the slot goes empty.

Solution

The office manager pastes the cancelled slot and waitlist phone numbers into one form; SlotBack texts the waitlist in priority order, parses replies, locks the first accept, and returns a confirmed booking link plus a filled-slot log.

Differentiation · An AI receptionist asks the clinic to change phone routing and trust a voice bot; SlotBack only touches the one moment money is already leaking and leaves every other workflow untouched.

SlotBack Text Rescue — 30-day solo launch report

Concept version 1. JEV score 63/100 (band C, confidence 0.72). Every revenue figure in this report is a projection, not verified revenue.

1. Product opportunity and positioning

A cancellation is a perishable asset. In a 2-10 staff dental, medspa or physio clinic the office manager knows the 2pm slot just opened, knows five waitlisted patients would take it, and has a check-in queue, a ringing phone and a hygienist waiting in front of her. She does not make the calls. The chair sits empty and the clinic eats the appointment value.

SlotBack Text Rescue does one thing: it turns a pasted cancellation into a text blast to the clinic's waitlist, in priority order, and books the first person who says yes. The office manager pastes the slot time, the value and the waitlist numbers into one form, hits send, and gets back a confirmed booking link plus a log line: slot filled, 14 minutes, estimated $180 recovered.

Positioning: faster than manual calling because it fires in seconds and never forgets; lighter than an AI receptionist because there is no phone routing, no PMS integration and no trust barrier. The buyer is not replacing software — she is buying back a chair this afternoon. That is why $99 can be approved by the person who feels the loss.

JEV flags two weaknesses: market demand (4.8/10) and operational simplicity (4.26/10). Both point the same direction — the product must be demonstrable in the first conversation, and every manual step (waitlist entry, opt-in status, reply ambiguity) must be solved before the clinic's second rescue.

2. Smallest sellable MVP

A logged-in page with three parts: a slot form (clinic, date, time, appointment value, waitlist numbers in priority order), a send button that fires ordered SMS via Twilio and stops at the first accept, and a dashboard that lists filled slots with an estimated recovered-revenue figure. Stripe checkout at $99/month sits behind it. No integration, no voice, no CRM. Four build days, launched on day 5.

The value proof is the log, not the feature list. A clinic that sees three filled slots in week one at $99 has an obvious arithmetic argument to keep paying.

3. Technical implementation plan

Next.js on Vercel for the app and marketing page, Supabase for clinics, slots, blasts, messages and reply state, Twilio for outbound and inbound SMS, OpenAI for parsing free-text replies into accept, decline or question, Stripe for the subscription. All managed services, no servers, no stateful workers beyond a scheduled poll.

The hard part is the reply race: two patients can answer within seconds, so the first valid accept must atomically lock the slot and the remaining recipients must receive a short "slot taken, you're first on the next one" message. Build that lock before anything cosmetic. The second risk is SMS compliance — start A2P 10DLC registration on day 2 and keep every message to one segment with an opt-out keyword. AI is used only for intent classification of inbound replies; it never composes prices or clinical content.

4. Pricing and monetization

One plan: Clinic Starter, $99 per month, unlimited slot rescues, unlimited SMS blasts, filled-slot dashboard, email support. The opening offer is $49 for the first month, then $99, no contract. Anchor every pitch against one saved appointment, not against software budgets. Growth after month three comes from annual prepay and a per-extra-location add-on, never from a new tier that muddies the pitch.

5. First-customer acquisition

One channel: direct outreach to clinics found through public online-booking pages that show same-day availability — the visible signal that chairs are going unfilled. Build a list of 150 clinics from local dental, medspa and physio booking pages, capture the office manager email or the practice Instagram, and send a 90-word email with a 60-second Loom of a simulated rescue for their city. No ads, no SEO, no partnerships. Follow up once on day 3 with a recovered-revenue example, then move on. The week-one goal is 30 sends and 3 booked conversations; the first paid customer target is day 12.

6. 30-day execution roadmap

Days 1-4 are build: repo, schema, Stripe, slot form, Twilio blast, reply parser with first-reply-wins locking, dashboard, booking link. Day 5 is launch — the MVP deadline — with live Stripe keys, opt-out language and a public page.

Days 6-11 are list-building and outreach: 150 clinics sourced from public booking pages, a 60-second Loom, 30 emails on day 8, 30 more plus Instagram DMs on day 9, follow-ups and free single-rescue trials on day 10, live screen-share onboarding on day 11.

Day 12 is the first-sale target: close the $49 first month, then deliver that rescue end-to-end personally and write the runbook from what actually broke.

Days 15-21 convert the manual process into a self-serve one: Stripe checkout plus magic-link signup so a clinic can onboard without the founder, tougher reply edge cases ("maybe", "what time", "can I bring my kid"), priority-ordering UI, and a follow-up pass over every non-responder. Day 21 is the channel decision: if outreach volume is producing conversations, double it; if not, change the message, not the product.

Days 22-30 are volume and retention: 50 outreach emails per day, referral asks, onboarding cut under six minutes, opt-out audit, reactivation of trial clinics, and a final push on day 29. Day 30 closes payments before the 13:00 UTC cutoff on December 16 and exports the revenue log for verification.

7. Revenue and profit scenarios (projections only)

Conservative: 3 clinics × $99 = $297 gross. Base: 10 × $99 = $990. Upside: 25 × $99 = $2,475 with $150 of paid boosts layered on top of organic outreach. Payment processing assumed at roughly 4% via Stripe; operating costs run $25-$90 across Vercel, Supabase, Twilio and OpenAI for that many clinics.

Two different numbers matter. Hackathon profit subtracts refunds, chargebacks, processing fees and paid marketing only. Business profit additionally subtracts hosting, tooling and SMS delivery cost. At base case the contest-relevant figure is near $951 and the business figure near $906. These are projections built from stated assumptions; no customer, revenue or traction is claimed.

8. Main risks and validation experiments

First, clinics refuse to type waitlist numbers by hand. Test by asking five office managers to paste a real waitlist during a screen share and timing it; if it takes more than four minutes, add a CSV paste and a "reuse last waitlist" button before scaling outreach.

Second, SMS compliance and opt-in. Test by registering A2P 10DLC on day 2 and sending a live blast to the founder's phone plus one friendly clinic; if messages are filtered or delayed, fall back to a clinic-owned Twilio number flow before selling.

Third, low reply rates destroy the ROI story. Test by running three free rescues in week two and measuring reply rate and time-to-first-accept; if fewer than one in six recipients replies, rewrite the message copy and add a decaying discount line.

Fourth, Twilio cost per rescue exceeds the $99 plan. Test by measuring segments per rescue for ten rescues; if cost per clinic passes $12/month, cap blasts per slot at the 25 highest-priority numbers.

9. First 24-hour action plan

Hours 0-2: register the domain, deploy the Next.js skeleton to Vercel, publish the landing page with the $99 offer. Hours 2-5: create the Supabase schema and connect Stripe with TrustMRR from the start. Hours 5-8: open Twilio, start A2P 10DLC, send the first test SMS to your own phone. Hours 8-12: build the slot form and ordered blast. Hours 12-18: build the inbound webhook and first-reply-wins lock, testing with two phones. Hours 18-24: write the 150-clinic list from public booking pages and draft the outreach template. The output by hour 24 is a deployed page, a working SMS round trip and a list ready to send.

Section 2 of 8

Smallest sellable MVP

A logged-in web form that texts a pasted waitlist in priority order, locks the first accepting reply, returns a confirmed booking link and logs the filled slot — with Stripe checkout at $99/month attached.

Must-have features

  • Clinic signup with magic-link login
  • Slot form: date, time, appointment value, waitlist numbers in priority order
  • Ordered Twilio SMS blast with per-recipient status
  • First-reply-wins atomic lock that stops remaining texts
  • AI reply classifier: accept, decline, question
  • Confirmed booking link returned to the office manager
  • Filled-slot dashboard with estimated recovered revenue
  • Stripe checkout for the $99 monthly plan
  • Opt-out keyword handling on every message
  • CSV paste and reuse-last-waitlist for repeat rescues

Explicitly out of scope

  • No PMS or calendar integration
  • No voice calls or AI receptionist
  • No patient CRM or marketing automation
  • No multi-location enterprise features
  • No mobile app
  • No insurance or clinical data storage

Demo flow (what the buyer sees)

  1. Office manager pastes slot time, value and 8 waitlist numbers
  2. SlotBack sends ordered SMS with a one-tap booking link
  3. Replies land in the dashboard; classifier tags accept, decline or question
  4. First accept locks the slot; other recipients get a short 'slot taken' text
  5. Office manager sees the confirmed booking link and the slot value
  6. Dashboard logs the rescue: 14 minutes, estimated $180 recovered
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase (Postgres + auth)Twilio Programmable SMSOpenAI for reply intent classificationStripe subscriptionsResend for transactional emailVercel cron for stuck-blast sweeps

Architecture

The Next.js app writes a slot and an ordered recipient list to Supabase, then calls a server route that sends Twilio messages one recipient at a time and records each message row. Twilio inbound webhooks hit a second route that classifies the reply, attempts a conditional update on the slot row to claim it atomically, and only the winning request sends the booking link and the 'slot taken' notices to the losers. A cron job closes blasts with no reply after 45 minutes and marks the slot unfilled. Stripe webhooks toggle the clinic's active flag.

Build steps

  1. Create repo, deploy the marketing page and app shell to Vercel
  2. Define Supabase tables: clinics, slots, recipients, messages, replies
  3. Wire Stripe checkout and TrustMRR-connected payment account
  4. Build the slot form with ordered waitlist entry and CSV paste
  5. Implement Twilio outbound send with per-recipient status rows
  6. Open Twilio account, start A2P 10DLC registration, send smoke test
  7. Build the inbound webhook and the conditional-update first-reply-wins lock
  8. Add OpenAI reply classification with a keyword fallback
  9. Build the filled-slot dashboard and recovered-revenue estimate
  10. Add cron sweep for unanswered blasts and opt-out handling

AI components

  • LLM intent classification of inbound patient replies (accept / decline / ask a question) with deterministic keyword fallback
  • Optional draft generation of the blast message body from the slot details, always reviewed before send
Hardest technical risk: Two replies arriving within the same second: without an atomic conditional update on the slot row, both patients get a confirmation and the clinic loses trust on its first rescue.
Section 3 of 8

Pricing and monetization

Clinic Starter

Entry offer
$99 / month

For Single-location dental, medspa or physio clinic with 2-10 staff

  • Unlimited slot rescues
  • Unlimited SMS waitlist blasts
  • First-reply-wins booking link
  • Filled-slot dashboard with recovered-revenue estimate
  • Email support

Model: Single flat monthly subscription per clinic location, with a discounted first month to lower the trial decision.

First revenue offer: $49 for the first month, then $99/month, no contract — set up by pasting one real cancellation into the form during a 10-minute screen share.

Expected ACV: $99

Upsell path: After month three, annual prepay at $990 and a $49/month add-on per extra location; the $99 anchor and the single pitch never change.

Target customers
10
Revenue model
$990
Costs
$120
Profit model
$870
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to clinics found via public online-booking pages that show same-day availability.

Where to find them

  • Dental clinics with same-day openings on their public booking widget
  • Medspas listing 'today' availability on booking pages or Instagram booking stickers
  • Physio and chiro clinics with online scheduling and a visible waitlist or cancellation policy
  • Practices with recent reviews complaining about long waits or hard-to-get appointments
  • Local business directories filtered by practice type and single-location status
  • Google Maps results for dental and medspa in four mid-size metros

Exact outreach motions

  • Send a 90-word email to the office manager with a 60-second Loom showing a simulated rescue for a slot on their own booking page
  • DM the practice Instagram with the same Loom link and one line about their same-day openings
  • Offer a free single rescue on their next real cancellation, no install and no card
  • Follow up once after three days with a one-line recovered-revenue example, then stop
  • Ask each onboarded clinic for the name of one neighbouring practice at the end of their first rescue week
  • Reply to every 'how does it work' thread with a 3-step paste-send-book description, not a deck

Message template

Hi [Name] — I saw [Clinic] lists same-day openings this week. I built a small SMS tool that texts your waitlist the moment a chair cancels and books whoever replies first. I ran a test today: 6 texts, first booking in 11 minutes, nothing installed. Want me to run one real cancellation for you free? $49 for the first month after that if it works.
Week-one goal: 150 clinics listed, 60 outreach messages sent, 3 booked conversations, 3 free rescue commitments.
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 1Foundation

Sellable shell

  • Deploy Next.js landing page to Vercel with the $99 offer.
  • Create Supabase tables for clinics, slots, recipients and messages.
  • Connect Stripe to the TrustMRR payment account.

Deliverable: Live landing page and a working checkout in test mode.

Day 2SMS pipeline

Outbound works

  • Open Twilio and start A2P 10DLC registration.
  • Build the slot form with ordered waitlist entry.
  • Send the first ordered blast to your own phone.

Deliverable: End-to-end outbound SMS from the web form.

Day 3Reply handling

First-reply-wins

  • Build the Twilio inbound webhook and store replies.
  • Add atomic slot claiming with a conditional update.
  • Send 'slot taken' notices to losing recipients.

Deliverable: Two-phone test where only one reply wins the slot.

Day 4Dashboard

Proof of value

  • Build the filled-slot dashboard with recovered-revenue estimate.
  • Generate a per-clinic confirmed booking link.
  • Add CSV paste and reuse-last-waitlist.

Deliverable: Dashboard showing a completed rescue with time-to-fill.

Day 5LaunchMVP shipped

Go live

  • Add opt-out keywords and compliance copy to every message.
  • Switch Stripe to live keys and finish onboarding copy.
  • Publish the product and announce it publicly.

Deliverable: Product live to the public on the MVP deadline.

Day 6Demand list

150 clinics

  • Source 150 clinics from public booking pages with same-day availability.
  • Capture office manager email or practice Instagram for each.

Deliverable: Spreadsheet of 150 qualified clinics with contact routes.

Day 7Sales asset

60-second demo

  • Record a Loom of a simulated rescue using a real clinic's slot time.
  • Write three email variants and the follow-up line.

Deliverable: Demo video link and outreach templates ready to send.

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

First sends

  • Send 30 personalized emails with the Loom.
  • Log replies and objections in a single sheet.

Deliverable: 30 sends, reply log started.

Day 9Outreach wave 2

Second surface

  • Send 30 more emails to a new metro.
  • DM 15 medspa Instagram accounts with the same demo.

Deliverable: 45 total sends for the day, 75 cumulative.

Day 10Trials

Free rescue offers

  • Follow up once on all non-responders.
  • Offer a free single rescue to the three warmest clinics.

Deliverable: Three free-rescue commitments booked.

Day 11Live onboarding

Screen shares

  • Run 10-minute screen-share setups with every interested clinic.
  • Paste each clinic's real waitlist while they watch.

Deliverable: At least two clinics with a real waitlist loaded.

Day 12First saleFirst sale target

Close revenue

  • Close the $49 first-month offer with the warmest clinic.
  • Send the Stripe payment link during the call.

Deliverable: First payment collected inside the contest window.

Day 13Pipeline

Refill top

  • Send 40 new outreach emails with a decaying-discount angle.
  • Check A2P 10DLC registration status.

Deliverable: 40 sends and a compliance status answer.

Day 14Delivery

Babysit a rescue

  • Personally run the first paid rescue end-to-end.
  • Write a runbook of every step and failure.

Deliverable: One delivered rescue and a one-page operating runbook.

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

Channel test

  • Send 40 outreach emails using the strongest subject line.
  • Track reply rate by practice type.

Deliverable: Reply-rate table by segment.

Day 16Self-serve

Remove the founder

  • Add Stripe checkout plus magic-link signup.
  • Publish an onboarding guide with the paste format.

Deliverable: A clinic can sign up and run a rescue without you.

Day 17Proof notes

Public evidence

  • Publish three short posts describing how a rescue works.
  • Add mechanism detail only, no invented metrics.

Deliverable: Three published posts and one landing-page section.

Day 18Outreach wave 3

Volume

  • Send 40 outreach emails to a third metro.
  • DM 15 clinics that posted same-day availability this week.

Deliverable: 55 sends, cumulative pipeline over 170.

Day 19Reply quality

Edge cases

  • Handle 'maybe', 'what time' and 'can I bring my kid' replies.
  • Add priority reordering in the waitlist UI.

Deliverable: Parser v2 with fallback and manual override.

Day 20Follow-up

Non-responders

  • Run a single follow-up across every non-responder.
  • Offer a free rescue to anyone who opened the demo twice.

Deliverable: Full follow-up pass logged.

Day 21Decision point

Keep or change

  • Tally revenue, replies and rescue volume to date.
  • Decide whether to keep the channel and message.

Deliverable: Written keep-or-change decision with numbers.

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

Warm intros

  • Ask every paying clinic for one neighbouring practice name.
  • Email each referred practice the same way as cold.

Deliverable: At least five referral names in the pipeline.

Day 23Outreach wave 4

Volume

  • Send 50 outreach emails.
  • Test two subject lines against each other.

Deliverable: Open and reply rates by line.

Day 24Onboarding speed

Under six minutes

  • Cut the signup-to-first-rescue path to three screens.
  • Add a sample CSV template download.

Deliverable: Timed onboarding under six minutes.

Day 25Outreach wave 5

Volume

  • Send 50 outreach emails.
  • Call five clinics that replied but stalled.

Deliverable: Five live conversations held.

Day 26Friction

Support load

  • Fix the top three support questions by changing the UI.
  • Audit opt-out and STOP keyword handling.

Deliverable: Support log with root causes fixed.

Day 27Reactivation

Stalled trials

  • Email every clinic that ran a free rescue but did not subscribe.
  • Send 50 new outreach emails.

Deliverable: Reactivation sequence sent.

Day 28Forecast

Final push plan

  • Review month-to-date revenue and pipeline conversion.
  • Decide how many outreach sends the last two days need.

Deliverable: Written close plan for days 29-30.

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

Convert pipeline

  • Send 60 outreach messages and DM every warm lead.
  • Offer to run a rescue live on the call.

Deliverable: All warm leads given a same-day close path.

Day 30Final cutoff

Collect and export

  • Collect every pending payment before 13:00 UTC on December 16.
  • Export the revenue log for TrustMRR verification.
  • Publish the build log with what worked and what did not.

Deliverable: Confirmed payment log inside the contest window.

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

  • Base: arpu is the flat $99 Clinic Starter plan; the $49 first month is treated as a temporary discount, not the model (Base).
  • Payment processing assumed at Stripe rates of roughly 4% including international and fixed per-charge fees (all scenarios).
  • All outreach is organic email and DM, so ad_spend is 0 in Conservative and Base (Conservative/Base).
  • Upside includes $150 of paid boosting of high-performing organic posts (Upside).
  • Refunds are near zero because the first month is discounted, with 2 refunds modelled in Upside (Upside).
  • Operating costs cover Vercel, Supabase, Twilio SMS delivery and OpenAI calls, scaling with rescue volume (all scenarios).
  • No customers, revenue, partnerships or verified traction exist; every number is a projection.

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.

These are scenario projections derived from the stated assumptions. They are not verified revenue, not existing customers and not traction of any kind.

Section 7 of 8

Main risks and validation experiments

Risk 1Office managers refuse to type waitlist phone numbers by hand.

Mitigation

Add CSV paste, reuse-last-waitlist and a bulk paste textarea; keep the first list load under four minutes.

Validation experiment

Ask five office managers to paste a real waitlist during a screen share and time each attempt.

Kill criteria

If four of five cannot load a waitlist in four minutes even with CSV paste, the manual-entry wedge is broken.

Risk 2SMS deliverability and A2P compliance delay or filter the blasts.

Mitigation

Start 10DLC registration on day 2, keep messages to one segment, include STOP on every send.

Validation experiment

Send a live blast to the founder's phone and one friendly practice, then measure delivery and latency.

Kill criteria

If blasts are filtered or delayed over 60 seconds by day 10, switch to a clinic-owned number flow before scaling outreach.

Risk 3Low reply rates make the recovered-revenue story unprovable.

Mitigation

Rewrite the blast copy around the specific slot time, add a decaying discount line, cap blasts at 25 priority numbers.

Validation experiment

Run three free rescues in week two and measure reply rate and time-to-first-accept.

Kill criteria

If fewer than one in six recipients replies across three rescues, the ROI story fails and the message must change before more selling.

Risk 4Twilio cost per rescue exceeds the $99 plan margin.

Mitigation

Cap recipients per slot, deduplicate numbers, and monitor cost per clinic weekly.

Validation experiment

Measure segments and spend across the first ten rescues.

Kill criteria

If delivery cost per clinic passes $12 per month at normal volume, tighten the recipient cap or reprice the plan.

Risk 5Clinics churn after the first month once the novelty of one filled slot fades.

Mitigation

Show a running recovered-revenue total in the dashboard and email a weekly summary of slots filled.

Validation experiment

Track day-14 and day-28 activity for every paying clinic; count rescues run per week.

Kill criteria

If paying clinics run fewer than one rescue per week by day 28, the habit is not forming and retention needs a workflow change.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create the Next.js repo.
  • Deploy the landing page to Vercel with the $99 offer and $49 first-month line.

Output: Public landing page URL.

Hours 2-5

  • Create Supabase tables for clinics, slots, recipients, messages and replies.
  • Connect Stripe and link the payment account to TrustMRR.

Output: Working schema and a test-mode checkout session.

Hours 5-8

  • Open the Twilio account and start A2P 10DLC registration.
  • Send a smoke-test SMS to your own phone.

Output: Twilio account live with one delivered message.

Hours 8-12

  • Build the slot form with priority-ordered waitlist entry.
  • Wire the server route that sends ordered Twilio messages.

Output: A blast from the web form reaching three test phones in order.

Hours 12-18

  • Build the inbound webhook and reply storage.
  • Implement the atomic first-reply-wins lock and loser notices.

Output: Two-phone test where exactly one reply wins.

Hours 18-24

  • Build the 150-clinic list from public booking pages.
  • Draft the outreach email and the Loom script.

Output: Contact-ready list of 150 clinics plus a send-ready template.

Complete report

Full 30-day launch report

Read the full generated report

SlotBack Text Rescue — 30-day solo launch report

Concept version 1. JEV score 63/100 (band C, confidence 0.72). Every revenue figure in this report is a projection, not verified revenue.

1. Product opportunity and positioning

A cancellation is a perishable asset. In a 2-10 staff dental, medspa or physio clinic the office manager knows the 2pm slot just opened, knows five waitlisted patients would take it, and has a check-in queue, a ringing phone and a hygienist waiting in front of her. She does not make the calls. The chair sits empty and the clinic eats the appointment value.

SlotBack Text Rescue does one thing: it turns a pasted cancellation into a text blast to the clinic's waitlist, in priority order, and books the first person who says yes. The office manager pastes the slot time, the value and the waitlist numbers into one form, hits send, and gets back a confirmed booking link plus a log line: slot filled, 14 minutes, estimated $180 recovered.

Positioning: faster than manual calling because it fires in seconds and never forgets; lighter than an AI receptionist because there is no phone routing, no PMS integration and no trust barrier. The buyer is not replacing software — she is buying back a chair this afternoon. That is why $99 can be approved by the person who feels the loss.

JEV flags two weaknesses: market demand (4.8/10) and operational simplicity (4.26/10). Both point the same direction — the product must be demonstrable in the first conversation, and every manual step (waitlist entry, opt-in status, reply ambiguity) must be solved before the clinic's second rescue.

2. Smallest sellable MVP

A logged-in page with three parts: a slot form (clinic, date, time, appointment value, waitlist numbers in priority order), a send button that fires ordered SMS via Twilio and stops at the first accept, and a dashboard that lists filled slots with an estimated recovered-revenue figure. Stripe checkout at $99/month sits behind it. No integration, no voice, no CRM. Four build days, launched on day 5.

The value proof is the log, not the feature list. A clinic that sees three filled slots in week one at $99 has an obvious arithmetic argument to keep paying.

3. Technical implementation plan

Next.js on Vercel for the app and marketing page, Supabase for clinics, slots, blasts, messages and reply state, Twilio for outbound and inbound SMS, OpenAI for parsing free-text replies into accept, decline or question, Stripe for the subscription. All managed services, no servers, no stateful workers beyond a scheduled sweep.

The hard part is the reply race: two patients can answer within seconds, so the first valid accept must atomically lock the slot and the remaining recipients must receive a short "slot taken, you're first on the next one" message. Build that lock before anything cosmetic. The second risk is SMS compliance — start A2P 10DLC registration on day 2 and keep every message to one segment with an opt-out keyword. AI is used only for intent classification of inbound replies; it never composes prices or clinical content.

4. Pricing and monetization

One plan: Clinic Starter, $99 per month, unlimited slot rescues, unlimited SMS blasts, filled-slot dashboard, email support. The opening offer is $49 for the first month, then $99, no contract. Anchor every pitch against one saved appointment, not against software budgets. Growth after month three comes from annual prepay and a per-extra-location add-on, never from a new tier that muddies the pitch.

5. First-customer acquisition

One channel: direct outreach to clinics found through public online-booking pages that show same-day availability — the visible signal that chairs are going unfilled. Build a list of 150 clinics from local dental, medspa and physio booking pages, capture the office manager email or the practice Instagram, and send a 90-word email with a 60-second Loom of a simulated rescue for their city. No ads, no SEO, no partnerships. Follow up once on day 3 with a recovered-revenue example, then move on. The week-one goal is 30 sends and 3 booked conversations; the first paid customer target is day 12.

6. 30-day execution roadmap

Days 1-4 are build: repo, schema, Stripe, slot form, Twilio blast, reply parser with first-reply-wins locking, dashboard, booking link. Day 5 is launch — the MVP deadline — with live Stripe keys, opt-out language and a public page.

Days 6-11 are list-building and outreach: 150 clinics sourced from public booking pages, a 60-second Loom, 30 emails on day 8, 30 more plus Instagram DMs on day 9, follow-ups and free single-rescue trials on day 10, live screen-share onboarding on day 11.

Day 12 is the first-sale target: close the $49 first month, then deliver that rescue end-to-end personally and write the runbook from what actually broke.

Days 15-21 convert the manual process into a self-serve one: Stripe checkout plus magic-link signup so a clinic can onboard without the founder, tougher reply edge cases ("maybe", "what time", "can I bring my kid"), priority-ordering UI, and a follow-up pass over every non-responder. Day 21 is the channel decision: if outreach volume is producing conversations, double it; if not, change the message, not the product.

Days 22-30 are volume and retention: 50 outreach emails per day, referral asks, onboarding cut under six minutes, opt-out audit, reactivation of trial clinics, and a final push on day 29. Day 30 closes payments before the 13:00 UTC cutoff on December 16 and exports the revenue log for verification.

7. Revenue and profit scenarios (projections only)

Conservative: 3 clinics × $99 = $297 gross. Base: 10 × $99 = $990. Upside: 25 × $99 = $2,475 with $150 of paid boosts layered on top of organic outreach. Payment processing assumed at roughly 4% via Stripe; operating costs run $25-$90 across Vercel, Supabase, Twilio and OpenAI for that many clinics.

Two different numbers matter. Hackathon profit subtracts refunds, chargebacks, processing fees and paid marketing only. Business profit additionally subtracts hosting, tooling and SMS delivery cost. At base case the contest-relevant figure is near $951 and the business figure near $906. These are projections built from stated assumptions; no customer, revenue or traction is claimed.

8. Main risks and validation experiments

First, clinics refuse to type waitlist numbers by hand. Test by asking five office managers to paste a real waitlist during a screen share and timing it; if it takes more than four minutes, add CSV paste and a reuse-last-waitlist button before scaling outreach.

Second, SMS compliance and deliverability. Test by registering A2P 10DLC on day 2 and sending a live blast to the founder's phone plus one friendly clinic; if messages are filtered or delayed, fall back to a clinic-owned number flow before selling.

Third, low reply rates destroy the ROI story. Test by running three free rescues in week two and measuring reply rate and time-to-first-accept; if fewer than one in six recipients replies, rewrite the message copy and add a decaying discount line.

Fourth, Twilio cost per rescue exceeds the $99 plan. Test by measuring segments per rescue for ten rescues; if cost per clinic passes $12/month, cap blasts at the 25 highest-priority numbers.

Fifth, churn after month one. Test by tracking rescues run per paying clinic per week; if it falls below one, the habit is not forming and the dashboard summary needs to change.

9. First 24-hour action plan

Hours 1-2: register the domain, deploy the Next.js skeleton to Vercel, publish the landing page with the $99 offer. Hours 2-5: create the Supabase schema and connect Stripe with TrustMRR from the start. Hours 5-8: open Twilio, start A2P 10DLC, send the first test SMS to your own phone. Hours 8-12: build the slot form and ordered blast. Hours 12-18: build the inbound webhook and first-reply-wins lock, testing with two phones. Hours 18-24: write the 150-clinic list from public booking pages and draft the outreach template. The output by hour 24 is a deployed page, a working SMS round trip and a list 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 →