Voice-verification report for AI-assisted book manuscripts
A side-by-side originality report that shows self-published authors which sentences/ideas in their AI-generated manuscript came from their own source material versus the model, for creators using AI book services.
Turn this into a build spec
One Universal Core, then the exact file layout your platform expects — CLAUDE.md, .cursor/rules, a Lovable knowledge base, a Bolt prompt under its 400-word ceiling. Evidence travels with it.
32 credits · every platform format after it is 5
Reading an open idea needs nothing. Generating a spec from it calls a model and costs real money, so it needs an account and credits — the cost is shown before you spend anything.
Building this?
Tell everyone else. It shows on this page and on the idea cards, and it collects in your dashboard. Ship it and add the link — we fetch it and re-check it weekly.
Sign in to tell others you're building this.
Supporting evidence2
Direct complaint that AI book services are a black box and creators cannot tell if the output sounds like them, indicating unmet demand for a verification layer.
Separate signal shows appetite for provenance/trust tooling around AI vs human-written books, including a vetted marketplace concept, suggesting the underlying 'prove this is authentically mine/human' problem recurs across contexts.
Falsifying evidence4
Only two signals from two different framings (personal voice verification vs marketplace-level human/AI distinction) support this cluster; it's unclear if they represent the same product need or two different products.
The AI book service providers themselves are best positioned to add a 'voice verification' or 'originality score' feature directly into their pipeline, since they already have the input and output text.
No competitor products are recorded, but that reflects gaps in our data collection, not an actual absence of AI-detection or plagiarism-check tools already addressing 'is this my voice/AI-written' questions.
No revenue or spend figures are verified in these signals despite the demand tier labels; willingness to pay for a standalone verification tool is unconfirmed.
Most likely cause of death
The most likely failure mode is that the AI book-generation platforms themselves ship a basic 'originality/voice match score' as a built-in feature once they notice the complaint, since they control both the input corpus and generated output and can compute this more cheaply than a third party. A standalone tool would need a defensible technical edge (e.g., a genuinely rigorous stylometric/provenance model marketplaces and platforms trust) plus a distribution wedge outside the platforms' reach, neither of which the current evidence demonstrates.
Demand ladder
A complaint is not a customer. Weighted ×1 / ×3 / ×8 / ×15.
Counted from clustered complaint signals. No candidate-relative commercial check was applied, so no revenue is attributed to this idea.
Verified revenue: not established for this idea. No record ties a revenue figure to a product selling what this would sell.
Momentum
Is this problem getting louder or quieter?
Saturation
How many people are already on it. Most sites hide this.
Problem evidence
Who feels this, how often, and why what they use today does not fix it.
- Who feels it
- Self-published / indie authors who paid an AI book service (or ghostwriting-with-AI service) to turn their notes, interviews or course material into a manuscript, and cannot tell how much of the result is theirs. Secondarily, readers and marketplace operators who want to know whether a book was written by a human.
- How often
- Once per manuscript — an event, not a workflow. An indie author ships maybe 1-4 books a year, so the trigger fires a handful of times per customer per year. Only 2 signals in 30 days across two sources, so frequency is inferred, not observed.
- Why current fixes fail
- The moment of pain is at handoff: the service returns a finished manuscript and the author has no artifact tying output sentences back to the source material they supplied. What they can reach for instead is a generic AI-detector (probabilistic, no notion of 'your' voice, and gives a single document-level percentage) or reading the whole draft themselves against their notes, which for an 80k-word manuscript is a multi-day job they hired the service to avoid. Neither answers the actual question — 'which of these paragraphs came from my material and which did the model invent' — because neither has the input corpus. The party that does have the input corpus is the AI book service itself, which is exactly why this gap may not stay open (X-340).
Creators using AI book services describe the pipeline as a black box: content goes in, a manuscript comes out, and they 'hope it sounds like you' — i.e. no verification artifact is returned.
Separately, authors and readers want a way to distinguish AI-generated books from human-written ones, framed as vetting for a 'human-only' bookstore or recommendation service.
The two signals may be two different products (personal voice verification for one author vs. marketplace-level human/AI attestation), not one demand cluster — the whole cluster rests on this ambiguity.
No record in this block shows anyone paying, or stating a price they would pay, for a standalone verification report; the 'spend' tier label is not backed by a figure.
The AI book platforms hold both the input corpus and the generated output and can compute a voice-match score more cheaply than any third party, so a built-in feature is the default resolution of this complaint.
The absence of recorded competitors is a data-collection gap, not an empty field — AI-detection and plagiarism tools already address adjacent versions of this question.
Demand is emerging and shallow: 2 signals, 1 in the last 30 days, from 2 sources (Hacker News, Product Hunt), with no repeat complainants.
Who buys it
The person who feels the pain and the person who signs are rarely the same.
Who buys it is part of membershipThe buyer, the budget it comes out of, and what these people already pay for.Product concept and MVP
Two versions: the one you deliver by hand first, and the one you build.
Product concept and MVP is part of membershipThe concierge version, the buildable version, and the features deliberately left out.Competitors and alternatives
Including the free workaround people use today, which is usually the real competitor.
Competitors and alternatives is part of membershipDirect products, indirect ones, the workarounds, and where the gap actually is.Pricing model
modelledA proposal, not an observation. Benchmarks come from the data; the ladder is ours.
Pricing model is part of membershipA tier ladder with the reasoning behind each price point.Revenue scenarios
modelledArithmetic on the assumptions listed underneath. Change an assumption and the number changes.
Revenue scenarios is part of membershipBase, upside and aggressive cases with every input written out.Market size
modelledReachable customers, not a top-down industry figure.
Market size is part of membershipHow many buyers exist, what they spend, and how many you could realistically reach.Go to market
Named places, not channel categories. These signals came from somewhere.
Go to market is part of membershipWhere the first ten customers come from, then the first hundred.Roadmap
Each version ships something a user can use. No infrastructure-only phases.
Roadmap is part of membershipVersion by version, with what belongs in each.Pivot paths
Where this goes if the first version does not land — and the number that says it did not.
Pivot paths is part of membershipAdjacent directions, and the measurable trigger for taking one.Risks and kill criteria
The thresholds at which the honest move is to stop. Written before you are attached to it.
Risks and kill criteria is part of membershipRanked risks, and the numeric conditions under which to walk away.Validation plan
Seven days that cost nothing but time and can kill the idea before you build.
Validation plan is part of membershipA day-by-day plan and the interview questions that do not lead the witness.Sources and freshness
Every reference opens the original post. This is the part you should check first.
How sure are we, per claim
Where the data is thin, we say so instead of rounding up.
- demand
- Low
- payment
- No data
- market size
- Low
- competitor gap
- No data
7 references from 2 signals · evaluation written Aug 29, 2026.
Related opportunities
Nearest by what the problem actually is, not by category label.
AI report translator for used-car pre-purchase inspections (VIN/plate → plain-English risk score)
Turns a VIN, plate, or uploaded inspection report/photos into a plain-English risk score and repair-cost estimate for private used-car buyers.
Bug-attribution linter for AI-generated PRs on large, multi-file diffs
A CI-integrated review tool that flags which specific AI-generated hunks in a large PR are most likely to contain production-risk bugs (missing error handling, hardcoded secrets, hallucinated calls), so a human reviewer knows where to spend their limited attention.
Continuity tracker for multi-book series fiction writers
A story-bible tool that auto-tracks character voice, world rules, and timeline continuity across a fiction series, flagging drift and contradictions as writers draft.
Eleven more sections behind this one
Who signs the cheque, what the space already charges, the seven-day validation plan, and the thresholds at which you should stop. Three ideas are open in full so you can judge the depth before paying.
2 people have looked at this · 0 turned it into a spec · 0 say they're building it