For SEO, consulting, training and coaching
Testimonials When Results Take Months
If your work pays off in month six, asking in week two gets you a polite note about how nice you were, and waiting until month six means the client has half forgotten the start. Split the ask in two. Put your start date in the planner below and get a dated plan: one request about working with you, a later one about what changed.
- An early ask about the experience, not the result
- A later ask once the outcome is visible
- Dates worked out from your own start date
The problem, solved
The timing trap of slow result work
Ask too soon and there is nothing to report. Ask too late and the client has moved on.
Situation 1 of 5
Nothing to report in the first month
A client three weeks into an SEO retainer can only say you are pleasant to work with. That is true, but it is not what a prospect needs.
How StoryProof solves it
Ask the early question about the experience only, and tag the reply as a process testimonial so it is not mistaken for proof of results.
Situation 2 of 5
By month six, the moment has passed
When the results arrive, the client is busy with what they unlocked. A cold request then reads like an afterthought.
How StoryProof solves it
Keep slow result clients in a smart list from day one, so the later request goes to the right people when the date comes round.
Situation 3 of 5
The later ask gets ignored
A busy client opens the email, means to reply and never does.
How StoryProof solves it
From Pro, follow ups send a reminder three days after the request and a last one four days later, and stop once the client responds.
Situation 4 of 5
Prospects assume results come instantly
A result quote with no time frame sets an expectation you cannot meet, and the next client is disappointed in month two.
How StoryProof solves it
Before approving, check the outcome testimonial says roughly how long it took. Hold it in the queue and ask if it does not.
Situation 5 of 5
Process quotes and result quotes get mixed
A sales page that shows "lovely to work with" where a buyer wanted evidence of outcomes weakens both.
How StoryProof solves it
Choose which approved testimonials go in each widget: experience quotes near your process section, outcome quotes near your offer.
Two stage plan
Your dated testimonial plan
Pick the day the engagement started. The offsets suit outcomes that show in roughly three to six months; stretch the later dates if yours take longer.
Day 0
Kickoff: record the starting point
Write down the baseline the client cares about, in their terms, so the later testimonial can describe a before and after honestly.
Day +30
Ask about the experience
Request a short process testimonial: how onboarding went, how you communicate, what reassured them. Do not ask about results yet.
Day +75
Early signals check in
In your normal reporting, ask what they have noticed so far. Note any concrete change they mention; it shapes the later request.
Day +150
Ask about the outcome
Request the result testimonial. Remind them of the starting point and ask what is different now and how long it took to show.
Day +157
Gentle reminder
If they have not replied, send one short reminder that refers back to the change they mentioned at the check in.
Day +365
One year on
For long retainers, ask whether the result has held. A quote that says it lasted is the strongest proof slow work can have.
The dates are worked out on this page. Nothing you pick is saved.
What changes when you split the ask
One request, badly timed
- Week two: "They are great, very responsive."
- Month six: no reply, the client is busy
- Results quotes with no time frame
- Every quote shown in the same carousel
Two requests on a plan
- Month one: a specific note on how the work is run
- Month five: a before and after in the client’s words
- Each outcome quote says how long it took
- Experience and outcome quotes placed separately
In StoryProof
Set the plan up in StoryProof
- 1
Build a list of slow result clients
Add clients as contacts and group the ones on long engagements into a smart list, so each stage goes to the right people.
- 2
Send the experience request
Email the collection link around month one. Clients can type a few lines, record audio or record video in the browser.
- 3
Send the outcome request later
Send the second request when results show. From Pro, reminders go out on their own and stop when the client replies.
- 4
Label and place each kind
Tag replies as "experience" or "outcome", check outcome quotes mention the time frame, then approve and place them in separate widgets.
What happens next: Review the plan once you have a few outcome testimonials. If results usually arrive sooner or later than you set, move the outcome request to match.
Before you start
Honest limits of a two stage plan
Some clients never see the result
If the outcome did not arrive, do not chase an outcome testimonial. The experience quote is the honest one to keep.
The dates are a starting guess
Every service lags differently. Treat the offsets as defaults and change them once you know your own pattern.
StoryProof will not time it for you
There is no trigger based on client results. You decide when the outcome request goes out, and the reminders follow from there.
Do not prompt a number
Ask what changed, not whether traffic doubled. A figure you suggest is your claim, not theirs.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is it worth asking before there are any results?
Yes, as long as you ask about the experience. Prospects for slow work worry about the months before results arrive, and a client describing how those months felt answers that worry.
Will asking twice annoy clients?
Two requests months apart, each about something different, rarely do. Say in the first one that you may check back once results show.
What if results arrive after the engagement ends?
Ask anyway, with a note that references the work and the starting point. Clients who saw a lasting change are often glad to be asked.
Should an outcome testimonial include how long it took?
It helps. A quote that says results showed after several months sets a fair expectation and stops the next client judging you in week three.
Still have a question? Ask the StoryProof team or book a demo.
Plan both asks before the work starts
Put long engagement clients in a list now and send each request when it will get a real answer.
Last updated 2026-11-07.