How to test willingness to pay with your existing readers

Test willingness to pay by putting a specific offer in front of readers who face the problem it solves. Start with their recent experience, establish what they already do and spend, then show the deliverables, limitations, and price. Record an actual purchase separately from a compliment, waitlist signup, or promise to buy later.

For an established nonfiction author, the complication is affection. A reader can love your book, want you to succeed, and have no current use for its paid companion. Your research needs to leave room for all three things to be true.

The five-conversation protocol below gives you a manageable first investigation. Five is a planning choice, not a statistically valid sample or a magic threshold. The purpose is to find what deserves another test before you build a substantial product.

Write one paragraph with a reader, a task, an output, and a boundary. Avoid asking whether people would buy “something interactive” or “an AI version of the book.” Neither description gives them enough information to evaluate.

Consider this fictional example:

Daniel wrote a book about useful customer interviews. He is considering a companion that helps independent founders prepare one interview guide. Readers provide their research question, customer type, assumptions, and constraints. They receive a draft guide and an explanation of the questions to remove or revise. It does not recruit participants, conduct interviews, or validate the business.

This description gives Daniel something concrete to investigate. The reader may need help recruiting, rather than writing questions. They may interview customers only once a year. They may already use the book's worksheet successfully. Each answer changes the commercial decision.

Do not add more features to neutralize every objection during the interview. Record the objection against the offer actually shown. Otherwise, your five participants will be evaluating five different products.

Start with readers who have recently tried to apply the relevant part of your method. Invite a mixture of people who found it useful and people who struggled. Newsletter subscribers who frequently praise your writing are easy to reach, but they are not the only people whose experience matters.

A useful invitation might say:

I'm researching how readers prepare customer interviews after reading the book. If you've done that in the last three months, I'd like to hear what happened. This is a research conversation, not an obligation to purchase anything. At the end, I may show an idea for a paid companion; negative reactions are useful too.

Use a timeframe that fits your topic. Three months makes sense for Daniel's hypothetical task; it would exclude too many relevant people for a book about a once-yearly planning process.

Record the recruitment channel and relationship. A long-standing consulting client, a personal friend, and a newsletter reader are different sources of evidence. If someone receives a thank-you payment, record that too. Do not make the incentive depend on favorable feedback or a purchase.

Allow enough time for a specific story before showing the offer. You are looking for context that explains a buying decision, not a rehearsed answer to whether your idea sounds good.

1. Reconstruct the last attempt

Ask: “Tell me about the last time you prepared an interview. What triggered it, and what did you do first?” Follow with questions about the actual sequence: materials used, people involved, decisions made, and where the work stalled.

If the participant speaks generally, return to the instance: “What happened in that particular interview?” Let them decline to share confidential details. You need the shape of the task, not sensitive customer information.

A concrete recent example belongs in the evidence sheet. “I would probably use that someday” belongs in a different column.

2. Understand the existing alternative

Ask what they used instead: the book, a blank document, a colleague, a template, another tool, or a paid adviser. Ask what was sufficient and what was missing.

Do not assume that doing the work manually is a painful failure. Some readers value that process. If the existing worksheet solves their problem, a new paid companion needs an additional benefit they recognize, not simply a new interface.

Ask about time and spending only when relevant. Keep the person's estimate labeled as an estimate. A remembered afternoon does not establish precisely four hours of recoverable value.

3. Identify timing and the buyer

Ask when the task is likely to happen again, what would make it urgent, and who would approve spending. A manager may like the companion but lack purchasing authority. A solo founder may control the budget but have no interviews scheduled.

For Daniel, “We have six interviews next week, and I choose our research tools” is different evidence from “Our team might try customer research next year.” Neither answer is morally better. They describe different buying situations.

Keep need, timing, and authority separate. Collapsing them into an “interested” checkbox hides the reason a person might not buy.

4. Show the same offer and price

Now show the short description, a representative sample, what is excluded, and one clearly labeled proposed price. Ask the reader to explain what they think they would receive before asking for a reaction.

If they misunderstand the deliverable, record the misunderstanding. Their response to the price cannot be interpreted cleanly until you know which product they thought they were evaluating.

Then ask: “Given your next interview project and what you use now, how would you decide whether to buy this?” Follow the reasoning. Avoid negotiating the price downward until they agree; that turns research into a series of leading offers.

If you change the offer between conversations, version it. A lower price plus more support is a new proposition, not evidence that the original offer was attractive.

5. Offer an honest next step

If a usable paid version exists, participants can choose whether to purchase it through the same clearly described terms as other buyers. If it does not exist, say so. An invitation to hear about a future pilot is interest, not a sale.

In a public startup discussion, u/inexorablyquixotic wrote: “It's the action that's the validation, not the imagined response to a hypothetical question.” This is a participant's advice, not a research finding, but it captures why your evidence sheet should distinguish what people say from what they do. Original comment.

Even a payment has limits: it establishes that one person bought that offer under those conditions. It does not establish repeat use, satisfaction, renewal, or profitable acquisition.

Use one row per conversation. Keep the participant's words separate from your interpretation. The following entries are fictional illustrations, not interviews we conducted.

Neither row contains a purchase. Reader A's request is a useful next step, but calling it willingness to pay would overstate the evidence. Reader B's response is useful too: it identifies a misleading expectation and helps Daniel improve the description.

Add columns for offer version, recruitment relationship, incentive, and follow-up permission. Keep identifying information only where needed for the research process. Do not paste private interview material into public marketing without separate permission.

Review the notes together instead of selecting the most encouraging sentence. Ask which observations repeated, which contradicted your idea, and what you still cannot explain.

One founder described the reason for slowing down this way: “As a techie, I've been known to rush ahead and start building.” Their Reddit post concerns a personal-trainer app, not an author product; its relevance is the temptation to build before understanding the buying situation. Original account by u/DJXenobot101.

Choose the next step from the evidence:

• Investigate the same offer further when relevant readers describe a recurring problem but you have little behavioral evidence.
• Revise the scope when readers consistently expect a different deliverable or need help at another point in the workflow.
• Prepare a limited paid test when the task, buyer, and offer are clear enough to deliver responsibly.
• Pause this product when the existing book or worksheet solves the problem adequately, or the need rarely arises among reachable readers.

Do not turn three positive conversations out of five into a forecast for your entire mailing list. This small, deliberately recruited group was chosen to help you understand a situation. It was not designed to estimate a population conversion rate.

Willingness to pay cannot compensate for a weak deliverable. Before asking readers to buy an applied version of your method, show what it does with a realistic input and examine whether the output meets your own standard. The guide to testing an agent skill covers that separate quality question.

For Daniel, the next commercial question might be whether readers will pay for help preparing their guide. The next quality question is whether that guide avoids leading questions and supports their actual research purpose. He needs evidence for both; neither substitutes for the other.

If your reader conversations point toward a paid way to apply your book's method, visit Skillfully and choose Book onboarding. Bring the offer paragraph, one representative task, and the objections you heard. Those specifics give the discussion a useful starting point without pretending the market has already said yes.