For B2B teams selling to buying committees
Collect Testimonials From Multiple Stakeholders
Your prospects buy as a committee, so one quote from one person at a happy account only reassures one of them. Write a request for each role below: the person who uses the product every day, the admin who set it up, and the buyer who signed. Then ask your champion to introduce you.
- A request written for each role
- An intro note for your champion to forward
- Questions that only that role can answer
The problem, solved
One happy account, three different stories
Situation 1 of 5
Only our champion ever gives quotes
The person who brought you in is happy to talk, so every testimonial from that account sounds like the same enthusiast.
How StoryProof solves it
Add each person at the account to your StoryProof contacts and send each one their own request by email.
Situation 2 of 5
Our questions only make sense to users
Asking a finance director about their favourite feature gets a polite blank. They care about cost, risk and whether the rollout landed.
How StoryProof solves it
From Pro, a multi-step form asks several questions in one sitting, so each role can get questions written for what they actually saw.
Situation 3 of 5
The executive will talk, not write
Senior buyers rarely sit down to write a paragraph, but most will give you two minutes between meetings.
How StoryProof solves it
The same link takes a short video or an audio note recorded in the browser, so a busy buyer can just speak.
Situation 4 of 5
Quotes from one account get jumbled
Six months later nobody remembers which quote came from the admin and which from the buyer, so they get used in the wrong places.
How StoryProof solves it
Tag every testimonial with the account and the role, so you can find the buyer quotes for one customer in seconds.
Situation 5 of 5
Every page shows the same voice
The pricing page needs the buyer, the security page needs the admin, the product tour needs the user. One quote cannot do all three.
How StoryProof solves it
Choose which approved testimonials appear in each widget, so every page hears from the role that reads it.
Request builder
Write a request for each role
Fill in the account and your champion’s name, then switch roles. The champion intro comes first: send it before any of the role requests.
- Ask the champion for introductions
Subject: Could you introduce me to two colleagues?
Hi [Daniel], Thank you again for your testimonial. People evaluating [the routing platform] keep asking to hear from someone in their own role, so I would love a short story from two other people at [Northfield Logistics]: whoever set it up, and whoever signed off on it. Would you be happy to introduce me? I will keep it to a few questions each, and they can answer by text or a quick video. Thanks, [Ines]
Everything you type stays in this page. Nothing is sent.
What each role can credibly say
Use each voice where its reader is. A buyer quote about ease of use convinces nobody who uses software every day.
In StoryProof
Collect the full set in StoryProof
- 1
Build a form per role
Three short multi-step forms with the role questions above. Each answers by text, audio note or video.
- 2
Get the introductions
Send the champion intro first. Ask only for people who would recognise your name when your email arrives.
- 3
Add each person to contacts and send
Send each role its own request, by email from StoryProof.
- 4
Approve and tag by account and role
Approve each reply, then tag it with the company and the role so the set stays together.
- 5
Place each voice on its page
Choose the buyer quote for the pricing widget, the admin quote for the security page, and so on.
What happens next: Thank the champion for each introduction that turned into a testimonial. They spent some of their own goodwill on you.
Before you start
Things that can go wrong
The company may still need to approve
Three people agreeing does not mean their employer has. Large customers may need a comms or legal sign-off for each quote.
Do not go around the champion
Emailing their boss without an introduction can embarrass the person who brought you in. Ask them first.
Not every role will reply
Two of three is a good result. A missing buyer quote is better than one you wrote for them.
Keep the stories consistent
If the user and the buyer describe the rollout differently, publish both as they said them. Do not smooth the difference away.
FAQ
Questions people ask
Short answers to what usually comes up next.
Should I ask everyone at the account at once?
No. Start with the champion, then the person they introduce first. Spacing the requests keeps the account from feeling like a campaign target.
Which role is most valuable to get?
The one your prospects are missing. If your sales team keeps losing deals at the finance step, the buyer quote is worth the most effort.
Can I combine the three into one case study?
Yes, and it is a strong format. Keep each person’s words attributed to them, and get each one’s approval for the combined piece.
What if the buyer has left the company?
Ask whoever owns the budget now. Someone who renewed has an informed view too, sometimes a better one than the person who first signed.
Still have a question? Ask the StoryProof team or book a demo.
Hear from the whole account, not one fan
Build the three role forms and send the champion intro this week.
Last updated 2026-11-05.