A useful B2B buyer persona is built from real conversations with closed-won and closed-lost deals, not from a marketing team’s best guess at a job title and a stock photo — and it needs to capture the specific trigger that makes someone start looking for a solution, the objections that stall a deal, and the other people who influence the decision, not just a demographic sketch of “Sarah, 38, Marketing Director.” Done properly, personas sharpen everything downstream: who you target on LinkedIn, what you say in outreach, and which objections your sales team prepares for before they come up.


TL;DR:

  • A real persona is built from interviews with actual customers and lost deals, not internal assumptions.
  • Job title alone is a weak targeting signal — the trigger event and job-to-be-done matter more.
  • B2B purchases involve buying committees, not individuals — you need at least a champion and a blocker persona, not just one.
  • Personas should directly shape LinkedIn Sales Navigator filters and message angles, not sit in a slide deck unused.
  • Revisit personas at least twice a year — ICPs drift as your product, market, and win/loss patterns change.
  • The most common mistake is building a persona around who you’d like to sell to, not who’s actually converting.

Table of Contents

What a Buyer Persona Actually Needs to Include

A working persona goes well beyond job title and company size. At minimum it should capture: the trigger event that starts their search (what changed that made this urgent now), their job-to-be-done (the outcome they’re actually hired to deliver, not their title), the objections and hesitations that typically stall the deal, where they go for information and peer validation, and the language they actually use to describe the problem — which is often different from the language your product marketing uses.

Skip the demographic filler that most persona templates default to — age range, hobbies, a stock photo — unless it genuinely changes how you sell to them. For B2B professional services and agencies, the commercially useful details are almost always about the buying context, not the person’s lifestyle.

Researching Personas from Real Data, Not Guesswork

The single biggest quality difference between useful and useless personas is the research method. A persona built in a workshop room from internal assumptions reflects what your team believes about buyers; a persona built from customer interviews reflects what buyers actually think, which are frequently not the same thing.

Aim to interview at least five to eight recent closed-won customers and, just as importantly, several closed-lost or stalled prospects — the lost deals often reveal objections and hesitations your happy customers have already forgotten they once had. Ask specifically about the moment they started looking for a solution, what almost stopped them from buying, and who else was involved in the decision.

Job Titles vs Job-to-Be-Done: A Common Persona Mistake

Targeting by job title alone is one of the most common and costly persona mistakes in B2B lead generation, because the same title can mean wildly different responsibilities and buying power across company sizes and industries — a “Head of Growth” at a 15-person startup and a 500-person scale-up are, functionally, almost different jobs.

A more durable approach is to define the persona around the job-to-be-done — the specific outcome they’re accountable for, such as “hitting a quarterly pipeline number” or “proving marketing’s contribution to revenue” — and then use job title as one filtering signal among several, alongside company size, industry, and behavioural signals like recent hiring or funding activity.

Building Personas Around Buying Committees, Not Individuals

Most meaningful B2B purchases, especially anything above a low four-figure spend, involve more than one person in the decision — a champion who wants the solution, an economic buyer who controls budget, and often a technical or operational stakeholder who needs to be satisfied on implementation risk. Building a single persona and assuming it represents the whole buying process misses the objections and messaging needs of the other roles entirely.

A practical minimum is three personas per ICP: the champion (who initiates and advocates internally), the economic buyer (who approves spend and cares most about ROI and risk), and a blocker or gatekeeper persona (whose default objection needs a specific answer — often around implementation effort, data security, or switching cost). Map how these three interact in a typical deal, since your outreach and content need to speak to whichever one you’re actually engaging at each stage.

Using Personas to Sharpen LinkedIn Targeting

Personas are only useful if they change what you actually do, and the most direct application is Sales Navigator targeting. Translate each persona’s job-to-be-done and trigger events into concrete filters: seniority level and function rather than exact title, company headcount and growth signals that correlate with the trigger event, and, where available, technology or hiring signals that indicate the underlying need exists right now.

This is also where persona research pays off in message relevance — knowing the specific trigger event and job-to-be-done lets you write an opening line that names the actual problem rather than a generic value proposition, which is consistently the biggest lever on cold outreach response rates.

Turning Personas Into Messaging That Converts

The language captured during persona interviews — the actual words buyers use to describe their problem — should show up directly in your outreach messaging, because it signals immediate relevance in a way that internal product terminology rarely does. If prospects describe their problem as “our pipeline dries up every quarter” rather than “inconsistent lead generation,” the former phrase in your opening line will land better because it mirrors how they actually think about the issue.

This is a genuinely underused technique: pull direct quotes from persona interviews (with permission, anonymised where needed) and test them as opening lines or subject lines in outreach. Messaging that mirrors a prospect’s own language consistently outperforms messaging built around how your team internally describes the problem — a small change that agencies running done-for-you outreach, including The Lead Lab, build into message testing as a matter of course, because it’s one of the highest-leverage, lowest-cost improvements available.

Keeping Personas Current as Your ICP Evolves

Personas built once and never revisited quietly go stale as your product, pricing, and win patterns evolve — the persona that fit your ICP a year ago may no longer reflect who’s actually converting today, especially after a pricing change, a new product line, or a shift in which segment is growing fastest.

Set a recurring cadence — every six months is a reasonable minimum — to revisit personas against your actual closed-won data from that period: has the average company size shifted, has a new job title started showing up repeatedly as the champion, has a previously common objection stopped appearing? Treat this as a standing agenda item in a sales and marketing alignment meeting rather than a one-off project.

Common Persona Mistakes That Waste Pipeline

The most damaging mistake is building a persona around who you’d like to sell to — a bigger, more prestigious logo — rather than who’s actually converting and getting value from your product today. Aspirational personas feel motivating but consistently misdirect outreach effort toward accounts with a lower realistic close rate.

A close second is treating a persona as a one-time document rather than a living reference that shapes weekly targeting decisions — a beautifully designed persona slide that nobody consults when actually building a Sales Navigator list has produced nothing of value. The test of a good persona isn’t how thorough it looks in a deck; it’s whether it changed who your team targeted this week.

Leave a Reply

Your email address will not be published. Required fields are marked *