There is a specific awkwardness in B2B testimonial collection that rarely gets named: the person who loves your product is often not the person whose name you most want on the quote. Your daily contact is a coordinator, an analyst, a junior specialist — someone who lives in your tool and would happily rave about it — but the testimonial that moves a prospect is one signed by a director or a VP, a title a buyer recognizes as carrying authority. The temptation is to bypass your contact and email their boss directly, which is fast, occasionally effective, and a reliable way to damage the one relationship you actually have. The better path is slower and routes through your junior contact rather than around them, and it produces a quote that is both authoritative and honest about who said what.
Why going over their head is the wrong move
The instinct to skip the junior contact comes from a real observation — their title will not impress a prospect — but acting on it treats your only advocate as an obstacle. The junior contact is the person who champions renewal internally, who files the support ticket instead of churning, who mentions your tool in the team meeting. Emailing their manager without warning tells that person, in effect, that they were useful only as a stepping stone. Even if the manager replies with a glowing line, you have taught your day-to-day champion that a testimonial request is something to be wary of, and you have made your next ask — for a renewal reference, a case study, an expansion conversation — measurably harder.
There is also a practical failure mode. A manager who has never used your product cannot write a specific testimonial. Ask them cold and you get a generic line — "great tool, helpful team" — that reads as filler precisely because it lacks the operational detail only a daily user could supply. The specificity that makes a testimonial persuasive lives with the junior contact. Routing around them throws away the very thing you were trying to capture.
Collect the substance from the person who has it
Start where the value actually is. Ask your junior contact for the testimonial first, framed around what they know better than anyone: the before-and-after of their own work. The questions that draw out usable material are concrete and rooted in their daily experience — what the workflow looked like before, what specifically changed, how much time or friction it removed, what they would tell a peer evaluating the tool. A daily user answers these with the texture that makes a quote believable, because they are describing something they lived rather than something they are guessing at.
Capturing this well is a matter of asking narrow questions and doing the drafting for them. If your intake process turns a few short answers into a clean, quotable paragraph — which is exactly the kind of friction a tool like ProofShow is built to remove — the junior contact spends two minutes, not twenty, and you walk away with the substantive core of the testimonial already written in their voice. That core is the asset. Whose name goes on top of it is the next, separate question.
Route the attribution upward — with your contact, not around them
Once you have the substance, treat the senior attribution as a favor you ask your contact to help arrange, not a person you approach behind their back. The move is to make your junior contact the one who takes the quote up the chain. A message like "This is genuinely useful for us to share — would it make sense to have [manager] put their name on it, or would you rather it come from you? Happy to draft whatever version works, and to send it over for their sign-off however you'd like to handle the intro" does three things at once. It hands the decision to your contact, it offers to do the work, and it signals that you will not blindside their boss.
Often the contact will say the quote is fine under their own name, and you should take that gladly — a specific testimonial from a real user with a modest title beats a vague one from a VP every time. When they do want to route it upward, they become your internal advocate for the sign-off, which is a far warmer channel than a cold email. The manager receives a pre-written, accurate quote, endorsed by their own team member, and is asked only to approve attaching their name. That is a low-effort yes, and it is an honest one, because the substance genuinely reflects their team's experience even if the words originated one level down.
Keep the attribution honest
There is a line here worth naming explicitly. Getting a senior name on a quote is legitimate when the senior person reviews and endorses it; it is not legitimate to invent a quote and paste an executive's title under it without their knowledge. The distinction is the sign-off. If the director reads the testimonial, agrees it reflects their view, and approves their name on it, the attribution is true — executives routinely endorse words drafted by their teams, and a testimonial is no different from any other statement they put their name to. What you are avoiding is the fabricated quote, the title borrowed without consent, the words no one at that level ever actually stood behind. Route the ask through your contact and secure a real sign-off, and the quote is both authoritative and clean.
The relationship dividend
Handled this way, the awkward constraint becomes an asset. Your junior contact learns that you treat them as a partner rather than a stepping stone, which strengthens the relationship you most depend on. The senior person is introduced to your product through a positive, low-effort interaction rather than a cold pitch. And you end up with a testimonial that carries a recognizable title on top and genuine operational detail underneath — the combination that actually convinces a buyer. The slow path, it turns out, produces the better quote and the better relationship. The shortcut produces neither.