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

Narrator Pronunciation Bible

Turns an audiobook manuscript into a record-ready pronunciation bible with phonetic spellings, rhyme hints, and audio clips for every character and invented term.

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.39/10
MVP build (solo)
5 days
Launch price
$79
Sales to $1,000 revenue
13 customers
First paying customer
Organic posts and direct messages in r/ACX and the Audiobook Narrators Facebook groups, led by a public sample bible.
Who pays

Solo audiobook narrators and 1-5 person narration studios producing 1-4 fiction titles per month, mostly fantasy, sci-fi and romance with invented vocabulary.

Biggest execution risk

Operational simplicity 5.0/10

Why this could work in 30 days: one founder can ship the MVP in 5 days; the plan targets a first sale on day 12; 13 sales at $79 clears $1,000 of collected revenue; strongest signal is speed to first revenue at 8.3/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
$79
Solo build
5 days
30d base revenue
$1,288
30d hackathon profit
$1,164
Section 1 of 8

Product opportunity and positioning

Target customer

Solo audiobook narrators and 1-5 person narration studios producing 1-4 fiction titles per month, mostly fantasy, sci-fi and romance with invented vocabulary.

Why now

LLM extraction plus per-term TTS now costs well under $1 per manuscript, so a $79 per-project artifact is profitable for a solo operator with no staff.

Problem

Narrators burn paid studio time and re-record takes because they guessed an invented name wrong, and asking the author costs days and signals they arrived unprepared.

Solution

A .docx or .pdf upload is parsed, terms are extracted with context, respelled consistently, synthesized to MP3 per term, and delivered as a PDF bible plus an audio ZIP via an expiring link.

Differentiation · The competitor is a manual Google Doc style sheet or a forum thread with conflicting answers, not another app; this delivers audio and context, not just spellings.

Narrator Pronunciation Bible — 30-Day Launch Report

Every number in this report is a projection derived from stated assumptions. No customers, revenue, partnerships or traction exist yet.

1. Product opportunity and positioning

Audiobook narrators are paid per finished hour. Every invented name — the sorceress, the planet, the duke — is a coin flip on the first take. A wrong guess costs a re-record, a studio slot, and an email to the author that admits you did not prepare. Nothing on the market solves this cheaply: style sheets are hand-built, forums give conflicting answers, and asking the author adds days to a project that started Monday.

Narrator Pronunciation Bible is not a language-learning product and it does not teach anyone to speak. It converts a manuscript into the single artifact a narrator needs before the mic opens: a PDF plus MP3 pack listing every proper noun and invented term with a consistent phonetic respelling, IPA, a rhyme hint, and the first context snippet showing usage.

The buyer is deliberately narrow: solo narrators and 1-5 person studios producing one to four fiction titles a month, concentrated in fantasy, sci-fi and romance. They decide alone, pay by card, and hit the trigger event — "I just accepted a new manuscript" — every few weeks. At $79 the comparison the buyer makes is against their own hourly rate, not against software, because one saved studio hour already pays for the sheet.

Why this is sellable now: LLM extraction plus per-term TTS costs roughly $0.30-$0.50 per manuscript, which makes a per-project artifact viable for a solo operator at this price. The generic alternative gives spellings without consistency, audio or context. The wedge is the artifact, not a platform.

2. Smallest sellable MVP

One page, one upload, one paywall, one delivery. The narrator drops a .docx or .pdf, the pipeline extracts terms with frequency and first-context snippets, generates phonetic respelling, IPA and a rhyme hint for each, synthesizes an MP3 per term, and produces a PDF bible with a QR code per entry plus a ZIP of audio. Stripe Checkout gates the download; no account, no dashboard, signed link expires in 72 hours. A public sample bible built from a public-domain fantasy excerpt proves the output before anyone pays. Out of scope for 30 days: accounts, subscriptions beyond one monthly tier, author collaboration, mobile app, human pronunciation review, marketplace.

3. Technical implementation plan

Next.js on Vercel, Stripe Checkout plus webhook, Supabase Storage for uploads and outputs, mammoth and pdf-parse for text, GPT-4o-mini for extraction and respelling, OpenAI TTS for clips, pdf-lib for the export. Flow: upload → extract text → chunk and extract candidate terms → canonicalize and dedupe → generate the pronunciation sheet as strict JSON → render MP3s in parallel → build PDF and ZIP → store → return signed URL after payment. Manuscripts are deleted after seven days; that promise is on the page. The hardest part is respelling consistency: the same invented name appearing twice must get the same answer. Mitigation is a canonicalization pass that resolves all variants to one headword before any respelling is generated, plus a 50-term gold set scored after every prompt change.

4. Pricing and monetization

Three one-time tiers plus one recurring: Single Manuscript $79, Studio 3-Pack $199, Publisher Monthly $399 for 15 manuscripts. No free tier; the sample bible is the free artifact. First revenue offer is a free bible for a narrator's current manuscript, followed by a $79 Stripe link 48 hours later. Upsell path is 3-Pack to anyone who mentions a second title in production, then Publisher Monthly to studios with steady volume. Blended ARPU in projections is $89-$106 because most buyers take the $79 tier.

5. First-customer acquisition

Organic only, in the two rooms narrators already occupy: r/ACX and the Audiobook Narrators Facebook groups, with stop-ins at r/VoiceActing. Read each group's promotion rules first; a post that looks like spam is dead on arrival. The opener is always the artifact, not the pitch: publish a sample bible for a public-domain excerpt with ten invented names, then DM narrators who mention a current project with a free bible offer. Ten free bibles in exchange for a one-line testimonial and permission generates both proof and paid conversions. Week-one goal is 30 conversations started and 3 free bibles delivered.

6. 30-day execution roadmap

Days 1-5 build to a live paid flow and ship the MVP by day 5. Days 6-7 create the sample bible, QA every respelling by hand, and finish the landing page with pricing and a rights/privacy FAQ. Days 8-12 launch: read group rules, post the sample, send 25 direct offers, deliver free bibles, fix the top three accuracy defects, then follow up with Stripe links — first paid sale targeted day 12. Days 13-21 add the flag-a-wrong-respelling control, a second community post, the 3-Pack page, testimonial asks, higher outreach volume, and a 20% affiliate offer to five audiobook proofers. Days 22-28 open the Publisher tier with 20 indie studio emails, ship CSV export, publish an anonymized case page, add referral credit, and run one $100 Reddit ad test. Days 29-30 push the deadline offer, reconcile Stripe payouts against TrustMRR, and write the retro.

7. Revenue and profit scenarios

Projections only. Conservative: 4 customers at $89 blended ARPU, $356 gross, no refunds or ad spend, $14 processing, $22 operating. Base: 14 customers at $92, $1,288 gross, one $79 refund, $45 processing, $58 operating — roughly $1,164 hackathon profit before operating costs, about $1,106 business profit. Upside: 32 customers at $106, $3,392 gross, $158 refunds, $119 processing, $120 ad spend, $135 operating. Hackathon profit excludes hosting and AI delivery by rule; business profit includes them. Payment fees assume Stripe at 2.9% + $0.30 blended with a small international mix, about 3.5-4%.

8. Risks and validation experiments

Accuracy is the product. If respellings for invented names are wrong or inconsistent, the bible is worse than nothing and refunds spike. Test: publish a 50-term gold set, hand-score generated respellings, and refuse to launch paid until at least 80% are acceptable. Community rejection is the second risk: posts get removed or ignored. Test: ask each moderator for permission before posting, and measure reply rate on 20 DMs before scaling to 30 a day. Market size is the third: the niche may not yield 100 buyers in 30 days. Test: if 40 DMs produce fewer than 4 free-bible requests by day 14, widen to r/VoiceActing and audiobook proofers or reprice to a $49 starter. Copyright concern is the fourth: unpublished manuscripts require an explicit delete-after-seven-days promise and a no-training clause on the page. TTS cost or rate-limit shocks are the fifth: cap uploads at 150k words and queue audio generation overnight if the API throttles.

9. First 24 hours

Buy the domain, deploy a Next.js skeleton to Vercel, connect Stripe and TrustMRR, and create the Supabase bucket — done inside three hours. Next three hours: build the .docx and .pdf text extraction endpoint and verify it against a real 90,000-word manuscript. Next two hours: write the extraction prompt and inspect the top 40 returned terms for false positives. Last block: draft the sample-bible plan on a public-domain excerpt and list the exact groups to join tomorrow. End of day one the app must accept a file and return text; nothing else ships until that works.

Section 2 of 8

Smallest sellable MVP

A single page where a narrator uploads a .docx or .pdf, pays $79 via Stripe Checkout, and receives a PDF pronunciation bible plus an MP3 ZIP through an expiring download link, with no account required.

Must-have features

  • Upload .docx and .pdf with text extraction and a 150,000-word cap
  • LLM extraction of character names, places and invented terms with frequency and first-context snippet
  • Canonicalization so every spelling variant resolves to one headword
  • Consistent phonetic respelling, IPA and rhyme hint per term
  • Per-term MP3 generated with OpenAI TTS and zipped
  • PDF export with term, respelling, IPA, rhyme hint, context and audio QR code
  • Stripe Checkout paywall with webhook-triggered 72-hour signed download URL
  • Public sample bible generated from a public-domain excerpt
  • Automatic file deletion after seven days with a stated no-training policy

Explicitly out of scope

  • User accounts, dashboards or saved projects
  • Real-time voice coaching or roleplay
  • Mobile app
  • Human pronunciation review or manual QA service
  • Author or publisher collaboration portal
  • Team seats or subscription billing beyond one monthly tier
  • Narrator marketplace, directory or job board
  • Languages other than English pronunciation output

Demo flow (what the buyer sees)

  1. Narrator lands on the sample bible page and opens the PDF
  2. Narrator uploads a .docx manuscript via the drop zone
  3. Pipeline extracts text and returns a preview of 10 detected terms free
  4. Narrator pays $79 through Stripe Checkout
  5. Webhook marks the job paid and triggers full generation
  6. PDF bible and MP3 ZIP are stored and a 72-hour signed link is emailed
  7. Narrator downloads both artifacts and flags any wrong respelling
Build plan

Technical implementation plan

Stack

Next.js on VercelStripe Checkout and webhooksSupabase Storage with signed URLsmammoth for .docx extractionpdf-parse for .pdf extractionOpenAI GPT-4o-mini for term extraction and respellingOpenAI TTS (tts-1) for per-term audiopdf-lib and qrcode for PDF exportResend for delivery emailUpstash Redis for job queue and rate limiting

Architecture

A Next.js app handles upload, serves the landing page and sample, and exposes a job API. Uploads stream to a private Supabase bucket; a serverless worker extracts text, chunks it, calls GPT-4o-mini to propose candidate terms with context, runs a canonicalization pass that maps variants to one headword, then a second pass that produces respelling, IPA and rhyme hint as strict JSON. A third step calls TTS once per headword in parallel batches and writes MP3s to storage. pdf-lib assembles the bible with QR codes pointing at the audio files, a ZIP bundles the clips, and Stripe's webhook flips the job to paid and issues a 72-hour signed URL. A nightly cron deletes anything older than seven days.

Build steps

  1. Create the Next.js repo, deploy to Vercel, wire environment variables and the Supabase bucket
  2. Build the upload endpoint with .docx/.pdf validation, a 150,000-word cap and text extraction
  3. Write the extraction prompt, chunk long manuscripts, and merge results by frequency
  4. Add canonicalization: normalise case, strip punctuation, merge near-duplicates to one headword
  5. Write the respelling prompt returning strict JSON with respelling, IPA and rhyme hint per headword
  6. Batch TTS calls, store MP3s, and assemble the audio ZIP
  7. Generate the PDF with pdf-lib including QR codes, then expose a preview of the first 10 terms
  8. Add Stripe Checkout, the webhook handler and signed-URL delivery email
  9. Add the sample-bible page, pricing, rights/privacy FAQ and file-deletion cron
  10. Load-test with two real manuscripts and fix the top failure modes

AI components

  • GPT-4o-mini for proper-noun and invented-term extraction with context snippets
  • GPT-4o-mini for phonetic respelling, IPA transcription and rhyme hints
  • OpenAI TTS for one MP3 clip per headword
Hardest technical risk: Consistency of respelling for the same invented name across a long manuscript; without a canonicalization pass the bible contradicts itself and the product loses trust in one page.
Section 3 of 8

Pricing and monetization

Single Manuscript

Entry offer
$79 one-time

For Solo narrator with one new fiction title

  • PDF pronunciation bible
  • MP3 audio pack
  • Context snippet for every term
  • 72-hour download link

Studio 3-Pack

$199 one-time

For Small narration studio with three titles in production

  • Three manuscripts
  • Priority processing queue
  • Consolidated audio ZIP

Publisher Monthly

$399 / month

For Indie audiobook publisher with steady volume

  • 15 manuscripts per month
  • CSV export of every term
  • Email support

Model: One-time per-manuscript pricing with a studio bundle and a monthly publisher tier; no free tier, the sample bible is the free proof.

First revenue offer: Free pronunciation bible for the narrator's current manuscript, delivered within 24 hours, with a $79 Stripe link sent 48 hours later for the full uncapped version and audio pack.

Expected ACV: $92

Upsell path: Single buyers who mention a second title in production get offered the $199 3-Pack; studios producing more than three titles a month move to the $399 Publisher Monthly, which converts a one-time sale into recurring revenue and justifies the CSV export build on day 23.

Target customers
100
Revenue model
$7,900
Costs
$320
Profit model
$7,580
Section 4 of 8

First-customer acquisition

Primary channel

Organic posts and direct messages in r/ACX and the Audiobook Narrators Facebook groups, led by a public sample bible.

Where to find them

  • r/ACX threads where narrators ask about pronunciation or new projects
  • r/VoiceActing and r/audiobooks self-promotion threads that permit tool posts
  • Audiobook Narrators Facebook group and two smaller narrator/producer groups
  • ACX and Findaway Voices narrator listings filtered by fantasy and sci-fi
  • Audiobook proofers and editors who work with narrators weekly
  • Indie audiobook production studios publishing 2-5 titles a month

Exact outreach motions

  • Read each group's rules and message a moderator for permission before posting the sample
  • Publish the sample bible PDF plus two MP3 samples as a post in groups that allow it
  • DM 25 narrators who posted about an active project in the last 14 days with a free-bible offer
  • Deliver 10 free bibles in exchange for one line of feedback and permission to quote
  • Follow up each free user at 48 hours with the $79 Stripe link and the three most-missed terms
  • Ask five audiobook proofers for a 20% affiliate payout on referrals
  • Post a second, differently angled post one week later showing a real side-by-side respelling

Message template

Hi [name] — saw you're starting [title]. I built a tool that turns a manuscript into a pronunciation bible: every invented name and place with phonetic respelling, IPA, a rhyme hint and an MP3 clip, so you're not guessing on take one. I'll make one for your manuscript free this week if you tell me what's wrong with it. Want it?
Week-one goal: 30 conversations started, 10 free bibles promised and 3 delivered, first paid Stripe payment by day 12.
Section 5 of 8

30-day execution roadmap

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

Get infrastructure live

  • Buy the domain and create the Next.js repo deployed to Vercel.
  • Open Stripe, connect the account to TrustMRR before any customer exists.
  • Create the private Supabase storage bucket and set env vars.

Deliverable: Deployed skeleton app, Stripe test key, empty bucket.

Day 2Text extraction

Upload to plain text

  • Build the upload endpoint with .docx/.pdf validation and a 150k-word cap.
  • Wire mammoth and pdf-parse and store the extracted text.
  • Test against a real 90,000-word manuscript.

Deliverable: Upload returns clean text with a word count.

Day 3Term extraction

Find the right words

  • Write the GPT-4o-mini extraction prompt for names, places and invented terms with context.
  • Add chunking and merge results by frequency.
  • Add a canonicalization pass merging spelling variants to one headword.

Deliverable: Top 40 headwords with frequency and first context for the test manuscript.

Day 4Pronunciation sheet

Respelling and audio

  • Generate strict-JSON respelling, IPA and rhyme hint per headword.
  • Batch OpenAI TTS calls and store one MP3 per term.
  • Zip the clips and cache the job record.

Deliverable: Complete sheet JSON plus audio ZIP for the test manuscript.

Day 5Paywall and deliveryMVP shipped

Ship the MVP

  • Render the PDF with pdf-lib including a QR code per term.
  • Add Stripe Checkout and a webhook that issues a 72-hour signed URL by email.
  • Add the seven-day deletion cron and deploy to production.

Deliverable: Live end-to-end paid flow; MVP shipped.

Day 6Sample asset

Build the proof artifact

  • Pick a public-domain fantasy excerpt with at least 10 invented names.
  • Generate the full sample bible and hand-check every respelling.
  • Re-run until no respelling is obviously wrong.

Deliverable: Publishable sample PDF plus a 10-clip audio sample.

Day 7Landing page

Make the offer legible

  • Write the hero, sample download and the $79/$199/$399 pricing block.
  • Add the rights and privacy FAQ: files deleted in seven days, never used for training.
  • Add a preview of the first 10 detected terms before payment.

Deliverable: Public landing page with sample and pricing.

Week 2 · Launch & first sale · 7 days
Day 8Community recon

Earn the right to post

  • Join r/ACX, r/VoiceActing, r/audiobooks and three narrator Facebook groups.
  • Read each group's promotion rules and note allowed posting days.
  • Message two moderators for permission to share the sample.

Deliverable: Permission status and posting calendar per group.

Day 9Soft launch

First public post

  • Post the sample bible in the groups that permit it.
  • Reply to every comment within an hour.
  • Log every objection and question verbatim.

Deliverable: Live post with logged objections.

Day 10Direct outreach

Start 25 conversations

  • List 25 narrators who posted about an active project in the last 14 days.
  • Send the free-bible message to each.
  • Track replies in a simple sheet.

Deliverable: 25 DMs sent, reply sheet started.

Day 11Free deliveries

Convert proof into trust

  • Generate and deliver 5 free bibles within 24 hours each.
  • Collect every flagged error into one list.
  • Fix the top three accuracy defects.

Deliverable: 5 delivered bibles and a prioritised defect list.

Day 12First sale pushFirst sale target

Take money

  • Follow up each free user with the $79 Stripe link.
  • Add the 3-Pack upsell to anyone mentioning a second title.
  • Record the first verified sale in TrustMRR.

Deliverable: First paid sale.

Day 13Feedback loop

Reduce wrong answers

  • Add a flag-a-wrong-respelling button on the PDF download page.
  • Re-run flagged jobs manually and reissue the PDF.
  • Log flag rate per manuscript.

Deliverable: Flag control live with a measured flag rate.

Day 14Second wave

Widen the funnel

  • Publish the Studio 3-Pack page.
  • Post a second, differently angled community post with a side-by-side example.
  • Send 20 new DMs.

Deliverable: 3-Pack page live, 20 new conversations.

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

Turn users into evidence

  • Ask all free users for a one-line quote and written permission.
  • Publish approved quotes only, with no invented names.
  • Add a testimonial block to the landing page.

Deliverable: At least two approved quotes on the page.

Day 16Outreach volume

Raise the top of funnel

  • Send 30 DMs to narrators with recent fantasy and sci-fi titles.
  • Personalise each with the book title.
  • Measure reply rate against day 10.

Deliverable: 30 DMs sent, reply rate computed.

Day 17Adjacent rooms

Test a second community

  • Post in r/VoiceActing and r/audiobooks where rules allow.
  • Email three audiobook proofers.
  • Log which room produced the best reply rate.

Deliverable: Channel comparison table.

Day 18Partnership probe

Borrow distribution

  • Offer a 20% affiliate payout to five proofers and editors.
  • Ship a simple referral code field in Stripe.
  • Follow up each conversation within 48 hours.

Deliverable: Five affiliate conversations started.

Day 19Accuracy hardening

Measure quality

  • Build a 50-term gold set from public-domain sources.
  • Hand-score generated respellings against it.
  • Iterate the prompt until at least 80% are acceptable.

Deliverable: Scored gold set and a baseline accuracy number.

Day 20Upsell

Raise order value

  • Email every past buyer about the $199 3-Pack.
  • Add a bundle checkbox to the upload page.
  • Track 3-Pack conversion separately.

Deliverable: Bundle path live with conversion data.

Day 21Checkpoint

Decide what to double down on

  • Review sales, refunds, flag rate and reply rates.
  • Compare against the kill criteria.
  • Pick the single channel to scale in week four.

Deliverable: Written checkpoint with one scaling decision.

Week 4 · Scale what works · 7 days
Day 22Publisher tier

Open recurring revenue

  • List 20 indie audiobook publishers and production studios.
  • Email each with the 15-manuscripts-per-month offer.
  • Book a $399 Publisher Monthly subscription as the goal.

Deliverable: 20 publisher emails sent.

Day 23CSV export

Fulfil the Publisher promise

  • Add CSV export of every term with respelling, IPA and rhyme hint.
  • Ship it behind the Publisher tier only.
  • Document it in one paragraph on the pricing page.

Deliverable: CSV export live.

Day 24Case page

Show the artifact

  • Publish an anonymised before/after bible page from a permitted manuscript.
  • Add turnaround time and word count to the page.
  • Link it from every outreach message.

Deliverable: Case page live.

Day 25Referrals

Make buyers recruit

  • Offer $20 credit to any narrator whose referral buys.
  • Add the referral line to the delivery email.
  • Track referral codes in Stripe.

Deliverable: Referral programme live.

Day 26Paid test

One cheap experiment

  • Run a $100 Reddit ad test against r/ACX and r/VoiceActing.
  • Cap spend at $100 and stop if cost per lead exceeds $10.
  • Log cost per free-bible request.

Deliverable: Paid test results with cost per lead.

Day 27Fulfilment speed

Remove the last objection

  • Add a 6-hour turnaround promise on the upload page.
  • Batch-generate overnight to keep the promise cheap.
  • Measure actual median turnaround.

Deliverable: Turnaround promise live with a measured median.

Day 28Renewals

Test recurring

  • Confirm Publisher Monthly billing has begun.
  • Email those buyers a usage summary.
  • Decide whether the tier stays after day 30.

Deliverable: Recurring billing confirmed or killed.

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

Close the window

  • Email every lead and free user with a deadline offer.
  • Post one final community update with the deadline.
  • Reply to every open thread.

Deliverable: Final outreach wave sent.

Day 30Reconcile

Measure the truth

  • Export Stripe payouts and reconcile against TrustMRR.
  • Subtract refunds, chargebacks, fees and ad spend to confirm profit.
  • Write a one-page retro with the next 30-day plan.

Deliverable: Reconciled profit statement and retro.

Section 6 of 8

Revenue and profit scenarios

How the numbers are defined

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

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

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

Stated assumptions

  • Conservative/Base/Upside: blended ARPU of $89-$106 reflects mostly the $79 Single tier with a minority of $199 3-Packs.
  • Conservative: 4 buyers, reached through organic community posts plus direct messages with no paid spend.
  • Base: 14 buyers, requiring roughly 40 free bibles delivered and a ~35% free-to-paid conversion.
  • Upside: 32 buyers, only achievable if a second community and an affiliate channel both produce.
  • Payment fees assume Stripe at 2.9% + $0.30 with a small international mix, about 3.5-4% of gross.
  • Refunds are modeled at 0 in conservative, one unit in base and two units in upside, driven by respelling accuracy.
  • Chargebacks are 0 across scenarios because buyers are individual cardholders with an artifact already delivered.
  • ad_spend is 0 in conservative and base because all outreach is organic; upside includes a $100 Reddit test plus $20 referral credit.
  • Operating costs cover Vercel, Supabase, domain, Resend, Upstash and roughly $0.40 of LLM plus TTS delivery per manuscript.
  • Hackathon profit excludes hosting and AI delivery by rule; business profit includes them.
  • Every figure is a projection from stated assumptions, not verified revenue.

Conservative

4 customers
$356
collected revenue · avg payment $89
Refunds
$0
Chargebacks
$0
Payment fees
$14
Paid marketing
$0
Hackathon profit
$342
Operating costs
$22
Business profit
$320

Base case

14 customers
$1,288
collected revenue · avg payment $92
Refunds
$79
Chargebacks
$0
Payment fees
$45
Paid marketing
$0
Hackathon profit
$1,164
Operating costs
$58
Business profit
$1,106

Optimistic

32 customers
$3,392
collected revenue · avg payment $106
Refunds
$158
Chargebacks
$0
Payment fees
$119
Paid marketing
$120
Hackathon profit
$2,995
Operating costs
$135
Business profit
$2,860

Model your own numbers

Runs in your browser · nothing is saved
Collected revenue
$1,106
Payment fees (3.9%)
$43
Paid marketing
$0
Hackathon profit
$1,063
Business profit
$1,005

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. Projections only; no customers or payments exist yet.

Section 7 of 8

Main risks and validation experiments

Risk 1Generated respellings for invented names are wrong or internally inconsistent, so narrators stop trusting the output and refund.

Mitigation

Canonicalization pass before respelling, hand QA on the sample, a flag-a-wrong-respelling button, and a 50-term gold set scored after every prompt change.

Validation experiment

Hand-score 50 generated respellings against a gold set before the first paid sale; publish the acceptance rate internally as the launch gate.

Kill criteria

If fewer than 60% of gold-set respellings are acceptable after three prompt iterations, stop selling and rework the pipeline before any further outreach.

Risk 2Community posts read as spam and get removed, killing the only acquisition channel.

Mitigation

Message moderators for permission first, lead with the free sample artifact rather than a pitch, and reply to every comment within an hour.

Validation experiment

Send 20 personalised DMs and post once with permission; measure reply rate and removal rate before scaling to 30 DMs a day.

Kill criteria

If 20 DMs produce zero free-bible requests and the post is removed, switch to direct email to ACX-listed narrators and proofers by day 16.

Risk 3The niche is too small to produce enough buyers in 30 days.

Mitigation

Keep the price at $79 to lower the decision cost, add the $199 bundle for multi-title studios, and open the Publisher tier in week four.

Validation experiment

Track free-bible requests per 20 DMs by day 14; if the rate is under 10%, test a $49 starter tier in the same community.

Kill criteria

If total revenue by day 21 is under $200 with 40+ conversations started, widen to audiobook proofers and indie publishers or change the artifact.

Risk 4Narrators refuse to upload unpublished manuscripts over copyright and confidentiality concerns.

Mitigation

State a seven-day deletion policy, a no-training clause, private storage with signed URLs, and offer an excerpt-only upload option.

Validation experiment

Put the rights FAQ above the upload box and track how many people view the page versus upload.

Kill criteria

If page views convert to uploads under 3% after the FAQ is live, offer a manual email-a-file path to test whether trust or friction is the blocker.

Risk 5TTS cost or rate limits spike during launch and break delivery promises.

Mitigation

Cap uploads at 150,000 words, batch audio generation, cache clips per headword, and queue jobs overnight when throttled.

Validation experiment

Run two full manuscripts end to end and record total delivery cost and wall-clock time per job.

Kill criteria

If delivery cost exceeds $2 per manuscript or a job exceeds 2 hours, drop per-term MP3 for the top 50 terms only.

Section 8 of 8

Hour-by-hour: the first 24 hours

Hours 1-2

  • Buy the domain and create the Next.js repo.
  • Deploy the skeleton to Vercel.
  • Open Stripe and connect the account to TrustMRR before any customer exists.
  • Create the Supabase private bucket.

Output: Live URL, Stripe test key, TrustMRR connection, storage bucket.

Hours 3-5

  • Build the upload form with .docx and .pdf validation.
  • Wire the text extraction endpoint and deploy it.
  • Run a real 90,000-word manuscript through it.

Output: Working upload-to-text endpoint with a verified word count.

Hours 6-8

  • Write the GPT-4o-mini extraction prompt for names, places and invented terms.
  • Add the context-snippet field.
  • Inspect the top 40 results for false positives and tighten the prompt.

Output: Extraction prompt v1 with a reviewed sample output.

Hours 9-10

  • Draft the sample-bible plan on a public-domain excerpt.
  • List the exact subreddits and Facebook groups to join on day 8.
  • Write the first outreach message draft.

Output: Launch checklist and the outreach message template.

Complete report

Full 30-day launch report

Read the full generated report

Narrator Pronunciation Bible — 30-Day Launch Report

Every number in this report is a projection derived from stated assumptions. No customers, revenue, partnerships or traction exist yet.

1. Product opportunity and positioning

Audiobook narrators are paid per finished hour. Every invented name — the sorceress, the planet, the duke — is a coin flip on the first take. A wrong guess costs a re-record, a studio slot, and an email to the author that admits you did not prepare. Nothing on the market solves this cheaply: style sheets are hand-built, forums give conflicting answers, and asking the author adds days to a project that started Monday.

Narrator Pronunciation Bible is not a language-learning product and it does not teach anyone to speak. It converts a manuscript into the single artifact a narrator needs before the mic opens: a PDF plus MP3 pack listing every proper noun and invented term with a consistent phonetic respelling, IPA, a rhyme hint, and the first context snippet showing usage.

The buyer is deliberately narrow: solo narrators and 1-5 person studios producing one to four fiction titles a month, concentrated in fantasy, sci-fi and romance. They decide alone, pay by card, and hit the trigger event — "I just accepted a new manuscript" — every few weeks. At $79 the comparison the buyer makes is against their own hourly rate, not against software, because one saved studio hour already pays for the sheet.

Why this is sellable now: LLM extraction plus per-term TTS costs roughly $0.30-$0.50 per manuscript, which makes a per-project artifact viable for a solo operator at this price. The generic alternative gives spellings without consistency, audio or context. The wedge is the artifact, not a platform.

2. Smallest sellable MVP

One page, one upload, one paywall, one delivery. The narrator drops a .docx or .pdf, the pipeline extracts terms with frequency and first-context snippets, generates phonetic respelling, IPA and a rhyme hint for each, synthesizes an MP3 per term, and produces a PDF bible with a QR code per entry plus a ZIP of audio. Stripe Checkout gates the download; no account, no dashboard, signed link expires in 72 hours. A public sample bible built from a public-domain fantasy excerpt proves the output before anyone pays. Out of scope for 30 days: accounts, subscriptions beyond one monthly tier, author collaboration, mobile app, human pronunciation review, marketplace.

3. Technical implementation plan

Next.js on Vercel, Stripe Checkout plus webhook, Supabase Storage for uploads and outputs, mammoth and pdf-parse for text, GPT-4o-mini for extraction and respelling, OpenAI TTS for clips, pdf-lib for the export. Flow: upload → extract text → chunk and extract candidate terms → canonicalize and dedupe → generate the pronunciation sheet as strict JSON → render MP3s in parallel → build PDF and ZIP → store → return signed URL after payment. Manuscripts are deleted after seven days; that promise is on the page. The hardest part is respelling consistency: the same invented name appearing twice must get the same answer. Mitigation is a canonicalization pass that resolves all variants to one headword before any respelling is generated, plus a 50-term gold set scored after every prompt change.

4. Pricing and monetization

Three one-time tiers plus one recurring: Single Manuscript $79, Studio 3-Pack $199, Publisher Monthly $399 for 15 manuscripts. No free tier; the sample bible is the free artifact. First revenue offer is a free bible for a narrator's current manuscript, followed by a $79 Stripe link 48 hours later. Upsell path is 3-Pack to anyone who mentions a second title in production, then Publisher Monthly to studios with steady volume. Blended ARPU in projections is $89-$106 because most buyers take the $79 tier.

5. First-customer acquisition

Organic only, in the two rooms narrators already occupy: r/ACX and the Audiobook Narrators Facebook groups, with stop-ins at r/VoiceActing. Read each group's promotion rules first; a post that looks like spam is dead on arrival. The opener is always the artifact, not the pitch: publish a sample bible for a public-domain excerpt with ten invented names, then DM narrators who mention a current project with a free bible offer. Ten free bibles in exchange for a one-line testimonial and permission generates both proof and paid conversions. Week-one goal is 30 conversations started and 3 free bibles delivered.

6. 30-day execution roadmap

Days 1-5 build to a live paid flow and ship the MVP by day 5. Days 6-7 create the sample bible, QA every respelling by hand, and finish the landing page with pricing and a rights/privacy FAQ. Days 8-12 launch: read group rules, post the sample, send 25 direct offers, deliver free bibles, fix the top three accuracy defects, then follow up with Stripe links — first paid sale targeted day 12. Days 13-21 add the flag-a-wrong-respelling control, a second community post, the 3-Pack page, testimonial asks, higher outreach volume, and a 20% affiliate offer to five audiobook proofers. Days 22-28 open the Publisher tier with 20 indie studio emails, ship CSV export, publish an anonymized case page, add referral credit, and run one $100 Reddit ad test. Days 29-30 push the deadline offer, reconcile Stripe payouts against TrustMRR, and write the retro.

7. Revenue and profit scenarios

Projections only. Conservative: 4 customers at $89 blended ARPU, $356 gross, no refunds or ad spend, $14 processing, $22 operating. Base: 14 customers at $92, $1,288 gross, one $79 refund, $45 processing, $58 operating — roughly $1,164 hackathon profit before operating costs, about $1,106 business profit. Upside: 32 customers at $106, $3,392 gross, $158 refunds, $119 processing, $120 ad spend, $135 operating. Hackathon profit excludes hosting and AI delivery by rule; business profit includes them. Payment fees assume Stripe at 2.9% + $0.30 blended with a small international mix, about 3.5-4%.

8. Risks and validation experiments

Accuracy is the product. If respellings for invented names are wrong or inconsistent, the bible is worse than nothing and refunds spike. Test: publish a 50-term gold set, hand-score generated respellings, and refuse to launch paid until at least 80% are acceptable. Community rejection is the second risk: posts get removed or ignored. Test: ask each moderator for permission before posting, and measure reply rate on 20 DMs before scaling to 30 a day. Market size is the third: the niche may not yield 100 buyers in 30 days. Test: if 40 DMs produce fewer than 4 free-bible requests by day 14, widen to r/VoiceActing and audiobook proofers or reprice to a $49 starter. Copyright concern is the fourth: unpublished manuscripts require an explicit delete-after-seven-days promise and a no-training clause on the page. TTS cost or rate-limit shocks are the fifth: cap uploads at 150k words and queue audio generation overnight if the API throttles.

9. First 24 hours

Buy the domain, deploy a Next.js skeleton to Vercel, connect Stripe and TrustMRR, and create the Supabase bucket — done inside two hours. Next block: build the .docx and .pdf text extraction endpoint and verify it against a real 90,000-word manuscript. Next: write the extraction prompt and inspect the top 40 returned terms for false positives. Last block: draft the sample-bible plan on a public-domain excerpt, list the exact groups to join, and write the outreach message. End of day one the app must accept a file and return text; nothing else ships until that works.

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 →