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

DeadZone Route Proof

A web tool that turns a phone's raw motion-sensor recording into a one-page PDF route certificate proving a worker walked a required indoor path where GPS fails.

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.

Speculative5.78/10
MVP build (solo)
5 days
Launch price
$99
Sales to $1,000 revenue
11 customers
First paying customer
Direct outreach to small facilities and cleaning contractors found via local business directories and LinkedIn.
Who pays

Operations or compliance manager at a small facilities, cleaning or inspection contractor with 5-50 field staff that must document indoor walkthroughs.

Biggest execution risk

Market demand 4.3/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 11 sales at $99 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.6/10.

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

Your first 24 hours

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

0/14
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

Operations or compliance manager at a small facilities, cleaning or inspection contractor with 5-50 field staff that must document indoor walkthroughs.

Why now

The certificate is a finished document with a $99 price, so an ops manager can approve it this week with no hardware, no IT project and no procurement cycle.

Problem

Managers cannot prove staff actually walked required indoor routes in basements, warehouses or tunnels, so client disputes and audits go unanswered.

Solution

Staff open a link, record a walk on their phone, upload it; the tool aligns the motion trace to an uploaded floor plan and emails a hashed PDF route certificate.

Differentiation · Paper sign-in sheets prove nothing about route coverage, beacon installs are a capital project, and workforce platforms need a full rollout; this outputs one artifact per walk.

1. Product opportunity and positioning

Small facilities, cleaning and inspection contractors run scheduled indoor walkthroughs — basement plant rooms, warehouse aisles, stairwells, service corridors — and have no cheap way to show they happened. GPS is dead in exactly those places. Beacon and RTLS installs quote in the thousands per site and need IT cooperation. The default is a paper sign-in sheet clipped to a wall, which proves nothing about route coverage.

DeadZone Route Proof sells the document, not the platform: a one-page PDF showing a worker's phone-measured trace overlaid on the customer's own floor plan, with start and end timestamps, dwell markers and a hash ID. The buyer is the operations or compliance manager at a 5-50 field-staff contractor who already has to answer "did someone actually go down there?" to a client, an auditor or an angry property manager.

Why it sells in week two: no hardware, no IT project, no procurement. The manager forwards a link to one worker's phone, the worker walks, the manager gets a PDF by email. That is a $99 decision an ops manager can approve on a Tuesday afternoon without asking anyone.

Differentiation is structural, not cosmetic. Paper sign-in sheets are unverifiable and capture no path. Beacon installs are a capital project with a site visit. Enterprise workforce platforms require rollout and per-seat contracts. This is a single-purpose tool producing one artifact, priced per pilot rather than per seat, delivered by email in minutes.

The wedge is deliberately narrow. The JEV scoring of this concept (57.8/100, band C) flags market demand at 4.27 and monetization at 4.97 as the weak points. The answer in this plan is not a broader product. It is a tighter trigger event (a client dispute or an audit request), a repeat purchase path (a second site), and a recurring $149/month tier anchored on certificates already delivered. The founder's job in 30 days is to prove one ops manager will pay $99 for a document, then sell the same document every month.

Geography and scope are intentionally limited: one metro, one floor-plan type, one buyer role. Every certificate produced in the first two weeks is manually inspected by the founder before it goes out, which is affordable at pilot volume and impossible at scale — which is exactly why the monthly tier is priced per site, not per user.

Section 2 of 8

Smallest sellable MVP

One hashed PDF route certificate produced from a real walk on one customer floor plan, delivered by email, paid for with a $99 Stripe checkout.

Must-have features

  • Shareable recorder URL capturing DeviceMotion and DeviceOrientation in the phone browser
  • Floor plan image upload with clickable start and end anchor points
  • Similarity-transform alignment that rotates, scales and translates the trace onto the anchors
  • PDF generator with start/end timestamps, duration, distance estimate, dwell markers and SHA-256 hash
  • Resend email delivery of the PDF to the manager
  • Stripe Checkout for the $99 Pilot Pack with a webhook that mints recorder tokens on payment

Explicitly out of scope

  • Native iOS or Android apps
  • Real-time live tracking or dashboards
  • Multi-user roles and permissions
  • Beacon or hardware integration
  • Insurance or legal certification claims
  • Multi-tenant billing and invoicing

Demo flow (what the buyer sees)

  1. Manager pays $99 on Stripe Checkout.
  2. Webhook issues a recorder token and an onboarding email with two fields.
  3. Manager uploads a floor plan and clicks start and end anchors.
  4. Worker opens the recorder link on their phone, taps Start, walks the route, taps Stop.
  5. Founder or system aligns the trace to the anchors and renders the overlay.
  6. PDF is generated with timestamps and hash, then emailed to the manager.
Build plan

Technical implementation plan

Stack

Next.js App Router on VercelSupabase Postgres and StorageDeviceMotion and DeviceOrientation Web APIsPlain JS similarity-transform alignment scriptpdf-lib for PDF compositionResend for transactional emailStripe Checkout and webhooksA vision model for one-time floor plan wall masking

Architecture

A Next.js app on Vercel serves a marketing page, a small buyer dashboard and a token-gated recorder route. The recorder runs client-side, requests motion permission on iOS, samples acceleration and orientation at roughly 30 Hz, integrates the signal with a drift filter, detects turns by yaw change and posts a compressed JSON track to Supabase. Floor plans and generated PDFs live in Supabase Storage; walks, anchors and certificate hashes live in Postgres. Alignment runs server-side as a plain JS similarity transform fitted to two anchors, optionally snapping points to a corridor mask. pdf-lib renders the certificate, Resend emails it, and a Stripe webhook flips a token from unpaid to active.

Build steps

  1. Create the Next.js repo, deploy the shell to Vercel, create the Supabase project and tables.
  2. Build the token-gated recorder page with permission handling and Stop-to-upload.
  3. Add floor plan upload and start/end anchor marking in the dashboard.
  4. Implement the similarity-transform alignment and render a preview overlay.
  5. Generate the PDF with pdf-lib, add timestamps, dwell markers and a SHA-256 hash.
  6. Send the PDF to the manager via Resend with the hash in the email body.
  7. Wire Stripe Checkout and the payment webhook that activates a recorder token.
  8. Add the confidence badge and a mid-route re-anchor button to the recorder.
  9. Add the one-time vision wall-mask pass and trace snapping for uploaded plans.
  10. Add automated QA (path length, dwell, anchor proximity) before a certificate is issued.

AI components

  • A vision model runs once per uploaded floor plan to extract walls and corridor polygons, cached in Storage; it is never called per walk.
  • No LLM sits in the certificate path — PDF text is templated so output is deterministic and cheap.
Hardest technical risk: Dead reckoning drift: a ten-minute walk can close a loop in the wrong place, making the overlay look like a scribble and destroying credibility.
Section 3 of 8

Pricing and monetization

Pilot Pack

Entry offer
$99 one-time

For Small contractor testing one site

  • 3 route certificates
  • One floor plan setup
  • PDF delivery by email

Monthly Site

$149 / month

For Contractor with recurring walkthroughs

  • Unlimited certificates for one site
  • Missed-route email alerts
  • Weekly summary PDF

Model: One-time paid pilot that converts to a per-site monthly subscription, both sold self-serve through Stripe Checkout.

First revenue offer: $99 Pilot Pack: send me your floor plan, I will produce three route certificates from real walks this week and email the PDFs — if the overlays are not useful, you do not pay again.

Expected ACV: $99

Upsell path: Pilot Pack to $149/month per site after three delivered certificates, plus $149 one-time setup for each additional floor plan and the same $149/month for each extra site.

Target customers
10
Revenue model
$990
Costs
$60
Profit model
$930
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to small facilities and cleaning contractors found via local business directories and LinkedIn.

Where to find them

  • Local chamber-of-commerce and business directory listings for commercial cleaning companies
  • LinkedIn search for operations manager and account manager titles at janitorial firms
  • Google Maps listings for commercial cleaning and facilities services in one metro
  • Property-management company vendor pages listing contracted cleaners
  • Local contractor association member lists

Exact outreach motions

  • LinkedIn message leading with the problem: how do you prove the basement plant room was walked last night without beacons?
  • Cold email to the published operations address with the same question and a one-line offer.
  • 48-hour follow-up carrying a sample certificate PDF built on a public-domain floor plan.
  • Phone call to the office line asking for the person who signs off on client inspections.
  • Group post in two local contractor communities asking the same question, no link in the first post.
  • Referral ask to every pilot buyer: one peer who runs walkthroughs at another site.

Message template

Hi {name} — quick question. When a client disputes that your crew walked the basement or back-of-house route, what do you show them? Paper sign-in sheets prove someone was near the clipboard, and beacon installs run into thousands per site. I built a tool that turns a phone walk into a one-page PDF with the route drawn on your floor plan, timestamped and hashed. $99 for three certificates on one of your plans. Want me to make the first one from your plan this week?
Week-one goal: 40 named prospects listed, 30 messages sent across two days, 3 replies and 1 booked demo call.
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

Repo, infra, prospect list

  • Scaffold Next.js app and deploy to Vercel.
  • Create Supabase project with plans, walks and certificates tables.
  • Build a 40-prospect sheet for one metro from directories and LinkedIn.
  • Open Stripe and connect the payout account to TrustMRR.

Deliverable: Live hello-world URL, prospect sheet v1, Stripe connected.

Day 2Recorder

Capture motion in the browser

  • Build the token-gated recorder route.
  • Sample DeviceMotion at about 30 Hz with a drift filter.
  • Post the compressed track to Supabase on Stop.
  • Test with a two-minute walk on a real phone.

Deliverable: Stored motion track from a real phone.

Day 3Compatibility

Permissions and re-anchoring

  • Add the iOS requestPermission flow.
  • Verify behaviour on Android Chrome.
  • Add a mid-route re-anchor button.
  • Log drift across three test walks.

Deliverable: Recorder works on iOS Safari and Android Chrome with a drift note.

Day 4Floor plan

Upload and anchors

  • Add JPG, PNG and PDF-page upload to Supabase Storage.
  • Build clickable start and end anchor marking.
  • Persist anchors per plan and per walk.

Deliverable: Plan upload and anchor marking live.

Day 5CertificateMVP shipped

Alignment and PDF (MVP gate)

  • Fit a similarity transform from the trace to the two anchors.
  • Render the overlay onto the plan with pdf-lib.
  • Add timestamps, distance estimate and a SHA-256 hash.
  • Email the PDF via Resend.

Deliverable: One end-to-end certificate PDF from a real 60-second walk.

Day 6Calibration

Accuracy against a known plan

  • Run five walks on one plan with two volunteers.
  • Score each trace against corridor boundaries.
  • Fix the top alignment bug.
  • Tune the step-length constant.

Deliverable: Five scored traces and a corrected alignment build.

Day 7Checkout

Payment to token

  • Create the $99 Stripe Checkout link.
  • Add a webhook that mints a recorder token on payment.
  • Gate the dashboard behind an active token.

Deliverable: Paid link issues a working recorder link.

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

Make the offer public

  • Publish the landing page with a sample certificate.
  • State plainly what the certificate proves and what it does not.
  • Add the $99 button and a two-field onboarding form.

Deliverable: Live sales page with sample certificate.

Day 9Outreach 1

First 15 messages

  • Send 15 messages to cleaning contractors.
  • Log sends, opens and replies in the prospect sheet.

Deliverable: 15 sends logged.

Day 10Outreach 2

Next 15 plus groups

  • Send 15 more messages from the list.
  • Post the problem question in two local contractor groups.
  • Prepare the sample certificate for follow-ups.

Deliverable: 30 sends total and a sample PDF ready.

Day 11Follow-up

Convert replies to calls

  • Follow up every non-responder at 48 hours with the sample PDF.
  • Book demo calls.
  • Write a 15-minute demo script including a live walk.

Deliverable: 3 or more replies and a booked call.

Day 12First saleFirst sale target

Close the $99 pilot

  • Run the call and record a live 60-second walk.
  • Send the certificate before the call ends.
  • Ask for the $99 Pilot Pack payment on the call.

Deliverable: First $99 payment collected.

Day 13Delivery

Deliver what was sold

  • Produce the buyer's three certificates.
  • Manually verify each overlay before sending.
  • Ask for a one-line written quote.

Deliverable: Three delivered certificates and a testimonial.

Day 14Upsell

Monthly offer and list 2

  • Offer the $149 Monthly Site to the pilot buyer.
  • Build a second 20-name list of facilities and property-maintenance contractors.

Deliverable: Upsell asked and list 2 ready.

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

Second list

  • Send 20 messages to the facilities and property-maintenance list.
  • Log replies and note which job titles respond.

Deliverable: 20 sends on list 2.

Day 16Accuracy v2

Better traces

  • Add turn-count normalisation to the alignment.
  • Add an honest confidence badge on the PDF.
  • Replay the five calibration walks.

Deliverable: Higher-confidence traces shipped.

Day 17Alerts

Missed-route email

  • Add a scheduled check per site for expected certificate windows.
  • Send a missed-route alert email via Resend.

Deliverable: Alert email working on one test site.

Day 18Batching

Weekly summary

  • Allow multiple walks to be combined into one weekly summary PDF.
  • Add a per-route coverage line to the summary.

Deliverable: Weekly summary PDF generator.

Day 19Proof content

Show the product working

  • Record a 90-second screen capture of a certificate being made.
  • Post it on LinkedIn and link it from outreach.

Deliverable: Public demo video.

Day 20Sales push

Pilots 2 and 3

  • Follow up every list-2 contact.
  • Run booked calls with the live walk demo.
  • Close pilots 2 and 3 if replies allow.

Deliverable: Follow-ups sent and calls run.

Day 21Review

Measure and rewrite

  • Compute reply rate per list and per message variant.
  • Rewrite the weakest message.
  • Update the pipeline sheet with next actions.

Deliverable: Message v2 and a pipeline review.

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

Convert pilots

  • Send the $149 subscription link to every buyer with three delivered certificates.
  • Add subscription billing to the Stripe webhook.

Deliverable: At least one subscription link sent.

Day 23Self-serve

Remove founder from onboarding

  • Let a buyer upload a plan and generate a recorder link themselves.
  • Add inline validation for anchor placement.

Deliverable: Self-serve onboarding path live.

Day 24QA

Automatic sanity gate

  • Add automated checks on path length, dwell and anchor proximity.
  • Block certificate issue when checks fail and show a reason.

Deliverable: Auto QA gate on certificate generation.

Day 25Wall mask

Snap traces to corridors

  • Run the vision model once per plan to extract walls.
  • Cache the mask in Supabase Storage.
  • Use it to snap the trace for new plans.

Deliverable: Wall-snapped overlay for new plans.

Day 26Referrals

Third list

  • Ask every buyer for one introduction to a peer.
  • Send 25 messages to a third list of inspection contractors.

Deliverable: 25 sends and referral asks done.

Day 27Support debt

Fix and document

  • Fix the most reported issue.
  • Write a six-question FAQ and publish it on the landing page.

Deliverable: FAQ page and a shipped bug fix.

Day 28Checkpoint

Reconcile revenue

  • Reconcile Stripe payments against the payout account records.
  • List unpaid or disputed invoices.
  • Deliver any outstanding certificates.

Deliverable: Reconciled revenue sheet.

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

Last outreach

  • Send 25 messages with a December pilot deadline.
  • Follow up every warm lead from all three lists.

Deliverable: 25 sends and warm-lead follow-ups complete.

Day 30Close

Deliver and record

  • Deliver all outstanding certificates.
  • Collect final invoices before 13:00 UTC.
  • Verify payout records match the delivered work.
  • Write the post-mortem and next-30-day list.

Deliverable: All deliveries complete and final revenue recorded.

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

  • Payment fees assume Stripe Checkout at 2.9% + $0.30, roughly 3.2-4% blended on $99 tickets (all scenarios).
  • Conservative: 3 Pilot Pack sales from about 120 outreach touches, no monthly conversion, no paid marketing.
  • Base: 10 Pilot Pack sales at $99, matching the concept target, no monthly conversion counted.
  • Upside: 25 transactions averaging $99, mixing Pilot Packs and first monthly payments, including one $150 sponsored LinkedIn post.
  • ad_spend_usd is 0 in Conservative and Base because outreach is organic; Upside assumes $150 of paid promotion.
  • Operating costs cover Vercel, Supabase, Resend, one domain and one vision-model call per uploaded floor plan.
  • No refunds or chargebacks are assumed in Conservative and Base; Upside carries one refunded pilot.
  • All figures are projections from these stated assumptions, not verified revenue, customers or traction.

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, revenue or partnerships exist at launch.

Section 7 of 8

Main risks and validation experiments

Risk 1Motion alignment is too poor to look credible, so the overlay reads as a scribble.

Mitigation

Mandatory start and end anchors, a mid-route re-anchor tap, turn-count normalisation and an honest confidence badge on the PDF.

Validation experiment

Record five walks on one known floor plan on days 3-6 and score whether each trace stays inside the walked corridors.

Kill criteria

If fewer than 3 of 5 traces stay plausibly inside the walked area after two alignment iterations, switch the deliverable to a timestamped checkpoint-sequence certificate instead of a continuous trace.

Risk 2Buyers expect legal-grade or insurance-grade proof the tool cannot provide.

Mitigation

Footer on every certificate states what was measured and what was not; outreach uses the words "internal operations evidence" and never "certified".

Validation experiment

Ask on every demo call who the buyer would show the document to and log the answer by category.

Kill criteria

If more than half of interviewees name a regulator or insurer as the audience, refund any pilot sold on that expectation and reposition or stop.

Risk 3Outreach reply rates collapse well below plan and no calls get booked.

Mitigation

Two message variants tracked per list, rotated across three list types, with a sample certificate attached on the 48-hour follow-up.

Validation experiment

Track 60 sends across two variants and two list types in week two and compute reply rate per cell.

Kill criteria

If 60 sends yield fewer than 3 replies, change list type (inspection, elevator and utility inspection firms) before changing channel; if a second 60 sends also fail, stop the concept.

Risk 4iOS or Android blocks motion access, so the recorder cannot capture a walk on a buyer's phone.

Mitigation

Permission request flow on iOS, an HTTPS recorder, and a fallback tap-anchor mode that reconstructs the route from checkpoint timestamps and plan geometry.

Validation experiment

Test the recorder on three physical devices on day 3 and record the exact permission behaviour per browser.

Kill criteria

If motion sampling fails on two of three devices, ship the tap-anchor fallback as the default deliverable within 48 hours rather than defending the trace overlay.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Scaffold the Next.js repo.
  • Deploy the shell to Vercel.
  • Create the Supabase project and three tables.

Output: A live URL and a working database.

Hours 3-5

  • Pull 40 cleaning and facilities contractors in one metro from directories.
  • Add contact name, role and route to each row.
  • Flag the ten most likely to have basement or back-of-house routes.

Output: Prospect sheet v1 with 40 named rows.

Hours 6-8

  • Build the token-gated recorder route.
  • Capture DeviceMotion and post a JSON track on Stop.

Output: A recorded motion track stored in Supabase.

Hours 9-11

  • Test the recorder on two physical phones.
  • Note permission prompts and sampling behaviour per browser.

Output: A one-page device compatibility note.

Hours 12-13

  • Open Stripe and connect the payout account to TrustMRR.
  • Create the $99 Pilot Pack payment link in test mode.

Output: A working checkout link.

Hours 14-16

  • Write the outreach message and the one-paragraph offer.
  • Draft the sample-certificate one-pager for follow-ups.

Output: A ready-to-send message and follow-up asset.

Complete report

Full 30-day launch report

Read the full generated report

DeadZone Route Proof — 30-Day Launch Report

Solo founder · Mon 16 Nov 2026 13:00 UTC → Wed 16 Dec 2026 13:00 UTC · JEV score 57.8/100 (band C, confidence 0.66)

1. Product opportunity and positioning

Small facilities, cleaning and inspection contractors run scheduled indoor walkthroughs — basement plant rooms, warehouse aisles, stairwells, service corridors — and have no cheap way to show they happened. GPS is dead in exactly those places. Beacon and RTLS installs quote in the thousands per site and require IT cooperation. The default is a paper sign-in sheet clipped to a wall, which proves nothing about route coverage.

DeadZone Route Proof sells the document, not the platform: a one-page PDF showing a worker's phone-measured trace overlaid on the customer's own floor plan, with start and end timestamps, dwell markers and a hash ID. The buyer is the operations or compliance manager at a 5-50 field-staff contractor who already has to answer "did someone actually go down there?" to a client, an auditor or a property manager.

Why it sells in week two: no hardware, no IT project, no procurement. The manager forwards a link to one worker's phone, the worker walks, the manager gets a PDF by email. That is a $99 decision an ops manager can approve on a Tuesday afternoon.

Differentiation is structural. Paper sign-in sheets are unverifiable and capture no path. Beacon installs are a capital project with a site visit. Workforce platforms need a full rollout and per-seat contracts. This is a single-purpose tool producing one artifact, priced per pilot, delivered by email in minutes.

The wedge stays narrow. The scoring flags market demand (4.27) and monetization (4.97) as the weak points, and the answer is not a broader product: it is a tighter trigger event (a client dispute or audit request), a repeat purchase (a second site) and a recurring $149/month tier anchored on certificates already delivered. Geography and scope are limited to one metro and one buyer role.

2. Smallest sellable MVP

One paid deliverable: a single PDF route certificate from a real walk on one customer floor plan. Five parts, nothing else. A shareable recorder URL that captures device motion in the worker's own browser. A dashboard where the manager uploads a floor plan and clicks the walk's start and end points. An alignment step that rotates, scales and translates the trace so its endpoints land on those anchors. A PDF with timestamps, duration, distance estimate, dwell markers and a SHA-256 hash. Email delivery to the manager.

Out of scope: native apps, live tracking, multi-user roles, beacon integration, and any insurance or legal certification claim. The certificate states what it measured and what it did not.

3. Technical implementation plan

Next.js on Vercel, Supabase for Postgres and Storage, Stripe Checkout, Resend, and pdf-lib for composition. The recorder requests motion permission on iOS, samples at roughly 30 Hz, integrates acceleration with a zero-velocity drift filter, detects turns by yaw change, and posts a compressed JSON track on Stop. Alignment is plain JavaScript: estimate path length from step count, fit a similarity transform to the two anchors, and snap points to a corridor centreline when a wall mask exists. A vision model runs once per uploaded plan (never per walk) to extract walls; that is the only inference cost.

The hardest technical risk is drift: a ten-minute walk can close a loop in the wrong place. Built-in mitigations from day 3 are mandatory anchors, a mid-route re-anchor button, turn-count normalisation and an honest confidence badge on the PDF.

4. Pricing and monetization

Two prices, both self-serve. Pilot Pack, $99 one-time: three certificates, one floor-plan setup, PDF delivery — the only offer used for the first 20 days, small enough to approve on a call. Monthly Site, $149/month: unlimited certificates for one site plus missed-route alerts, offered only after three certificates have been delivered, so the recurring tier is anchored on a result rather than a promise. Expected first-sale ACV is $99. The upsell path is pilot → monthly per site → additional sites at $149 each, plus $149 setup per extra floor plan. No per-seat pricing, because seats invite procurement.

5. First-customer acquisition

One channel: direct outreach to small facilities and cleaning contractors found through local business directories and LinkedIn. Build 40 named prospects in one metro, then rotate through three list types — janitorial firms, facilities and property-maintenance contractors, inspection firms.

Messages lead with the problem: "How do you prove your crew actually walked the basement plant room last night without installing beacons?" Follow up at 48 hours with a sample certificate built on a public-domain plan, then offer three certificates on their own plan for $99 on a 15-minute call. Demo live: record a 60-second walk while the prospect watches and email the PDF before the call ends. Week-one goal: 40 prospects, 30 sends, 3 replies, 1 booked call.

6. 30-day execution roadmap

Days 1-5 are build-only and end at the MVP gate: one certificate from one real walk. Days 6-7 add calibration with two volunteers and a live Stripe checkout that mints a recorder token on payment. Days 8-14 are launch: landing page on day 8, 30 outreach messages across days 9-10, follow-ups day 11, calls day 12 with the first $99 pilot targeted for that day, first certificate delivered within 24 hours on day 13, monthly upsell and a second 20-name list on day 14. Days 15-21 repeat outreach on the second list, ship turn-count normalisation and drift correction, add the missed-route alert the monthly tier promises, and publish a 90-second screen recording of a certificate being produced. Days 22-28 convert pilots to monthly, make onboarding self-serve, add an automated QA gate before a certificate issues, add the one-time wall-mask snapping pass, and send 25 messages to a third list. Days 29-30 are the closing sprint: 25 final messages, collect outstanding invoices, deliver every promised certificate, reconcile payouts, and write the post-mortem.

Hard gates: no payment link after day 7; if a certificate cannot be delivered the same day it is sold, stop outreach and fix delivery first.

7. Revenue and profit scenarios

All three are projections, not verified revenue. Conservative: 3 Pilot Packs, $297 gross, $12 payment fees, no ad spend, $25 operating. Base: 10 Pilot Packs, $990 gross, $39 fees, no ad spend, $45 operating. Upside: 25 transactions at $99 average, $2,475 gross, $50 refunds, $97 fees, $150 paid promotion, $90 operating. Payment fees assume Stripe Checkout at 2.9% + $0.30, about 3.2-4% blended. Operating costs are Vercel, Supabase, Resend, one domain and per-plan vision calls. No customers exist at launch; nothing here is traction.

8. Main risks and validation experiments

Alignment is not credible. If the overlay looks like a scribble the product is worthless. Test: five recorded walks on one known plan, scored on whether traces stay inside the walked corridors. Kill: fewer than 3 of 5 pass after two iterations — switch to a checkpoint-sequence certificate.

Buyer wants legal-grade proof. On every call ask who they would show the document to. If more than half name a regulator or insurer, reprice the positioning as internal operations evidence and refund pilots sold on the wrong expectation.

Reply rates collapse. Two message variants across 40 prospects, tracked per list. If 60 sends produce fewer than 3 replies, change list type before changing channel.

Motion access blocked on the worker's phone. Test three physical devices on day 3. If sampling fails on two, ship the tap-anchor fallback as the default deliverable within 48 hours.

9. First 24-hour action plan

Hours 1-2: scaffold and deploy the app shell, create the Supabase project. Hours 3-5: build the 40-prospect sheet for one metro. Hours 6-8: build the recorder and store one real motion track. Hours 9-11: test on two phones and write the compatibility note. Hours 12-13: open Stripe, connect the payout account, create the $99 link in test mode. Hours 14-16: write the outreach message and the sample-certificate one-pager.

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 →