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

Misheard Report

A per-video clarity report that shows non-native English YouTube creators exactly which lines their US/EU viewers mishear, and hands back a corrected caption file ready to upload.

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.35/10
MVP build (solo)
4 days
Launch price
$49
Sales to $1,000 revenue
21 customers
First paying customer
Personalized cold email to creators whose latest video the founder has already analyzed, with three real timestamped flagged lines in the opening.
Who pays

Solo or two-person YouTube channels at 10k-500k subscribers, run by non-native English speakers in India, Nigeria, the Philippines or Brazil in tech, education or finance, who are actively pitching US/EU sponsors or pushing US watch time.

Biggest execution risk

Market demand 4.6/10

Narrow the buyer to a segment with an urgent, already-budgeted problem and reference the specific trigger event that creates willingness to pay.

Why this could work in 30 days: one founder can ship the MVP in 4 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.7/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

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

0/10
Entry price
$49
Solo build
4 days
30d base revenue
$793
30d profit†
$723
Section 1 of 8

Product opportunity and positioning

Target customer

Solo or two-person YouTube channels at 10k-500k subscribers, run by non-native English speakers in India, Nigeria, the Philippines or Brazil in tech, education or finance, who are actively pitching US/EU sponsors or pushing US watch time.

Why now

The prospect list is public, the pitch is the prospect's own flagged lines, and the deliverable is a file used the same day, so the decision takes minutes and needs no call or trial.

Problem

Global viewers drop off or comment that the English was hard to follow, and the creator cannot hear the problem in their own accent or see it in their auto-captions.

Solution

Paste a YouTube URL; the pipeline pulls the auto-caption track, flags risky lines segment by segment, and returns a one-page Global Clarity Score report with timestamped 'what you said vs what a US viewer hears' plus a corrected .srt/.vtt to re-upload.

Differentiation · Auto-captions transcribe without judgment, subtitle editors rewrite text but not spoken phrasing, and a native friend is slow and unavailable; this is a paid, timestamped, corrected caption file sold per video.

Opportunity and positioning

Misheard Report sells a per-video clarity audit to non-native English YouTubers between 10k and 500k subscribers in tech, education and finance. JEV scored this concept 63.5/100 (band C). The weakest criterion is market demand at 4.57, and the fix is not a broader pitch — it is a narrower trigger. The buyer is not "any non-native creator". It is the creator who just received a US sponsor inquiry, or a comment saying "couldn't follow this", or who watched retention fall on an English tutorial. That moment converts because the loss is already visible and already costs money.

The insight inherited from the original product is durable: non-native speakers cannot self-diagnose how their English lands on a listener. What changed is who pays. Learners need months of practice and churn; creators already have a published artifact, a public business email and a sponsor deadline. The deliverable is a file, not a habit.

Auto-captions transcribe; they do not judge. A subtitle editor rewrites text but not the spoken phrasing. A native friend is free, slow and unavailable. Misheard Report occupies that gap: paste a URL, get a timestamped list of lines a US viewer misreads, plus a rewritten .srt the creator drops into YouTube Studio the same day.

Speed to first revenue scored 8.71 — the highest criterion — because the founder can run the analysis before asking for money. Sending a prospect three real timestamped lines from their own last upload is a demo, not a pitch. Defensibility scored 5.82, so the plan does not rely on a moat; it relies on a solo founder doing more personalized analyses per day than anyone else will bother to do.

The wedge holds only if three things stay true: business emails are visible on the About tab, most target channels have auto-caption tracks, and a corrected caption file is genuinely usable in YouTube Studio. Day 1 through Day 5 exist to prove those three before a single message is sent.

Positioning statement: for non-native creators who lose US watch time and sponsor deals to unclear English, Misheard Report is the $49 file that names the exact misheard lines and hands back a fixed caption track — not a course, not a tutor, not a subtitle marketplace.

Section 2 of 8

Smallest sellable MVP

A Stripe payment link that, after payment, takes a YouTube URL, emails a one-page misheard report and returns a downloadable corrected .srt the creator can re-upload.

Must-have features

  • YouTube URL intake and auto-caption fetch with a clear failure message when no track exists
  • Timestamped segment builder producing per-line risk flags with the original text
  • Rewritten global-English suggestions for each flagged line
  • Corrected .srt/.vtt generator that preserves original timing
  • One-page report: Global Clarity Score, top 10 recurring fixes, timestamped misread table
  • Stripe Checkout payment link and magic-link delivery page with no accounts
  • Resend email delivery when a report finishes
  • Batch mode: 5-video channel audit with cross-video recurring fixes

Explicitly out of scope

  • No audio, pronunciation or accent scoring
  • No video editing, dubbing or re-recording
  • No YouTube OAuth channel connection or auto-publishing
  • No dashboard, team seats or user accounts
  • No non-English source videos in the first 30 days
  • No subscription billing engine at launch

Demo flow (what the buyer sees)

  1. Prospect pastes or sends a YouTube URL
  2. System fetches the auto-caption track and builds timed segments
  3. LLM rubric pass flags risky lines per segment
  4. Rewrite pass produces global-English replacements
  5. Report renders with Global Clarity Score and top 10 fixes
  6. Corrected .srt/.vtt is generated with original timings
  7. Delivery email with magic link sends the PDF and caption files
Build plan

Technical implementation plan

Stack

Next.js on Vercelyoutube-transcript plus YouTube Data API v3 fallbackOpenAI or Gemini API for the rubric and rewrite passesStripe Checkout payment linksResend for delivery emailSupabase or Vercel KV for job stateHTML-to-PDF for the one-page report

Architecture

A single Next.js app on Vercel owns three routes: a public intake form, a Stripe webhook, and a magic-link delivery page. Intake writes a job row to Supabase, then a background route pulls the caption track, chunks it into timed segments from caption cue start/end values, and sends each chunk through one LLM rubric call that returns structured JSON flags. A second pass rewrites only flagged lines. The .srt generator reattaches the original start/end timestamps to rewritten text so nothing desyncs, renders the report to PDF, stores both files, and triggers a Resend email with a signed link. No accounts, no sessions beyond the signed link.

Build steps

  1. Scaffold Next.js repo, deploy a hello-world route to Vercel
  2. Add caption fetch route and test 10 real videos including no-caption cases
  3. Build segment builder that preserves cue start/end times
  4. Write the rubric prompt returning strict JSON flags per segment
  5. Write the rewrite pass and the .srt/.vtt serializer
  6. Render the one-page report to PDF from an HTML template
  7. Add Stripe payment link plus webhook that creates the job
  8. Add Supabase job table and a polling worker route
  9. Add Resend delivery email with signed magic link
  10. Run 5 end-to-end tests on known videos and fix desync

AI components

  • Rubric pass scoring idiom opacity, region-specific phrasing, run-on density and filler rate per segment
  • Rewrite pass producing global-English replacements that fit the original time window
  • Top-10 recurring-fix clustering across a 5-video channel audit
Hardest technical risk: Caption timing desync in the corrected .srt: if rewritten lines are longer than the cue window they spill into the next line and the file becomes unusable.
Section 3 of 8

Pricing and monetization

Single Video Report

Entry offer
$49 one-time

For Creator testing the product on one video before a sponsor pitch

  • Timestamped misread table
  • Global Clarity Score
  • Corrected .srt/.vtt file

Channel Audit

$149 one-time

For Creator with a sponsor deal or global push in progress

  • 5 video reports
  • Cross-video recurring-fix list
  • 5 corrected caption files

Clarity Pass

$199 / month

For Creator publishing weekly who wants ongoing clarity

  • 4 video reports per month
  • Corrected caption files
  • Priority 20-minute delivery

Model: One-time per-video and per-channel purchases at launch, with a monthly recurring tier added only after repeat buyers appear.

First revenue offer: "I already ran this on your last video — here are 3 lines a US viewer mishears at 02:14, 07:41 and 11:03. Full report plus the rewritten .srt is $49, in your inbox in 20 minutes."

Expected ACV: $99

Upsell path: Every single-video report ends with a teaser of recurring fixes across the channel and a $149 Stripe link; buyers of two or more single reports get offered the $199 monthly Clarity Pass.

Target customers
20
Revenue model
$1,980
Costs
$130
Profit model
$1,850
Section 4 of 8

First-customer acquisition

Primary channel

Personalized cold email to creators whose latest video the founder has already analyzed, with three real timestamped flagged lines in the opening.

Where to find them

  • YouTube search for 'python tutorial', 'excel tutorial', 'IELTS speaking' filtered to 10k-500k subs, bio signalling India/Nigeria/Philippines/Brazil
  • About tab business emails on channels with recent US-sponsor mentions in descriptions
  • Creators replying 'couldn't follow' style comments in their own comment sections
  • X/Twitter posts about failing a sponsor pitch or losing US watch time
  • Reddit and Discord communities for Indian and global YouTube creators (post only, never spam links)

Exact outreach motions

  • Send 20 emails/day with 3 real timestamped flagged lines from the prospect's latest upload
  • Day 3 follow-up adding one more flagged line and the Global Clarity Score
  • Day 7 follow-up attaching the corrected .srt excerpt of their own intro
  • Post one anonymized before/after breakdown in two creator subreddits
  • DM 10 creators per day on X who posted about sponsor or retention problems

Message template

Hi [Name] — I ran a clarity pass on your video "[title]". Three lines a US viewer likely misreads: 02:14 "[line]", 07:41 "[line]", 11:03 "[line]". The full report plus a corrected .srt you can upload straight to Studio is $49: [stripe link]. No call needed, delivered in 20 minutes.
Week-one goal: 150 personalized emails sent with real flagged lines, at least 12 replies, and one paid $49 order.
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 1Fetch spike

Prove caption fetching works

  • Scaffold the Next.js repo and deploy a hello-world route to Vercel.
  • Test youtube-transcript on 10 real target videos, including no-caption cases.
  • Store raw transcript JSON in a local fixtures folder.

Deliverable: Working caption-fetch route plus a fixtures set.

Day 2Rubric

Segment builder and flag pass

  • Chunk captions into timed segments preserving cue start/end.
  • Write the rubric prompt returning strict JSON flags per line.
  • Log flags for 5 test videos and eyeball precision.

Deliverable: Rubric pass returning per-line flags.

Day 3Rewrite

Corrected caption file

  • Write the rewrite pass for flagged lines only.
  • Serialize a corrected .srt/.vtt that keeps original timings.
  • Load one file into a player and verify sync.

Deliverable: Downloadable corrected .srt with verified timing.

Day 4Money path

Report, payment, delivery

  • Build the one-page HTML report template with score and top 10.
  • Add Stripe payment link plus webhook that creates a job row.
  • Add Resend delivery email with a signed magic link.

Deliverable: End-to-end paid flow from URL to inbox.

Day 5MVP shipMVP shipped

Freeze scope and go live

  • Run 5 end-to-end tests and fix desync or fetch failures.
  • Record a 90-second demo showing report and .srt.
  • Publish the live URL with pricing on the page.

Deliverable: MVP live and self-tested.

Day 6List build

150 prospect channels

  • Search YouTube for '[topic] tutorial' in tech, education, finance.
  • Filter to 10k-500k subs with non-native bios.
  • Capture business emails from the About tab into a sheet.

Deliverable: 150-row prospect sheet with emails.

Day 7Pre-analysis

Run pipeline on prospects

  • Batch-run the pipeline on 25 prospect latest uploads.
  • Record each Global Clarity Score and strongest flags.
  • Pick the 20 clearest examples for outreach.

Deliverable: 25 pre-analyzed prospects with flagged lines.

Week 2 · Launch & first sale · 6 days
Day 8First sends

20 personalized emails

  • Send 20 emails with 3 real timestamped lines each.
  • Track opens, replies and Stripe link clicks.

Deliverable: 20 emails sent, tracker live.

Day 9Volume

More sends plus public proof

  • Send 20 more personalized emails.
  • Post one anonymized before/after in two creator subreddits.

Deliverable: 40 total emails, one public post.

Day 10Follow-up

Day-3 sequence

  • Send day-3 follow-ups with a second flagged line.
  • Rewrite the opening line based on reply patterns.

Deliverable: Follow-up batch sent, revised opener.

Day 11DMs

X outreach

  • Send 40 more emails to pre-analyzed prospects.
  • DM 10 creators on X who posted about sponsor or retention issues.

Deliverable: 80 total emails, 10 DMs.

Day 12First saleFirst sale target

Close and deliver

  • Close at least one $49 order via Stripe link.
  • Deliver the report and .srt within 20 minutes.
  • Ask buyer what was missing from the report.

Deliverable: First collected revenue and one feedback note.

Day 13Upsell

Channel audit teaser

  • Add the cross-video recurring-fix teaser to every report.
  • Email all single-video buyers the $149 audit link.

Deliverable: Upsell live in the report template.

Week 3 · Repeat & systematize · 8 days
Day 14Retro

Fix what blocks sales

  • Review replies and note the top objection verbatim.
  • Ship one fix that removes that objection.
  • Confirm corrected .srt uploads cleanly in Studio.

Deliverable: One objection removed, verified upload.

Day 15Batch mode

5-video channel audit

  • Loop the pipeline over 5 videos and aggregate recurring fixes.
  • Zip 5 corrected caption files for delivery.

Deliverable: Channel Audit deliverable working.

Day 16Trigger targeting

Sponsor-inquiry creators

  • Send 40 emails to creators showing sponsor or brand mentions.
  • Emphasize sponsor-readiness in the opener.

Deliverable: 40 trigger-targeted emails sent.

Day 17Public proof

Case study page

  • Publish an anonymized sample report page on the site.
  • Link it in every future outreach message.

Deliverable: Public sample report URL.

Day 18Follow-up

Day-7 sequence

  • Send day-7 follow-ups with an .srt excerpt of their own intro.
  • Re-target everyone who opened but did not buy.

Deliverable: Follow-up batch with attachment excerpt.

Day 19Testimonials

Proof from buyers

  • Ask 2 buyers for a one-line testimonial, no logos without consent.
  • Send 40 new emails.

Deliverable: Up to 2 quotes, 40 sends.

Day 20Recurring tier

Clarity Pass

  • Create the $199 monthly Stripe link with priority queue.
  • Offer it to any repeat buyer.

Deliverable: Recurring tier purchasable.

Day 21Metrics

Cut losing angle

  • Compute reply rate and buy rate per message angle.
  • Kill the worst-performing angle and rewrite it.

Deliverable: One-angle decision with numbers.

Week 4 · Scale what works · 9 days
Day 22Second segment

Nigeria and Philippines batch

  • Build 50 prospects in Nigeria and Philippines finance education.
  • Send 50 personalized emails.

Deliverable: 50 sends to a new segment.

Day 23Precision

False-positive audit

  • Re-read 10 delivered reports and mark over-flagged lines.
  • Tighten the rubric prompt to reduce false positives.

Deliverable: Updated prompt with measured false-positive drop.

Day 24Trust

Refund policy

  • Publish a plain refund policy and FAQ on the site.
  • Send 50 new emails referencing the policy.

Deliverable: FAQ and refund page live.

Day 25Upsell push

Audit conversions

  • Email every single-video buyer with the $149 audit.
  • Add the recurring teaser to delivery emails.

Deliverable: Upsell email to the full buyer list.

Day 26Public proof 2

Second breakdown post

  • Post a second anonymized breakdown in a creator community.
  • Send 50 new emails.

Deliverable: Second public post plus 50 sends.

Day 27Reliability

Failure handling

  • Add retries and a clear 'no caption track' message.
  • Check the error log and fix the top failing case.

Deliverable: Retry logic and monitored error log.

Day 28Pipeline

Consolidate metrics

  • Pull sends, replies, sales and refunds into one sheet.
  • Send 50 new emails with the winning angle.

Deliverable: Single metrics sheet plus 50 sends.

Day 29Final push

Clear backlog

  • Send the last outreach batch with the winning angle.
  • Deliver every pending report within 20 minutes.

Deliverable: Zero pending deliveries.

Day 30Books

Close the 30 days

  • Count collected revenue, refunds and API costs.
  • Write the post-30-day plan based on measured rates.

Deliverable: Verified 30-day P&L and next-30 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

  • Blended average order value near $99 across the $49/$149/$199 tiers is a hypothesis, not observed pricing.
  • Conservative assumes 3 buyers from roughly 250-300 personalized sends.
  • Base assumes 9 buyers from roughly 450 sends with a mix skewed to $49.
  • Upside assumes 20 buyers, some $149 audits, from 500+ sends plus public posts.
  • Most target channels have auto-caption tracks; manual-caption-only channels are out of scope.
  • Costs cover LLM and API usage, Stripe fees, Resend and Vercel within one month.
  • Delivery under 20 minutes is assumed achievable with one LLM pass over a 10-20 minute transcript.
  • No customer has been contacted or validated at the time of writing.

Conservative

3 customers
$247
collected revenue · avg payment $82
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): $202.

Base case

9 customers
$793
collected revenue · avg payment $88
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): $723.

Optimistic

20 customers
$1,990
collected revenue · avg payment $100
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): $1,840.

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$441
Payment fees (3.9%)
$17
Paid marketing
$0
Hackathon profit
$424
Business profit
$424

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.

These are projections only. They are not verified revenue, not existing customers, and not traction of any kind.

Section 7 of 8

Main risks and validation experiments

Risk 1Creators believe their English is fine and do not perceive the problem, so outreach is ignored.

Mitigation

Lead with their own timestamped lines and a competitor-free score, never with a claim about their English.

Validation experiment

Send 20 emails with real flagged lines and count replies mentioning the lines specifically.

Kill criteria

Fewer than 4 of 100 emails get any reply after two follow-ups.

Risk 2YouTube caption fetching breaks or rate-limits, blocking the core pipeline.

Mitigation

Add a YouTube Data API fallback and a clear 'no caption track' message with manual file upload.

Validation experiment

Run the fetch route against 50 videos and record failure rate.

Kill criteria

Failure rate above 30% on target channels after the fallback is added.

Risk 3The LLM over-flags normal non-native phrasing and reports feel insulting.

Mitigation

Cap flags at the top 10 highest-risk lines and phrase all fixes as 'heard as', never 'wrong'.

Validation experiment

Have 10 delivered reports re-graded for false positives before scaling sends.

Kill criteria

More than one refund request citing tone or accuracy in the first 10 sales.

Risk 4Corrected .srt desyncs from audio and the deliverable is unusable.

Mitigation

Preserve original cue timings and enforce a character-per-second ceiling in the rewrite pass.

Validation experiment

Upload 5 generated files into a video player and check three random timestamps each.

Kill criteria

Any confirmed desync that the timing guardrails cannot fix within one day.

Risk 5Cold outreach is framed publicly as unsolicited or condescending.

Mitigation

Use public business emails only, one follow-up maximum after day 7, and honor any opt-out immediately.

Validation experiment

Review every send against a two-line etiquette checklist before day 8.

Kill criteria

Two public complaints about the outreach approach.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Create the Next.js repo and deploy a hello-world route to Vercel.
  • Set up Supabase and an OpenAI API key with spend caps.

Output: Deployed skeleton and capped API keys.

Hours 3-5

  • Build the caption fetch route using youtube-transcript.
  • Test against 10 target videos and record pass/fail and failure reasons.

Output: Fetch route plus a 10-video reliability log.

Hours 6-8

  • Build the timed segment builder from caption cues.
  • Draft the rubric prompt and run it on one transcript.

Output: First flagged-lines JSON for a real video.

Hours 9-11

  • Write the .srt serializer that keeps original timings.
  • Verify one corrected file in a local player.

Output: One corrected .srt with verified sync.

Hours 12-14

  • Draft the opening outreach message with a real flagged line.
  • Pick 5 target channels and confirm their business emails are public.

Output: Final message template and 5 confirmed leads.

Complete report

Full 30-day launch report

Read the full generated report

Misheard Report — 30-Day Solo Launch Plan

1. Product opportunity and positioning

Misheard Report sells a per-video clarity audit to non-native English YouTubers between 10k and 500k subscribers in tech, education and finance. JEV scored the concept 63.5/100 (band C). The weakest criterion is market demand at 4.57, and the correction is not a broader pitch — it is a narrower trigger. The buyer is the creator who just got a US sponsor inquiry, or a comment saying "couldn't follow this", or who watched retention drop on an English tutorial. That creator already feels the loss and already knows it costs money.

The insight inherited from the original product holds: non-native speakers cannot self-diagnose how their English lands on a listener. What changed is who pays. Learners need months of practice and churn; creators already have a published video, a public business email and a sponsor deadline. The deliverable is a file, not a habit.

Auto-captions transcribe without judging. A subtitle editor rewrites text but not spoken phrasing. A native friend is free, slow and usually unavailable. Misheard Report sits in that gap: paste a URL, receive a timestamped list of lines a US viewer misreads, plus a corrected .srt the creator drops into YouTube Studio the same day.

Speed to first revenue scored 8.71, the highest criterion, because the founder can run the analysis before asking for money. Three real timestamped lines from the prospect's own upload function as a live demo. Defensibility is modest at 5.82, so this plan does not depend on a moat. It depends on one person doing more personalized analyses per day than anyone else will bother to do.

2. Smallest sellable MVP

The sellable unit is a single video report: one Stripe link, one URL field, one PDF, one corrected caption file. Nothing else is required to charge money. The pipeline fetches the auto-caption track, splits it into timed segments, flags lines against a four-part rubric, rewrites only the flagged lines, reattaches original timings and emails the result.

The one-page report leads with a Global Clarity Score, then a timestamped table of "what you said vs. what a US viewer hears", then the top 10 recurring fixes. The caption file is the part that makes it usable rather than interesting.

Explicitly not built: audio or accent scoring, video editing, YouTube OAuth, dashboards, team seats, non-English source videos, and a recurring billing engine. Each of those adds weeks and removes nothing from the first sale.

3. Technical implementation plan

A single Next.js app on Vercel handles intake, the Stripe webhook and a signed delivery page. Intake writes a job row to Supabase. A worker route pulls the caption track, builds timed segments, and sends each chunk through one LLM rubric call returning strict JSON. A second pass rewrites flagged lines under a character-per-second ceiling. The serializer reattaches original start and end times, renders the report to PDF, stores both files, and triggers Resend with a signed link. No accounts, no sessions beyond the link.

The hardest risk is caption timing desync. A rewritten line longer than its cue window spills into the next and the file becomes unusable. The guardrail is a hard character-per-second limit plus a verification pass in a player before any delivery. The second risk is caption availability; the plan adds a YouTube Data API fallback and a manual upload path if no track exists.

4. Pricing and monetization

Three one-time tiers at launch: $49 single video, $149 five-video channel audit, and a $199 monthly Clarity Pass added only after repeat buyers appear. The $49 entry exists so the first purchase is a reflex, not a budget decision. The $149 tier is the real margin driver and gets teased inside every delivered report with a line about recurring fixes across the channel. The monthly tier is withheld until at least two buyers have purchased twice, so the founder does not spend build days on billing infrastructure before demand is proven.

5. First-customer acquisition

One channel only: personalized cold email to creators whose latest video has already been analyzed. The list comes from YouTube search filtered to 10k-500k subscribers with bios signalling India, Nigeria, the Philippines or Brazil, plus public business emails from the About tab. Each message opens with three real timestamped lines from that creator's own upload, states the price and the delivery window, and needs no call. Follow-ups at day 3 and day 7 add one more flagged line and an .srt excerpt of the creator's own intro. Two anonymized before/after posts run in creator communities as supporting proof, never as the main channel.

6. 30-day execution roadmap

Days 1-5 are build: fetch spike, rubric pass, corrected caption serializer, payment and delivery path, then a frozen MVP with five end-to-end tests. Days 6-12 are list and first sale: build 150 prospects, pre-analyze 25, send 80 emails across the week, and close the first $49 order by day 12 with a 20-minute delivery. Days 13-21 are conversion: add the channel-audit upsell, ship batch mode, publish an anonymized sample report, run day-3 and day-7 follow-ups, add the monthly tier, and cut the worst-performing message angle on measured reply rates. Days 22-30 are scale and settle: a second geographic segment, a false-positive audit to protect tone, a refund policy, an upsell push to all buyers, reliability work on caption failures, and a final books close with verified revenue, refunds and API costs.

7. Revenue and profit scenarios

All three cases are projections built from assumed reply and buy rates; none are observed. Conservative assumes 3 buyers at a blended $82 average order value from roughly 250-300 sends. Base assumes 9 buyers at $88 from about 450 sends. Upside assumes 20 buyers at $99.50, mixing in channel audits, from 500+ sends plus two public posts. Costs stay inside $150 across all cases, covering LLM usage, Stripe fees, Resend and Vercel. The $100K target is not projected here; the plan projects low thousands in 30 days, with the meaningful upside arriving after day 30 when repeat buyers and the monthly tier compound.

8. Main risks and validation experiments

The central risk is demand perception: creators think their English is fine. The test is 20 emails with real flagged lines, counting replies that reference the lines. Kill if fewer than 4 of 100 emails reply after two follow-ups. The second risk is pipeline breakage from caption fetch failures; test against 50 videos and measure the failure rate before scaling. The third is tone: over-flagging turns a useful report into an insult. Cap flags at the top 10 lines, phrase every fix as "heard as", and re-grade 10 delivered reports for false positives. The fourth is desync in the corrected file, mitigated by timing guardrails and a player check. The fifth is outreach etiquette; use public business emails only, one follow-up after day 7, and honor opt-outs immediately.

9. First 24-hour action plan

Hours 1-2: deploy the Next.js skeleton and set capped API keys. Hours 3-5: build the caption fetch route and test it on 10 target videos, logging pass and fail reasons. Hours 6-8: build the timed segment builder and run the rubric prompt on one real transcript. Hours 9-11: write the .srt serializer and verify one corrected file plays in sync. Hours 12-14: finalize the outreach message using a real flagged line and confirm five prospects have public business emails. By end of day one the founder has a working fetch, one flagged transcript, one synced caption file and a message ready to send.

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 →