There is a specific kind of customer whose testimonial does more work than any other, and most companies never think to ask them for one. It is the customer who started with a single team, saw it work, and then rolled you out to a second — a different department, another office, a new function that does the job differently. That expansion is not a happy coincidence. It is the customer running an experiment on your behalf and deciding the result was worth repeating. When they carry a tool from the team that adopted it into a team that didn't ask for it, they are staking a little of their own credibility on you working the second time. A testimonial from that customer answers the exact question a scaling prospect is afraid to ask out loud — does this hold up when we push it past the team that loved it? — and it answers it with a decision, not a promise.
Why the second-team rollout is the testimonial prospects trust most
A first-team success proves you can win over the people who chose you. A second-team rollout proves something harder: that you survived contact with people who didn't. That distinction is exactly what a cautious buyer is trying to resolve.
- It is proof against the "it only works for early adopters" fear. Every prospect evaluating a tool quietly worries that the reference customers are unusually motivated. A customer who rolled you into a second, less-enthusiastic team has already tested that worry and beaten it — and can say so.
- The expander has skin in the game. When someone champions a tool into a team that isn't theirs, they are spending internal capital. Their testimonial isn't the opinion of a satisfied user; it's the position of a person who bet on you internally and was proven right.
- It names the mechanism of scaling. These customers can describe how the second rollout went — what they worried about, what made it easier or harder than the first, what convinced the new team. That is precisely the operational detail a prospect planning their own rollout is starving for.
Catch the moment the second team goes live
The window for this testimonial opens the moment the second team is genuinely using you and closes as the rollout becomes old news. The signals are usually visible in your own data before anyone says anything.
- Watch for the expansion signal. A jump in seats, a new set of email domains or team names, a second workspace, a usage spike from a department that wasn't there last quarter — any of these is your cue that a rollout just happened. Treat it as a testimonial trigger, not just an upsell milestone.
- Ask right after the new team's first win. Don't ask the day the seats are provisioned; ask a few weeks in, once the second team has had its own small success. The champion is proudest — and most articulate — when their bet has just paid off, not while it's still unproven.
- Go to the person who drove it. The best quote comes from whoever pushed the rollout, not from a new user on the second team. The driver can speak to the before-and-after and the decision; the new user can only speak to this week.
Ask questions that surface the rollout story
A generic "how's it going?" gets you a generic answer. To get a testimonial that proves scale, ask about the expansion specifically — the doubts, the decision, and the outcome.
- Ask what made you confident enough to expand. "You'd only used us on the support team — what made you comfortable putting us in front of sales?" This invites them to lay out their own reasoning, which is the substance of the quote.
- Ask what the second team was skeptical about. "Did the new team push back at all, and what changed their mind?" A testimonial that names a real objection and its resolution is far more persuasive than one that reports smooth sailing, because prospects expect friction and trust a source that admits it.
- Ask them to compare the two rollouts. "Was the second rollout easier or harder than the first?" The answer often produces the single best line — "honestly it was faster the second time, the team saw what the support side had done" — which is exactly the reassurance a prospect planning a phased rollout wants.
Turn the answer into a quote, and do the work for them
The champion who just expanded you is, by definition, busy and influential — the two traits most likely to make a testimonial request die on the vine. Remove every ounce of effort from the ask.
- Reflect their own words back. If they said "the second rollout basically ran itself," quote that line directly in your ask: "That's a perfect summary — can we use it?" People approve their own words far more readily than they compose new ones.
- Draft the sentence and let them approve it. Write one clean testimonial from what they told you and send it for a yes/no edit. A champion will fix a draft in ten seconds; they will let a blank "please write us a testimonial" sit for a month.
- Anchor it to the scale, with permission. With their okay, a testimonial that states the tool is now used by two teams — "we started with support and have since rolled it out to sales and success" — carries the weight of an internal endorsement that survived expansion. That framing is the whole reason this testimonial is worth more than a single-team quote.
Make expansion a standard testimonial trigger
The reason these testimonials are rare isn't that the moment is weak — it is one of the strongest signals a customer ever sends — but that companies file expansion under "revenue" and never under "proof." The fix is to wire the two together: whenever an account expands to a new team, an automatic prompt should tell whoever owns the relationship to catch the story, ask the rollout questions, and draft a quote while the win is fresh. Do that consistently and your most valuable social proof — evidence that you scale past the team that first believed in you — starts arriving as a natural byproduct of the growth you were already tracking. The customer already proved you work at scale, in the most convincing way there is. All you have to do is ask them to say it out loud.