How to Ask for a Testimonial Without Feeling Awkward About It

by Eric Hanson, Backend Developer at Clean Systems Consulting

Most contractors who want testimonials never ask for them — because the ask feels uncomfortable. A simple reframe and a clear request eliminates most of that discomfort.

Why Contractors Do Not Ask

The discomfort around asking for testimonials is real and almost universal. It feels self-promotional. It feels like asking for a favor. It feels like it might make the client think less of you.

None of these feelings reflect what actually happens when you ask a client who had a good experience to share a short note.

What actually happens: the client says yes, writes something brief and honest, and thinks no less of you. In most cases, they are glad to help — they just would not have thought to do it unprompted.

The testimonial that does not exist is not because clients did not want to give it. It is because no one asked.

The Right Time to Ask

Timing is the most important variable. Ask too early and the engagement is not complete. Ask too late and the client has moved on, the memory has faded, and the ask feels out of context.

The right window: immediately at the close of a successful engagement, or within the first week after delivery. The engagement is fresh. The satisfaction is at its peak. The client has just received something that helped them. The goodwill is real and accessible.

After three months, that same client has mentally moved on. The ask still works, but the response is less immediate and usually less specific.

How to Ask Without Making It Awkward

The ask that works is direct, specific, and makes it easy:

"Working with you on this project was a great experience — I'm glad the integration landed well. Would you be willing to share a short note about what it was like to work together? Even two or three sentences would be genuinely helpful for my portfolio. If you're open to it, I can send a quick guide on what to include or draft something you can adjust."

This request:

  • Is direct without being demanding.
  • Makes the specific ask (two or three sentences) instead of leaving the client guessing how much work it is.
  • Offers to make it easier by providing a draft or a prompt.

The offer to draft something is worth making. Many clients are happy to provide a testimonial but find the writing uncomfortable. A draft they can adjust takes the work out of it and substantially increases the response rate.

What to Put in the Draft

If you write a draft for the client to adjust, it should cover: what the project was, what went well, and what it was like to work with you. Keep it specific and honest — the client will adjust anything that does not feel accurate.

"Working with [your name] on our payment integration was straightforward from the start. They got up to speed quickly, communicated clearly throughout, and delivered something our team could maintain without them. We'd work with them again."

That is a testimonial that is useful to you and feels authentic coming from a client. It is also easy to adjust to fit the client's voice.

Where to Use It

Once you have a testimonial, make it visible:

  • On your website or portfolio, attributed to the client (with permission to use their name and company).
  • On your LinkedIn profile in the recommendations section.
  • In proposals, when a past reference is relevant to the current client's situation.

A testimonial that sits in your email inbox is not doing anything for your business. The visibility is what makes it worth having.

The testimonial you never asked for is a piece of professional evidence that does not exist — and the only reason it does not exist is that you did not ask.

Scale Your Backend - Need an Experienced Backend Developer?

We provide backend engineers who join your team as contractors to help build, improve, and scale your backend systems.

We focus on clean backend design, clear documentation, and systems that remain reliable as products grow. Our goal is to strengthen your team and deliver backend systems that are easy to operate and maintain.

We work from our own development environments and support teams across US, EU, and APAC timezones. Our workflow emphasizes documentation and asynchronous collaboration to keep development efficient and focused.

  • Production Backend Experience. Experience building and maintaining backend systems, APIs, and databases used in production.
  • Scalable Architecture. Design backend systems that stay reliable as your product and traffic grow.
  • Contractor Friendly. Flexible engagement for short projects, long-term support, or extra help during releases.
  • Focus on Backend Reliability. Improve API performance, database stability, and overall backend reliability.
  • Documentation-Driven Development. Development guided by clear documentation so teams stay aligned and work efficiently.
  • Domain-Driven Design. Design backend systems around real business processes and product needs.

Tell us about your project

Our offices

  • Copenhagen
    1 Carlsberg Gate
    1260, København, Denmark
  • Magelang
    12 Jalan Bligo
    56485, Magelang, Indonesia

More articles

Why Some Projects Are Impossible to Save

“Can we still fix this?” Sometimes the real answer is: it was never set up to succeed.

Read more

Naming Your API Endpoints Is Harder Than It Looks

Endpoint naming seems trivial until it becomes inconsistent, ambiguous, and hard to evolve. Good naming requires treating APIs as long-lived contracts, not quick implementations.

Read more

Git Is Not Just a Backup Tool. Here Is What It Actually Is.

Most developers use Git as a glorified save button. Understanding what Git actually models — a directed acyclic graph of snapshots — changes how you use every command.

Read more

ActiveRecord Query Patterns That Actually Scale

ActiveRecord makes simple queries trivial and complex queries dangerous. These are the patterns that remain correct under load — and the common ones that quietly fall apart at scale.

Read more