A thank-you email after a project can do more than close a polite loop. It can confirm what was delivered, acknowledge the client’s collaboration, and invite useful feedback while the experience is still fresh. If the relationship went well, you may also want to ask whether the client is willing to leave a review or provide a short testimonial.
The difficult part is making the request feel human rather than transactional. A review should be voluntary, specific, and based on the client’s own words. It should not imply that a client owes you praise because an invoice was paid, and it should never ask someone to invent results they did not experience.
This guide includes email structures and scripts for freelancers, virtual assistants, designers, writers, and operations providers. Use only the claims and channels that fit your agreement. Ask permission before publishing a client’s name, company, logo, private details, or identifiable project information.
Choose the right moment
The best timing depends on the engagement. A natural moment may be:
- immediately after a successful handoff;
- after the client confirms that the deliverable meets the brief;
- at the end of a project or retainer period;
- after the client mentions that the work was useful;
- during a planned offboarding process.
Do not ask while a deliverable is still under review, a correction is unresolved, or an invoice dispute is active. A thank-you can still be appropriate during a complicated project, but a public review request may add pressure at the wrong time.
You also do not need to ask every client. If the work was not a good fit or the relationship ended poorly, close the engagement professionally and keep the feedback request private or skip it.
Start with a real thank-you
A useful thank-you names something concrete. Instead of “Thanks for everything,” mention the collaboration, decision, or opportunity that made the work possible.
Thank you for the clear feedback on the onboarding workflow and for making time to confirm the final handoff. I appreciated how quickly you answered the open questions, and I’m glad the process documentation is now in your team’s shared folder.
Specific appreciation is more credible than exaggerated praise. It also shows the client that you noticed their contribution rather than treating them as a source of a testimonial.
If the project is complete, include a short operational closeout:
- what was delivered;
- where the final files live;
- what remains open, if anything;
- the next support or contact step.
The thank-you email should stand on its own even if the client declines a review.
A simple thank-you email
Subject: Thank you for working together on [project]
Hi [Name],
Thank you for the opportunity to support [project or business]. I especially appreciated [specific collaboration, decision, or context].
The final [deliverables] are here: [link]. We also confirmed that [brief status or next step]. If you notice anything that needs clarification, please let me know by [date or reasonable window].
Thank you again for your time and trust. I enjoyed working with you.
Best,
[Your name]
This version does not request a review. That is sometimes the right choice, especially when the client relationship is new or the engagement was sensitive.
Ask for feedback before asking for a public review
Feedback and a public review are different requests. Feedback helps you improve. A review helps other people understand what it is like to work with you. You can ask for both, but make the choices clear.
If you have two minutes, I’d value one piece of feedback: what part of the process was most helpful, and what could I make easier next time? You can reply privately—there is no need to write a public review.
This gives the client a low-pressure way to respond. It can also reveal a useful process improvement even when the client does not want their comments published.
A review request with a clear choice
When the project is genuinely complete and the client has indicated satisfaction, try this:
Subject: Thank you — optional feedback on [project]
Hi [Name],
Thank you for working with me on [project]. I appreciated [specific detail], and I’m glad we were able to complete [factual deliverable].
If you’re comfortable, would you consider leaving a short review about your experience here? [review link]
A sentence or two about the type of support, communication, or process you experienced is plenty. Please use your own words, and feel free to skip this request—there is no obligation.
If you would rather share private feedback, you can reply directly to this email. I’d especially value knowing [specific question].
Thank you again,
[Your name]
The phrase “use your own words” matters. Do not provide a glowing draft for the client to copy unless the platform and your agreement clearly allow it—and even then, do not put claims in their mouth. You may offer prompts, not a manufactured endorsement.
Give prompts without steering the answer
Some clients want to help but do not know what to write. Neutral prompts make the task easier:
- What type of work did we complete together?
- What was the process like from your perspective?
- What did you find clear, reliable, or useful?
- Who would you recommend this service to?
Avoid prompts that assume a result, such as “How much time did I save you?” or “How did I increase your revenue?” unless the client independently documented that outcome and wants to discuss it. Honest, modest feedback is better than a dramatic claim that cannot be supported.
Ask for permission to reuse private feedback
A private reply is not automatically public marketing material. If a client sends a kind note, ask before quoting it:
Thank you for the thoughtful feedback. Would you be comfortable with me quoting the sentence about [specific point] on my website or service page? I can attribute it to [name and role / first name only / anonymous], or keep it private. No problem at all if you prefer that I don’t use it.
Wait for a clear yes. Confirm the exact wording, attribution, and places where it may appear. If the client later changes their mind, remove or update the quote where reasonably possible.
Do the same for logos, screenshots, project examples, and identifiable details. A successful collaboration does not automatically grant permission to publish the client’s information.
What not to promise
A review request should not include claims such as “This will help me grow,” “You’ll get a discount if you leave five stars,” or “Please mention the results we discussed” when those results are not verified. Incentives may also conflict with a platform’s rules or your professional obligations, so check the relevant terms before offering one.
Avoid collecting confidential details in a public review. If the work involved sensitive operations, internal data, or private client information, suggest describing the type of support in general terms or keeping the feedback private. One gentle follow-up is reasonable; repeated reminders are not.
For broader client follow-ups and admin, use the free Mosaic Maker Templates checklist: https://mosaicmaker5.gumroad.com/l/skgtmh
Top comments (0)