Buyer persona development for B2B PMMs: how to build profiles that actually drive decisions

Most buyer personas describe a person. Almost none of them describe a decision.

Here's the one nearly every B2B team has on file. Director of operations, 35 to 50, reports to the COO, mid-market company, uses Salesforce, reads LinkedIn, wants to reduce manual work.

Every line of that is probably accurate. None of it tells us what to write.

The paperwork persona

It reads like the packet HR hands us on the first morning. Address, emergency contact, direct deposit, T-shirt size, a policy acknowledgment nobody opens.

Forty minutes of correct information about a human being, and not one field that has anything to do with how they'll do the job.

Call that a paperwork persona. Verified, filed, quoted in briefs, and silent on the only question worth asking. What would make this buyer stop?

We build them because they're easy. A workshop, a whiteboard, a few customers we half remember, and by lunch there's a deck.

It sounds authoritative because it's organized. Organized guessing is still guessing.

Two related habits do the same damage. We fold the buyer and the user into one profile, when the person signing the contract and the person living in the product are answering completely different questions. And we write the thing once, then leave it alone while the market moves underneath it.

Companies, then people

A quick distinction, because teams blur it constantly.

Ideal customer profile work is about companies. Size, stack, behavior, which accounts deserve our attention.

Persona work is about the people inside those accounts and how they decide.

Do only the first and we aim the wrong words at the right companies. Do only the second and we write lovely messaging for buyers who were never going to qualify.

The shape of a decision

A persona that changes our work answers five things. Demographics aren't one of them.

Start with the trigger. Nobody wakes up wanting to evaluate software, so something happens first. A new VP arrives with a mandate, a system falls over during the busiest week of the year, a board asks a question nobody has a good answer to, a competitor announcement lands in an exec's inbox.

The trigger tells us when this buyer is reachable, and what they type into a search bar when they go looking.

Then the job. What they've been hired to accomplish, and what they're hiring a product to help with.

A support director shopping for a ticketing platform wants the repeat questions to stop, so her team can survive the holiday spike without adding headcount. Lead with that and the message connects.

Then the internal obstacle. What stops this buyer even when they want to move.

A skeptical finance lead. A security review that adds five weeks.

The external constraint is a different animal. It's what the buyer can't change. Fiscal-year budget cycles, contracts already signed, compliance requirements, a hiring freeze that showed up with the new quarter.

No amount of objection handling moves a budget cycle.

Last, the success definition. What a win looks like to this person, past the product working.

Economic buyers need something they can report upward. Champions usually need something more personal. Fewer hours in spreadsheets, or a tool that doesn't embarrass them in front of their own team.

Questions that get answers

Interview data is harder to argue with than a whiteboard.

Forty-five minutes with a real buyer about a real purchase. Not a pitch, not a survey. Eight to twelve conversations per persona before we go looking for patterns, because below that we're pattern-matching on noise.

Talk to buyers who just chose us, buyers who chose somebody else, and customers who left. That last group is the most uncomfortable and the most useful, because that's where the obstacles live. Personas built only from won deals describe our happiest customers and stay quiet about everyone we're losing.

Four questions do most of the work.

"Walk me through what was happening right before you started looking. What changed?"

"What were you actually trying to accomplish, in your role, at that point?"

"Was there a moment this could have fallen apart internally? What happened?"

"How would you describe the problem to a colleague who wasn't involved?"

That last one is the money question. The phrase a buyer reaches for without thinking is almost always better headline copy than anything we'd invent, which is the whole premise of voice of customer research.

The report kicked back twice

But the answers that change our work most aren't about us at all.

Think about the expense report. A client dinner, clearly inside policy, submitted Monday.

Wednesday it comes back because the cost center is wrong. Fixed and resubmitted, and it comes back a second time because the itemized receipt is missing and the card slip won't do.

Three weeks to get reimbursed for a meal nobody ever disputed. None of that delay was disagreement. It was a process nobody had written down, discovered one rejection at a time.

Most stalled deals are exactly that. The buyer wants it, and the buyer said yes out loud.

Then the yes has to survive a security questionnaire, a finance review, a legal redline, and a vendor policy older than anyone in the room.

So the useful part of a persona is the part that maps the kickbacks. Where does the yes go next, who can send it back, and what do they need to see so it doesn't come back again. Win/loss interviews surface this better than anything else we run, because a lost deal remembers every rejection in order.

It also reframes the committee. Think of the economic buyer, the technical evaluator, the champion and procurement as four places a yes can get sent back.

A marketer who knows which one is holding the form can tell a rep exactly what to send, and that's sales enablement built on something real instead of on adjectives.

Where personas earn out

Then the messaging decisions stop being matters of taste.

Which outcome leads on the homepage depends on who lands there first. Which customer story sits on which page depends on the kind of win that reader has to justify.

The objections sales needs answers to come straight off the obstacle map. When the same one keeps coming back, that answer has to exist as something a rep can send in a single click.

Map the profiles against the content library and the gap is usually identical everywhere. Plenty written for the people who use the product. Almost nothing for the person who has to approve it.

That's where this meets the messaging house, which decides what variations of the core message exist and who each one belongs to.

It's also most of what people mean by GTM alignment. Product, marketing and sales have to agree on how the buyer decides. Everything after that is vocabulary.

A persona that can't tell us where a yes gets sent back is paperwork.

Go find the second rejection.

---

About the author

Bare Strategy is a product marketing consultancy that helps B2B SaaS companies build the research, messaging, and go-to-market infrastructure that drives growth. Our work spans the full PMM discipline, from persona development and competitive intelligence to launch strategy and sales enablement.

If your team is building buyer personas from scratch or fixing ones that aren't driving decisions, we can run the research and build the framework. See how we work.

---