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

VanWitness Handover

VanWitness turns a 3-minute phone walkaround into a signed, timestamped campervan handover PDF that protects small rental operators from damage disputes.

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.06/10
MVP build (solo)
5 days
Launch price
$499
Sales to $1,000 revenue
3 customers
First paying customer
Direct cold email to independent campervan hire operators found on Google Maps in the UK, France and Spain, offering a free sample handover PDF from three photos of their own van.
Who pays

Owner-operator of a 1-15 vehicle campervan or motorhome rental company in the UK, France, Spain or Germany, 1-5 staff, triggered by an upcoming booking or a recent deposit dispute.

Biggest execution risk

Market demand 4.2/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 11; 3 sales at $499 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.1/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

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

0/8
Entry price
$499
Solo build
5 days
30d base revenue
$4,990
30d hackathon profit
$4,765
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a 1-15 vehicle campervan or motorhome rental company in the UK, France, Spain or Germany, 1-5 staff, triggered by an upcoming booking or a recent deposit dispute.

Why now

Operators have vans and bookings today and no liquidity problem to solve; the artifact replaces an existing manual ritual and can be demonstrated on their own van photos in a 15-minute call.

Problem

Handovers are documented with scattered WhatsApp photos, paper forms and memory, so return-day damage arguments become he-said-she-said and deposits are withheld late or written off.

Solution

A mobile web app: pick a vehicle, follow a guided 12-shot photo checklist, pin damage on a campervan outline, log odometer, fuel and cleanliness, capture the renter signature, and email both parties a timestamped PDF; a return mode links back and produces a pre/post comparison PDF.

Differentiation · Not WhatsApp photo dumps, not paper forms, not a booking platform: one forced, consistent evidence artifact with a damage map and a signature, delivered to both inboxes before the van leaves.

Opportunity and positioning

Campervan rental is a trust business run on improvised paperwork. A small operator with four vans hands over a vehicle at 9am on a Saturday with a phone full of reference photos, a paper sheet nobody signs, and a memory of where the last scratch was. Three weeks later the van comes back with a cracked bumper and the argument is unwinnable: no consistent photo set, no timestamp, no renter signature, no shared record. The operator either eats the repair or damages the relationship with a customer who may book again.

VanWitness Handover sells into that exact moment. It is not a marketplace, does not list vans, does not connect renters, does not process rental payments and does not sell insurance. It is the supply-side tool that produces one defensible document: a timestamped, signed handover PDF emailed to the operator and the renter before the van leaves the yard, plus a linked return report that puts before and after side by side.

The buyer is narrow on purpose: the owner-operator of a 1-15 vehicle campervan or motorhome hire business in the UK, France, Spain or Germany, with one to five staff. This person answers their own email, decides alone, and can pay $499 without procurement. The trigger is concrete — an imminent booking, or a damage or deposit dispute that just cost them money. That trigger is why a cold email with a free sample PDF built from their own van can start a conversation; it lands on a live nerve rather than an abstract efficiency pitch.

Competitive reality: rental management platforms bundle checklists, and big operators use fleet software. But the long tail of independent hire firms is running on WhatsApp and paper because those platforms are priced and shaped for larger fleets. VanWitness wins by being the smallest possible thing that produces the artifact, at a one-time price below a single disputed bumper repair.

The wedge holds because the founder can deliver the entire value in the sales conversation: take three photos of the operator's van, send back a filled-in sample report the next morning. No integration, no data migration, no onboarding project, no regulatory approval — the output is an evidence record, not insurance or a legal guarantee. Everything the operator needs to see is in one PDF they can forward to their own customer.

JEV scores this concept 6.06 weighted (band C, confidence 0.73), strongest on speed to first revenue (8.11 normalized) and solo build feasibility (7.62), weakest on market demand (4.24) and monetization (4.87). The plan below attacks those two weak spots directly: narrow to operators with an active dispute or a new-season fleet, and make the $499 licence attach to a measurable avoided loss rather than a vague sense of tidiness.

Section 2 of 8

Smallest sellable MVP

A mobile web app where a paying operator creates a vehicle, completes a guided 12-photo inspection with a damage pin map and renter signature, and gets a timestamped PDF emailed to both parties — plus a linked return report producing a pre/post comparison PDF.

Must-have features

  • Operator account with magic-link login and Stripe $499 checkout that unlocks reporting
  • Vehicle profiles with registration, photo and campervan outline template
  • Guided 12-shot photo checklist that blocks progress until every slot is filled
  • Odometer, fuel level and cleanliness inputs
  • Damage pin map on a campervan outline with note and severity
  • Renter signature pad plus renter email capture on the operator's phone
  • Timestamped handover PDF rendered and emailed to operator and renter via Resend
  • Return inspection linked to the original report, generating a pre/post comparison PDF
  • Dashboard listing all reports with download links and timestamps

Explicitly out of scope

  • No marketplace, listing or renter discovery
  • No booking calendar, deposits, rental payments or contracts
  • No insurance, roadside assistance or claims adjudication
  • No AI damage detection or repair estimates
  • No native iOS or Android app
  • No multi-language UI
  • No fleet software integrations or enterprise SSO

Demo flow (what the buyer sees)

  1. Founder opens a sample vehicle already loaded with the operator's three van photos.
  2. Founder runs the 12-shot checklist on a phone in under three minutes, ticking each slot.
  3. Founder pins two pre-existing scratches on the van outline and sets severity.
  4. Founder enters odometer and fuel, hands the phone to a colleague to sign as renter.
  5. PDF is rendered, emailed to both inboxes, and opened on screen within 20 seconds.
  6. Founder opens return mode, marks one new scuff, and shows the side-by-side comparison PDF.
Build plan

Technical implementation plan

Stack

Next.js (App Router) on VercelSupabase Auth (magic link) and PostgresCloudflare R2 for photo storage with signed upload URLsStripe Checkout (one-time $499) and webhook licence activationResend for transactional email with PDF attachments@react-pdf/renderer for handover and comparison PDFsTailwind CSS for the mobile capture flowUpstash Redis for rate limiting sample generation

Architecture

A single Next.js app on Vercel serves both marketing pages and the authenticated operator app. Supabase handles login and stores operators, vehicles, inspections, photos metadata, damage pins and signatures. Photos go straight from the phone browser to R2 via signed URLs so no image bytes pass through the server function. When an inspection is completed, a serverless route pulls the inspection row plus photo URLs, renders the PDF in memory with @react-pdf/renderer, uploads the PDF to R2 for the dashboard download link, and emails it through Resend to operator and renter. Return mode reads the original inspection id and renders a second PDF that pairs photo slots. Stripe Checkout creates a licence row via webhook; a licence flag gates report generation so unpaid accounts can browse but not export.

Build steps

  1. Scaffold Next.js app, connect Supabase, deploy an empty authenticated dashboard to Vercel.
  2. Create tables: operators, vehicles, inspections, inspection_photos, damage_pins, licences.
  3. Build vehicle CRUD with R2 photo upload and outline template selection.
  4. Build the mobile inspection flow with 12 fixed photo slots and completion guard.
  5. Add odometer, fuel, cleanliness and damage pin map with notes and severity.
  6. Add signature pad and renter email capture; store PNG signature in R2.
  7. Render the handover PDF with @react-pdf/renderer and send via Resend.
  8. Add return mode, photo pairing, and the pre/post comparison PDF.
  9. Wire Stripe Checkout in live mode plus webhook that flips licence_active.
  10. Add dashboard report list, download links and email resend action.
  11. Harden: signed URL expiry, file size caps, retry on email failure, error logging.
  12. Build the internal no-signup sample generator that accepts three uploaded photos.

AI components

  • No LLM or model in the MVP; no AI damage detection, captions or estimates by design.
Hardest technical risk: PDF rendering on serverless with 12+ remote images: timeouts and memory limits can fail a report mid-render and leave an operator with no artifact at the moment the van is leaving. Mitigate by pre-resizing images at upload, rendering with a 30-second timeout, and emailing a fallback ZIP of photos if PDF generation fails.
Section 3 of 8

Pricing and monetization

Founding Fleet Licence

Entry offer
$499 one-time

For Independent campervan or motorhome hire operator with up to 25 vehicles

  • Unlimited handover and return reports for 12 months
  • Up to 25 vehicle profiles
  • Branded PDF handover reports
  • Pre/post comparison PDF
  • Email delivery to renter and operator

Model: One one-time Founding Fleet Licence at $499 per operator, covering 12 months of unlimited reports and up to 25 vehicle profiles.

First revenue offer: Send a free sample handover PDF built from three of the operator's own van photos within 24 hours, then a Stripe link for the $499 Founding Fleet Licence with a 15-minute activation call slot.

Expected ACV: $499

Upsell path: Within the window, ask each buyer whether a second depot or sister company needs its own licence, and ask for two named operator introductions. After the window, expansion comes from additional fleet licences and the 12-month renewal; no monthly plan is introduced during the 30 days.

Target customers
200
Revenue model
$99,800
Costs
$3,200
Profit model
$96,600
Section 4 of 8

First-customer acquisition

Primary channel

Direct cold email to independent campervan hire operators found on Google Maps in the UK, France and Spain, offering a free sample handover PDF from three photos of their own van.

Where to find them

  • Google Maps searches: campervan hire Bristol, motorhome hire Manchester, campervan hire Edinburgh
  • Google Maps searches: location camping-car Lyon, location van aménagé Bordeaux
  • Google Maps searches: alquiler autocaravana Valencia, alquiler autocaravana Sevilla
  • Google Maps searches: Wohnmobil Vermietung Hamburg, Camper Vermietung München
  • Campervan hire directories and local tourism listings linking to independent operators
  • Owner-run Facebook groups for campervan rental and motorhome hire where vendor posts are permitted

Exact outreach motions

  • Email 1: short note offering a free sample PDF using three photos of one of their vans, no signup.
  • Reply to every sample request within 24 hours with a filled PDF carrying their registration and damage map.
  • Follow up once after 48 hours on the same thread with the sample attached.
  • Invite warm repliers to a 15-minute call to run the report live on their own van.
  • Send the Stripe $499 link during or immediately after the call.
  • Post the sample PDF angle in two or three owner groups only where rules allow vendor posts.
  • Ask every buyer for two named operator introductions and email those names directly.

Message template

Subject: A signed handover report for one of your vans

Hi [Name] — I build a tool that turns a 3-minute phone walkaround into a signed, timestamped handover PDF for campervan rentals: 12 photos, damage pinned on a van outline, odometer, renter signature, emailed to you and the renter before the van leaves.

Want a free sample using three photos of one of your vans? Send them over and I will send the finished PDF back within 24 hours. No signup, no call needed.

[Founder name] — VanWitness Handover
Week-one goal: 110 verified operator contacts in the sheet, 40 personalised emails sent, and at least 2 sample PDF requests received by end of day 7.
Section 5 of 8

30-day execution roadmap

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

Live skeleton plus list start

  • Create Next.js and Supabase project, deploy to Vercel.
  • Wire magic-link auth and an empty dashboard.
  • Create Stripe $499 product in test mode and verify Resend sending domain.
  • Build a 50-row UK operator list from Google Maps.

Deliverable: Live app shell with login and 50 verified operator emails.

Day 2Vehicles

Vehicle profiles and storage

  • Vehicle create/edit with registration and photo upload to R2.
  • Store outline template per vehicle.
  • Dashboard table of vehicles and past reports.

Deliverable: Operator can add three vans with photos and see them listed.

Day 3Inspection

Guided 12-shot capture flow

  • Mobile capture flow with 12 required slots and a completion guard.
  • Odometer, fuel and cleanliness inputs.
  • Persist the inspection draft to Postgres at each step.

Deliverable: A complete 12-shot pickup inspection saved from a phone.

Day 4Evidence

Damage map, signature, PDF

  • Damage pin map on the campervan outline with note and severity.
  • Signature pad plus renter email capture.
  • Render the handover PDF and email it via Resend.

Deliverable: Signed handover PDF delivered to operator and renter inboxes.

Day 5ShipMVP shipped

Return mode and live checkout

  • Return inspection linked to the original report.
  • Pre/post comparison PDF with paired photos.
  • Switch Stripe to live mode with webhook licence activation.

Deliverable: MVP live at the domain; $499 checkout unlocks unlimited reports.

Day 6Samples

Sample pipeline and list expansion

  • Internal no-signup sample generator accepting three uploaded photos.
  • Add 60 French and Spanish operators to the sheet.
  • Write three subject-line variants and a tracking sheet.

Deliverable: Working sample generator and a 110-row contact sheet.

Day 7Outreach

First send wave

  • Send 40 personalised emails offering the free sample PDF.
  • Log every send with a follow-up date.
  • Reply to sample requests within two hours.

Deliverable: 40 sends logged and 2-4 sample requests in flight.

Week 2 · Launch & first sale · 7 days
Day 8Samples out

Deliver proof, keep sending

  • Send 60 more emails.
  • Produce and return three sample PDFs.
  • Publish a one-page public sample PDF with a checkout link.

Deliverable: Three sample PDFs delivered; public sample page live.

Day 9Distribution

Groups and follow-ups

  • Post the sample angle in two owner groups where rules allow.
  • Send 50 more emails.
  • Follow up once on the day-7 non-repliers.

Deliverable: 150 cumulative sends and two group posts live.

Day 10Calls

Convert replies into calls

  • Add the Stripe payment link into the email signature and PDF footer.
  • Book five 15-minute calls.
  • Write a six-line call script: dispute story, sample, price.

Deliverable: Five calls booked with a clickable payment link.

Day 11First saleFirst sale target

Run calls and close

  • Run calls using the operator's own van photos.
  • Send the checkout link during the call.
  • Manually onboard any paying operator the same day.

Deliverable: First paid $499 licence.

Day 12Friction

Fix what calls exposed

  • Fix the top three onboarding blockers from calls.
  • Add operator logo upload for branded PDFs.
  • Collect three verbatim operator lines for email copy.

Deliverable: v1.1 deployed and a three-line quote bank.

Day 13Wave two

Wider European sends

  • Send 80 emails to French, Spanish and German operators.
  • Swap in the best-performing subject line.
  • Add an objection-handling block to the email.

Deliverable: 80 sends out with revised copy.

Day 14Review

Measure and cut

  • Measure sends, opens, replies, samples, calls, sales.
  • Drop the worst subject line and worst segment.
  • Set the week-three send target.

Deliverable: Metrics row and a week-three target list.

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

List building and sends

  • Build 150 more contacts in Germany and northern UK.
  • Send 80 emails.
  • Answer every sample request within 24 hours.

Deliverable: 260 cumulative contacts and 80 sends.

Day 16Volume

Samples and clarity

  • Send 80 emails.
  • Deliver four sample PDFs.
  • Add a three-line what-it-replaces section to the sample email.

Deliverable: Four samples delivered and 340 cumulative sends.

Day 17Close

Second sales push

  • Offer a 15-minute activation call in every sample reply.
  • Follow up with all day-11 call leads.
  • Record a 90-second phone screen demo.

Deliverable: Demo clip plus three live follow-ups.

Day 18Proof

Show evidence visually

  • Send 80 emails.
  • Publish an anonymised before/after photo pair on the sample page.
  • Ask each buyer for one referral name.

Deliverable: Sample page v2 and referral asks sent.

Day 19Support

Bound the support load

  • Write a six-step self-serve setup note and link it everywhere.
  • Add an in-app tooltip on the 12-shot checklist.
  • Set a two-hour daily support window.

Deliverable: Self-serve setup doc and a bounded support window.

Day 20Expansion

Second depot and non-openers

  • Ask buyers whether a second depot needs its own licence.
  • Re-touch all non-openers once.
  • Log any refund reason verbatim.

Deliverable: Expansion asks and non-opener re-touch complete.

Day 21Review

Double down on the best segment

  • Compare conversion by country and by email angle.
  • Double sends to the best-converting segment.
  • Fix the single biggest checkout objection.

Deliverable: Segment decision and a deployed copy fix.

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

High-volume sends

  • Send 100 emails to the best segment.
  • Deliver five sample PDFs.
  • Batch calls into a single two-hour block.

Deliverable: 100 sends and five samples delivered.

Day 23Sprint

Reach and receipts

  • Send 100 emails.
  • Post the sample angle in two more owner groups.
  • Automate a receipt PDF in the checkout email.

Deliverable: 200 sends this week and automated receipts.

Day 24Conversion

Clear warm leads

  • Call every replying contact who has not paid.
  • Add a 30-day money-back line to the checkout email.
  • Onboard new licences same day.

Deliverable: Warm-lead call list cleared.

Day 25Referrals

Buyer-sourced leads

  • Ask every buyer for two named operator introductions.
  • Email those introductions referencing the buyer.
  • Track referral source on each sale.

Deliverable: Referral sends logged with source.

Day 26Sprint

Volume and quality

  • Send 100 emails.
  • Deliver remaining sample requests.
  • Fix any PDF rendering bug reported by buyers.

Deliverable: Clean PDF output and 100 sends.

Day 27Deadline

Cost of waiting

  • Email all non-buyers that the founding price closes December 16.
  • Confirm every buyer can log in and generate a report.
  • Reconcile Stripe payouts against TrustMRR.

Deliverable: Close date communicated and a reconciliation sheet.

Day 28Polish

Zero open issues

  • Resolve all open support threads.
  • Ship final PDF layout polish.
  • Export reports generated per customer.

Deliverable: Zero open support tickets and usage export.

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

Last call

  • Send 100 final emails with 'closes Wednesday'.
  • Call any unpaid warm lead once.
  • Confirm no pending refund requests.

Deliverable: Final send batch out and refund check complete.

Day 30Close

Reconcile and document

  • Verify Stripe balance and refunds fall inside the contest window.
  • Write a one-page changelog for January customers.
  • Archive all PDF reports and contact lists.

Deliverable: Final revenue and refund statement plus a January roadmap.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

Hackathon profit — Collected revenue − refunds − chargebacks − payment processing fees − paid marketing spend.

Business profit — Hackathon profit − operating costs (hosting, domains, tooling, AI/API delivery costs).

The contest ranks entrants on hackathon profit only. Hosting, tooling and AI/API delivery costs are not deducted by the organisers, but each sale still has to cover them — so we show both. Definitions verified on 2026-11-15 against the official rules.

Stated assumptions

  • Conservative: roughly 400 cold emails plus follow-ups produce 3 paid licences at $499 inside the 30 days.
  • Base: roughly 1,200 targeted emails, 8-12 operator calls and referrals produce 10 licences.
  • Upside: roughly 2,000 emails, permitted owner-group posts and buyer referrals produce 28 licences; this is a stretch and far below the concept's unvalidated 200-customer math.
  • ARPU is $499 in every case because the only offer is the one-time Founding Fleet Licence; no monthly plan is introduced in the window.
  • Payment fees assumed at a blended 4.5% of gross: Stripe 2.9% plus $0.30, plus about 1.5% for international cards in the UK and EU.
  • Refunds are zero in conservative and base; one refund is budgeted in the upside case because volume raises the chance of a poor-fit buyer.
  • Chargebacks are zero across all cases because licences are activated manually after a call and buyers receive a receipt PDF.
  • Operating costs cover Vercel Pro, Supabase Pro, Resend, Cloudflare R2, one domain and about $0.15 of rendering and storage per report.
  • Ad spend is zero in conservative and base because all outreach is organic; the upside case budgets $250 for permitted sponsored posts in owner groups.
  • Every figure is a projection built from the stated assumptions; no customers, revenue or traction exist yet.

Conservative

3 customers
$1,497
collected revenue · avg payment $499
Refunds
$0
Chargebacks
$0
Payment fees
$67
Paid marketing
$0
Hackathon profit
$1,430
Operating costs
$85
Business profit
$1,345

Base case

10 customers
$4,990
collected revenue · avg payment $499
Refunds
$0
Chargebacks
$0
Payment fees
$225
Paid marketing
$0
Hackathon profit
$4,765
Operating costs
$115
Business profit
$4,650

Optimistic

28 customers
$13,972
collected revenue · avg payment $499
Refunds
$499
Chargebacks
$0
Payment fees
$629
Paid marketing
$250
Hackathon profit
$12,594
Operating costs
$210
Business profit
$12,384

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$4,990
Payment fees (3.9%)
$195
Paid marketing
$0
Hackathon profit
$4,795
Business profit
$4,680

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. All figures are projections for the 30-day window only.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold email lands in spam or is ignored because the sender is an unknown solo founder.

Mitigation

Send from a warmed custom domain, plain text, no images, one link maximum, and offer the free sample PDF with no signup as the only call to action.

Validation experiment

Send 40 emails across two subject lines on day 7 and count replies, not opens; if reply rate is under 3% after 200 sends, rewrite the offer before sending more.

Kill criteria

Fewer than 4 replies from 200 sends and no sample requests means the channel is dead and the offer must change before day 14.

Risk 2Operators already use rental management software that includes condition checklists, so they see a duplicate tool.

Mitigation

Position as the exportable evidence artifact, not the checklist: ask on every call what their current software produces for a dispute, and lead with the signed PDF.

Validation experiment

Ask five operators on calls to name their current tool and whether it emails a signed PDF to the renter; log the answer verbatim.

Kill criteria

If four of five interviewed operators already produce a signed PDF emailed to the renter, the core value is gone and the concept must be re-scoped.

Risk 3December is low season in parts of Europe and operators defer buying until spring.

Mitigation

Target operators with a live dispute or a fleet-prep trigger, and use the closing founding price on December 16 as a concrete reason to act now.

Validation experiment

Tag each reply as 'has spring fleet prep' versus 'dormant'; compare conversion between the two tags after 40 replies.

Kill criteria

If no operator with an active dispute converts after 15 conversations, the urgency assumption is wrong.

Risk 4The PDF is treated as a legal guarantee and an operator refunds after a dispute goes badly.

Mitigation

State in the PDF footer and the checkout email that this is an evidence record, not insurance or legal advice, and keep the capability scope narrow.

Validation experiment

Ask three buyers to read the footer and repeat back what the document does; note any misunderstanding.

Kill criteria

Two or more refund requests citing legal expectations means the framing must be fixed before any further selling.

Risk 5A solo founder is swamped by onboarding and support at 15-25 licences while still selling.

Mitigation

Self-serve setup note linked in every email, a two-hour daily support window, and a fixed activation call slot instead of ad-hoc requests.

Validation experiment

Track minutes per onboarding on the first five buyers; if it exceeds 30 minutes each, cut the activation call from the offer.

Kill criteria

Onboarding exceeding an hour per buyer with no reduction after two iterations means the offer is too hands-on for one person.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create the repository.
  • Scaffold Next.js, commit, deploy to Vercel and confirm the live URL responds.

Output: Live URL serving a placeholder page.

Hours 2-4

  • Create Supabase project and enable magic-link auth.
  • Create tables: operators, vehicles, inspections, inspection_photos, damage_pins, licences.

Output: Working login and a signed-in empty dashboard.

Hours 4-6

  • Create Stripe product at $499 one-time and capture the payment link.
  • Verify the Resend sending domain and send a test email to yourself.

Output: Payment link and verified sending domain.

Hours 6-8

  • Build the first 30 rows of the UK operator list from Google Maps with emails.
  • Draft the sample-PDF outreach email and three subject lines.

Output: 30-row contact sheet and the first email draft ready to send on day 7.

Complete report

Full 30-day launch report

Read the full generated report

VanWitness Handover — 30-Day Launch Report

1. Product opportunity and positioning

Campervan hire runs on trust and improvised paperwork. A four-van operator hands over a vehicle at 9am Saturday with phone photos nobody signs and a memory of where the last scratch was. Three weeks later a cracked bumper comes back and the argument is unwinnable: no consistent photo set, no timestamp, no signature, no shared record. The operator eats the repair or withholds a deposit and damages a repeat customer.

VanWitness Handover sells into that moment. It is not a marketplace and does not list vans, connect renters, process rental payments or sell insurance. It produces one artifact: a timestamped, signed handover PDF emailed to operator and renter before the van leaves, plus a linked return report with a pre/post comparison.

The buyer is deliberately narrow: owner-operator of a 1-15 vehicle campervan or motorhome hire business in the UK, France, Spain or Germany, one to five staff, who answers their own email and pays without procurement. The trigger is a live booking or a recent damage dispute. That trigger is what makes a cold email with a free sample PDF built from their own van land on a nerve instead of a theory.

JEV scored this concept 6.06 weighted (band C, confidence 0.73). Strengths: speed to first revenue at 8.11 normalized and solo build feasibility at 7.62. Weaknesses: market demand at 4.24 and monetization at 4.87. The plan below attacks those two directly by qualifying for urgency and tying the price to a specific avoided loss.

2. Smallest sellable MVP

A paying operator creates a vehicle, runs a guided 12-photo inspection, pins damage on a campervan outline, logs odometer and fuel, captures the renter signature, and receives a PDF emailed to both inboxes. Return mode links to the original and renders a comparison PDF. Nothing else ships: no calendar, no deposits, no renter discovery, no AI detection, no native apps.

The demo is the product. Take three photos of the operator's van, generate the report, open it on screen during a 15-minute call.

3. Technical implementation plan

Next.js on Vercel, Supabase for auth and Postgres, Cloudflare R2 for photos via signed upload URLs, Stripe Checkout for the $499 licence with webhook activation, Resend for delivery, @react-pdf/renderer for both PDFs. Photos never pass through the serverless function, which keeps memory and latency low.

The hardest risk is PDF rendering at the worst possible moment: 12+ remote images, a cold start and a timeout can produce no artifact while the van is leaving. Mitigations are pre-resizing at upload, a 30-second render budget, and an automatic fallback email containing a photo ZIP if rendering fails.

No AI component exists in the MVP by design. That removes model cost, latency and any temptation to over-claim accuracy.

4. Pricing and monetization

One offer: the Founding Fleet Licence at $499, one-time, covering 12 months of unlimited reports, up to 25 vehicle profiles, branded PDFs and renter delivery. The price is set against a single disputed repair or a written-off deposit, not against software alternatives. No monthly plan is introduced in the window; adding tiers would slow the close and muddy the offer.

Revenue grows after the first sale through second-depot licences for operators with more than one yard, buyer referrals, and the renewal in month 13. Every licence is activated on a call so no seat is sold without someone able to use it.

5. First-customer acquisition

One channel: direct cold email to independent campervan hire operators on Google Maps in the UK, France and Spain, offering a free sample handover PDF from three of their own photos. No ads. The email is plain text, one link, one call to action. Replies get a finished PDF within 24 hours, a follow-up after 48 hours, and a 15-minute activation call. Owner-run Facebook groups are used only where vendor posts are explicitly allowed.

Week one target: 110 verified contacts, 40 sends, at least two sample requests.

6. 30-day execution roadmap

Day-by-day tasks are in the roadmap object. Milestones:

WeekDatesMilestone
1Nov 16-22MVP live day 5, 110 contacts, 40 sends
2Nov 23-29First paid licence target day 11, 150 sends, 5 calls
3Nov 30-Dec 6340 cumulative sends, support bounded, referrals started
4Dec 7-13200 sends in week, warm leads cleared, closing date announced
5Dec 14-16Final push, reconciliation, archive

Build is front-loaded into five days so selling starts on day 6 and occupies 24 of the 30 days. The rule is simple: no day passes without outreach sent, and no sample request ages past 24 hours.

7. Revenue and profit scenarios

All figures are projections from stated assumptions, not verified revenue.

  • Conservative: 3 licences, $499 ARPU, $1,497 gross, $67 fees, $0 refunds, $0 ad spend, $85 operating costs. Hackathon profit about $1,430; business profit about $1,345.
  • Base: 10 licences, $4,990 gross, $225 fees, $115 operating costs. Hackathon profit about $4,765; business profit about $4,650.
  • Upside: 28 licences, $13,972 gross, $499 refunded, $629 fees, $250 ad spend, $210 operating costs. Hackathon profit about $12,594; business profit about $12,384.

The concept's 200-customer math is not treated as a plan; it requires a conversion rate this plan does not assume.

8. Main risks and validation experiments

The five risks are listed with mitigations, experiments and kill criteria in the JSON. Three tests run early and cheaply: a 40-email A/B on day 7 to test reply rate; a five-call question about what their current software actually produces for a dispute; and a footer read-back test to confirm buyers understand the PDF is an evidence record, not insurance. Any kill criterion firing before day 14 triggers an offer rewrite, not more volume.

9. First 24-hour action plan

Hours 1-2: domain, repo, Vercel deploy. Hours 2-4: Supabase auth and schema. Hours 4-6: Stripe $499 product and verified Resend domain. Hours 6-8: first 30 UK operator contacts and the outreach draft. By hour 8 the app exists, the checkout works and the first emails are ready for day 7.

Scenario models from stated assumptions, not verified revenue.

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 →