Buyer persona

What is a buyer persona?

A buyer persona is a documented profile of a specific stakeholder type inside your ideal customer profile — the individual on the buying committee, not the company. Each persona captures role and title, what they care about (priorities), what they're trying to fix (pains), how their success is measured (KPIs), what tools they already use, what objections they raise, and what would have to be true for them to back the purchase.

Personas exist because B2B buying is committee buying. A modern enterprise SaaS decision involves 6–10 stakeholders across functions — CFO, VP Sales, VP Engineering, Director of RevOps, Procurement, Security, sometimes Legal. Each cares about different outcomes, hears the value prop in different language, and raises different objections. One generic message to 'sales leaders' lands with no one. A persona-tuned message to the CRO about pipeline visibility lands; a different message to the VP of RevOps about CRM data hygiene lands; both are needed to close the same deal.

Personas are not buyer demographics. 'Female, 35–55, urban' is a demographic. 'VP of RevOps at a Series C SaaS company who owns CRM hygiene and is measured on forecast accuracy' is a persona. The persona has a job, a problem, and a decision-making role — the demographic does not.

What goes into a real buyer persona

1. Role and title. Specific function and seniority. 'VP of Sales' is specific; 'sales leader' is not.

2. Committee role. Economic Buyer, Champion, Technical Buyer, User Buyer, Detractor. Each has a different conversion path.

3. Top three priorities. What this person is being measured on this quarter — in their own language, not yours.

4. Top three pains. What's actively broken or annoying enough to make them take a meeting.

5. Success metrics. The numbers their boss looks at. If you can move one of those numbers, you have a deal.

6. Common objections. The five or six things this persona consistently pushes back on — pricing, security, change management, integration, vendor consolidation.

7. Preferred channels and content. Where this persona consumes information — LinkedIn, podcasts, peer communities, specific publications.

8. Watering holes. The Slack groups, conferences, and online communities where this persona actually engages.

How to build personas from real buyers

1. Pick the top 3–5 stakeholder types your deals consistently involve. Don't try to build 12 personas — start with the 3 that show up in 80% of deals.

2. Interview 5 buyers per persona. Real customers who closed, not target buyers in your TAM. Ask: what made you take the first meeting, what convinced you we were the right fit, what almost killed the deal, what would have made you walk away.

3. Pull win/loss patterns by persona role. Which persona type kills deals when they don't engage? Which one drives the deal when they do? That's your Champion vs Detractor map.

4. Document each persona on one page. Role, committee role, three priorities, three pains, success metrics, top objections, preferred channels, watering holes. One page each — anything longer doesn't get used.

5. Tune outreach, discovery, and demos to each persona. The CRO gets a pipeline-velocity message; the VP RevOps gets a CRM-hygiene message; both lead to the same product. The framing is what changes.

Persona vs ICP — and how they fit together

ICP defines the company. Persona defines the individual. A single deal has one ICP fit and 3–6 personas to engage. ICP determines whether to pursue the account at all; personas determine how to multi-thread once you're in.

A common mistake is building personas without an ICP. The result is generic personas that map to no specific company type — 'a VP of Sales' becomes a stereotype rather than a real role at a specific company stage. Real personas are always anchored to ICP: 'the VP of Sales at a Series B B2B SaaS company with 30 reps' is a useful persona; 'the VP of Sales' is a stock photo with a title.

Common persona mistakes

1. Persona built from imagination, not interviews. The persona that comes out of a marketing offsite reflects what the team wishes were true. The persona that comes out of 20 customer calls reflects what is true.

2. Too many personas. 12 personas means none get used. Start with 3 and add more only when a real deal pattern justifies one.

3. Personas that read like demographic descriptions. 'Female, 35–55, urban, college-educated' is not a persona — it has no job, no decision role, and no relevance to a B2B deal.

4. Personas that live in marketing decks but not in sales conversations. If the rep doesn't know which persona they're talking to mid-call and tune the framing accordingly, the persona work was theatre. Personas have to live in the discovery framework and the call prep brief, not just the marketing strategy slide.

How Gangly uses buyer personas

Gangly's Outreach Writer auto-tunes cold messaging per persona — the same value prop framed for CRO vs VP RevOps vs VP Engineering pulls different pains and different success metrics into each draft. The rep doesn't have to manually rewrite messaging per stakeholder; the system handles it from the persona library.

Call Prep Engine pulls persona-specific discovery questions, common objections, and likely success metrics into the brief before every meeting. Live Call Coach watches the call and flags when the conversation drifts from the persona's stated priorities. The persona work that historically lived in a strategy deck becomes the rep's per-call playbook.

See how Outreach Writer works →

Frequently asked questions