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

HandoverSeal

Turns a 3-minute phone walkaround into a sealed, renter-accepted handover and return packet for high-value rental cars, so damage disputes and chargebacks die on arrival.

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.40/10
MVP build (solo)
5 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Direct Instagram DM carrying a personalised 60-second Loom, followed by a WhatsApp or SMS to the listed business number the next morning.
Who pays

Owner-operators of independent exotic and luxury rental firms with 1-15 cars worth $60k-$400k in the US, UK, UAE and Australia, taking direct Instagram/WhatsApp bookings, who had a damage dispute or messy handover in the last 90 days.

Biggest execution risk

Market demand 4.6/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; 26 sales at $39 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 7.8/10.

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

Your first 24 hours

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

0/15
Entry price
$39
Solo build
5 days
30d base revenue
$990
30d hackathon profit
$951
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operators of independent exotic and luxury rental firms with 1-15 cars worth $60k-$400k in the US, UK, UAE and Australia, taking direct Instagram/WhatsApp bookings, who had a damage dispute or messy handover in the last 90 days.

Why now

Direct-booking operators now carry the fraud and damage exposure that killed HiGear, card disputes turn on documentation, and every operator already has a smartphone camera - no new hardware or behaviour to adopt.

Problem

Pickup documentation is a WhatsApp photo dump and a paper sheet nobody signs: no timestamp chain, no renter acceptance, no odometer baseline, no structured return comparison.

Solution

A mobile web wizard captures eight guided angles, odometer, fuel and damage pins; the renter accepts on a link with typed name and consent; the system emails a sealed PDF with a SHA-256 hash to both parties and produces a return delta sheet.

Differentiation · The alternative is a WhatsApp album that proves a photo existed; a sealed packet proves what the renter accepted, when, and that nothing in it changed afterwards.

1. Product opportunity and positioning

HiGear did not die of weak demand. It died because four cars worth $300,000-$400,000 were handed to people using stolen identities, and the handover record could not survive a dispute. Operators still renting $60k-$400k cars direct through Instagram and WhatsApp inherited that risk minus the process: pickups run on a phone photo dump and a paper sheet nobody signs.

HandoverSeal is not a marketplace, booking calendar or insurance product. It is the documentation layer on top of bookings the operator already has. At pickup the operator opens a mobile web wizard: eight guided angles, odometer and fuel, damage pins tapped onto a car diagram, the renter's licence behind a consent screen. The renter opens a link, reviews condition and deposit terms, types their name, accepts. The system emits a sealed PDF - photos, readings, pins, terms, acceptance timestamp, IP and a SHA-256 hash of the packet - emailed to both parties. At return the same wizard outputs a delta sheet of new damage only.

The wedge is narrow on purpose. The buyer already owns cars and bookings, so the product replaces one recurring step: no marketplace cold start, no SEO ramp, no procurement cycle. One owner decides, and $99 sits below the threshold where they call a lawyer.

JEV scored the concept 6.4/10 (band C, confidence 0.64): strong on speed to first revenue (7.8) and solo build feasibility (7.4), weak on market demand (4.6) and operational simplicity (4.7). Both weaknesses are answered here by narrowing the target to operators with a dispute inside the last 90 days, and by avoiding KYC vendors, human review and long-lived regulated data.

The real alternative is a WhatsApp album. The difference is not sharper photos; it is the acceptance event and the hash. An album proves a photo existed. A sealed packet proves what the renter agreed to, when, and that nothing in it changed.

Section 2 of 8

Smallest sellable MVP

A mobile web wizard that seals one renter-accepted handover PDF with a SHA-256 hash, plus a return delta sheet and Stripe Checkout gating.

Must-have features

  • Operator account with vehicle profiles (make, plate, declared value, deposit terms)
  • Mobile browser wizard: eight guided angles, odometer and fuel entry, no app install
  • Tap-on-diagram damage pins saved per handover and carried into the next rental
  • Renter acceptance page with condition report, terms, licence photo, consent checkbox and typed name
  • Sealed packet generator: PDF plus SHA-256 hash of photos and metadata, emailed to both parties
  • Return check-in that reuses the same angles and outputs a new-damage delta sheet
  • Stripe Checkout subscription with per-plan limits enforced per account

Explicitly out of scope

  • No ID verification, KYC or background-check vendor integration
  • No booking calendar, availability or renter-to-operator payments
  • No handling or escrow of security deposits
  • No native iOS or Android app
  • No telematics, GPS hardware or odometer API
  • No insurance quoting, claims filing or legal-advice framing
  • No 24/7 support promise or human review queue

Demo flow (what the buyer sees)

  1. Founder enters plate, declared value and deposit terms to create a vehicle profile
  2. Operator opens the wizard on a phone and captures eight guided angles
  3. Operator taps a scuff onto the diagram and types the odometer reading
  4. Renter opens the acceptance link on a second phone, reviews terms, types name and accepts
  5. Sealed PDF with hash and acceptance timestamp lands in both inboxes
  6. Return check-in reuses the angles and shows the one new pin as a delta sheet
Build plan

Technical implementation plan

Stack

Next.js on Vercel, mobile-firstSupabase Postgres with row-level securitySupabase Storage for photo objectsStripe Checkout and BillingResend for transactional packet emails@react-pdf/renderer for the sealed PDFNode crypto SHA-256 in a serverless sealing routeVercel Cron for licence-photo retention deletion

Architecture

A single Next.js app serves the operator wizard and the public renter acceptance pages. Supabase holds relational rows (operators, vehicles, handovers, photos, acceptances, packets) plus photo objects; row-level security scopes every row to its operator. The sealing route sorts photo checksums and metadata canonically, hashes the concatenation, writes the hash into the PDF footer and the email body, and stores it against the packet ID so any regeneration can be verified. Stripe webhooks flip plan entitlements; Resend delivers the packet to operator and renter with a signed download link.

Build steps

  1. Create Vercel and Supabase projects, schema for operators, vehicles, handovers, photos, acceptances, packets
  2. Build auth and vehicle profile CRUD
  3. Build the capture wizard with client-side downscale and Supabase Storage upload
  4. Build the tap-on-diagram damage pin component with carry-forward to the next handover
  5. Build the renter acceptance page with licence capture, consent checkbox and typed name
  6. Implement the canonical hash route and the @react-pdf/renderer template
  7. Wire Resend delivery with signed download link and attachment fallback
  8. Build the return check-in flow and delta sheet
  9. Add Stripe Checkout, webhooks and per-plan limit enforcement
  10. Add the retention cron for licence-photo deletion and a data-export path

AI components

  • None in v1: sealing is deterministic hashing, not inference
  • Deferred: optional OCR pre-fill of the odometer reading from the photo, only after first revenue
Hardest technical risk: An eight-photo packet can hit 20MB, render slowly on a mid-range Android in a car park and bounce in email; mitigate with client-side downscale to 1600px at JPEG 0.75, an 8MB packet ceiling and a signed link as primary delivery.
Section 3 of 8

Pricing and monetization

Single Seal

Entry offer
$39 one-time

For One-car owners, event and photo-shoot rental operators needing one defensible handover

  • One sealed handover packet
  • Renter acceptance link and hash-stamped PDF
  • Return delta sheet for that rental

Starter

$99 / month

For Independent operator with 1-5 high-value cars doing 5-20 rentals a month

  • Up to 25 sealed handovers per month
  • Unlimited vehicle profiles and damage pin maps
  • Renter acceptance links with hash-stamped PDFs
  • Return delta sheets and packet archive

Fleet

$249 / month

For Operator with 6-15 cars or a multi-city exotic rental brand

  • Unlimited sealed handovers
  • Operator logo and custom terms on packets
  • Multi-user access for lot staff
  • CSV export of all handovers for insurer or chargeback submissions

Model: One-time per-seal price for single-car operators plus two monthly subscription tiers with handover caps.

First revenue offer: A free sealed packet for their next real rental, no card required; when they open the second handover, send the $99 Starter checkout link in the same thread.

Expected ACV: $99

Upsell path: Single Seal buyers are credited $39 toward Starter; Starter accounts past five cars move to Fleet at $249; Starter overage is billed per packet above the 25 cap instead of hard-stopping.

Target customers
25
Revenue model
$2,475
Costs
$130
Profit model
$2,345
Section 4 of 8

First-customer acquisition

Primary channel

Direct Instagram DM carrying a personalised 60-second Loom, followed by a WhatsApp or SMS to the listed business number the next morning.

Where to find them

  • Google Maps searches for 'exotic car rental' and 'luxury car rental' in Miami, Los Angeles, Las Vegas, London, Dubai and Gold Coast
  • Instagram hashtag pages #exoticcarrental and #luxurycarrental
  • Instagram tagged-location pages for those six metros
  • Turo host profiles listing cars above $80k in the same metros
  • Exotic-rental operator groups on Facebook and WhatsApp

Exact outreach motions

  • Record a 60-second Loom running that operator's own advertised car through the wizard and showing the sealed PDF and hash
  • Send the Loom by Instagram DM ending with 'want your first three handovers sealed free?'
  • Call the listed business number the next morning with the same offer in two sentences
  • Deliver one free sealed packet for their next real rental, no card, and ask for feedback on the packet
  • At the second handover send the $99 Starter Stripe link in the same thread
  • After the first paid month ask for one named introduction to another operator

Message template

Saw your Huracan listed on Instagram - I ran it through HandoverSeal (60s video attached). It produces a PDF your renter signs on their phone at pickup, with a hash so nothing can be edited after. Want your first three handovers sealed free, no card?
Week-one goal: 80 operators researched, 30 personalised Looms recorded, 30 DMs sent, 5 replies, 3 free packets scheduled.
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 and data model

  • Create Vercel and Supabase projects and push the Next.js skeleton
  • Write schema for operators, vehicles, handovers, photos, acceptances, packets
  • Ship auth and vehicle profile CRUD

Deliverable: Deployed app with login and a saved vehicle profile

Day 2Capture

Eight-angle wizard

  • Build the guided capture wizard with angle prompts
  • Add client-side downscale to 1600px and Supabase Storage upload
  • Add odometer and fuel entry

Deliverable: Eight photos from a real phone stored against a handover

Day 3Acceptance

Diagram pins and renter link

  • Build tap-on-diagram damage pins with carry-forward
  • Build the public renter acceptance page with licence capture and consent
  • Store typed name, timestamp and IP

Deliverable: A renter link that records a signed acceptance

Day 4Sealing

Hash and PDF delivery

  • Implement the canonical SHA-256 sealing route
  • Build the packet PDF template with hash footer
  • Wire Resend delivery with signed link to both parties

Deliverable: Sealed packet in two inboxes with a verifiable hash

Day 5Paid productMVP shipped

Delta sheet and billing

  • Build return check-in reusing the same angles
  • Output the new-damage delta sheet
  • Add Stripe Checkout and per-plan limit enforcement

Deliverable: Live v1 that accepts payment

Day 6Self-test

Real handovers and list build

  • Run three full handovers on your own phone and time each
  • Fix capture friction and packet size
  • Build the first 40 operator list rows

Deliverable: Three complete packets and a 40-row list

Day 7Sales assets

Loom production

  • Write and record the master Loom script
  • Record five personalised Looms from listed cars
  • Draft the DM, call script and free-packet offer

Deliverable: Six Looms and a three-touch script

Week 2 · Launch & first sale · 7 days
Day 8First touches

Send 10 DMs

  • Send 10 DMs with personalised Looms
  • Log every send in the tracking sheet
  • Add 20 more list rows

Deliverable: 10 DMs sent, 60 list rows

Day 9Follow-up

Calls plus new DMs

  • Phone the day-8 batch
  • Send 10 new DMs
  • Ship the $39 Single Seal checkout

Deliverable: 10 calls logged, Single Seal purchasable

Day 10Free packets

Deliver value live

  • Send 10 DMs
  • Book free sealed packets with every replier
  • Fix any bug found while delivering

Deliverable: Three free packets scheduled

Day 11Proof

Live handover on a call

  • Run a handover live with an operator on a video call
  • Capture screenshots of the accepted packet
  • Ask for one sentence of feedback

Deliverable: One real operator packet and a testimonial line

Day 12First saleFirst sale target

Ask for money

  • Send the $99 Starter link to any thread that used a free packet
  • Publish the demo as a reel
  • Post the offer in two operator groups

Deliverable: First paying subscriber

Day 13Volume

List to 90

  • Send 15 DMs
  • Call five business numbers
  • Add 30 list rows

Deliverable: 90 list rows, 45 cumulative DMs

Day 14Retro

Fix top friction

  • Review every call note for the top objection
  • Ship the one fix that unblocks conversion
  • Rewrite the DM opener

Deliverable: Revised opener and a shipped fix

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

Second-handover closes

  • Trigger Starter asks on every second handover
  • Send 10 new DMs
  • Offer Fleet to any multi-car replier

Deliverable: Two Starter conversions in motion

Day 16Product gap

Delta and export

  • Improve the delta sheet layout with side-by-side angles
  • Add a CSV export of handovers
  • Re-run a full handover to verify

Deliverable: Delta sheet v2 and CSV export

Day 17Referrals

Named introductions

  • Ask every active user for one named introduction
  • Send 10 new DMs
  • Log intros with the introducer's name

Deliverable: Three named introductions requested

Day 18Final follow-up

Third and last touch

  • Send final follow-ups to all non-repliers
  • Close the loop in the tracking sheet
  • Send 10 DMs to fresh rows

Deliverable: All non-repliers closed at three touches

Day 19Content

Operator-facing post

  • Publish a before-and-after post using your own demo packet
  • Post it in three operator groups
  • Reply to every comment with the free-packet offer

Deliverable: One post, three groups, replies logged

Day 20Volume

List to 120

  • Send 15 DMs
  • Call five numbers
  • Add 30 list rows

Deliverable: 120 list rows

Day 21Retro

Pricing page and FAQ

  • Publish a pricing page with an objection FAQ
  • Add the FAQ link to the DM follow-up
  • Review reply rate by metro

Deliverable: Live pricing page with FAQ

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

Multi-car accounts

  • Run Fleet demos with any 6+ car operator
  • Send 10 new DMs
  • Collect the top Fleet requirement

Deliverable: Two Fleet demos booked

Day 23Fleet build

Logo, terms, multi-user

  • Add operator logo and custom terms to the packet
  • Add multi-user access per account
  • Verify plan gating for Fleet

Deliverable: Fleet tier sellable

Day 24Referrals

Convert intros

  • Follow up every named introduction
  • Send 10 DMs
  • Ask two paying users for a written line

Deliverable: Two referral conversations opened

Day 25Reach

Second reel and groups

  • Post a second reel showing the return delta sheet
  • Post in three more operator groups
  • Reply to all inbound within four hours

Deliverable: Second reel published, inbound answered

Day 26Trust

Data retention

  • Add consent copy and a 90-day licence-photo auto-delete cron
  • Add an export-then-purge path per account
  • Publish a one-page data handling note

Deliverable: Retention policy shipped and documented

Day 27Closing push

Warm repliers

  • DM every warm replier with a 16 December framing
  • Offer the free packet again to anyone who stalled
  • Send 10 DMs to uncontacted rows

Deliverable: Every warm lead contacted once more

Day 28Reconcile

Payments and refunds

  • Match Stripe payouts against TrustMRR records
  • Confirm no refunds or chargebacks are pending
  • Document the reconciliation in a sheet

Deliverable: Clean payment reconciliation

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

Close outstanding trials

  • Convert every unexpired free packet into a Starter link
  • Chase two stalled Fleet demos
  • Fix only blocking bugs

Deliverable: All trial users asked to pay

Day 30Cutoff

Final 24 hours to 13:00 UTC

  • Send the final checkout links before the cutoff
  • Re-run Stripe reconciliation to the minute
  • Record the closing numbers and known risks

Deliverable: Verified closing revenue record

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

  • All three scenarios are projections from stated assumptions, not verified revenue, customers or traction.
  • Conservative: 3 Starter subscribers from roughly 45 DMs and calls, no paid acquisition.
  • Base: 10 Starter subscribers from about 120 targeted DMs and calls at a blended close near 1 in 12.
  • Upside: 25 Starter subscribers, with two reels boosted for $120 total.
  • Blended ARPU held at $99 by modelling a Starter-dominant mix; Single Seal at $39 is treated as an on-ramp credited toward Starter, not as durable revenue.
  • Payment processing assumed at roughly 4% blended of collected revenue across Stripe card fees.
  • Operating cost band of $60-$145 covers Vercel, Supabase, domain and Resend at these volumes; PDF rendering scales but stays negligible.
  • Refunds modelled at zero in conservative and base; one Single Seal refund plus one prorated Starter refund in upside.
  • No chargebacks modelled because the free-packet trial keeps the first payment inside the contest window with low dispute exposure.
  • Every sale covers delivery cost by a wide margin, so no below-cost pricing is involved.

Conservative

3 customers
$297
collected revenue · avg payment $99
Refunds
$0
Chargebacks
$0
Payment fees
$12
Paid marketing
$0
Hackathon profit
$285
Operating costs
$60
Business profit
$225

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
$85
Business profit
$866

Optimistic

25 customers
$2,475
collected revenue · avg payment $99
Refunds
$39
Chargebacks
$0
Payment fees
$97
Paid marketing
$120
Hackathon profit
$2,219
Operating costs
$145
Business profit
$2,074

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$390
Payment fees (3.9%)
$15
Paid marketing
$0
Hackathon profit
$375
Business profit
$290

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 scenarios are projections derived from the stated assumptions. They are not verified revenue, existing customers, traction or validation of demand.

Section 7 of 8

Main risks and validation experiments

Risk 1Operators treat photo documentation as a free habit and refuse to pay $99 for record-keeping.

Mitigation

Ask for payment only after a second handover, when the packet has already been used in a live rental.

Validation experiment

From day 9, charge $39 Single Seal after the free packet and count how many free-packet users pay.

Kill criteria

Fewer than 1 in 8 free-packet users pays anything across the first 20 free packets.

Risk 2A typed-name acceptance page may not satisfy a card network or insurer as dispute evidence.

Mitigation

Include timestamp, IP, consent text, terms version and packet hash; avoid any claim that the packet guarantees a chargeback win.

Validation experiment

Walk three operators through filing the packet in a real past chargeback and log exactly which fields they say are missing.

Kill criteria

All three say the packet would not have changed the outcome, with the same missing field named.

Risk 3Instagram DM and cold phone outreach get flagged, producing a reply rate too low to build a funnel.

Mitigation

Three-touch cap, personalised Loom using the operator's own car, and manual sending rather than automation.

Validation experiment

Measure reply rate on the first 30 DMs before scaling to 120 contacts.

Kill criteria

Reply rate stays under 5% after two different DM openers and one phone follow-up.

Risk 4The reachable list of independent exotic rental operators is under 120, capping the upside case.

Mitigation

Add Turo host profiles above $80k and operator groups as secondary list sources.

Validation experiment

Try to build 40 verified rows in one metro within two hours on day 6.

Kill criteria

Fewer than 40 verified rows found across two metros after four hours of list building.

Risk 5Storing renter licence photos creates privacy and retention obligations that add liability for the operator.

Mitigation

Consent copy on the acceptance page, 90-day auto-delete and an export-then-purge path, shipped before the 25th customer.

Validation experiment

Ask three operators whether their current process keeps licence photos and for how long.

Kill criteria

Operators say collecting licence photos through a third-party tool is a blocker they cannot approve.

Risk 6Photo quality on cheap phones and bad lot lighting produces packets that look unconvincing.

Mitigation

Angle prompts, a minimum-brightness warning and a re-shoot nudge before the wizard allows sealing.

Validation experiment

Run three handovers at night under lot lighting and review the PDF with an operator.

Kill criteria

Operators reject the packet quality as unusable in two of three night tests.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Buy the domain and create Vercel and Supabase projects
  • Push the Next.js skeleton
  • Write schema for operators, vehicles, handovers, photos, acceptances, packets

Output: Deployed app with a working login

Hours 3-5

  • Build the eight-angle capture wizard
  • Add client-side downscale and Supabase Storage upload
  • Test on a real phone in a car park

Output: Eight photos stored against a handover row

Hours 6-8

  • Build the tap-on-diagram pin component
  • Build the renter acceptance page with licence capture, consent and typed name
  • Record acceptance timestamp and IP

Output: A renter link that writes an acceptance record

Hours 9-11

  • Implement the canonical SHA-256 sealing route
  • Build the packet PDF template with hash footer
  • Wire Resend delivery to operator and renter

Output: One sealed packet delivered to two inboxes

Hours 12-14

  • Build the first 20 operator list rows from Google Maps and Instagram
  • Write the master Loom script
  • Draft the DM and phone scripts

Output: A 20-row spreadsheet and a Loom script ready for day 6

Complete report

Full 30-day launch report

Read the full generated report

HandoverSeal - 30-Day Solo Launch Report

Window: Monday 16 November 2026 13:00 UTC to Wednesday 16 December 2026 13:00 UTC. One founder, no team, no ad budget at the start.

1. Product opportunity and positioning

HiGear did not die of weak demand. It died because four cars worth $300,000-$400,000 were handed to people using stolen identities, and the handover record could not survive a dispute. Operators still renting $60k-$400k cars direct through Instagram and WhatsApp inherited that risk minus the process: pickups run on a phone photo dump and a paper sheet nobody signs.

HandoverSeal is not a marketplace, booking calendar or insurance product. It is the documentation layer on top of bookings the operator already has. At pickup the operator opens a mobile web wizard: eight guided angles, odometer and fuel, damage pins tapped onto a car diagram, the renter's licence behind a consent screen. The renter opens a link, reviews condition and deposit terms, types their name, accepts. The system emits a sealed PDF - photos, readings, pins, terms, acceptance timestamp, IP and a SHA-256 hash of the packet - emailed to both parties. At return the same wizard outputs a delta sheet of new damage only.

The wedge is narrow on purpose. The buyer already owns cars and bookings, so the product replaces one recurring step: no marketplace cold start, no SEO ramp, no procurement cycle. One owner decides, and $99 sits below the threshold where they call a lawyer.

JEV scored the concept 6.4/10 (band C, confidence 0.64): strong on speed to first revenue (7.8) and solo build feasibility (7.4), weak on market demand (4.6) and operational simplicity (4.7). Both weaknesses are answered here by narrowing the target to operators with a dispute inside the last 90 days, and by avoiding KYC vendors, human review and long-lived regulated data.

The real alternative is a WhatsApp album. The difference is not sharper photos; it is the acceptance event and the hash. An album proves a photo existed. A sealed packet proves what the renter agreed to, when, and that nothing in it changed.

2. Smallest sellable MVP

Ship seven things: vehicle profiles; a mobile capture wizard; a damage pin diagram carried forward between rentals; a renter acceptance page with licence photo and typed-name consent; a sealed PDF with SHA-256 hash emailed to both parties; a return delta sheet; Stripe Checkout with plan limits.

Out of scope for all 30 days: KYC vendors, booking calendar, deposit escrow, native apps, telematics, insurance or legal positioning, and any 24/7 support promise.

Demo flow: enter a plate and declared value, capture eight angles on a phone, pin a scuff and type the odometer, have the renter accept on a second phone, watch the PDF with hash arrive in both inboxes, then run a return check-in that shows the one new pin as a delta.

3. Technical implementation plan

Next.js on Vercel, Supabase Postgres and Storage with row-level security, Stripe Checkout and Billing, Resend, @react-pdf/renderer, a Node serverless hashing route and a cron for retention deletion.

Build order: schema and auth; capture and upload; pin diagram; acceptance page; hash and PDF; email delivery; return delta; Stripe gating; retention cron.

The sealing route must be exactly right. Sort photo checksums and metadata canonically, hash the concatenation, store the hash against the packet ID, print it in the PDF footer and the email body. Regenerating a packet must reproduce the same hash or the promise is dead.

Hardest risk: an eight-photo packet can reach 20MB, render slowly on a mid-range Android in a car park and bounce in email. Mitigate with client-side downscale to 1600px at JPEG 0.75, an 8MB packet ceiling, and a signed download link as primary delivery with the attachment only under 5MB.

No AI in v1. Sealing is deterministic hashing, not inference. Odometer OCR is the first post-revenue candidate.

4. Pricing and monetization

Single Seal at $39 one-time for one handover. Starter at $99/month for 25 sealed handovers, unlimited vehicles and the packet archive. Fleet at $249/month for unlimited handovers, operator logo and custom terms, multi-user lot staff and CSV export for insurer and chargeback submissions.

The mechanic is the free sealed packet, then Starter when the second handover opens. Single Seal exists so a hesitant buyer pays $39 instead of walking, and doubles as the on-ramp: the checkout success page offers Starter with $39 credited. After month one, Fleet for operators past five cars, and per-packet overage above the Starter cap instead of a hard stop.

5. First-customer acquisition

One channel: Instagram DM carrying a personalised 60-second Loom, then a WhatsApp or SMS to the business number the next morning. No ads, no content marketing, no cold email.

Build 120 rows from Google Maps searches for exotic and luxury car rental in Miami, Los Angeles, Las Vegas, London, Dubai and Gold Coast, from the hashtags #exoticcarrental and #luxurycarrental, and from tagged-location pages. Capture owner name, phone, handle and one advertised car.

For the top 30, record the Loom on that exact car: run it through the wizard, show the sealed PDF and hash, close by offering their first three handovers sealed free. One phone follow-up, one final DM, then stop.

The offer removes risk: a free sealed packet for their next real rental, no card. Payment is asked only after two uses.

6. 30-day execution roadmap

Days 1-5 build. Days 1-4 cover wizard, acceptance, hash, PDF and email; day 5 adds the return delta and Stripe gating so a payable product exists before the first call. Days 6-8: three self-run handovers, 60 list rows, a master Loom plus five personalised cuts.

Days 9-14 sell. Ten DMs a day, phone follow-ups on the prior batch, free packets for every reply. Day 11 runs a live handover with an operator on a call. Day 12 is the first-sale target: the Stripe link goes into a thread that already used a free packet. Day 14 is a retro plus the $39 checkout.

Days 15-21 convert. Second-handover conversions, delta-sheet fixes, a CSV export stub, the first introduction ask, final follow-ups to non-repliers, and the list grown to 120.

Days 22-30 compound. Fleet with logo, custom terms and multi-user; licence-photo auto-delete; a warm-replier push framed on the 16 December cutoff; reconciliation against Stripe before 13:00 UTC on the closing day.

Every day closes with three numbers written down: DMs sent, replies, packets sealed.

7. Revenue and profit scenarios

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

Conservative: 3 Starter subscribers, $297 collected, $12 processing, $60 operating cost, nothing else. Hackathon profit $285; business profit $225.

Base: 10 subscribers, $990 collected, $39 processing, $85 operating cost. Hackathon profit $951; business profit $866.

Upside: 25 subscribers, $2,475 collected, $97 processing, $39 refunds, $120 paid promotion on two reels, $145 operating cost. Hackathon profit $2,219; business profit $2,074.

The contest ranks hackathon profit, which excludes hosting, domains, tooling and delivery cost; business profit subtracts them. Operating cost stays in the $60-$145 band because everything runs on low Vercel and Supabase tiers plus a domain. The only cost that scales with customers is PDF rendering, negligible at these volumes, so every sale covers delivery cost by a wide margin and no sale is priced below cost.

8. Main risks and validation experiments

Payment refusal: operators may treat documentation as a free habit. Test by charging $39 after the free packet from day 9 and counting how many free-packet users pay. Kill signal: fewer than 1 in 8 pays across the first 20 packets.

Evidence value: an acceptance page may not satisfy a card network. Test by walking three operators through filing it in a real chargeback and logging the missing field. Kill signal: all three name the same gap and say it would not have helped.

Channel starvation: DMs get flagged. Measure reply rate on the first 30. Under 10% means the Loom angle or the segment is wrong. Kill signal: under 5% after two openers.

List size: fewer than 120 reachable operators caps the upside case. Test by trying to build 40 rows in one metro in two hours. Kill signal: fewer than 40 verified rows across two metros in four hours.

Data liability: licence photos create obligations. Consent copy, 90-day auto-delete and an export-then-purge path ship before the 25th customer, not after.

9. First 24-hour action plan

Hours 1-2: domain, Vercel and Supabase projects, repo skeleton, schema for operators, vehicles, handovers, photos, acceptances and packets. Output: a deployed login.

Hours 3-5: capture wizard with client-side downscale writing into Supabase Storage. Output: eight photos from a real phone in a bucket.

Hours 6-8: pin diagram and the acceptance page with typed name, consent and licence capture. Output: a link that writes an acceptance row.

Hours 9-11: canonical hash route, PDF template and Resend delivery to two addresses. Output: one sealed packet in two inboxes.

Hours 12-14: the first 20 list rows and the master Loom script. Output: a spreadsheet and a script ready for day 6.

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 →