Open most B2B SaaS personas and you'll find the same document: a name, a stock photo, a made-up job title, and a paragraph about what she does on a typical Tuesday — a list of hobbies, a commute, maybe two kids and a nanny who may or may not show up.
That's a day-in-the-life consumer persona. It's built for someone deciding, on her own, whether to buy a subscription box or a pair of shoes.
It's the wrong template for someone deciding whether their company should sign a $40K SaaS contract.
The one difference that changes everything
In B2C, one person decides and one person pays, usually with their own money. That's why the emotional, personal detail in a consumer persona works — it's describing one person's actual life, and one person's actual decision.
In B2B, almost nobody is spending their own money. Forrester found that an average B2B buying process pulls in 13 internal stakeholders, plus another nine people quietly influencing them from the sidelines. The person who feels the pain your product solves is often a completely different person from the one who signs the contract, who is often a different person again from the people that signer has to go convince internally.
A persona modeled on one consumer, with one set of feelings and one bank account, was never built to describe that.
Where the B2C template ends up
Stijn Hendrikse, who spent the first half of his career at Microsoft before founding and advising smaller software companies, calls this the "decoration version of a persona." It gets a beautiful name and a beautiful photo. It gets printed out and taped to a conference room wall, where everyone nods at it once and never opens the underlying doc again.
None of this means the emotional detail in a B2C persona is worthless. Understanding what someone worries about, what makes them feel like a hero at work, still matters in B2B. It's just not the first thing a B2B persona needs — and on its own, it can't tell you who actually signs, who actually blocks, or who you don't even know exists yet.
Five things to build instead
A working B2B persona replaces the stock photo and the hobby list with:
- Buyer voice. Not your marketing team's paraphrase of what a customer wants — the actual words. Pull them from recorded sales calls, support tickets, and CRM notes. If a prospect described their problem in a specific phrase on a call last month, that phrase belongs in your content this month. It's how a prospect starts to feel like you're part of their tribe instead of a vendor reciting features at them.
- Dollarized pain. Not "this is frustrating," but a number. What does the problem cost if nobody fixes it? How often does it happen? What's the specific behavior you can point to? If you can't put a number on the pain, it isn't defined well enough yet.
- A one-sentence job-to-be-done. When [situation], I want to [do this], so that I can [achieve this outcome]. One sentence. If you can't write it in one sentence, you don't understand the job yet.
- A trigger. The specific event that moves someone from "this is a nice-to-have someday" to "I am actively looking for a solution right now." Without a trigger, you're marketing to everyone who could theoretically buy, instead of the people actually in-market this quarter.
- A validation test. Hand your persona criteria to an SDR and ask them to build a prospect list from it, with no other input. If their list looks nothing like the list you had in mind, your persona isn't precise enough to be useful yet.
The upside: you already have what you need
Every SaaS company is worried that AI is making differentiation harder — that everyone's content is starting to sound the same because everyone's using the same tools to write it. That's a real risk. But it also means the one thing you have that nobody else can copy is your own conversations with your own customers. The sales calls. The support tickets. The CRM notes. That's the raw material for a persona nobody else has access to.
Watch the full recording of the webinar below to see this framework mapped out live, including the tool Kalungi uses internally to build it.