Asking the champion who has just left the account.
Trigger the request at the win, while the person who chose you is still the person using it.
All use cases
Sales teams
Reps do not need more proof. They need the right piece, quickly.
Most sales teams already have testimonials. They are in a deck someone made last year, a Slack thread, and a folder nobody can find. The problem is not collection, it is retrieval: a rep on a call needs the story from a company of this size, with this objection, in this industry, and they need it before the follow-up email goes out. A library that keeps the campaign, format and person attached to each item is what makes that possible.
The workflow
The right quote, for the objection actually being raised.
Turn closed-won moments into approved proof, keep it in one library filtered by campaign and format, and give reps something specific to send after the call.
Best request moment
After a win, or a renewal that went quietly well
- 1Create a campaign the account team triggers after a win
- 2Collect the story while the evaluation is still recent
- 3Approve it into a library reps can search
- 4Publish the strongest to the pages buyers check alone
How the setup looks
Sales teams- Campaign
- Closed-won stories
- Destination
- Text · video · G2
- Published to
- Proof library · wall
Ready for review in the proof library
Growth adds Slack, Teams, Zapier and webhooks, so a new approved story can reach the team where they already work.
What to ask
Four questions that return something usable.
Broad questions get broad answers. These are written to surface a specific before and after.
- 01What were you using before, and what made you start looking?
- 02What almost stopped you from going ahead?
- 03Who else had to be convinced, and what convinced them?
- 04What has changed since, in terms someone in your role would recognise?
In the product
What this looks like once it is running
Every approved item keeps its campaign, format and date, which is what makes it findable in the middle of a call.
Common mistakes
Three things that quietly kill response quality.
One deck of quotes for every conversation.
An objection about implementation is not answered by a quote about pricing. Filter the library by campaign and format so the rep sends the one that fits.
Quoting a two-year-old story about a product that has changed.
Each approved item keeps its date and its campaign. Retire the ones describing a version you no longer ship.
Questions, answered
How is this different from a testimonial page?
A page is for buyers. The proof library is for the team: every approved item keeps the person, the campaign and the format, so a rep can find the one story that answers the objection in front of them.
Can new proof reach the team automatically?
On Growth and above, Slack, Teams, Zapier and webhook connections let an approved item land where the team already works instead of waiting to be noticed.
Can we route customers to G2 as well?
Yes. The same campaign can point at a public review destination you configure, so a win can produce both a private story and a public review.
Your happiest customers are ready to sell for you.
Give them the mic. Launch your first campaign free and watch quiet goodwill turn into public proof.