Ask what the reader did before asking for praise
A useful testimonial about an expertise product describes an actual task, the part of your method the reader used, and what happened next. Ask about those details first. Then ask whether you may publish a short, approved account.
For a nonfiction author, this separates affection for the book from evidence about its practical companion. Someone can love your writing without having used the exercise. Someone else can find your tone unremarkable and still use the method to finish a difficult piece of work.
Both are valid experiences. Only the second supports a claim about application. Neither automatically supports a claim about eventual business results.
Use the templates below to collect a small, permissioned account. They are designed for a written excerpt, rather than a full customer case study or a compulsory video interview.
Choose a moment that matches the claim
In a copywriting discussion, u/mrharriz described the state of a client project:
“The client loved it and copy pasted the copy to their website. They are all set for the launch.”
The original question concerned what to ask in a testimonial. The timing matters: delivery and approval had happened; the launch had not. That account could support a statement about the working experience, but not yet a statement about sales after launch.
Apply the same distinction to a reader using your product:
| What happened | What you can ask about now | What remains unknown |
|---|---|---|
| Reader opened the companion | Clarity of the starting instructions | Whether they applied the method |
| Reader produced a draft | How they made it and what changed | Whether they used it outside the exercise |
| Reader used the draft | What happened in that situation | Whether results persist or generalize |
| Reader returned for another task | Why they returned and what differed | Typical results for other readers |
You do not need to wait for a dramatic transformation. A modest, accurately described change can help the next buyer understand the product's job.
Send a request that permits an ordinary answer
Adapt this original request to a reader whose actual use you know about:
You mentioned using the editing companion on your how-to article. Would you be willing to answer three short questions about that experience? I'm interested in what you tried, what changed, and anything that remained difficult. A few rough sentences are fine. You can reply privately without agreeing to publicity. If there is a useful excerpt, I'll send the exact wording and proposed placement for your approval before publishing. No problem if you'd rather pass.
Name the task only if the reader already shared it. Otherwise ask whether they have used the product yet. Do not turn an unopened purchase into an assumed success story.
Make the choice real. Declining should not affect access, ordinary support, or your willingness to hear criticism. If they do not reply, leave them room to be busy. One polite reminder may fit the relationship; a sequence of increasingly personal requests can make a voluntary favor feel owed.
Use these questions in order
Start with three questions. Use the follow-ups only when something important is unclear.
- What were you trying to do when you used this? Ask for the specific task rather than their general aspiration.
- What did you try, and what changed in the work itself? An added section, a rejected option, or a clearer next step can be described without inventing a number.
- What remained difficult or did not change? Preserve the boundary of the account.
Useful follow-ups include:
- What would your usual approach have been?
- Which instruction influenced the change you described?
- Did you use the result, or is it still a draft?
- Did another person, tool, or resource contribute?
- Is there a before-and-after example you are comfortable sharing privately?
Avoid questions that smuggle in your preferred conclusion. “How much time did this save?” assumes a saving. Ask whether it changed the time required, and how they know. “Why would you recommend it to everyone?” assumes both a recommendation and universal fit. Ask who, if anyone, they think would find it useful.
If their answer is simply “I haven't used it yet,” thank them. That is information for your product work, not raw material to reshape into praise.
Turn a vague compliment into a specific account
The following example is fictional. It shows how questions can uncover detail; it is not a Skillfully testimonial or an observed reader result.
An author teaches people to edit practical how-to articles. A reader writes, “Great tool. Much clearer now.” The author asks what the reader was editing and what changed.
The reader explains that their article introduced three alternatives before telling beginners what to do first. They used the companion's ordering exercise to put the basic sequence first and move exceptions below it. They have not published the revision or watched someone follow it.
An accurate proposed excerpt would be:
“I used the ordering exercise to move the basic steps above the exceptions in my how-to draft. It gave me a concrete revision to make. I haven't tested the article with readers yet.”
The detail makes this more informative than the initial compliment. It still says nothing about traffic, completion rates, income, or saved time. The author should not add those claims in a headline above it.
The next useful question is whether the reader approves that wording. It is not whether they can make it sound more enthusiastic.
Offer a format the reader actually wants
A small-business commenter, u/turo9992000, explained a personal limit:
“I just don't like the idea of a video of me out there. Nothing to do with them as a company.”
That comment is one person's preference, not evidence that video is generally bad. It illustrates why declining a format tells you little about satisfaction.
Offer a written reply, a short conversation with agreed notes, or no public account. If you want to record a conversation, ask separately before recording. Do not assume permission to quote an email also permits a headshot, employer name, screenshot, or video clip.
Both Reddit accounts above are public, pseudonymous discussions, not verified customer interviews or endorsements of this approach.
Approve the words and the presentation together
Use this compact approval record:
| Field | What to send or record |
|---|---|
| Exact excerpt | Every sentence proposed for publication |
| Attribution | Name, role, initials, or other description the reader approves |
| Placement | Specific product page, email, or other intended use |
| Nearby claim | Heading or caption that changes how the excerpt will be understood |
| Editing | Any shortening or grammar changes, shown in the proposed text |
| Relationship | Relevant free access, payment, employment, or other connection |
| Permission | Explicit approval, any restrictions, and a contact for changes |
In the United States, FTC endorsement guidance says endorsements must reflect honest opinions and cannot support claims the marketer could not otherwise make. Approval of a quote does not independently establish that a result is typical.
Keep the original reply with the approved version so later edits do not drift beyond what the reader meant. If the product changes substantially, check whether the account still describes what you sell. A testimonial about personal help from you should not silently become proof of what an unattended companion does.
Let the account inform the product too
A narrow testimonial can reveal the exact instruction worth preserving. A qualified account can reveal where the next test belongs. Keep those observations in your improvement notes even if you never publish a quote.
If the same exercise matters repeatedly, define the quality standard before making broader claims. The guide to measuring agent skill quality can help distinguish a promising account from a repeatable evaluation.
When you are ready to explore a practical companion for your own method, bring one real reader task, the instruction they used, and what remains uncertain to Skillfully and choose Book onboarding. Those details provide a firmer starting point than a page of unspecific praise.