Ring My Client, Not My Deck
Photo: YBStauber, CC BY-SA 4.0, via Wikimedia Commons
I have a capabilities deck. It's nice. It's got a clean grid, some logos, and a page of principles that I rewrote four times. In the last eighteen months I don't think it has won me a single piece of work on its own.
The thing that keeps winning work is a phone call between two people I don't control. Before a proposal gets signed, I offer the prospect a short conversation with a past client — with that client's permission, and with a briefing note in both pairs of hands beforehand.
It sounds almost too simple to be a strategy. It is simple. But it is not easy, and the details matter more than the idea.
The offer, in one sentence
"Before we go any further, would it help to speak to the client I did something similar for? I'll set it up and brief you both."
That's the whole pitch. Note what it isn't: a testimonial, a case study, or a logo on a slide. It's an unscripted conversation between a buyer and someone who has already been where they're standing.
Setting it up without putting anyone on the spot
Ask the referee before you need them, not the week you need them. I keep a short mental list of clients who have said, unprompted, that they'd be happy to talk about the work. When a new prospect appears, I go back to that person with a specific request — the shape of the work, the sector, the size of the buyer — so they can see why they specifically are being asked.
Then I do three things:
- I confirm the referee is genuinely willing, not merely polite. One sentence of enthusiasm is worth more than a page of consent form.
- I ask what they'd rather not discuss — commercials, a difficult internal stakeholder, a delay that wasn't anyone's fault. Some things aren't mine to hand out.
- I promise the prospect will not use it as a sales pitch back at them. The referee isn't a lead-gen asset and I say so out loud.
The call is scheduled for twenty minutes, at the referee's convenience, and I am not on it. That last part is the whole point. A reference call with the consultant listening is a performance. A reference call without them is a conversation.
The briefing note
One page, sent to both parties a day ahead. Mine has four headings:
What the buyer is weighing up. Two or three lines. No jargon, no flattery. "They're choosing between a managed service and a project team, and they're worried their internal team doesn't have the bandwidth to absorb either."
What I'd find useful for them to hear. Specific and honest. "How the first three weeks actually ran. What surprised you. How we handled the bit where the data didn't exist."
What they don't need to cover. Explicit permission to skip the commercial detail, the internal politics, and anything under NDA.
The ask. "Fifteen minutes, no preparation needed, and no follow-up from them afterwards unless they want it."
That note does most of the work. It stops the call turning into an aimless catch-up and stops the referee feeling ambushed by questions about things they can't discuss.
What I ask the referee to cover
Not "was he good?". Nobody answers that honestly and nobody believes the answer anyway. I ask for three things instead:
- The shape of the work, in their words. What they asked for versus what they actually needed, and how far apart those two things turned out to be.
- The worst week. Every project has one. How it was handled tells a buyer more than any smooth testimonial ever will.
- What they'd do differently. This is the one that lands hardest, because it costs the referee nothing to be honest and costs me nothing to hear.
I'd rather a prospect hear one real caveat than a wall of praise. A referee who says "the first fortnight was scrappy, we should have given him access to the systems sooner" is more persuasive than one who says everything was marvellous, because the buyer has been doing this long enough to know that nothing is.
When the reference is lukewarm
Sometimes you ask and the answer is careful. "I'll do it if it's helpful" is not the same as "yes, definitely". When I hear that, I don't push the call onto a prospect. Two options instead:
Use it as my own feedback loop. A half-hearted reference is data. Ask the referee, directly, what they'd want to see from me next time. Then fix it.
Offer a different referee, or none. If the best available voice is a seven-out-of-ten, I'll say so: "I've got someone who can speak to the sector, though the engagement was shorter than this one. Alternatively I'll skip the reference and you can lean on the written case study." Being the first person to lower expectations is oddly reassuring to a buyer.
What I never do is coach the referee toward a better answer. The moment you've scripted the call, you've turned a reference into a testimonial, and the whole value evaporates.
Why it beats another deck
A deck is me talking about myself, edited by me, in an order I chose. A reference call is somebody else answering a question I didn't get to draft. That asymmetry is the product.
It also does something practical for the buyer's own risk position. In a lot of UK organisations — particularly anything touching public money — the person signing off needs a defensible reason for choosing a smaller supplier over a big name. "I spoke to their previous client and it went well" goes in the file. A PDF of pretty slides doesn't.
And there's a quieter benefit. Asking a past client to vouch for me keeps me honest during delivery. You behave differently in month two when you know you might be asked about it in month nine by a stranger in a meeting room in Leeds.
The admin, honestly
It costs me maybe twenty minutes per serious prospect: one email to the referee, one briefing note, one follow-up thank-you. Two of the three people I've referred in the past year have ended up working with me again in some form, which tells you something about what a well-run reference call does for the relationship on both sides.
If you only try one sales habit this quarter, try this one. Bin the deck for a fortnight. See what happens when the buyer hears it from someone who isn't you.