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

DockProof Handover

A mobile web app that turns each boat rental handover into a timestamped, e-signed departure-vs-return condition report PDF, so small charter operators can defend damage deposits instead of arguing over WhatsApp photos.

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.27/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct Instagram DM and email to 200 named small charter operators, each message carrying a sample DockProof report built from that operator's own public boat photo.
Who pays

Owner-operator of a small boat rental or charter business with 2-15 boats (day boats, bareboats, small crewed charters) selling direct via their own site and Instagram plus one listing platform, in Gold Coast, Cairns, Florida Keys, Miami, the Canary Islands or Phuket.

Biggest execution risk

Market demand 4.4/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; 21 sales at $49 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.5/10.

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

Your first 24 hours

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

0/12
Entry price
$49
Solo build
5 days
30d base revenue
$2,388
30d hackathon profit
$2,244
Section 1 of 8

Product opportunity and positioning

Target customer

Owner-operator of a small boat rental or charter business with 2-15 boats (day boats, bareboats, small crewed charters) selling direct via their own site and Instagram plus one listing platform, in Gold Coast, Cairns, Florida Keys, Miami, the Canary Islands or Phuket.

Why now

December is peak or shoulder season in every target market, so operators are running handovers daily and a disputed deposit is a live, already-budgeted loss rather than a hypothetical; the buyer is a named business with a public phone number and Instagram handle, reachable without a marketplace cold-start.

Problem

When a boat returns with a scratched hull, bent cleat, missing fender or fuel discrepancy, the operator has no defensible record of its departure condition, so deposit deductions get disputed, bad reviews land, chargebacks are filed and damage-waiver claims are refused for lack of evidence.

Solution

Operator opens a trip, captures 12 named photo slots plus numeric fuel and engine-hour readings, and the renter types and draws a signature; on return the same 12 slots are repeated and DockProof auto-generates a server-timestamped, SHA-256-hashed PDF with paired photos, fuel and hour deltas, damage callouts, a deposit deduction summary and both signatures.

Differentiation · It is not a marketplace, booking engine or insurance product and needs no platform integration: it produces one signed, hash-sealed artifact per trip, whereas the generic alternative is an unordered camera roll plus a paper form with no renter signature and no audit trail.

1. Product opportunity and positioning

DockProof Handover sells to exactly one buyer: the owner-operator of a 2-15 boat rental or charter business in a warm-water peak-season market — Gold Coast, Cairns, Florida Keys, Miami, the Canary Islands, Phuket. That operator already loses money at the handover moment. A hull comes back with a bent cleat, a missing fender or a fuel delta, the only record is an unordered WhatsApp photo thread with no booking reference and no renter signature, and a legitimate deposit deduction turns into an argument, a one-star review or a card chargeback.

The JEV score for this exact concept is 62.7/100 (band C, confidence 0.74). Speed to first revenue is the strongest criterion at 8.47: the buyer has a public phone number and an Instagram handle, so the first paying customer is one direct message away. Solo build feasibility (7.26) and reachable customers (7.30) are also solid, because nothing here depends on integration with Click&Boat, GetMyBoat or Boatsetter. The flagged weakness is market demand at 4.39, and this plan is built to answer that weakness rather than deny it. Every outreach message leads with a specific, already-budgeted loss — the disputed deposit or refused damage-waiver claim — and a named trigger event, the next weekend's returns. The free first report is delivered before price is mentioned, so the operator experiences the artifact before being asked to believe in it.

Positioning is deliberately narrow. DockProof is not a marketplace, a booking engine, an availability calendar or an insurance product. It does not hold or move renter deposits and it does not collect money on the operator's behalf. It sits on the operator's own phone and produces one artifact: a server-timestamped, hash-sealed, e-signed departure-versus-return PDF per trip. The generic alternative is a camera roll plus a paper form. The difference is that DockProof's output carries a renter signature, an IP-stamped audit trail and a side-by-side comparison page that can be attached to a card dispute or a listing-platform damage claim.

One honest constraint runs through the product and the sales copy: the report is a record, not a guarantee of any claim outcome. The PDF footer and the message template both say so, because a buyer who believes it guarantees a payout will refund the moment a claim is refused. At $49 to $399 one-time, bought out of a deposit-loss budget, no procurement cycle and no regulatory approval are involved.

Section 2 of 8

Smallest sellable MVP

One operator, one boat, one trip: a signed, server-timestamped departure-versus-return PDF the operator can attach to a deposit deduction or a chargeback response, generated from a 12-slot mobile capture flow.

Must-have features

  • Magic-link operator login plus a boat profile (name, registration, photo) and per-boat pass status
  • Mobile capture flow with 12 named photo slots, each carrying a one-line framing hint
  • Numeric fuel-gauge and engine-hour fields stored as numbers so deltas can be computed
  • Renter sign-off screen: typed name, drawn signature canvas, server timestamp, IP capture and SHA-256 hash of the report payload
  • Return flow reusing the same 12 slots with an auto-built paired departure-versus-return comparison page
  • Damage markers placed on any photo with a label and estimated cost, rolling into a deposit deduction summary
  • PDF render of the full report plus an expiring read-only share link emailed to renter and operator via Resend
  • Stripe Checkout for the three passes with report-count gating after 3 free reports
  • Dashboard listing open, returned and disputed trips with report status

Explicitly out of scope

  • No marketplace, listing syndication, availability calendar or booking engine
  • No holding or moving renter deposits and no payment collection on behalf of operators
  • No AI damage detection or automated photo grading
  • No native iOS or Android app — mobile web only
  • No API integrations with Click&Boat, GetMyBoat, Boatsetter or SamBoat
  • No multi-language localisation
  • No multi-user team permissions beyond one login per operator in the first 30 days

Demo flow (what the buyer sees)

  1. Operator opens a new trip for a named boat and enters renter name and booking reference
  2. Operator taps through 12 labelled camera slots and types fuel level and engine hours
  3. Renter types their name and draws a signature; the app stamps server time, IP and a SHA-256 payload hash
  4. On return the operator repeats the same 12 slots and records the new fuel and hour readings
  5. Operator taps a scratch on the return hull photo, labels it and enters an estimated cost
  6. DockProof renders the PDF with paired photos, fuel and hour deltas, the damage callout and a deposit deduction summary
  7. The PDF and an expiring share link are emailed to the renter and the operator
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres, Storage and AuthStripe Checkout plus webhookPuppeteer-based serverless PDF rendererResend for transactional email and share linksTailwind CSS with a camera-first mobile layoutWeb Crypto SHA-256 for payload hashing

Architecture

A single Next.js app on Vercel handles both the operator UI and the API routes. Supabase Auth issues magic links; Postgres holds operators, boats, trips, slots, signatures and passes; Storage holds downscaled photos with signed URLs. Each capture is written row-by-row, and a trip is sealed by computing SHA-256 over a canonical JSON serialisation of its rows plus the server timestamp, stored alongside the record. The return pass writes to the same 12 slot keys, so the comparison page and the PDF are pure reads. A serverless Puppeteer route renders one HTML report template to PDF, stores it in Storage and returns a signed URL with a 30-day expiry, which Resend emails to renter and operator. Stripe Checkout creates the pass; the webhook writes boat quota and a 12-month expiry to Postgres, and trip creation is gated on pass status after 3 free reports.

Build steps

  1. Day 1: create the Next.js repo, deploy to Vercel, define the Postgres schema and wire magic-link auth
  2. Day 1: build the boat profile and trip creation screens
  3. Day 2: build the 12-slot camera capture with framing hints, client-side downscale and Storage upload
  4. Day 2: add numeric fuel and engine-hour fields and the departure seal action
  5. Day 3: build the renter sign-off screen with signature canvas, typed name, IP capture and SHA-256 hashing
  6. Day 3: build the return pass reusing the same slot keys and compute deltas
  7. Day 4: build the paired comparison page with damage markers and the deposit deduction summary
  8. Day 4: render the PDF with Puppeteer, store it, generate the expiring share link and send both emails via Resend
  9. Day 5: wire Stripe Checkout and the webhook, add report gating, deploy and run a full self-serve trip end to end
  10. Day 5: dogfood on a real boat photo set and fix layout breaks on a small phone screen

AI components

  • None in the first 30 days — damage callouts are operator-placed markers, not model output, and no LLM or vision model sits in the delivery path; this keeps per-report delivery cost near zero and avoids overstating automated damage detection.
Hardest technical risk: Serverless PDF rendering of 24+ images into a paginated paired report is the most likely thing to time out or blow the function limit; mitigate by pre-resizing images to 1200px on upload, rendering with a headless Chromium layer sized for the task, and keeping the report HTML free of external assets.
Section 3 of 8

Pricing and monetization

Single Boat Pass

Entry offer
$49 one-time

For Private owner renting one boat peer-to-peer on a listing platform

  • 12 months of unlimited handover reports for one boat
  • Departure-versus-return comparison PDF
  • Expiring renter share link
  • Renter e-signature and audit trail

Fleet Pass

$199 one-time

For Owner-operator of a small rental or charter fleet with 2-5 boats

  • 12 months of unlimited reports for up to 5 boats
  • Operator logo and branding on the PDF
  • Damage annotation with deposit deduction summary
  • CSV export of all handovers and flagged damage

Marina Pass

$399 one-time

For Larger independent fleet or small marina with 6-20 boats

  • Everything in Fleet Pass for up to 20 boats
  • Per-boat sub-accounts with separate login
  • Bulk PDF export of a season's handovers

Model: One-time annual passes by fleet size: a per-boat entry price, a fleet price that covers most buyers, and a larger-fleet price, each unlocking 12 months of unlimited handover reports.

First revenue offer: I built your first DockProof report for free using your own boat photo — it is attached. If it is useful, the Fleet Pass is $199 for 12 months and up to 5 boats, and this link takes you straight to checkout.

Expected ACV: $199

Upsell path: Move Single Boat buyers to Fleet Pass when a second boat appears, move Fleet Pass buyers to Marina Pass at 6+ boats, and start a month-13 renewal email sequence in November 2027 that converts one-time passes into annual repeat revenue.

Target customers
35
Revenue model
$6,965
Costs
$280
Profit model
$6,685
Section 4 of 8

First-customer acquisition

Primary channel

Direct Instagram DM and email to 200 named small charter operators, each message carrying a sample DockProof report built from that operator's own public boat photo.

Where to find them

  • Google Maps listings for boat rental and charter businesses in Gold Coast, Cairns, Miami, Florida Keys and Tenerife, filtered to operators with 2-15 boats
  • Operator own websites, capturing boat names, owner first name, phone number and a usable boat photo URL
  • Instagram business accounts tagged in boat rental hashtags for those cities
  • GetMyBoat and Click&Boat listing pages, used only to identify operator names and fleet size, never integrated
  • Two boat-owner Facebook groups and r/boating for the secondary inbound loop

Exact outreach motions

  • Day 6-7: build the 200-row list in a spreadsheet with boat name, owner first name, IG handle, email and one boat photo URL per row
  • Day 7: generate 40 personalised sample PDFs using each operator's own listing photo, clearly labelled as a sample with one example damage callout
  • Day 8: send 25 Instagram DMs with the sample attached and the boat name in the first line
  • Day 8-14: reply to every response within the hour and build their first real report manually, free, before mentioning price
  • Day 10 and day 14: follow up with a 40-second screen recording of the diff page, not a pitch, tied to their next busy weekend
  • Day 9: send 25 emails to operators with no Instagram presence, same angle, sample PDF linked
  • Day 11: post the blank departure-versus-return template into two boat-owner Facebook groups and r/boating with a free-first-report offer
  • Day 15-26: sustain 25 personalised messages per day, five days a week, and log every reply and outcome

Message template

Hi {first_name} — I saw {boat_name} on your site. Right now the handover record is a WhatsApp photo, which proves nothing when a renter disputes a scratch. I built a sample signed departure-versus-return report for {boat_name} using your own photo — it is attached. Reply with the boat name and I will build your first real one free today, no card. It is a record, not a guarantee of any claim.
Week-one goal: 200 operators listed, 40 sample reports generated, 75 personalised messages sent, at least 6 real replies and 3 free reports delivered on real trips.
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

Schema, auth and deploy

  • Create the Next.js repo on Vercel with a camera-first mobile layout shell.
  • Define Postgres tables for operators, boats, trips, slots, signatures and passes.
  • Wire Supabase magic-link auth and the boat profile screen.

Deliverable: Deployed app with working login and a saved boat profile.

Day 2Capture

12-slot photo flow and numeric readings

  • Build the 12 named slots with one-line framing hints.
  • Downscale images client-side to 1200px and upload to Supabase Storage.
  • Add fuel-gauge and engine-hour numeric fields and the departure seal action.

Deliverable: A complete departure capture saved as a sealed trip record.

Day 3Sign-off

Signature and audit trail

  • Build the renter screen with typed name and drawn signature canvas.
  • Stamp server time and request IP on submit.
  • Compute SHA-256 over canonical trip JSON and store it with the record.

Deliverable: Signed trip with timestamp, IP and hash visible in the dashboard.

Day 4Report

Return flow and PDF

  • Build the return pass on the same slot keys and compute fuel and hour deltas.
  • Build the paired comparison page with damage markers and the deposit deduction summary.
  • Render the PDF serverlessly, store it, and email an expiring share link via Resend.

Deliverable: End-to-end signed departure-versus-return PDF delivered by email.

Day 5MonetisationMVP shipped

Stripe, gating and MVP freeze

  • Wire Stripe Checkout for the three passes and the webhook that grants quota and expiry.
  • Gate trip creation after 3 free reports.
  • Run one full self-serve trip on a phone and fix layout breaks.

Deliverable: Sellable MVP live; no feature work after today without a buyer request.

Day 6List

Build the 200-operator list

  • Pull operators with 2-15 boats from Google Maps in Gold Coast, Cairns, Miami, Florida Keys and Tenerife.
  • Record boat names, owner first name, IG handle, email and a boat photo URL per row.
  • Tag the 40 highest-fit rows for sample reports.

Deliverable: Spreadsheet of 200 named operators with contact routes and photos.

Day 7Samples

40 personalised sample reports

  • Generate sample PDFs from each operator's own boat photo, labelled as samples.
  • Add one example damage callout and a deposit deduction summary to each.
  • Queue the first 25 DMs and 25 emails with the boat name in the first line.

Deliverable: 40 sample PDFs and a queued first outreach wave.

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

First contact at volume

  • Send 25 Instagram DMs with the sample attached.
  • Send 25 emails to operators without an Instagram presence.
  • Reply to every response within the hour and book free first reports.

Deliverable: 50 personalised messages sent and reply log started.

Day 9Delivery

Free reports on real trips

  • Build each requested free report manually within the hour.
  • Note every friction point the operator hits on their own phone.
  • Post the blank template in two boat-owner Facebook groups.

Deliverable: At least 3 free reports delivered on real trips.

Day 10Follow-up

Screen recording, not a pitch

  • Send the 40-second diff-page recording to every day-8 non-responder.
  • Tie the follow-up to their next busy weekend.
  • Fix the top two friction points found during day-9 delivery.

Deliverable: Follow-up wave sent and two fixes shipped.

Day 11Outreach

Wave two and inbound loop

  • Send 25 new DMs and 25 new emails.
  • Post the template to r/boating with the free-first-report offer.
  • Log reply source so channel performance is measurable.

Deliverable: 100 total messages sent and first inbound DM tracked.

Day 12RevenueFirst sale target

First sale

  • Put the Stripe Fleet Pass link in every warm thread that has received a free report.
  • Ask directly for the card on the next busy-weekend deadline.
  • Watch the first checkout complete end to end and confirm quota unlocks.

Deliverable: First paid pass collected inside the contest window.

Day 13Retention

Make the first buyers use it

  • Onboard each buyer with a 10-minute screen share and set up their boats.
  • Ask for a one-line quote and permission to name their fleet size only.
  • Add the operator logo to the PDF header for Fleet Pass buyers.

Deliverable: Every buyer has at least one completed report on a real trip.

Day 14Review

Week two numbers

  • Count messages sent, replies, free reports and paid passes.
  • Cut the worst-performing message angle and keep the best.
  • Ship the highest-value fix requested by more than one buyer.

Deliverable: Written week-two scorecard and one shipped fix.

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

Sustain volume

  • Send 25 personalised messages to list rows 101-125.
  • Send the day-7 follow-up to all day-11 non-responders.
  • Reply and deliver free reports within the hour.

Deliverable: 125 total messages sent.

Day 16Outreach

Sustain volume

  • Send 25 personalised messages to list rows 126-150.
  • Test a second opening line built around a refused damage-waiver claim.
  • Deliver every outstanding free report.

Deliverable: 150 total messages sent and A/B opening lines live.

Day 17Product

Dispute evidence pack

  • Add a one-click evidence pack: report PDF plus a short cover page listing the deposit line items.
  • Test it on a real disputed handover if a buyer has one.
  • Document the pack in the PDF footer disclaimer.

Deliverable: Evidence pack shipped and used on a real dispute.

Day 18Outreach

Second market push

  • Send 25 messages to Canary Islands and Phuket operators.
  • Ask each existing buyer for one neighbouring fleet introduction.
  • Reply to every inbound within the hour.

Deliverable: 175 total messages sent and first referral introductions requested.

Day 19Product

CSV export and Marina sub-accounts

  • Ship CSV export of handovers and flagged damage for Fleet Pass.
  • Ship per-boat sub-accounts behind the Marina Pass.
  • Verify report gating still behaves correctly after each change.

Deliverable: Marina Pass is genuinely deliverable at $399.

Day 20Outreach

Sustain volume

  • Send 25 personalised messages to list rows 151-175.
  • Follow up on every referral introduction with a named sample report.
  • Log all outcomes in the sheet.

Deliverable: 200 total messages sent.

Day 21Review

Week three numbers

  • Recount replies, free reports, paid passes and refund requests.
  • Kill any feature that no buyer used.
  • Set the pricing question for week four.

Deliverable: Week-three scorecard and a decision on pass mix.

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

Work the warm list hard

  • Send a direct ask to every operator who received a free report but did not pay.
  • Offer to run their next handover live on a call.
  • Set a December 16 deadline tied to the contest window.

Deliverable: Every warm lead has a dated, specific ask.

Day 23Acquisition

New segments from the same list

  • Re-message the 30 best-fit non-responders with a different boat sample.
  • Send 25 messages to Gold Coast and Cairns operators not yet contacted.
  • Deliver free reports the same day.

Deliverable: Second-touch coverage complete on the top 30.

Day 24Product

Trust and polish

  • Add the explicit 'record, not legal or insurance advice' footer to every PDF.
  • Add a three-slot onboarding walkthrough for new operators.
  • Fix the slowest step in the mobile capture flow.

Deliverable: Reduced refund risk and a faster first report.

Day 25Acquisition

Inbound loop

  • Post the free-first-report offer in two more owner communities.
  • Publish one public sample report page with a labelled example.
  • Reply to every inbound DM within the hour.

Deliverable: First inbound-sourced paid conversation.

Day 26Conversion

Close week

  • Send the final follow-up to all warm leads with the Stripe link.
  • Offer the Single Boat Pass at $49 to one-boat owners as a low-friction entry.
  • Confirm every checkout, refund and fee lands cleanly in the payment account.

Deliverable: All warm conversations resolved one way or the other.

Day 27Operations

Books and delivery check

  • Export the full transaction list and match it to reports generated.
  • Verify every sale covers its delivery cost per report.
  • Write the refund policy in one sentence and publish it.

Deliverable: Verified transaction and delivery reconciliation.

Day 28Review

Week four numbers

  • Recount every metric and compare against the conservative, base and upside scenarios.
  • Decide which scenario the run actually tracked.
  • Note the single biggest blocker to conversion.

Deliverable: Scenario comparison written down.

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

Final push before the window shuts

  • Message every remaining warm lead with the hard December 16 cutoff.
  • Fix the one blocker identified on day 28 if it is a copy or onboarding issue.
  • Confirm TrustMRR is receiving the payment account data correctly.

Deliverable: Final push sent and revenue sync confirmed.

Day 30Wrap

Lock the numbers and plan month 2

  • Freeze the figures: collected revenue, refunds, chargebacks, fees, ad spend.
  • Write the month-2 plan around renewals and the best-converting message angle.
  • Archive the outreach sheet with outcomes for the record.

Deliverable: Final verified numbers and a written month-2 plan.

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 and Base assume the $199 Fleet Pass is the default basket; the $49 Single Boat and $399 Marina Pass are treated as mix noise.
  • Upside assumes a blended ARPU of $214 from the same $199 anchor plus a minority of $399 Marina and $49 Single Boat passes.
  • Payment processing assumed at 3.5% blended on a typical $199 basket (Stripe 2.9% + $0.30).
  • Refunds modelled at 0% Conservative, 2.5% Base and 3.1% Upside; chargebacks modelled at zero in all three because the buyer is a verified business paying by card for a delivered artifact.
  • No paid marketing in Conservative or Base because the primary channel is organic direct outreach; Upside includes $120 of sponsored posts in owner communities.
  • Operating costs cover Vercel, Supabase, PDF rendering, Resend and one domain, and are non-zero because PDF rendering and storage scale with the number of reports generated.
  • Each sale is priced well above the marginal cost of delivering its reports, so no scenario relies on below-cost selling.

Conservative

3 customers
$597
collected revenue · avg payment $199
Refunds
$0
Chargebacks
$0
Payment fees
$21
Paid marketing
$0
Hackathon profit
$576
Operating costs
$35
Business profit
$541

Base case

12 customers
$2,388
collected revenue · avg payment $199
Refunds
$60
Chargebacks
$0
Payment fees
$84
Paid marketing
$0
Hackathon profit
$2,244
Operating costs
$95
Business profit
$2,149

Optimistic

30 customers
$6,420
collected revenue · avg payment $214
Refunds
$199
Chargebacks
$0
Payment fees
$225
Paid marketing
$120
Hackathon profit
$5,876
Operating costs
$210
Business profit
$5,666

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$588
Payment fees (3.9%)
$23
Paid marketing
$0
Hackathon profit
$565
Business profit
$470

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 built from the stated assumptions. They are not verified revenue, existing customers or real traction, and they will not be presented as such.

Section 7 of 8

Main risks and validation experiments

Risk 1Cold DM and email deliverability to small operators suppresses the response rate well below the 7% close rate the projection assumes.

Mitigation

Send from a warmed domain, keep the message under 90 words with one attachment, split volume across Instagram DM and email, and follow up exactly twice before dropping the lead.

Validation experiment

Send 50 messages on day 8 and count replies within 72 hours; anything under 3 replies means the channel or the message is wrong.

Kill criteria

If 150 messages produce fewer than 5 replies, stop outreach volume and switch to phone calls to the 20 highest-fit operators before spending more days.

Risk 2Operators believe WhatsApp photos plus a paper form are already good enough and refuse to pay for a second place to record the same thing.

Mitigation

Lead every message with a specific already-budgeted loss (a disputed deposit or a refused damage-waiver claim) and show the signed diff page, not a feature list.

Validation experiment

Ask 10 operators one question: what happened the last time a renter disputed a deposit? Record whether they mention photos as sufficient.

Kill criteria

If 8 of 10 say their current process has never cost them money, the pain is not real enough and the wedge must be re-scoped to the damage-waiver claim angle instead.

Risk 3Buyers demand Click&Boat or GetMyBoat integration before paying, which is out of scope and unnecessary for the artifact to be useful.

Mitigation

State in the first message that DockProof works with any booking source because it records the handover, not the booking.

Validation experiment

Track how many warm leads raise integration as a blocker versus a nice-to-have across the first 100 messages.

Kill criteria

If more than half of warm leads make integration a hard precondition, the wedge is wrong and the offer should move to marinas that run their own bookings.

Risk 4The report's legal and insurance weight is overstated by the buyer, leading to a refused claim and a refund or chargeback.

Mitigation

Put 'a record, not legal or insurance advice' in the PDF footer and in the message template, and never claim a claim outcome.

Validation experiment

Include the disclaimer in the first 25 messages and count how many prospects push back on it or ask whether it guarantees a payout.

Kill criteria

If more than two buyers refund after a refused claim in the window, the positioning needs a narrower record-keeping framing before further selling.

Risk 5December holiday closures in some target markets delay replies past the December 16 cutoff.

Mitigation

Front-load Gold Coast, Cairns and Florida Keys operators, who are in peak season and open, and treat Canary Islands and Phuket as secondary.

Validation experiment

Compare reply rates by market across the first 100 messages before day 14.

Kill criteria

If a market returns zero replies across 30 messages, drop it and reallocate the messages to the best-performing city.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create the Next.js repo on Vercel with Tailwind.
  • Create the Supabase project and write the schema for operators, boats, trips, slots, signatures, reports and passes.
  • Push the first deploy and confirm HTTPS works on a phone.

Output: A live skeleton URL that loads correctly on a mobile browser.

Hours 2-5

  • Wire Supabase magic-link auth and a session guard.
  • Build the boat profile form with name, registration and photo upload.
  • Build the trip creation screen with renter name and booking reference.

Output: An operator can log in, save a boat and open a trip.

Hours 5-8

  • Build the 12-slot capture grid with framing hints and client-side image downscaling.
  • Add fuel-gauge and engine-hour numeric inputs.
  • Upload to Supabase Storage and render thumbnails in the grid.

Output: A full departure capture saved and visible in the app.

Hours 8-12

  • Build the renter signature screen with typed name and canvas.
  • Stamp server time, request IP and a SHA-256 payload hash on submit.
  • Draft the 200-operator list skeleton with the target cities and columns.

Output: One sealed, signed trip record and a list skeleton ready to fill on day 6.

Complete report

Full 30-day launch report

Read the full generated report

DockProof Handover — 30-Day Solo Launch Report

1. Product opportunity and positioning

DockProof Handover sells to exactly one buyer: the owner-operator of a 2-15 boat rental or charter business in a warm-water peak-season market — Gold Coast, Cairns, Florida Keys, Miami, the Canary Islands, Phuket. That operator already loses money at the handover moment. A hull returns with a bent cleat, a missing fender or a fuel delta, the only record is an unordered WhatsApp photo thread with no booking reference and no renter signature, and a legitimate deposit deduction becomes an argument, a one-star review or a card chargeback.

The JEV score for this exact concept is 62.7/100, band C, confidence 0.74. Speed to first revenue is the strongest criterion at 8.47, because the buyer is a named business with a public phone number and Instagram handle — the first customer is one direct message away. Solo build feasibility at 7.26 and reachable customers at 7.30 hold up because nothing depends on integration with Click&Boat, GetMyBoat or Boatsetter. The flagged weakness is market demand at 4.39, and this plan answers it instead of denying it: every message leads with a specific, already-budgeted loss and a named trigger event, and a free report is delivered before price is mentioned.

Positioning is deliberately narrow. DockProof is not a marketplace, booking engine, availability calendar or insurance product. It does not hold or move renter deposits. It sits on the operator's own phone and produces one artifact: a server-timestamped, hash-sealed, e-signed departure-versus-return PDF per trip. The generic alternative is a camera roll plus a paper form; the difference is a renter signature, an IP-stamped audit trail and a side-by-side comparison page that can be attached to a card dispute.

2. Smallest sellable MVP

One operator, one boat, one trip, one signed PDF. The sellable unit is a document an operator can attach to a deposit deduction or a chargeback response. Everything not required to produce it by day 5 is cut.

Live on day 5: magic-link login, boat profile, the 12-slot capture flow with framing hints, numeric fuel and engine-hour fields, renter typed name and drawn signature, server timestamp and IP, SHA-256 payload hash, the return pass on the same slot keys, the paired comparison page, damage markers with cost line items rolling into a deposit deduction summary, PDF render, expiring share link, and Stripe Checkout with gating after three free reports.

Not built: marketplace, calendar, booking engine, deposit handling, AI damage detection, native apps, platform integrations, multi-language, team permissions.

3. Technical implementation plan

A single Next.js app on Vercel handles UI and API routes. Supabase provides auth, Postgres and Storage. Photos downscale to 1200px in the browser before upload. Each trip seals with SHA-256 over canonical JSON plus the server timestamp, stored with the record. The return pass writes the same 12 slot keys, so comparison and PDF are pure reads. A serverless Puppeteer route renders one HTML template to PDF, stores it, and returns a 30-day signed URL that Resend emails to renter and operator. Stripe Checkout creates a pass; the webhook writes boat quota and 12-month expiry.

The hardest technical risk is PDF rendering 24-plus images into a paginated paired report without timing out. Mitigation: pre-resize on upload, keep the report HTML free of external assets, and cap the report at the 12 paired slots. There is no AI in the delivery path — damage callouts are operator-placed markers, which keeps per-report cost near zero and avoids overstating automated detection.

4. Pricing and monetization

Three one-time annual passes: Single Boat at $49 for a private owner, Fleet at $199 for 2-5 boats, Marina at $399 for 6-20 boats with per-boat sub-accounts. Fleet is the anchor and the default ask. Nothing is subscription in the first 30 days, because a one-time card charge removes the renewal objection during a December buying window. The month-13 renewal sequence is the path to recurring revenue and is explicitly not counted in the projection.

5. First-customer acquisition

One channel: direct Instagram DM and email to 200 named operators, each message carrying a sample report built from that operator's own public boat photo. Day 6 builds the list from Google Maps and operator websites; day 7 generates 40 samples; day 8 sends the first 50 messages. Every reply gets a real free report within the hour. Follow-ups are a 40-second screen recording of the diff page, not a pitch, tied to the operator's next busy weekend. A secondary inbound loop posts the blank template in two owner communities. The message always says the report is a record, not a guarantee of a claim outcome.

6. Thirty-day arc

Days 1-5 are build only, with a hard feature freeze at the end of day 5. Days 6-7 build the list and the personalised samples. Days 8-14 are the first outreach wave, manual free-report delivery, two follow-ups and the first sale target on day 12. Days 15-21 sustain 25 messages per day while shipping only what buyers asked for: an evidence pack, CSV export and Marina sub-accounts. Days 22-28 work the warm list hard, add the disclaimer footer, and reconcile every transaction against reports generated. Days 29-30 freeze the numbers and write the month-2 plan. No feature is built after day 5 without a request from a paying or free-report operator.

7. Revenue and profit scenarios

All three scenarios below are projections from stated assumptions, never verified revenue. Conservative is 3 Fleet Passes, Base is 12, Upside is 30 with a blended $214 ARPU from some Marina and Single Boat mix. Processing fees sit at a blended 3.5%. Refunds are 0% Conservative, 2.5% Base, 3.1% Upside. Chargebacks are zero in all three because the buyer is a verified business paying by card for a delivered artifact. No ad spend is modelled in Conservative or Base, since the channel is organic outreach; Upside carries $120 of sponsored posts. Operating costs are non-zero because PDF rendering and storage scale with reports generated. Hackathon profit is gross revenue minus refunds, chargebacks, processing fees and ad spend; business profit additionally subtracts operating costs. Every sale prices well above the marginal cost of delivering its reports.

8. Risks and validation experiments

The five live risks are deliverability, operators believing WhatsApp is good enough, integration demands, overstating the report's legal weight, and December closures. Each has a cheap test inside the window. Fifty messages on day 8 must produce at least 3 replies within 72 hours. Ten operators must be asked what happened the last time a renter disputed a deposit. Integration objections are counted across the first 100 messages. The disclaimer is included from message one and pushback is logged. Reply rates are compared by market before day 14, with weak markets dropped and messages reallocated. Each risk carries explicit kill criteria so the concept gets re-scoped rather than defended.

9. First 24 hours

Hours 1-2: domain, Next.js repo on Vercel, Supabase schema, first mobile deploy. Hours 2-5: magic-link auth, boat profile, trip creation. Hours 5-8: 12-slot capture with hints, fuel and hour fields, Storage upload. Hours 8-12: signature canvas, server timestamp, IP capture, SHA-256 seal, plus the 200-operator list skeleton. By the end of the first day there is a live URL, one sealed signed trip, and a list structure ready to fill on 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 →