← The Journal

Revenue Communication

·16 June·6 min read

The Testimonial Request You Never Sent

Most business owners delay requesting testimonials longer than necessary. The delay is often not about the relationship. It is about the language of the ask.

By Casey Bawden

Most business owners know, at the end of a successful engagement, that they should ask for a testimonial. Most of them do not ask immediately. Many wait longer than makes practical sense. Some do not ask at all.

The reasons given are usually relational: the client seems busy, the timing doesn't feel right, they don't want to seem presumptuous, they're not sure if the engagement went well enough to warrant asking. These framings locate the delay in the relationship. In many cases, the actual cause is simpler: the business owner does not have language for the ask that does not feel uncomfortable.

Why the ask feels difficult

Requesting a testimonial is structurally similar to the other professional asks that activate the reflex apology and hedging patterns: it involves making a request that has a social cost for the asker, asking for something that benefits the asker rather than the recipient, and risking a no.

These conditions reliably activate the structural habits. The result is that the testimonial request, when it is eventually composed, is written in language that makes it as easy as possible for the client to decline: I know you're incredibly busy and I completely understand if you don't have time, but I just wanted to ask whether there was any chance you might be able to write a few words if it wasn't too much trouble.

This request does not communicate that a testimonial would be valued. It communicates that the business owner expects it to be an imposition, has pre-apologised for it, and will not be surprised or disappointed if the answer is no. The client receives permission not to respond — which, given that testimonial requests require effort, they often take.

What the delayed ask costs

The optimal moment to request a testimonial is immediately after the outcome is visible — when the client is most aware of the value, most disposed to attribute it, and most available to recall specifics. Delay erodes all three.

A client asked two days after a successful project outcome can recall the outcome, the specific way the work affected them, and the context in which the value was produced. A client asked six weeks later is recalling from memory, may have attributed the outcome to other factors in the interim, and is less emotionally connected to the result. The testimonial they write six weeks later is structurally less specific, and therefore less useful.

The testimonial that would have named a context, a mechanism, and an outcome often becomes, six weeks later, a general statement of satisfaction. The delay is not just a timing problem. It is a structural cost with a specific cause.

The structural alternative

A testimonial request is a professional ask. It is made clearly, directly, and without pre-apology for the fact of asking.

Working with you on the [specific project] was a good experience for me — the outcome was [specific result]. I'm building out my client reference materials and a short testimonial from you would be useful. If you're open to it, even two or three sentences about what the experience was like from your side would be excellent. Happy to suggest some prompts if that would make it easier.

This ask is direct. It does not apologise for the request. It explains the purpose clearly. It reduces the effort required by offering prompts. It is specific enough about the project that the client's memory is immediately engaged. It is short enough that it does not feel like a formal process.

The business owner who writes this ask immediately after a successful engagement will receive more testimonials, more specific ones, and faster, than the one who waits until the discomfort of the ask feels manageable — because the structural quality of the ask itself is part of what makes it manageable.

What a useful testimonial needs to contain

The final structural point in the testimonial process is not about the ask but about the output. A testimonial that names a context, a mechanism, and an observable outcome is structurally useful in professional materials. A testimonial that expresses general satisfaction is not.

The prompts offered in the ask can shape the structure of the response: What was the situation before we worked together? What specifically changed? What outcome did you notice? These prompts are not manipulation — they are a structural guide that produces useful evidence from a client who wants to support the business owner but does not know how to frame what they want to say.

Subscribe

Field notes, in your inbox.

New analyses on structural language and professional authority — sent every two to three weeks, never to your spam folder.

No spam · Unsubscribe anytime

Subscribers receive Seven Professional Emails, Rewritten — free.

Structural Revenue System™

Identify the patterns costing your business revenue. Free Revenue Language Diagnostic. Five communications. Ten minutes.