How to write a referral blurb people can actually send

Most consultants don't have a referral problem. They have a referral language problem. Their past clients would happily make introductions. Their network wants to be helpful. The gap is that nobody has a sentence that's easy to send.

A referral blurb isn't your biography. It isn't your positioning statement compressed into one paragraph. It is copy written for the person doing the referring — something specific enough that they can paste it into a message and feel confident it will land.

Why referrals stall at the writing step

When a referrer has to write something from scratch, most of them don't. The intention to introduce you is real. The execution doesn't happen because writing a good intro for someone else is work, and most people's mental model of your consulting is either too vague to summarize or too complicated to translate quickly.

This is not a failure of relationship. It is a failure of asset. The referral blurb is an asset, and right now most consultants don't have one. They rely on their LinkedIn profile — which is usually too long, too backward-looking, and not written for a referral context — or they trust that the connector will improvise something good.

Improvised referrals tend to say: "You should meet [name], she does really interesting consulting work on strategy and operations." That sentence gets a "sounds cool" reply and nothing else. It doesn't answer "why now?" and it doesn't give the recipient a clear reason to respond.

The structure of a blurb that actually gets forwarded

A good referral blurb has three pieces. It doesn't need more. Adding more makes it sound like a pitch deck.

• The situation: What is happening in a business right now that makes your work relevant? Not "what you do" in general — the specific trigger moment that should make someone's ears perk up. This is how the connector recognizes when to make the intro.
• The problem you solve: Stated plainly, in terms of what the buyer feels, not what the work looks like on paper. "When a team has grown faster than its management structure can hold" lands better than "organizational design and change management consulting."
• The short proof signal: One line that makes the claim credible without requiring the reader to know your full history. A past company type, a repeated pattern, a role you've played — something concrete, not a credential list.

Optionally: a light social proof note. If you have a real line a past client said that captures the value — not a manufactured testimonial, a real thing a real person said — one sentence of that is worth adding. It lowers the connector's risk of looking bad for making the intro.

What makes a blurb easy to forward versus hard to use

Easy to forward:

• Short enough to paste into a Slack message or email without editing
• Answers "when to bring her in" — the buying moment is clear
• Doesn't require the recipient to already know what "fractional COO" or "revenue operations" means
• Has a clear implied next step (usually: a 30-minute intro call)

Hard to use:

• Describes credentials in sequence: "After 15 years at Fortune 500 companies, she now helps…"
• Uses undefined category terms: "strategic advisor," "transformation consultant," "growth expert"
• Is more than 4–5 sentences (connectors will not edit your copy before forwarding it)
• Focuses on your range of capabilities rather than the specific problem you solve

The version for different referral contexts

You likely need two versions, not one. They cover different contexts:

The connector blurb — written for someone who knows you but isn't deep in your work. This is what your former colleagues, clients, and network contacts use to introduce you to people they know. It should be simple, situation-based, and short. The connector needs to feel confident it won't embarrass them.

The direct outreach version — written for you to use when someone asks "can you send me something I can share?" or when you need to introduce yourself in a cold or warm context. This one can be slightly longer and can include more proof, but it still shouldn't read like a capabilities summary.

A note on timing: why "why now" matters in the blurb

The most underused element in referral language is timing. Connectors need to know not just what you do but when someone needs you. Without that, even interested connectors don't know when to bring up your name in a conversation.

Compare: "She does revenue strategy consulting" versus "She's the person to call when a founder realizes their sales process isn't built for the buyer they're now selling to." The second gives the connector a trigger. They hear a conversation that sounds like that moment, and your name comes up naturally.

That trigger is the most valuable part of your referral language. Most consultants skip it because they don't want to be too narrow. But narrow triggers get used. Broad descriptions get forgotten.

Building your referral blurb from the right inputs

The best referral blurb comes out of your actual proof — the patterns you've seen across engagements, the moments you've been brought in, the specific problem types where you've been useful more than once. It is not invented from scratch; it is extracted from what you already know about your own work.

That's exactly what the Builder does. It walks you through extracting the inputs — the situations, the proof signals, the outcomes — and then helps you assemble them into referral-ready language that someone can actually use.