For consultancies, systems integrators and implementation partners
Implementation Partner Testimonials at Go Live
Go live is the day your client is most relieved and least available. Ask then and you get silence; wait a year and the project team has moved on. Enter the go live date and get a plan that asks after stabilisation, reaches the right people, and leaves room for the vendor’s rules on how its name appears.
- Asks timed after stabilisation, not on cutover day
- Project sponsor and day to day users asked separately
- A check on vendor naming before anything is published
The problem, solved
Why go live testimonials slip away, and how StoryProof holds on to them
Implementation projects generate a lot of goodwill and very few published quotes. These are the usual leaks.
Situation 1 of 5
We ask during cutover week
On go live the client is handling issues, training users and reporting to the board. A testimonial request lands as noise.
How StoryProof solves it
Add the client contacts to StoryProof when the project closes and email the request once the plan says so, with reminders on a plan with automations.
Situation 2 of 5
The sponsor left before we asked
Project sponsors move on within months of go live, and their successor never saw the before.
How StoryProof solves it
Requests go out on a dated plan from go live, so the sponsor is asked while they still own the result.
Situation 3 of 5
Executives will not write a paragraph
The finance director who signed off the project will happily say two sentences on a call, and never type them.
How StoryProof solves it
The same link lets them record a short video or audio note in the browser, or type if they prefer.
Situation 4 of 5
Quotes misuse the vendor’s product name
Clients write the vendor’s product in shorthand, or say things about it the vendor would not let a partner publish.
How StoryProof solves it
Nothing goes public until you approve it, so the naming can be checked against your partner rules before a quote goes anywhere.
Situation 5 of 5
Every practice uses the same quotes
A prospect looking at your HR practice sees a quote about a finance rollout, which tells them little.
How StoryProof solves it
Tag each testimonial by platform, module or industry, and choose which ones each practice page shows.
Go live planner
Plan testimonial requests from the go live date
Enter the date the system went live. The plan waits out the stabilisation period, asks the sponsor and the users separately, and returns once the client has seen a full cycle on the new system.
Day 0
Go live: ask nothing
Support the cutover. Note the people who praised the project in the moment; they are your candidates.
Day +21
Stabilisation review
Once early issues are closed, check with the client lead that the system is settled enough to ask about.
Day +28
Ask the project sponsor
Request a short testimonial about the project: how it was run, how the team worked together, what the business can do now.
Day +35
Ask key users
Ask two or three day to day users about training and the first weeks on the new system. Their view complements the sponsor’s.
Day +42
Naming and approval check
Check each answer against your partner agreement’s rules on the vendor’s name and logo, then confirm attribution with the client.
Day +120
After the first full cycle
Once the client has run a month end, payroll or quarter on the new system, invite the sponsor to record a short video about the outcome.
Dates are calculated in your browser. Nothing is saved.
Who to ask, and about what
A project has several client voices. Each can speak credibly to a different part of the work.
In StoryProof
Run it in StoryProof
- You will need
- A go live date and the client contacts for the project
- Your partner agreement’s rules on the vendor’s name and logo
- 1
Add the client team as contacts at project close
Sponsor, project manager and two or three key users, grouped by project.
- 2
Send each request on the planner’s date
StoryProof emails the collection link. On a plan with automations, reminders follow and stop as soon as someone replies.
- 3
Check naming, then approve
Read every answer for vendor naming and confidential detail before approving. Tag approved ones by platform and industry.
- 4
Show them on the matching practice page
Choose testimonials by tag for each practice or platform page.
What happens next: Add a testimonial step to your project close checklist, so every go live date starts a new plan.
Before you start
Things StoryProof does not settle for you
What this does not cover, and what to check on your side. Better to know now than after launch.
- 01
Vendor rules are yours to check
Partner programmes often set rules on using the vendor’s name and logo. StoryProof does not know your agreement; read it before publishing.
- 02
Client approval chains still apply
Large clients often need comms or legal to approve a named quote. Plan for that time after the testimonial arrives.
- 03
No project tool integration
StoryProof does not read go live dates from your project or delivery tools. The plan above is worked out from a date you enter.
- 04
Troubled projects need a different approach
If go live was rocky, do not run the routine plan. Wait until the issues are resolved, and ask about how you handled them.
FAQ
Questions people ask
Short answers to what usually comes up next.
How long after go live should we ask for a testimonial?
After stabilisation, typically a few weeks once the early issues are closed. Then come back after the first full business cycle for a longer story.
Can the testimonial mention the vendor’s product?
Usually yes, since that is what you implemented, but follow your partner agreement on naming and logo use, and do not publish claims about the product you could not make yourself.
Should we ask the sponsor or the users?
Both, separately. The sponsor speaks to the decision and the outcome; users speak to training and support, which prospects also want to hear.
What if the client cannot be named?
Use a role and an industry, such as a finance director at a regional manufacturer, with the client’s agreement on that description.
Still have a question? Ask the StoryProof team or book a demo.
Start the plan at your next go live
Set up a form now so the request is ready when the stabilisation period ends. No credit card needed to start.
Last updated 2026-11-05.