Some of your strongest accounts didn't arrive through a sales process. One person — an engineer, a designer, a support lead — signed up on a free plan, found it genuinely useful, and started nudging colleagues to try it too. By the time anyone in procurement noticed, half the team was already logged in. This is bottom-up, or product-led, adoption, and the customers who arrive this way make unusually credible testimonials: nobody forced the tool on them, so their praise reads as earned rather than mandated.
But the standard testimonial playbook assumes a top-down deal — a buyer who "chose" you, a sponsor who signed off, a kickoff you can anchor the story to. Bottom-up accounts have none of that. There's frequently no single decision-maker, no formal evaluation, and no tidy "we selected this vendor" narrative. Ask the wrong person the wrong question and you get a shrug. Here is how to work with how these customers actually adopted you.
Why Bottom-Up Testimonials Are Worth the Extra Effort
A top-down testimonial answers the question "did the buyer feel good about the purchase?" A bottom-up testimonial answers a better one: "did the people who actually use this every day want to keep using it?" That second question is the one your next prospect — especially a hands-on practitioner evaluating you — is really asking.
Grassroots adoption is itself the proof point. When a quote can honestly say "nobody told us to use this; we started on our own and it spread," you've bottled the most persuasive signal in software: voluntary, peer-driven uptake. The catch is that this signal lives in the details of how it spread, and those details evaporate if you ask a generic "would you recommend us?" question months later.
First, Find the Right Voice — There May Be More Than One
In a bottom-up account, "the customer" is not one person. You usually have three distinct voices, and each tells a different part of the story:
- The originator — the person who signed up first. They can speak to the initial problem and the moment the tool clicked. This is often your most authentic quote.
- The spreader — whoever pushed adoption to teammates. They can speak to why it was worth telling others about, which is exactly the peer-recommendation angle a prospect trusts.
- The eventual approver — the manager or buyer who later formalized it. They matter for a logo and title, but their quote is usually the least interesting, because they adopted a decision the team had already made.
Identify all three in your usage and CRM data before you reach out. The originator and spreader are frequently the same person; when they're not, a two-voice testimonial ("I found it, then my whole team was using it within a month") is stronger than either alone.
Ask in a Way That Matches How They Adopted You
The reason a stock request falls flat here is that it asks about a decision that never happened. Don't ask "why did you choose us?" — they didn't choose in any formal sense. Ask about the spread:
- "How did you first come across us, and what made you keep using it?"
- "You started on your own — at what point did you start telling teammates?"
- "What did you say to a colleague to get them to try it?"
That last question is gold. The answer is a peer recommendation captured in the customer's own words, which is the exact thing a bottom-up prospect wants to hear. If you're drafting a version for them to approve rather than asking cold, the same principle applies — lead with the organic-spread story, not a manufactured selection narrative.
Time the Ask to the Adoption Curve, Not the Contract
With top-down deals you often ask after signing. Bottom-up is different: the emotional peak happened before the contract, when the tool first solved a real problem and the person felt like they'd discovered something. If you wait until procurement formalizes the account, you've missed the moment that makes the best quote.
Watch for in-product signals of that peak — a spike in seats invited, a jump in usage, a support ticket that ends in genuine thanks. Those are your natural openings. A request that lands right after a team crosses from one active user to five is far warmer than one sent quarter later during a renewal.
Protect the Specifics That Make It Believable
The trap with grassroots stories is that they get sanded down into "great tool, easy to use" — which proves nothing. What makes a bottom-up testimonial land is the texture of the spread:
- The concrete starting problem ("I was tracking this in a spreadsheet nobody else could open")
- The organic mechanism ("I shared one link in our team channel and by Friday six people had accounts")
- The absence of a mandate ("no one asked me to — I just kept using it")
Keep those. They're the parts a fabricated quote would never bother to include, and they're what let a reader picture the same thing happening on their own team.
Turn One Account Into a Repeatable Pattern
Bottom-up testimonials are most powerful in aggregate, because a pattern of grassroots adoption is more convincing than a single instance. Once you've captured a few, group them so a prospect sees the recurring shape: one person starts, the team follows, formalization comes last. As you collect more of these, it helps to have a way to organize your testimonial library so you can pull the bottom-up stories on demand when a product-led prospect is evaluating you.
The One Thing to Remember
A bottom-up customer didn't buy you — they adopted you, and then convinced their colleagues to do the same. Don't force their story into a top-down "why we chose this vendor" frame. Ask how they found you, why they kept using it, and what they said to the first teammate they pulled in. Capture the spread while it's fresh, protect the specifics, and you'll have the one testimonial a skeptical, hands-on prospect actually trusts: proof that real users chose you without being told to.