What counts as proof of concept for a book topic?

Proof of concept for a book topic is a documented case that a specific reader wants help with the subject, books are a credible way to provide that help, and your angle has a plausible place in the current market. It is a decision standard, not a universal sales-rank threshold and never a guarantee of sales.

What should a book proof of concept prove?

A useful proof of concept answers four separate questions:

1. Reader: Can you identify who wants the book and the situation that makes it relevant?
2. Demand: Is interest visible in more than one independent signal?
3. Book fit: Do people seek enough depth, sequence, reference, story, or exercises to justify a book?
4. Positioning: Can your book make a clear, honest promise that is not merely a copy of an existing title?

Many weak topic decisions answer only the fourth question. A publisher finds an apparently empty angle and assumes the gap equals opportunity. Without reader demand, the gap may be empty for a good reason.

Which signals count as evidence?

Use a mix. Each signal has limitations, but convergence is informative.

Separate direct evidence from interpretation in your notes. “Five directly relevant books appear in the first search results” is an observation. “The market is easy” is an interpretation that requires more support.

How do you run a proof-of-concept check?

1. Define the hypothesis. Write: “Readers who are [specific audience] want a book that helps them [outcome] in [situation or constraint].”
2. List close search phrases. Include problem, outcome, audience, method, and format language.
3. Inspect genuinely relevant books. Exclude accessories, unrelated books, and incidental keyword matches.
4. Record market evidence. Save titles, positioning, publication context, formats, visible engagement, and the date checked.
5. Read public reviews qualitatively. Look for recurring expectations and gaps. Do not reuse reviewers' stories as your own examples.
6. Check adjacent demand. Search broader questions, communities, and related solutions to understand whether the need exists outside one retailer query.
7. Draft the proposed angle and contents. A real angle changes the book's audience, method, scope, or experience.
8. Compare the draft against alternatives. Explain why an appropriate reader would choose this book without attacking competitors.
9. Make a proceed, refine, or stop decision. Write the reasons and the main uncertainty.

Breakthrough Topic Research provides filters, trends, and a topic checker on Starter, Plus, and Elite. It helps organize a demand decision but does not establish a universal success threshold or predict future sales.

What does a good evidence note look like?

Avoid a single unexplained score. Use a short claim-evidence-limit record:

Claim: There appears to be continuing demand for a practical beginner book on the broader subject. Evidence: Several directly relevant books and recurring public questions use similar problem language. Limit: Existing books already serve general beginners, so the proposed angle needs a narrower reader and fresh usefulness.

That is a generic example. It does not describe a researched market.

This format makes uncertainty visible. A later reviewer can challenge the evidence or update it without pretending the decision came from an objective formula.

How much competition is healthy?

There is no fixed amount. Competition can confirm demand and show that readers accept books as a solution. It becomes difficult when current, strong books already serve the same reader, outcome, method, and format and your proposed book adds little.

Assess competitors at the level of positioning:

• Who is the book for?
• What outcome does it promise?
• How does it organize the solution?
• What depth and format does it offer?
• What do public reviews repeatedly value or find missing?
• Can you address a gap credibly?

Do not use poor reviews as a writing brief by themselves. Readers may disagree, and a complaint can be outside the book's intended scope. Look for repeated, relevant needs that fit your capabilities.

What does not count as proof of concept?

One bestseller. Its performance may depend on an established audience, timing, brand, or promotion you cannot observe.

A large general search count. Broad interest in a subject does not prove demand for your specific book.

Low competition. Few relevant books can indicate a small or unsuitable market.

A keyword suggested by a tool. A suggestion is a research lead, not a completed case.

Friends saying they like the idea. Encouragement is not behavior from the intended market.

A title that sounds marketable. Packaging cannot create a reader problem the manuscript does not solve.

An arbitrary review or rank cutoff. Thresholds without context hide differences in topic, format, age, price, audience, and seasonality.

When should you proceed, refine, or stop?

Proceed when demand appears across multiple relevant signals, books fit the need, you can state a meaningful angle, and you have the knowledge and production resources to deliver it.

Refine when the need is visible but your topic is too broad, the reader is unclear, or competitors already own the same promise. Narrow by audience, constraint, method, depth, or format only when the new angle remains supported by evidence.

Stop when you cannot find credible reader interest, the subject is unsuitable for a book, the only opening relies on misleading metadata, or the content requires expertise and verification you cannot provide.

The earlier guide to choosing a book topic with demand gives the full research sequence. Once the proof of concept is documented, translate it into an editorial brief and then a clear title and subtitle. Keep the evidence note with the project and date it. Proof of concept is strongest when another person can see exactly why the decision was made and what remains uncertain.