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

ClipTrust Proof Clips

Turns a creator's raw testimonial or product demo video into three captioned, brand-safe short clips with a signed provenance receipt for each.

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.16/10
MVP build (solo)
5 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Direct outreach to creators who publicly post raw testimonial or demo footage and ask for editing help, offering one free clip from their own video.
Who pays

Solo course creators and small e-commerce brands (1-10 people) who already own raw testimonial or product-demo footage and post on short-video platforms weekly.

Biggest execution risk

Market demand 4.8/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 10; 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

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

0/13
Entry price
$49
Solo build
5 days
30d base revenue
$490
30d hackathon profit
$468
Section 1 of 8

Product opportunity and positioning

Target customer

Solo course creators and small e-commerce brands (1-10 people) who already own raw testimonial or product-demo footage and post on short-video platforms weekly.

Why now

Short vertical video is the default format for testimonials and product demos, and the people reposting those clips are increasingly asked whether the footage was altered.

Problem

Turning raw footage into postable vertical clips takes hours in an editor, and there is no simple way to show a buyer, sponsor or customer that a published clip was not manipulated.

Solution

Upload an MP4 under 15 minutes; the pipeline removes silences and filler words, transcribes, burns captions, crops to 9:16, selects three clips of 15-45 seconds, and emails a ZIP with three MP4s plus one PDF receipt per clip containing source and output hashes.

Differentiation · Free editors produce clips and nothing else. ClipTrust ships a fixed three-clip pack plus a per-clip hash receipt in one automated pass, sold as a $49 purchase instead of another editing subscription.

1. Product opportunity and positioning

The buyer is one person: a solo course creator or a 1-10 person e-commerce brand that already owns raw footage - a testimonial, a product demo, a founder talking head - and needs clips to post this week. They do not want an editor. They want three finished vertical clips with captions, delivered the same day.

What they pay today is either $150-400 to a freelance editor or two hours inside CapCut. ClipTrust Proof Clips is a $49 fixed pack: upload an MP4, receive three 9:16 captioned clips plus a PDF provenance receipt per clip holding the SHA-256 of the source file, the SHA-256 of the delivered file, the processing parameters and a timestamp.

The receipt is the wedge. Silence removal and auto-captions are commodity. A brand reposting a real customer's words has a legitimate question to answer about whether the clip was altered, and a hash receipt gives the creator a specific artifact to attach to a testimonial page or a sponsor pitch. That artifact is also the reason a buyer forwards the tool to another creator, which matters because the only acquisition channel here is direct outreach.

JEV scored this concept 61.6/100, band C. The strengths it identified are speed to first revenue (8.46 normalized) and solo build feasibility (7.38). The weaknesses are market demand (4.77) and monetization (4.87). This plan attacks the weaknesses, not the strengths.

Demand is narrowed by a trigger event: a creator with a launch date, a testimonial campaign, or an existing weekly posting cadence. Those are the moments when a $49 charge is approved in one message instead of a procurement thread. Monetization gets a second path: a $99/month tier for creators posting weekly, so the 30 days build a recurring base rather than 30 isolated transactions.

Nothing here is verified traction. There are no customers, no partnerships and no revenue at the time of writing. Every number in this report is a projection from stated assumptions.

Section 2 of 8

Smallest sellable MVP

One upload, one payment, one email containing a ZIP of three captioned vertical clips and three PDF provenance receipts.

Must-have features

  • MP4 upload (max 15 minutes, 1 GB) or a direct file link
  • Whisper transcription with word-level timestamps
  • Silence and filler-word removal driven by the transcript
  • 9:16 vertical crop with burned-in captions
  • Automatic selection of three clips between 15 and 45 seconds
  • SHA-256 provenance receipt PDF per clip
  • Stripe Checkout for the $49 pack and the $99 monthly tier
  • Emailed download page with the ZIP

Explicitly out of scope

  • No b-roll or stock library
  • No team seats or collaboration
  • No social scheduling or publishing
  • No mobile app
  • No browser timeline editor
  • No brand kits or custom fonts
  • No public API

Demo flow (what the buyer sees)

  1. Creator pays $49 via Stripe Checkout and gets an upload link
  2. Creator uploads a raw MP4 under 15 minutes
  3. Worker transcribes and builds a silence and filler cut list
  4. FFmpeg cuts, crops to 9:16 and burns captions
  5. Segment scorer picks three non-overlapping 15-45s windows
  6. Pipeline hashes each output and renders a PDF receipt
  7. Creator receives an email with a ZIP and a download page
Build plan

Technical implementation plan

Stack

Next.js on VercelSupabase Postgres for job rowsSupabase Storage with signed upload URLsFFmpeg in a container worker on Cloud Run or Fly.ioOpenAI Whisper API for word-level timestampsStripe Checkout plus webhookResend for delivery emailpdf-lib for receipt rendering

Architecture

The Next.js app handles the landing page, Stripe Checkout, upload and download. Supabase stores one row per job with states queued, paid, processing, done and failed, plus the source and output files in storage. A Stripe webhook marks the job paid. A separate container worker polls paid jobs, calls Whisper, builds a cut list, renders three vertical clips with FFmpeg, hashes the outputs, generates the receipt PDFs, zips the bundle and writes a download URL, then triggers the email. The app never renders video itself because serverless functions cannot hold a multi-minute encode.

Build steps

  1. Create the Next.js repo, deploy to Vercel, connect the domain
  2. Create Supabase tables for jobs, clips and receipts with signed URL storage
  3. Build the upload form and Stripe Checkout with a webhook that flips jobs to paid
  4. Call Whisper and persist word-level timestamps to the job row
  5. Convert timestamps into a silence and filler-word cut list
  6. Render one clipped, cropped, captioned MP4 with FFmpeg in a container
  7. Add the density-based three-window segment scorer
  8. Compute SHA-256 of source and each output, render the PDF receipt
  9. Zip the bundle, upload it and send the delivery email
  10. Add a job timeout with automatic refund and a failure email
  11. Add the $99/month Stripe subscription with a clip quota counter
  12. Run five real videos end to end and log cost and wall-clock time per job

AI components

  • OpenAI Whisper for word-level transcription used to drive silence and filler removal and caption timing
  • One optional LLM call that reads the transcript and picks the three strongest clip windows, with a deterministic fallback if it fails
Hardest technical risk: Render time and memory on long source files: a 15-minute 1080p input with caption burn-in can exceed a small container's memory and blow past the job timeout, producing a paid order that fails.
Section 3 of 8

Pricing and monetization

Clip Pack

Entry offer
$49 one-time

For Solo creators and small brands with one raw video

  • Three captioned vertical 9:16 clips
  • Silence and filler-word removal
  • One SHA-256 provenance receipt per clip
  • Same-day turnaround

Creator Monthly

$99 / month

For Creators posting weekly

  • Up to 12 clips per month
  • Priority processing queue
  • Receipt archive with verification page
  • Email support

Model: A fixed one-time pack for the first purchase and a monthly clip subscription for repeat buyers, both sold through Stripe Checkout with no free tier.

First revenue offer: Send me one raw video. I will send back three captioned vertical clips plus a signed SHA-256 receipt for each, free, today. If they are usable, the pack is $49.

Expected ACV: $49

Upsell path: Pack buyers get the $99 monthly offer after their second one-off purchase, plus a three-pack bundle at $120 for creators with a launch date. The monthly tier is the only revenue that persists past day 30.

Target customers
40
Revenue model
$1,960
Costs
$180
Profit model
$1,780
Section 4 of 8

First-customer acquisition

Primary channel

Direct outreach to creators who publicly post raw testimonial or demo footage and ask for editing help, offering one free clip from their own video.

Where to find them

  • X posts showing unedited testimonial or product demo footage
  • Course-creator Discords and Slack groups
  • Subreddits for online course creators and small DTC brands
  • Reply threads under editing-request posts
  • Indie founder communities where people post build-in-public demos
  • Newsletter writers who publish creator interviews

Exact outreach motions

  • Send 10-15 personalised DMs per day, each referencing a specific public video of theirs
  • Deliver one free vertical clip plus its receipt within 12 hours of any reply
  • Attach the receipt PDF to the delivery email and explain what the hash proves
  • Offer the $49 pack in the same message as the free clip, never in a later thread
  • Follow up once at 48 hours with a second sample clip, then stop
  • Post one before/after clip pair with a receipt on X and reply to every editing request on the thread

Message template

Saw your testimonial clip in the thread. I ran the first 40 seconds through a tool I am building - here is a vertical captioned version, plus a receipt that hashes the file so you can show it was not altered. Want the other two clips? It is $49 for the pack, delivered today.
Week-one goal: 80 outreach messages sent, 8 free clips delivered, 2 paid Clip Packs collected.
Section 5 of 8

30-day execution roadmap

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

Accounts and skeleton

  • Create the Next.js repo and deploy it on Vercel with the domain attached.
  • Open Stripe and connect the payment account to TrustMRR before any checkout exists.
  • Create the Supabase project with storage buckets and a jobs table.

Deliverable: Deployed empty app with a payments account ready.

Day 2Upload path

Ingest and job state

  • Build the MP4 upload form writing to Supabase storage via signed URLs.
  • Add job rows with states queued, paid, processing, done, failed.
  • Enforce the 15-minute and 1 GB upload cap client and server side.

Deliverable: Upload form that stores a file and creates a job row.

Day 3Transcription

Cut list generation

  • Call Whisper and persist word-level timestamps.
  • Compute the silence and filler-word cut list from timestamps.
  • Write the cut list as JSON on the job row for FFmpeg.

Deliverable: A cut list JSON for one test video.

Day 4Render

Vertical clips with captions

  • Run FFmpeg in a container to cut, concat and crop to 9:16.
  • Burn captions using the stored word timestamps.
  • Score transcript windows and select three clips of 15-45 seconds.

Deliverable: Three MP4 clips rendered from a single upload.

Day 5Receipts

Provenance artifacts

  • Compute SHA-256 for the source file and each output clip.
  • Render a one-page PDF receipt with hashes, parameters and a UTC timestamp.
  • Zip three clips and three receipts and upload the bundle.

Deliverable: Downloadable ZIP containing three clips and three receipts.

Day 6MVP doneMVP shipped

End-to-end validation

  • Run five of your own videos through the full pipeline.
  • Log cost and wall-clock time per job.
  • Fix the three most common failures found.

Deliverable: Working MVP with a cost-per-job table.

Day 7Storefront

Paid checkout live

  • Build the landing page with sample clips and a sample receipt.
  • Wire Stripe Checkout for the $49 pack and the $99 monthly tier.
  • Add an order form that accepts a file link and an email address.

Deliverable: Live paid checkout on the production domain.

Week 2 · Launch & first sale · 7 days
Day 8Prospect list

Named outreach targets

  • Build a list of 150 named creators and small brands with raw footage.
  • Record a direct link to one candidate video per prospect.
  • Write three outreach message variants to test.

Deliverable: Spreadsheet of 150 named prospects with links and variants.

Day 9Outreach wave 1

Free clip offer

  • Send 40 direct messages offering one free clip from a linked video.
  • Post one sample clip thread with a receipt on X.
  • Log every send and reply in the sheet the same day.

Deliverable: 40 messages sent, replies logged.

Day 10First saleFirst sale target

Convert wave 1

  • Deliver the free clip to every replier inside 12 hours.
  • Send the $49 checkout link in the same delivery email.
  • Follow up on threads that went quiet.

Deliverable: First paid Clip Pack collected.

Day 11Fulfilment

Delivery SOP

  • Fulfil every paid order and confirm the receipts opened.
  • Template the delivery email with the download link and receipt explanation.
  • Ask each buyer for one sentence of feedback.

Deliverable: Written delivery SOP and first paid fulfilments shipped.

Day 12Outreach wave 2

Second variant

  • Send 40 more messages with a different opening line.
  • Reply to every public editing request found that day.
  • Offer the $99 monthly to anyone posting weekly.

Deliverable: 80 cumulative sends, 2 or more sales.

Day 13Verification page

Make the receipt public

  • Build a public /verify page that accepts a hash and returns a receipt.
  • Link the page from every delivery email.
  • Add the verification link to the ZIP readme.

Deliverable: Public verification page live.

Day 14Week 2 review

Measure and cut

  • Count sends, replies, deliveries and sales per variant.
  • Kill the worst-converting message and double the best one.
  • Rewrite the offer using buyer wording from replies.

Deliverable: Conversion table and a revised offer.

Week 3 · Repeat & systematize · 7 days
Day 15Monthly tier

Recurring revenue

  • Add the $99/month Stripe subscription with a 12-clip quota counter.
  • Email every past buyer the upgrade link.
  • Track the upgrade rate separately from new sales.

Deliverable: Working monthly subscription with quota enforcement.

Day 16Outreach wave 3

Shift to brands

  • Send 50 messages to small e-commerce brands with product demo footage.
  • Post a before/after clip pair with both receipts.
  • Ask two buyers for a one-line quote with written permission.

Deliverable: 180 cumulative sends, two permissioned quotes.

Day 17Reliability

Queue and retries

  • Move rendering to a worker with retries and a hard job timeout.
  • Add a failure email that offers an automatic refund.
  • Target under 20 minutes per job end to end.

Deliverable: Retry-safe job queue with refund fallback.

Day 18Pricing test

Second SKU

  • Add a $79 rush option with 12-hour turnaround.
  • Tag each checkout so the tier choice is measurable.
  • Keep the $49 pack as the visible anchor.

Deliverable: Two live price points with tagged Stripe links.

Day 19Outreach wave 4

Communities

  • Send 50 more direct messages.
  • Answer editing requests in two creator Discords.
  • Offer a free clip to any engaged community moderator.

Deliverable: 230 cumulative sends.

Day 20Delivery polish

Shareable output

  • Build a shareable delivery page per job with clip and receipt links.
  • Add a second caption style preset.
  • Make the download link work without login for 30 days.

Deliverable: Shareable delivery page per order.

Day 21Week 3 review

Margin and objections

  • Recompute cost per job and margin per pack from the Stripe export.
  • Decide whether new buyers pay $59 rather than $49.
  • List the top three objections heard verbatim.

Deliverable: Margin table and objection list.

Week 4 · Scale what works · 7 days
Day 22Objection copy

Landing page rewrite

  • Rewrite the headline around the top objection.
  • Add an FAQ covering price, turnaround and what a hash proves.
  • Embed one 30-second sample clip on the page.

Deliverable: Revised landing page live.

Day 23Outreach wave 5

Launch-date targeting

  • Send 60 messages to creators with a visible launch or course date.
  • Follow up once with everyone who opened but did not reply.
  • Log which trigger event each prospect matched.

Deliverable: 290 cumulative sends with trigger tags.

Day 24Referral loop

Word of mouth

  • Add a referral code to every receipt email worth one free clip.
  • Track redemptions manually in the sheet.
  • Ask every buyer to forward one clip to a peer.

Deliverable: Referral code live and redemption list started.

Day 25Failure testing

Operational safety

  • Test three deliberately broken uploads against the pipeline.
  • Confirm the timeout triggers a refund automatically.
  • Write a one-page failure runbook.

Deliverable: Failure runbook tested against real broken inputs.

Day 26Outreach wave 6

Volume and receipts

  • Send 60 more direct messages.
  • Post a receipt-focused explainer thread with a real sample.
  • Offer two newsletter writers a free pack with no expectation of coverage.

Deliverable: 350 cumulative sends.

Day 27Upsell

Monthly conversion

  • Email every one-time buyer the $99 monthly offer.
  • Offer a three-pack bundle at $120.
  • Record upgrade decisions per buyer.

Deliverable: Upsell sent to all existing buyers.

Day 28Collections

Reconcile the money

  • Verify every payment landed in the TrustMRR-connected account.
  • Reconcile refunds and chargebacks against the Stripe export.
  • Export a clean revenue statement for the window.

Deliverable: Reconciled revenue statement.

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

Last conversions

  • Send 60 final messages with an explicit deadline framing.
  • Fulfil every remaining order within 12 hours.
  • Confirm every receipt was delivered and opened.

Deliverable: 410 cumulative sends, all orders fulfilled.

Day 30Close

Numbers and post-mortem

  • Recompute hackathon profit from the Stripe export.
  • Write a one-page post-mortem with sends, replies, sales, refunds and margin.
  • Publish the changelog entry and the final sample bundle.

Deliverable: Final profit figure and a public post-mortem.

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 from stated assumptions, not verified revenue.
  • Conservative: roughly 410 outreach messages convert at about 0.7% to paid, giving 3 buyers at the $49 pack price.
  • Base: the same funnel converts at about 2.4%, giving 10 buyers at the $49 pack price.
  • Upside: stronger reply rate plus a few $99 monthly conversions, giving 28 buyers at a blended $62 ARPU (28 x 62 = 1736).
  • Payment processing assumed at roughly 4.5-5% blended, based on Stripe at 2.9% + $0.30 per charge plus about 1% international and currency cost.
  • ad_spend_usd is 0 in every scenario because acquisition is organic direct outreach; no ads, sponsored posts or affiliate payouts are planned.
  • Operating cost covers Whisper at about $0.006 per minute, container render time per job, Vercel, Supabase, email and the domain.
  • Refunds are 0 in conservative and base and one $49 pack in upside; chargebacks are 0 in all scenarios.
  • Hackathon profit excludes hosting and AI delivery costs; business profit subtracts them.
  • Per-pack delivery cost stays near $1-3, well below the $49 price, so no sale is below cost.

Conservative

3 customers
$147
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$7
Paid marketing
$0
Hackathon profit
$140
Operating costs
$30
Business profit
$110

Base case

10 customers
$490
collected revenue · avg payment $49
Refunds
$0
Chargebacks
$0
Payment fees
$22
Paid marketing
$0
Hackathon profit
$468
Operating costs
$75
Business profit
$393

Optimistic

28 customers
$1,736
collected revenue · avg payment $62
Refunds
$49
Chargebacks
$0
Payment fees
$87
Paid marketing
$0
Hackathon profit
$1,600
Operating costs
$160
Business profit
$1,440

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$490
Payment fees (3.9%)
$19
Paid marketing
$0
Hackathon profit
$471
Business profit
$396

Hypothetical arithmetic, not a forecast. The fee rate is a flat 3.9% assumption, refunds and chargebacks are left at zero here, and none of this is tracked data.

Scenario models from stated assumptions, not verified revenue. No customers, partnerships or traction exist at the time of writing.

Section 7 of 8

Main risks and validation experiments

Risk 1Free editors such as CapCut and Descript erode willingness to pay $49 for clips alone.

Mitigation

Sell the receipt and the same-day turnaround, not the edit; lead every message with the provenance PDF.

Validation experiment

Send 20 creators their free clip with the $49 ask in the same email and record explicit yes or no.

Kill criteria

If fewer than 1 in 40 asks converts by day 18, drop to $29 per pack or move to a paid single-clip offer at $19.

Risk 2Render cost or failure rate spikes on longer uploads, making paid orders unprofitable or undelivered.

Mitigation

Cap uploads at 15 minutes, use a fast preset, scale once to 1080x1920, and add a job timeout with automatic refund.

Validation experiment

Run five real 10-15 minute videos through the pipeline on day 6 and log cost, memory and wall-clock time.

Kill criteria

If cost per job exceeds $8 or the failure rate exceeds 20%, cut output to two clips or 720p and re-measure.

Risk 3Outreach converts far below the assumed rate, leaving the month near zero revenue.

Mitigation

Send 410 messages across six waves with three message variants and a fixed 48-hour single follow-up.

Validation experiment

Track reply and paid-conversion rate per variant from wave 1 on days 9-12.

Kill criteria

If 120 sends produce zero paid conversions, change the segment from course creators to DTC brands or change the offer to a $19 single clip.

Risk 4Buyers ignore the provenance receipt, removing the differentiator and the word-of-mouth hook.

Mitigation

Put the verification link in the delivery email and ask about usage in the same follow-up.

Validation experiment

Ask every buyer one question: did you send the receipt to anyone, and who.

Kill criteria

If 0 of the first 5 buyers used or sent a receipt, de-emphasise receipts and lead with turnaround and price.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Register the domain and create Vercel, Supabase, Stripe and Whisper API accounts.
  • Connect the Stripe payment account to TrustMRR before any checkout is exposed.

Output: Live empty deployment and a payments account wired to TrustMRR.

Hours 3-5

  • Build the upload form writing to Supabase storage with signed URLs.
  • Create the jobs table with the five states.

Output: Working upload that creates a job row.

Hours 6-9

  • Call Whisper and store word-level timestamps.
  • Generate the silence and filler cut list JSON.

Output: Cut list JSON for one sample video.

Hours 10-14

  • Run FFmpeg in a container to cut, crop to 9:16 and burn captions.
  • Render the first three candidate clips from your own footage.

Output: First captioned vertical clip rendered end to end.

Hours 15-18

  • Compute SHA-256 for source and output files.
  • Render the one-page PDF receipt.

Output: One signed provenance receipt PDF.

Hours 19-24

  • Publish a landing page with a sample clip and receipt.
  • Wire Stripe Checkout at $49 and $99/month.
  • Send the first 10 outreach messages.

Output: Public URL with live checkout and 10 messages out.

Complete report

Full 30-day launch report

Read the full generated report

ClipTrust Proof Clips - 30-Day Public Report

Concept version 1. JEV score 61.6/100, band C. Single-operator plan, 30 days, no team and no funding.

1. Product opportunity and positioning

The buyer is one person: a solo course creator or a 1-10 person e-commerce brand that already owns raw footage - a testimonial, a product demo, a founder talking head - and needs clips to post this week. They do not want an editor. They want three finished vertical clips with captions, delivered the same day.

What they pay today is either $150-400 to a freelance editor or two hours inside CapCut. ClipTrust Proof Clips is a $49 fixed pack: one upload in, three 9:16 captioned clips out, plus a PDF provenance receipt per clip holding the SHA-256 of the source file, the SHA-256 of the delivered file, the processing parameters and a timestamp.

The receipt is the wedge. Silence removal and auto-captions are commodity. A brand reposting a customer's words has a legitimate question to answer about whether the clip was altered, and a hash receipt gives the creator a specific artifact to attach to a testimonial page or a sponsor pitch. That artifact is also the reason a buyer forwards the tool to another creator, which matters because there is exactly one acquisition channel here: direct outreach.

JEV scored the concept 61.6/100, band C. Its high-confidence strengths are speed to first revenue (8.46 normalized) and solo build feasibility (7.38). Its weaknesses are market demand (4.77) and monetization (4.87). This plan attacks the weaknesses.

Demand is narrowed by a trigger event: a creator with a launch date, a testimonial campaign, or an existing weekly posting cadence. Those are the moments when a $49 charge is approved in one message instead of a thread. Monetization gets a second path, a $99/month tier for creators posting weekly, so 30 days build a recurring base rather than 30 isolated transactions.

Nothing here is verified traction. There are no customers, no partnerships and no revenue at the time of writing. Every number is a projection from stated assumptions.

2. Smallest sellable MVP

One upload box, one payment, one ZIP. The buyer pays $49 through Stripe Checkout, uploads an MP4 under 15 minutes and 1 GB (or pastes a file link), and receives an email with a download page. The ZIP holds three MP4 clips in 9:16 with burned-in captions and silences and filler words removed, plus three one-page PDF receipts.

In scope for day 6: upload, Whisper transcription, silence and filler cut list, FFmpeg render, caption burn-in, three-segment selection, SHA-256 receipts, Stripe Checkout, emailed delivery, and the $99 monthly tier.

Out of scope: b-roll, team seats, social scheduling, a mobile app, a browser timeline editor, brand kits, a public API. Each is a week of work no first buyer has asked for.

The demo flow is the sales pitch. Send a creator three clips made from their own footage, attach the receipt, then the checkout link. The artifact does the selling; the founder never has to describe an editing feature.

3. Technical implementation plan

Next.js on Vercel serves the landing page, checkout and download page. Supabase holds one job row per order with five states and stores the source and output files behind signed URLs. A container worker on Cloud Run or Fly.io runs FFmpeg, because Vercel functions cannot hold a multi-minute encode. Whisper supplies word-level timestamps. A Stripe webhook flips the job to paid. Resend sends the delivery email.

Pipeline: upload, job row, Whisper, cut list, FFmpeg cut and concat and crop, caption burn-in, segment scoring, three outputs, hash each output, PDF receipt, ZIP, email.

Segment selection is deliberately dumb: split the transcript on sentence boundaries, score every 15-45 second window by speech density, sentence completeness and absence of filler, take the top three non-overlapping windows. Deterministic and free. An optional single LLM call can re-rank the windows, with the heuristic as fallback.

The hardest technical risk is render time and memory on long files. A 15-minute 1080p source with caption burn-in can exhaust a small container and exceed the job timeout, leaving a paid order undelivered. Mitigations: hard upload cap, fast preset, one scale to 1080x1920, timeout with automatic refund and a failure email.

AI appears in two places only: transcription, and clip-window ranking.

4. Pricing and monetization

Two SKUs. Clip Pack at $49 one-time: three clips, silence and filler removal, receipts. Creator Monthly at $99/month: up to 12 clips, priority queue, receipt archive and verification page. No free tier - on a $49 product it attracts the wrong buyer and burns render time.

Cost per job at this volume is roughly $1-3. Fixed monthly tooling sits near $50-60. Margin per pack is above 90%, so no sale is close to below cost.

The first-revenue offer is narrow on purpose: one raw video in, three captioned clips plus signed receipts back today, free; $49 if they are usable.

Upsell path: pack, then monthly at $99 after a second one-off purchase, then a three-pack bundle at $120 for creators with a launch date. Only the monthly tier survives past day 30.

5. First-customer acquisition

One channel: direct outreach where creators already post raw footage and ask for editing help. Sources are X posts showing unedited testimonial or demo footage, course-creator Discords and Slacks, small DTC brand founder communities, reply threads under editing requests, and build-in-public demo posts.

Daily action: 10-15 personalised messages, each referencing a specific public video of theirs, offering one free clip. Deliver within 12 hours of any reply. Log every send, reply, delivery and sale in one sheet. Follow up exactly once at 48 hours.

Message: saw your testimonial clip in the thread; here is a vertical captioned version plus a receipt that hashes the file so you can show it was not altered; want the other two clips, it is $49 for the pack, delivered today.

Week-one goal: 80 messages, 8 free clips delivered, 2 paid packs.

6. 30-day execution roadmap

Week 1 builds and sells nothing: days 1-5 ship upload, transcription, render, segment selection and receipts; day 6 runs five real videos end to end and logs cost per job; day 7 puts a live Stripe checkout on the domain.

Week 2 is the first sales push: day 8 builds a 150-name prospect list with a linked video per prospect, day 9 sends 40 messages, day 10 targets the first paid pack, days 11-13 add fulfilment SOP and a public verification page, day 14 cuts the worst message variant.

Week 3 adds recurring revenue and reliability: the $99 monthly tier with a quota counter on day 15, wave 3 outreach to brands on day 16, a retry-safe worker with refund fallback on day 17, a $79 rush SKU on day 18, and a shareable delivery page on day 20. Day 21 recomputes margin from the Stripe export.

Week 4 is volume and conversion: landing page rewritten around the top objection on day 22, waves 5 and 6 bringing cumulative sends to 350 by day 26, a referral code on day 24, failure testing on day 25, and the upsell email to every buyer on day 27. Day 28 reconciles payments, refunds and chargebacks.

Days 29-30 send a final wave with deadline framing and close with a reconciled profit number and a public post-mortem.

7. Revenue and profit scenarios

All three scenarios are projections, not verified revenue.

Conservative: 3 buyers at $49, gross revenue $147, refunds $0, chargebacks $0, payment fees $7, ad spend $0. Hackathon profit $140. Business profit after $30 of hosting and API delivery cost: $110.

Base: 10 buyers at $49, gross revenue $490, refunds $0, chargebacks $0, payment fees $22, ad spend $0. Hackathon profit $468. Business profit after $75 of operating cost: $393.

Upside: 28 buyers at a blended $62 ARPU (packs plus a few monthly conversions), gross revenue $1,736, refunds $49, chargebacks $0, payment fees $87, ad spend $0. Hackathon profit $1,600. Business profit after $160 of operating cost: $1,440.

Two profit numbers matter and are not interchangeable. Hackathon profit is collected revenue minus refunds, chargebacks, payment fees and paid marketing spend; hosting, domains and AI delivery are not deducted for ranking. Business profit subtracts those operating costs as well. Payment fees assume Stripe at 2.9% + $0.30 plus about 1% international and currency cost, roughly 4.5-5% blended. Ad spend is zero in all three scenarios because acquisition is organic outreach only.

8. Risks and validation experiments

Free editors erode willingness to pay. Test: 20 creators get a free clip and the $49 ask in the same email; record explicit yes or no. Kill trigger: fewer than 1 in 40 converting by day 18 means dropping to $29 or switching to a paid single clip at $19.

Render cost or failure on long uploads. Test: five real 10-15 minute videos on day 6, logging cost, memory and wall-clock time. Kill trigger: cost above $8 per job or failure rate above 20% means cutting to two clips or 720p.

Outreach converts below plan. Test: reply and paid-conversion rate per message variant from wave 1. Kill trigger: 120 sends with zero paid conversions means changing segment or offer, not sending more.

Receipts are ignored, removing the differentiator. Test: ask every buyer whether they sent the receipt to anyone. Kill trigger: 0 of the first 5 buyers used it means leading with turnaround and price instead.

9. First 24-hour action plan

Hours 1-2: accounts and domain, Stripe connected to TrustMRR before any checkout is public. Hours 3-5: upload form and jobs table. Hours 6-9: Whisper plus cut-list JSON. Hours 10-14: FFmpeg container producing the first captioned vertical clip. Hours 15-18: SHA-256 hashing and the PDF receipt. Hours 19-24: landing page, live $49 checkout, first 10 outreach messages sent. By hour 24 the founder has a public URL that can take money and a first pipeline that produced a real clip and a real receipt.

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 →