For web designers and studios
Get two testimonials from every website you launch
At launch a client can tell you how the project felt. A couple of months later they can tell you what the site changed. Write both requests below, then let StoryProof collect them and put them on your portfolio.
“We put the review wall under our pricing table and prospects quote the reviews back to us on calls.”
“StoryProof made collecting and showing real customer video reviews effortless for us.”
“The widget looks native on our site. Nobody can tell it is embedded.”
“Collecting video reviews used to be the hardest part. Now it takes one link.”
“Set up in ten minutes, and support answered the one question I had straight away.”
The problem, solved
Where web design testimonials go missing, and the StoryProof fix
Situation 1 of 4
Clients go quiet once the final invoice clears
After handoff the client is busy running the new site, and one unanswered request is usually where the testimonial dies.
How StoryProof solves it
On plans with automations, StoryProof sends a reminder three days after the request and a last email four days after that, and stops the moment the client responds.
Situation 2 of 4
The client talks happily but hates writing copy
Owners who spent weeks approving web copy are tired of writing, so a blank text box gets put off indefinitely.
How StoryProof solves it
The request link takes a video or an audio note in the browser as well as text, so the client can simply say what they think.
Situation 3 of 4
A restaurant prospect sees only law firm quotes
Prospects look for proof from businesses like theirs, and a portfolio with mixed industries hides the relevant praise.
How StoryProof solves it
Tag each testimonial by project and industry, then choose which ones appear in the widget on each portfolio page.
Situation 4 of 4
Adding a new quote means redeploying my own site
Your own studio site is the last thing you have time to edit, so new praise sits in an inbox instead.
How StoryProof solves it
An embedded widget loads its testimonials from StoryProof each time, so approving a new one updates your portfolio without republishing.
Templates
Write your launch and results requests
Fill in the project details. Switch between the launch-day ask and the one you send once the site has been live for a couple of months.
- Launch day request
Subject: [the new bakery website] is live
Hi [Maya], [the new bakery website] is officially live. Thank you for trusting me with it. While the project is fresh, would you share a few words about what working together was like? It takes a couple of minutes: [your StoryProof link] Two questions to answer, in writing, as an audio note or on video: 1. What made you start looking for a new website? 2. What was the process like for you? Thanks, [Leo]
- Handoff checklist line
Add this to the handoff document you already send.
Last step: if you are happy with [the new bakery website], I would really value a short testimonial. Here is the link: [your StoryProof link]
Filled in your browser. Nothing you type is sent anywhere.
Prompts
Different questions for different moments
Put one set in your launch form and the other in a second form for the check-in.
At launch
- What made you start looking for a new website?
- What was the process like for you?
- What surprised you about working together?
Leave out
- Asking about results before the site has had time to produce any
60 to 90 days after launch
- What has changed since the new site went live?
- What do customers say about it?
- How easy is it for your team to update?
Leave out
- Suggesting figures for them to repeat
In StoryProof
Run both asks from StoryProof
- You will need
- A StoryProof workspace
- Your project list with launch dates
- 1
Create the launch form
Add the launch prompts. Clients answer by video, audio note or text from the link in your handoff email.
- 2
Send it on launch day
Use the template above, or have StoryProof email the request to the client.
- 3
Let reminders chase the busy ones
On a plan with automations, the follow-up template reminds clients who have not answered and stops when they do.
- 4
Diary the results check-in
Two or three months after launch, send the results template with a link to a second form that uses the later prompts.
- 5
Approve, tag by project, publish
Approve each answer, tag it with the project and the industry, and add the best to the matching portfolio page or your Wall of Love.
What happens next: Pair each project in your portfolio with its launch quote and its results quote. Together they show both the process and the outcome.
Before you start
Keep it credible
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Let the client choose the numbers
If a client says enquiries doubled, that is their claim to make. Never write a figure into their quote, and leave it out if they are guessing.
- 02
Not every site produces a visible result
Some sites are about credibility rather than leads. A client saying they are proud to send people to it is a perfectly good testimonial.
- 03
Ask before naming the client’s business
Most will agree, since it promotes them too, but ask before you link to their site from yours.
- 04
A redesign can date the quote
If the client later replaces or rebuilds the site, a testimonial beside a screenshot of the old version no longer matches what visitors find. Review portfolio pages each year and retire pairs that have drifted.
FAQ
Questions people ask
Short answers to what usually comes up next.
When should a web designer ask for a testimonial?
Twice: on launch day for the process, and 60 to 90 days later for what the site has changed.
What if the client has not seen any results yet?
Ask them to say so. A testimonial about a smooth process is still useful, and you can check in again later.
Who should I ask when the project had several people on the client side?
Ask the person who lived with the site after launch, usually whoever updates it or handles the enquiries. The person who signed off the budget can speak to the process, so they suit the launch request better.
Should I ask a client whose project went over time?
Yes, if it ended well. Clients often mention how a delay was handled, and that honesty can reassure a prospect more than a quote that says everything was perfect.
Still have a question? Ask the StoryProof team or book a demo.
Send your first launch-day request
Create the launch form in a few minutes and send it with your next handoff.
Last updated 2026-11-04.