FIT
Recurring problem
Does the reader face this task often enough to value a reusable tool?
READER DEMAND
How do you validate a book app idea?
Move from a promising manuscript exercise to observed reader use and an evidence-based product decision.
Understand the work before you invest in it.
START WITH READERS
Evidence of use matters more than interest.
A survey response saying that a book companion app sounds interesting does not prove that someone will use it regularly. Start with a specific reader problem and a task the reader already attempts to complete.
Interview a small number of people who resemble the intended audience. Ask about recent situations, the tools they tried, the consequences when the process went wrong, and how frequently the task occurs. Avoid leading questions that invite agreement.
Put a prototype, worksheet or clickable flow in front of potential users. Ask them to complete a real task with minimal assistance. Record what they actually do, not only what they say they would do.
Document the participants, assumptions, errors, support needed and any repeated demand. If the evidence is weak, simplify the concept or stop.
SIX DECISIONS
Test the business case before the build.
VALUE
Clear useful outcome
Can the app produce a result that materially improves on a paper worksheet or email?
RIGHTS
Content and permissions
Are the manuscript, examples, images and third-party materials available for licensed reuse?
ECONOMICS
Support and delivery cost
Include hosting, third-party services, customer support, maintenance, payment fees and refunds.
TRUST
Data and user security
Review personal information, access rights, backup and deletion requirements before collecting data.
DEMAND
Willingness to pay
Use realistic commitments and observed retention, not invented subscription forecasts.
Choose a proportionate business model
A downloadable workbook, one-off paid companion, professional licence, membership benefit or subscription may all be appropriate. Subscriptions require sustained value and continuing operational commitments. They should not be selected merely because monthly revenue sounds attractive.
Define the go/no-go decision
Before testing, write down what evidence would justify proceeding: the task users must complete, acceptable quality and error levels, maintenance costs and evidence of continued need. Retain a record of negative as well as positive results.
See how to find app candidates in a manuscript and the minimum viable product brief. This guide explains an evaluation method; it does not guarantee commercial performance.