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

Replay Handoff

Turns a recorded client walkthrough video into a branded, redacted, step-by-step HTML guide and PDF that an implementation consultant can hand to the client the same day.

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.12/10
MVP build (solo)
6 days
Launch price
$39
Sales to $1,000 revenue
26 customers
First paying customer
Hand-sent direct messages and value-first community replies to consultants who publicly post about client onboarding, migration or Loom walkthroughs.
Who pays

Solo or 1-10 person implementation consultants - bookkeepers and QuickBooks/Xero ProAdvisors, MSP onboarding technicians and freelance software implementers in the US, UK, Canada and Australia - who just finished a recorded client onboarding, migration or handover call and owe the client documentation.

Biggest execution risk

Operational simplicity 4.7/10

Remove regulated data, human review steps and custom infrastructure; keep the product self-serve and stateless on managed services.

Why this could work in 30 days: one founder can ship the MVP in 6 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 8.0/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
6 days
30d base revenue
$2,520
30d profit†
$2,410
Section 1 of 8

Product opportunity and positioning

Target customer

Solo or 1-10 person implementation consultants - bookkeepers and QuickBooks/Xero ProAdvisors, MSP onboarding technicians and freelance software implementers in the US, UK, Canada and Australia - who just finished a recorded client onboarding, migration or handover call and owe the client documentation.

Why now

The raw material already sits on the consultant's disk with a deadline attached this week, and Whisper plus frame-alignment LLMs make a first-pass guide good enough that only minutes of editing are needed instead of hours.

Problem

The consultant records the walkthrough, the client never rewatches it, questions repeat for weeks, and producing a real step-by-step guide means two to three hours of pausing, screenshotting, cropping and pasting into a doc that the consultant cannot bill.

Solution

Upload the existing MP4/MOV, get transcript-aligned keyframes turned into titled steps with one-sentence captions, drag blur boxes over sensitive fields, add logo and brand colour, then publish a hosted guide page at /g/{slug} plus a PDF.

Differentiation · Generic screen-recording and documentation tools capture new work inside a browser and output an internal knowledge-base page; Replay Handoff consumes a video the consultant already has and outputs a white-label, redacted, client-facing handoff artifact.

1. Product opportunity and positioning

The buyer is a solo or 1-10 person implementation consultant standing at the end of a recorded client onboarding call with an obligation they cannot bill for: documentation. Bookkeepers and QuickBooks/Xero ProAdvisors, MSP onboarding technicians and freelance software implementers in the US, UK, Canada and Australia all run the same loop - record the walkthrough on Zoom or Loom, send the link, then answer the same questions by email for three weeks because nobody rewatches 40 minutes of video.

The alternative is not a competitor, it is two to three hours of unpaid labour: pause the video, screenshot, crop, caption, paste into Google Docs, export a PDF. That work is unbillable, so it does not get done, and the engagement closes looking less professional than the consultant's actual work.

Replay Handoff takes the file that already exists and returns the artifact the consultant owes: titled steps, one-sentence captions, blur boxes over account numbers and client names, their own logo and brand colour, a hosted page at a shareable link plus a PDF. Same day, minutes of editing instead of hours of screenshotting.

Why this wedge rather than the general documentation market: there is no behaviour change to sell. The video exists, the deadline is this week, and the buyer pays from a client project budget rather than a tooling budget, so $149 clears without procurement. The output is client-facing and carries attribution, so every delivered guide is a small distribution surface.

Against generic screen-recording and doc tools the difference is direction of travel. Those tools capture new work inside a browser and produce an internal knowledge-base entry. Replay Handoff consumes an existing recording and produces a white-label handoff the consultant puts their own name on. Against a manual Google Doc, the difference is six minutes versus two hours.

JEV scores this concept 61.2/100 (band C, confidence 0.66). Its strengths are speed to first revenue (7.96 normalized) and reachable customers (6.56): the buyer gathers in named public communities and can be approached by hand on day one. Its weak spots are monetization potential (4.71) and operational simplicity (4.70). This plan answers both directly - the 10-pack and 40-pack create repeat purchase instead of one low-value charge, and the pipeline stays stateless on managed services with a written 7-day deletion policy instead of regulated data handling or human review steps.

The 30-day thesis: 6 to 40 pack purchases from roughly 600-800 hand-sent messages at 5-7% conversion, with free-sample acceptance as the single number that decides whether the concept lives.

Section 2 of 8

Smallest sellable MVP

A paid flow where a consultant uploads one MP4/MOV up to 20 minutes and receives a branded, redacted hosted guide page plus a PDF, unlocked by a $39 Stripe checkout or a prepaid credit pack.

Must-have features

  • Upload page for MP4/MOV up to 20 minutes, with stated 7-day auto-delete
  • ffmpeg scene-change keyframe extraction (8-30 frames) plus timestamped Whisper transcript
  • LLM alignment of transcript segments to keyframes, emitting titled steps with one-sentence captions
  • Review editor: reorder, delete, retitle steps; drag blur rectangles on screenshots
  • Logo upload, brand colour, hosted guide page at /g/{slug} with footer attribution
  • PDF export from the same step data and Resend email delivery
  • Stripe Checkout credit gate: $39 single, $149 ten-pack, $399 forty-pack
  • Dashboard listing guides, credit balance and auto-delete countdown

Explicitly out of scope

  • Live browser capture extension
  • Automated UI execution or click-ops against client systems
  • Team seats, SSO, roles or approval workflows
  • Translation or multi-language output
  • View analytics or client engagement dashboards
  • Public API or Zapier integration

Demo flow (what the buyer sees)

  1. Consultant uploads a 12-minute client walkthrough MP4
  2. Worker extracts keyframes and a timestamped transcript
  3. LLM emits 14 titled steps with captions
  4. Consultant drags two blur boxes, sets logo and brand colour, deletes one weak step
  5. Consultant pays $39 and publishes to /g/abc123
  6. Client receives the hosted link and a PDF by email
Build plan

Technical implementation plan

Stack

Next.js on Vercel for upload UI, editor and hosted guide pagesSupabase Postgres, auth and object storageOpenAI Whisper API for timestamped transcriptionGPT-class model for step segmentation and frame alignmentffmpeg on a single Fly.io worker for keyframes and blur renderingStripe Checkout for one-time credit purchasesResend for transactional email and PDF links

Architecture

Next.js on Vercel handles auth, upload, the step editor and public guide pages. Uploads land in Supabase storage with a 7-day expiry row. A Fly.io worker pulls the job, extracts scene-change keyframes with ffmpeg, sends the audio track to Whisper, then asks the LLM to map transcript segments onto keyframes and return structured steps as JSON. Steps, screenshots and blur rectangles are stored in Postgres. Publish renders the guide server-side from stored data, produces a PDF, and unlocks only when a credit is deducted. Stripe webhooks add credits; nothing runs as a persistent service except the single worker.

Build steps

  1. Create Supabase schema: guides, steps, keyshots, credits, jobs, deletions
  2. Ship upload page with 20-minute validation and storage write
  3. Run ffmpeg worker on Fly.io: scene detection, keyframe PNG capture
  4. Add Whisper call and store timestamped transcript JSON
  5. Write the alignment prompt and persist steps with title and caption
  6. Build the review editor with reorder, retitle and drag blur rectangles
  7. Render blur through ffmpeg and cache the redacted image
  8. Build /g/{slug} server-rendered page and PDF generator
  9. Wire Stripe Checkout, webhook credits and dashboard balance
  10. Add Resend email with guide link and PDF attachment
  11. Add 7-day deletion cron and a visible countdown

AI components

  • Whisper for timestamped transcription
  • GPT-class model for segmenting transcript into steps and choosing the keyframe per step
  • Prompt-level deduplication of repeated or filler steps
Hardest technical risk: Frame-to-transcript alignment on messy recordings - quiet speech, long mouse-only stretches and screen scrolls - producing steps that need so much manual editing the consultant never buys a second pack.
Section 3 of 8

Pricing and monetization

Single Guide

Entry offer
$39 one-time

For Solo consultant or SMB owner with one recording to convert

  • One video up to 20 minutes
  • Hosted branded guide page
  • PDF export
  • Manual blur tool

Consultant 10-Pack

$149 one-time

For Bookkeepers, MSPs and freelance implementers shipping guides per client project

  • 10 guide credits
  • Custom logo and brand colour
  • PDF exports
  • Footer attribution removable

Agency 40-Pack

$399 one-time

For Small implementation agencies onboarding several clients a month

  • 40 guide credits
  • White-label hosted pages
  • Priority processing queue

Model: One-time credit packs - each credit converts one video into one hosted guide plus PDF - so a small client project budget covers the purchase with no subscription commitment.

First revenue offer: Send the converted guide and PDF free, then in the same thread: 'Here is your guide. If you want nine more for the rest of this quarter, the ten-pack is $149 - link below, no subscription.'

Expected ACV: $149

Upsell path: Single-guide buyers get a ten-pack upgrade email after their second guide; ten-pack buyers who publish more than three guides in a month are offered the $399 forty-pack with white-label pages and priority queue.

Target customers
40
Revenue model
$5,960
Costs
$145
Profit model
$5,815
Section 4 of 8

First-customer acquisition

Primary channel

Hand-sent direct messages and value-first community replies to consultants who publicly post about client onboarding, migration or Loom walkthroughs.

Where to find them

  • r/Bookkeeping threads about client onboarding and handover
  • r/msp threads about onboarding, offboarding and documentation
  • LinkedIn search: QuickBooks ProAdvisor, Xero advisor, implementation consultant, MSP onboarding
  • Facebook and Slack groups for QuickBooks ProAdvisors and MSP owners
  • Public Loom and YouTube walkthroughs posted by bookkeepers and implementers
  • X/Twitter replies complaining about client walkthrough follow-up questions

Exact outreach motions

  • Build a free sample guide from a consultant's own public walkthrough and DM the link with a 40-second before/after clip.
  • Reply in onboarding threads offering one free conversion in 24 hours, no signup required.
  • DM consultants who posted about a migration or handover in the last 14 days with the sample guide as proof.
  • Message fractional COOs and small agencies offering a free guide for one of their clients plus the 40-pack terms.
  • Follow up once at day 3 and once at day 7 on every unpaid free-guide offer.
  • Ask every paying customer for one named peer intro in the delivery email.

Message template

Saw your post about the client handover. I built a tool that turns a walkthrough recording into a step-by-step client guide with your logo and blurred account numbers. Send me one MP4 under 20 minutes and I will send back the hosted guide plus PDF free within 24 hours - no signup, files deleted in 7 days. If it is useful, ten guides is $149.
Week-one goal: 40 DMs and 2 community posts sent, at least 6 consultants accepting a free conversion, guide pipeline working end to end.
Section 5 of 8

30-day execution roadmap

MVP deadline: day 7First sale target: day 1230 days planned
Week 1 · Build & validate · 7 days
Day 1Setup

Accounts and skeleton

  • Create Next.js repo on Vercel and Supabase project.
  • Write tables: guides, steps, keyframes, credits, jobs.
  • Create the three Stripe products.
  • Ship an empty upload page.

Deliverable: Deployed skeleton with auth and Stripe products live.

Day 2Ingest

Upload to keyframes

  • Accept MP4/MOV up to 20 minutes into Supabase storage.
  • Add a cron job that deletes files after 7 days.
  • Run ffmpeg scene-change keyframe extraction on Fly.io.

Deliverable: Video in, 8-30 keyframes out.

Day 3Transcribe and align

Steps from speech

  • Send the audio track to Whisper for a timestamped transcript.
  • Prompt the LLM to map transcript segments to keyframes.
  • Persist steps with title and one-sentence caption.

Deliverable: First generated guide draft from a test recording.

Day 4Editor

Human control

  • Build step list with reorder, delete and retitle.
  • Add drag-rectangle blur rendered through ffmpeg.
  • Add logo upload and brand colour picker.

Deliverable: Editable guide with redaction and branding.

Day 5Publish

The delivered artifact

  • Render hosted page at /g/{slug} with footer attribution.
  • Generate PDF from the same step data.
  • Email guide link and PDF via Resend.

Deliverable: Shareable branded guide page and PDF.

Day 6Payments

Credit gate

  • Gate publish behind a Stripe-purchased credit.
  • Build dashboard: guides, credit balance, deletion countdown.
  • Credit purchases via Stripe webhook.

Deliverable: End-to-end paid flow testable with a live card.

Day 7ProofMVP shipped

First real video

  • Run a 12-minute recording through the whole pipeline.
  • Fix the three worst alignment failures.
  • Build a sample guide from a public bookkeeping walkthrough.

Deliverable: Public sample guide plus landing page with Stripe link.

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

Proof assets

  • Build two more sample guides from public walkthroughs.
  • Record a 40-second before/after clip.
  • Publish a confidentiality and deletion page.

Deliverable: Three samples, one clip, one trust page.

Day 9Community

First public posts

  • Post the sample value-first in r/Bookkeeping.
  • Post the same in r/msp with MSP framing.
  • Reply to every comment within an hour.

Deliverable: Two live posts and a comment queue.

Day 10Outreach

30 DMs

  • DM 30 consultants who posted about onboarding or migration.
  • Offer one free conversion within 24 hours.
  • Log every name, community and date in a sheet.

Deliverable: 30 DMs sent, 30 rows logged.

Day 11Free conversions

Deliver fast

  • Convert every accepted free video within 24 hours.
  • Send guide, PDF and $149 pack link in one message.
  • Record editing minutes per guide.

Deliverable: First free guides delivered with pack links.

Day 12First saleFirst sale target

Close one pack

  • Follow up every free-guide recipient once.
  • Fix the top bug real videos expose.
  • Post a second community thread.

Deliverable: First paid pack, or a documented reason why not.

Day 13Groups

Second surface

  • Post in two ProAdvisor and MSP Slack or Facebook groups.
  • DM 30 more consultants on LinkedIn.
  • Ask the loudest commenters for a 10-minute call.

Deliverable: Two group posts, 30 DMs, call bookings.

Day 14Week two review

Measure the channel

  • Tally posts, DMs, replies, free guides and paid packs.
  • Cut any channel with zero free-guide acceptances.
  • Rewrite the DM opener around the winning phrase.

Deliverable: Channel scorecard and revised message.

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

40 DMs

  • DM 40 consultants with the revised opener.
  • Target QuickBooks ProAdvisor and MSP onboarding titles.
  • Follow up day-3 non-replies.

Deliverable: 40 DMs and follow-ups sent.

Day 16Trust

Confidentiality objection

  • Add the written 7-day deletion promise to checkout.
  • Add two anonymised guide examples to the landing page.
  • Add a short list of what the tool never does.

Deliverable: Trust objections answered on page.

Day 17Volume

Keep sending

  • DM 40 more consultants.
  • Reply to new community comments same day.
  • Convert accepted free videos.

Deliverable: 40 DMs and free guides shipped.

Day 18Distribution

Attribution loop

  • Publish the before/after case study on LinkedIn.
  • Enable footer attribution on all published guides.
  • Ask two paying customers for one intro each.

Deliverable: Case study live and referral asks sent.

Day 19Adjacent buyer

Agencies

  • DM 20 fractional COOs and small agencies.
  • Offer the 40-pack with white-label pages.
  • Offer one free guide for their own client.

Deliverable: 20 agency DMs and one pilot offer.

Day 20Free batch

Clear the queue

  • Ship every outstanding free guide.
  • Send the $149 link in the same thread as delivery.
  • Record editing minutes per guide.

Deliverable: Zero outstanding free guides.

Day 21Week three review

Conversion math

  • Compute free-to-paid conversion rate.
  • Compute revenue per DM by community.
  • Decide the one channel to double.

Deliverable: Conversion math and a single doubled channel.

Week 4 · Scale what works · 9 days
Day 22Push

Doubled channel

  • DM 40 consultants in the doubled channel.
  • Promote the $39 single tier to one-guide posters.
  • Post a sample guide in a new subreddit.

Deliverable: 40 DMs and a live single-tier post.

Day 23Quality

Cut edit time

  • Rewrite the alignment prompt using the worst 10 edited steps.
  • Cap keyframes at 20 for videos over 12 minutes.
  • Re-run three past videos and compare edit time.

Deliverable: Shorter edit time on the same three videos.

Day 24Proof

Public sample

  • Publish a client-facing sample guide page publicly.
  • Post a 60-second teardown of one converted guide.
  • Email past buyers about the 40-pack upgrade.

Deliverable: Public sample plus upgrade email sent.

Day 25Agencies

Bigger packs

  • Follow up the 20 agency DMs.
  • Ship the priority queue for 40-pack buyers.
  • Offer same-day turnaround on the first guide.

Deliverable: Agency follow-ups and priority queue live.

Day 26Push

40 DMs

  • DM 40 consultants.
  • Follow up all unpaid free-guide offers.
  • Fix the newest recurring failure mode.

Deliverable: 40 DMs and a bug fix shipped.

Day 27Reliability

No founder in the loop

  • Add failure capture and one automatic retry to the worker.
  • Send a plain error email when processing fails.
  • Test a 20-minute 1080p video end to end.

Deliverable: Failed jobs recover without founder intervention.

Day 28Referrals

Warm intros

  • Ask every paying customer for one named peer intro.
  • DM 40 consultants with the case study link.
  • Post one value thread in a new community.

Deliverable: Referral asks and 40 DMs sent.

Day 29Close

Final offer

  • Run a 24-hour same-day turnaround offer.
  • Follow up every open thread once.
  • Check credit balances for upgrade signals.

Deliverable: Final offer live and all threads followed up.

Day 30Tally

Verified numbers

  • Export Stripe revenue, costs and refunds.
  • Count guides delivered and editing minutes per guide.
  • Write the next-30-day decision: keep, narrow or stop.

Deliverable: Verified revenue and profit tally plus a written decision.

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 figures are projections, not verified revenue.
  • Customers are credit-pack purchases, not subscriptions.
  • Blended ARPU reflects a mix of $39, $149 and $399 packs rather than a single tier.
  • Conversion modelled at 5-7% on 600-800 hand-sent messages and community replies.
  • Every free-guide recipient has at least a 25% chance of buying a pack.
  • Costs are Vercel, Supabase, Fly.io, Whisper, LLM tokens and Stripe fees only.
  • No paid ads, no contractors and no founder salary counted.
  • Average video under 20 minutes keeps per-guide inference cost near $0.15-$0.40.
  • No refunds counted in revenue; refunds are assumed offset in costs.
  • Community posts stay up and are not removed as promotion.
  • Founder sells and fixes bugs in the same week without stalling either.
  • Editing time stays under 15 minutes per guide so repeat purchase holds.

Conservative

6 customers
$720
collected revenue · avg payment $120
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $680.

Base case

18 customers
$2,520
collected revenue · avg payment $140
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $2,410.

Optimistic

40 customers
$5,960
collected revenue · avg payment $149
Refunds
n/a
Chargebacks
n/a
Payment fees
n/a
Paid marketing
n/a
Hackathon profit
n/a
Operating costs
n/a
Business profit
n/a

Pre-breakdown estimate. This report was generated before costs were itemised, so refunds, fees, ad spend and operating costs cannot be separated without inventing them. Nothing is estimated here. Original modelled profit (all costs included): $5,815.

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$702
Payment fees (3.9%)
$27
Paid marketing
$0
Hackathon profit
$675
Business profit
$675

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.

Projection only. These are hypotheses, not verified revenue, existing customers or real traction.

Section 7 of 8

Main risks and validation experiments

Risk 1Frame-to-transcript alignment produces sloppy steps on messy recordings, forcing heavy manual editing and killing repeat purchase.

Mitigation

Measure editing minutes per guide from day 11 and cap keyframes at 20 for long videos; rewrite the alignment prompt weekly using the worst edited steps.

Validation experiment

Run three real client recordings and time the manual edit; if any exceeds 15 minutes, prompt and keyframe strategy change before more outreach.

Kill criteria

If median editing time stays above 20 minutes after two prompt revisions, the alignment approach is not viable as built.

Risk 2Consultants treat a text guide as nice-to-have and keep sending raw Loom links, so free-sample offers get polite declines.

Mitigation

Lead with the finished artifact, not the tool; make the free conversion a one-file-upload ask with no signup.

Validation experiment

Send 40 DMs across two message variants and compare free-guide acceptance rate.

Kill criteria

Fewer than 3 acceptances from 60 DMs means the deliverable is not wanted at any price.

Risk 3Sending client recordings to an unknown vendor raises confidentiality concerns that block the sale.

Mitigation

Publish a written 7-day deletion promise, keep files in a private bucket, and state refusal of regulated data.

Validation experiment

Track how often confidentiality is cited as the reason for declining across the first 60 conversations.

Kill criteria

If confidentiality is the stated blocker in more than half of declines, switch to local processing or stop.

Risk 4Community moderators remove promotion posts, cutting off the only acquisition channel before volume is reached.

Mitigation

Lead with a free sample and specific help, never a link in the post body, and spread across six surfaces instead of two.

Validation experiment

Post in two subreddits and two Slack or Facebook groups in week one and log removal or engagement within 24 hours.

Kill criteria

If both subreddits remove posts and group posts get zero replies, move fully to direct DMs and LinkedIn.

Risk 5Long or high-resolution videos create inference and processing costs that exceed the near-zero operating budget.

Mitigation

Hard-cap at 20 minutes and 1080p, downscale frames before extraction, and reject oversized uploads at the door.

Validation experiment

Process five videos at the cap and reconcile actual Whisper and token spend against the modelled $0.40 per guide.

Kill criteria

If measured cost per guide exceeds $2, repricing or a lower processing cap is required before scaling outreach.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Vercel, Supabase and Stripe accounts.
  • Scaffold the Next.js app with auth and an upload route.
  • Write the initial Postgres schema.

Output: Deployed skeleton at a live URL with an empty dashboard.

Hours 3-5

  • Wire storage upload with a 20-minute file validation.
  • Create the three Stripe products and prices.
  • Add the credits row and the 7-day expiry field.

Output: A working upload that gets rejected above 20 minutes and three live Stripe prices.

Hours 6-8

  • Stand up the Fly.io worker and run ffmpeg scene detection.
  • Extract and store keyframes for one test video.
  • Log frame timestamps to Postgres.

Output: Keyframe extraction proven on a real recording.

Hours 9-11

  • Call Whisper on the same file and store the timestamped transcript.
  • Draft the alignment prompt and generate the first step list.
  • Save steps with titles and captions.

Output: First machine-generated guide draft, however rough.

Hours 12-14

  • Pick one public bookkeeping walkthrough as the sample.
  • Run it through the pipeline end to end.
  • Write down the three worst output problems.

Output: A named sample video, a ranked defect list, and tomorrow's build order.

Complete report

Full 30-day launch report

Read the full generated report

Replay Handoff - 30-Day Launch Report

1. Product opportunity and positioning

The buyer is a solo or 1-10 person implementation consultant standing at the end of a recorded client onboarding call with an obligation they cannot bill for: documentation. Bookkeepers and QuickBooks/Xero ProAdvisors, MSP onboarding technicians and freelance software implementers across the US, UK, Canada and Australia share one loop - record the walkthrough on Zoom or Loom, send the link, then answer the same questions for three weeks because nobody rewatches 40 minutes of video.

Replay Handoff takes that existing file and returns the artifact the consultant owes: titled steps, one-sentence captions, blur boxes over account numbers and client names, their logo, a hosted page and a PDF. The competitor is not another documentation product; it is two to three hours of unpaid screenshotting in Google Docs, which is why the guide never ships.

JEV scores this concept 61.2/100 (band C, confidence 0.66). Speed to first revenue (7.96 normalized) and reachable customers (6.56) are the strengths this plan leans on. Monetization (4.71) and operational simplicity (4.70) are the weaknesses this plan answers with repeat-purchase packs and a stateless managed-service pipeline.

2. Smallest sellable MVP

One upload box, one pipeline, one publish button, one Stripe gate. A consultant drops an MP4 up to 20 minutes, gets 8-30 keyframes with a transcript-aligned step list, edits titles, drags two blur rectangles, sets a logo and colour, pays $39, and receives a hosted guide page plus PDF. Nothing else is built: no capture extension, no execution engine, no seats, no analytics. Six build days is the ceiling; anything that does not appear in the demo flow on day 6 is cut.

3. Technical implementation plan

Next.js on Vercel serves auth, upload, the editor and public guide pages. Uploads land in Supabase storage with a 7-day expiry row. A single Fly.io worker pulls the job, extracts scene-change keyframes with ffmpeg, sends audio to Whisper, then asks a GPT-class model to map transcript segments onto keyframes and return structured steps. Steps, screenshots and blur rectangles live in Postgres; publishing renders the page server-side and generates the PDF. Stripe webhooks add credits. The whole system is stateless apart from one worker and one bucket, which keeps operating cost near zero and removes any human review step.

The hardest part is alignment on messy recordings - quiet speech, long mouse-only stretches, screen scrolls. Mitigation is measurement, not hope: editing minutes per guide are logged from day 11, keyframes are capped at 20 for videos over 12 minutes, and the prompt is rewritten on day 23 using the ten worst edited steps.

4. Pricing and monetization

One-time credit packs. Single Guide at $39 converts a curious first-timer, the Consultant 10-Pack at $149 is the intended default and targets a blended $140 ARPU, and the Agency 40-Pack at $399 exists for the buyers who publish several guides a month. There is no subscription in the first 30 days because a solo founder cannot service churn and a consultant should not have to justify a recurring line item to a client project budget. Repeat purchase replaces recurrence: buyers who burn three credits get a forty-pack upgrade email, and every published guide carries a removable footer credit that reaches the consultant's own clients.

5. First-customer acquisition

One channel, worked by hand: DMs and value-first community replies. The sequence is fixed. Build three sample guides from publicly posted walkthroughs, record a 40-second before/after clip, post it where the buyer gathers, then DM everyone who engages plus every consultant who publicly described a recent onboarding or migration. The ask is never 'buy' - it is 'send me one recording, I will return the guide free in 24 hours.' The $149 link rides in the same message as the delivered guide, when the artifact is in their hands and the value is undeniable. Every free offer gets one follow-up at day 3 and one at day 7. Referral asks go out on delivery, not later.

6. 30-day execution roadmap

Days 1-6 are build only. Day 1 stands up accounts, schema and Stripe products. Day 2 gets video in and keyframes out. Day 3 generates the first step list. Day 4 makes steps editable and adds redaction. Day 5 publishes the hosted page and PDF. Day 6 puts the credit gate and dashboard in front of it. Day 7 is the first full pass on a real recording plus a public sample guide.

Days 8-14 convert proof into conversations: three samples, two community posts, 60 DMs, and free guides delivered within 24 hours. Day 12 is the first-sale target. Day 14 is a hard review - any channel with zero free-guide acceptances is cut.

Days 15-21 are volume and trust: 80 more DMs, a written deletion promise on checkout, anonymised examples on the landing page, footer attribution switched on, and the first agency conversations. Day 21 computes free-to-paid conversion and picks one channel to double.

Days 22-30 double that channel and harden the product: 120 more DMs, prompt rewrite from real edit data, priority queue for forty-pack buyers, automatic retry so failed jobs recover without the founder, and a same-day-turnaround close on day 29. Day 30 exports Stripe revenue and writes the keep-narrow-stop decision.

7. Revenue and profit scenarios

All three scenarios are projections, not verified revenue, and no customers exist at the time of writing. Conservative: 6 customers at $120 blended ARPU for $720 revenue, $40 costs, $680 profit. Base: 18 customers at $140 for $2,520 revenue, $110 costs, $2,410 profit. Upside: 40 customers at $149 for $5,960 revenue, $145 costs, $5,815 profit. Costs cover Vercel, Supabase, Fly.io, Whisper, model tokens and Stripe fees, with no salary and no ads. The spread between conservative and upside is almost entirely free-guide acceptance rate, which is why it is the number measured weekly.

8. Main risks and validation experiments

Alignment quality is the existential risk: if editing takes 20 minutes, nobody buys a second pack. Test by timing edits on three real recordings before scaling outreach. Demand risk: consultants may prefer raw Loom links. Test with two DM variants across 40 sends and compare acceptance. Trust risk: client recordings are confidential. Test by tracking how often confidentiality is the stated reason for declining. Channel risk: moderators remove promotion posts. Test with one post per group across four surfaces in week one. Cost risk: long videos exceed the budget. Test by reconciling actual inference spend against the modelled $0.40 per guide on five capped videos. Each risk carries an explicit kill criterion so the decision is made by data on a fixed day, not by mood.

9. First 24 hours

Hours 1-2: accounts, app scaffold, schema, deployed skeleton. Hours 3-5: upload with 20-minute validation, three Stripe prices, credit and expiry fields. Hours 6-8: Fly.io worker and ffmpeg keyframe extraction proven on one file. Hours 9-11: Whisper transcript plus the first LLM-generated step list. Hours 12-14: run a public bookkeeping walkthrough end to end, name the sample, rank the three worst defects. The day ends with a live URL, real keyframes, a rough generated guide and tomorrow's build order. No outreach happens until day 9, and no day is allowed to borrow from the next.

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 →