When a customer switches teams inside their own company — moving from marketing to operations, from one product line to another, from a regional office to headquarters — and brings your product with them, they have just done something more valuable than renew. They have voted with their feet. Nobody made them re-adopt your tool on the new team; they chose to, because their firsthand experience told them it was worth the effort of introducing it all over again. That single act is one of the strongest expansion signals a proof strategy can capture, and almost nobody collects it as a testimonial.
Why an internal team switch is a testimonial goldmine
A lateral move is different from a promotion and different from a champion leaving for a new employer. The person hasn't gained authority over you, and they haven't taken your product to a stranger's company — they have carried it sideways, into a team of colleagues who could easily have said "we already have a tool for that." When your champion pushes past that friction to bring you along, they are demonstrating conviction in the purest form: unpaid, unprompted, and personally costly, because now their new teammates will judge the choice.
This is the land-and-expand motion happening organically, and prospects find it enormously persuasive. A quote that says "I liked it so much I brought it to my next team the moment I moved" answers the buyer's quietest fear — that adoption will stall after the initial deal. It is close kin to the credibility you get when a champion brings your product to their new company, but with an added advantage: the switch happened inside your existing account, so you can often verify it in your own usage data.
Notice the switch before it goes quiet
The obstacle, as always, is noticing. An internal team change rarely comes with an announcement to you. It shows up as small anomalies in your own data:
- A known user's activity drops on one workspace and a new workspace with the same email domain lights up.
- A champion's job title changes in your CRM enrichment or in their email signature.
- A support conversation mentions "my new team" or "now that I've moved over to..."
- A fresh seat gets provisioned and the inviter is someone who was previously in a different department.
Build a lightweight trigger for these. When a long-tenured user starts a new workspace, or when account enrichment flags a title change for an active contact, that should route to whoever owns advocacy — not just to the renewal forecast. The emotional and narrative peak is right after the switch, while the champion is actively re-selling you internally and feeling good about the decision. Wait a quarter and it becomes background; reach out within a couple of weeks and you catch a story in motion.
What to actually ask
Lead with recognition of what they did, not with a request. The champion just did you a favor by re-adopting; opening with "can we get a quote?" flattens a generous act into an errand. Anchor the ask to the specific thing they did:
"I noticed you've brought us over to the [new team] — thank you, that genuinely means a lot. You didn't have to introduce a new tool to a team that could've just kept doing things the old way, so it says a lot that you did. I'd love to understand what made you want to bring us along. And if you're open to it, that story — someone choosing to re-adopt on a new team — is exactly the kind of thing other buyers find reassuring."
Then ask one pointed question rather than a vague request: "What made bringing us to the new team worth the effort?" The answer to that question is the testimonial. It naturally captures the situation (a team switch), the motivation (why you were worth re-introducing), and the recommendation — all in the customer's own words. A specific question yields a usable sentence; an open-ended "would you give us a testimonial?" yields a paragraph you have to salvage.
Frame the story around organic expansion
When you publish, position the quote for what it proves: adoption that spreads on its own. Pair it with the concrete before-and-after — "started on the marketing team, now running on operations too" — so the reader sees the expansion, not just the praise. If you can add a light metric ("two teams, one champion, zero sales touches"), the proof gets sharper.
This kind of testimonial also compounds. A champion who re-adopts on a new team is a prime candidate to become a repeat advocate — the same person who might later refer a peer unprompted or, if their career keeps rising, give you an even stronger quote after getting promoted. Treat the team-switch testimonial as the first entry in a relationship, not a one-off extraction.
Don't let the data-driven start feel like surveillance
One caution: because you often spot the switch in usage data rather than from the customer telling you, the outreach can feel a little Big-Brother if you lead with "I saw your activity move to a new workspace." Soften it. Frame your awareness as attentiveness, not tracking — "I noticed you've been setting things up with a new team" reads warmly; "our analytics show you provisioned a new workspace on Tuesday" does not. The goal is to make the champion feel appreciated for spreading you, not monitored. Get that tone right and an internal team switch becomes one of the most credible, most repeatable testimonials in your library — proof that your product is good enough that people carry it with them wherever they go inside a company.