How many personas do we need?

Most companies need 3-5. Too few (1-2) misses the buying committee. Too many (>7) creates paralysis — reps can't remember which persona to target. Start with 3, add as the segmentation genuinely diverges.

Who owns personas — Marketing or Sales?

Product Marketing typically owns them. Sales validates them (reps see the buyers daily). Marketing consumes them for content and campaigns. Personas owned by nobody in particular go stale in months.

Do personas apply to product design?

Yes but differently. Product personas (user segments) focus on jobs-to-be-done and workflow, not sales objections. Some companies use one persona set for both; others maintain distinct product and sales personas. Both patterns work if the ownership is clear.

Buyer Persona: Building Personas Reps Actually Use

A buyer persona describes the human being on the other end of your sales cycle — their role, priorities, pain, and the objections they raise.

Buyer Persona: The Sales-Useful Version, Not the Marketing-Deck Version

A buyer persona is a documented description of a specific type of person who buys your product — their job title, seniority, day-to-day priorities, the pain your product solves for them, the alternatives they consider, and the objections they raise in the sales cycle. Done well, personas drive real changes to messaging, discovery questions, and objection handling. Done poorly — as a design exercise producing a poster with a stock-photo face — they become the artifact everyone references but nobody uses.

The difference between ICP and persona

ICP (Ideal Customer Profile) describes the company you sell to — industry, size, tech stack, geography. Persona describes the person at that company who signs, uses, or blocks the deal. A company can be ICP-fit but have no persona in the room; a persona can exist at non-ICP companies. Both matter. Confusing them is why some GTM strategies target the right companies but pitch the wrong person.

The three-persona minimum

Most B2B deals involve three archetypes: (1) Economic Buyer — signs the contract, cares about ROI and risk. (2) Champion/User — day-to-day user, cares about workflow and features, will advocate internally. (3) Blocker — Security, IT, Procurement, Legal — cares about compliance, integration, cost. Effective persona documentation covers all three; documenting only the champion is why sales cycles get ambushed by security review or procurement pushback.

What actually belongs in a persona

Useful fields: job title and seniority range, primary business metrics they're measured on, top 3 pains you solve, top 3 objections they raise, tools they currently use, publications/communities they follow, quote from a real customer in that role. Not useful: fake names, stock photos, invented backstories, favorite coffee orders. If a field wouldn't change a rep's sales conversation, it doesn't belong on the persona.

Persona-driven artifacts

A persona becomes real when it drives specific artifacts: (a) discovery questions tailored to that persona's likely pain, (b) demo scripts emphasizing the workflows they care about, (c) objection-handling docs anticipating the pushback they typically raise, (d) content marketing pieces speaking directly to their job. Without these downstream artifacts, personas are inert.

How to build them

Skip the whiteboard-brainstorming version. Interview 8-15 real people per persona — half customers, half sales-lost prospects. Ask about their day, their goals, what triggered their evaluation, who else was involved, what almost killed the deal. Synthesize patterns, not individuals. Update personas annually or when a segment shifts materially. Personas from 3 years ago describing a market that's since changed are worse than none.

Frequently asked questions

How many personas do we need?: Most companies need 3-5. Too few (1-2) misses the buying committee. Too many (>7) creates paralysis — reps can't remember which persona to target. Start with 3, add as the segmentation genuinely diverges.
Who owns personas — Marketing or Sales?: Product Marketing typically owns them. Sales validates them (reps see the buyers daily). Marketing consumes them for content and campaigns. Personas owned by nobody in particular go stale in months.
Do personas apply to product design?: Yes but differently. Product personas (user segments) focus on jobs-to-be-done and workflow, not sales objections. Some companies use one persona set for both; others maintain distinct product and sales personas. Both patterns work if the ownership is clear.