Buyer Persona Template
A detailed buyer persona template covering demographics, goals, frustrations, buying behavior, tools, and messaging — built for product managers and marketers. Free to copy, download, and use. No signup required.
# Buyer Persona **Persona Name:** [Give them a memorable name, e.g. "Startup Sarah"] **Created:** [Date] **Based on:** [N customer interviews / survey of N respondents / assumption — mark clearly] --- ## At a Glance > *"[A memorable quote that captures their mindset — use a real customer quote if you have one]"* | | | |---|---| | **Job Title** | [e.g. Head of Product, Senior PM, Founder] | | **Industry** | [e.g. B2B SaaS, Fintech, E-commerce] | | **Company Size** | [e.g. Series A startup, 50–200 employees] | | **Location** | [City/Country or remote] | | **Reports To** | [e.g. VP Product, CEO] | | **Team Size** | [e.g. manages 3 engineers + 1 designer] | --- ## Demographics - **Age range:** [e.g. 28–38] - **Education:** [e.g. B.Tech from IIT, MBA from ISB — or "varies"] - **Years of experience:** [e.g. 4–7 years in product] - **Tech savviness:** Low / Medium / High --- ## Goals 1. **[Primary goal]** — [Why this goal matters to them] 2. **[Secondary goal]** — [Why this goal matters to them] 3. **[Personal goal]** — [Career growth, recognition, reducing stress] --- ## Frustrations & Pain Points 1. **[Pain point]** — [What causes this and how frequently it happens] 2. **[Pain point]** — [What causes this and how frequently it happens] 3. **[Pain point]** — [What causes this and how frequently it happens] --- ## A Day in Their Life [2–4 sentences describing a typical workday: what they do in the morning, what meetings they attend, where they feel friction, how they end the day. Make it concrete.] --- ## How They Make Buying Decisions - **Discovers tools via:** [e.g. peer recommendations, Twitter/X, LinkedIn, Google search] - **Evaluation process:** [e.g. signs up for trial, loops in manager, compares 2–3 options] - **Decision drivers:** [e.g. integrations with existing stack, security, time-to-value] - **Blockers to buying:** [e.g. needs IT approval, budget frozen, switching costs] - **Champion vs. buyer:** [e.g. they champion the tool but manager signs the contract] --- ## Tools They Use | Category | Current Tools | |---|---| | Product management | [e.g. Jira, Linear, Notion] | | Communication | [e.g. Slack, email, Zoom] | | Analytics | [e.g. Mixpanel, Amplitude, GA4] | | Documentation | [e.g. Confluence, Notion, Google Docs] | | Design collaboration | [e.g. Figma, Miro] | --- ## How Our Product Wins Them Over 1. **[Value proposition 1]** — [Why this resonates specifically with this persona] 2. **[Value proposition 2]** — [Why this resonates specifically with this persona] 3. **[Value proposition 3]** — [Why this resonates specifically with this persona] --- ## What They Say vs. What They Mean | What they say | What they actually mean | |---|---| | "We need more features" | "The current features don't solve my real workflow" | | "It's too expensive" | "I don't see enough value for the price" | | "[Their objection]" | "[Underlying concern]" | --- ## Messaging That Resonates - **Headline:** [One-line message that speaks to their primary goal] - **Pain to lead with:** [The frustration you should open with] - **Proof they need:** [Case study type, metric, or social proof that converts them] - **Channel to reach them:** [Where they consume content]
How to use this Persona template
Ground it in real interviews
A persona built from 5+ customer interviews is 10x more useful than one built from assumptions. Mark any section that's assumed vs. validated so your team knows where to be cautious.
Fill the quote first
The 'At a Glance' quote anchors the whole persona. If you don't have a real quote, use one that sounds like something a real customer would say — it makes the persona feel human.
One persona per user type
Don't blend two different users into one persona to save time. If your SMB buyer and your enterprise buyer have fundamentally different goals, create two separate personas. Blended personas lead to blended product decisions.
Share it widely
A persona that lives only in the PM's Notion is worthless. Present it in an all-hands, paste it in your team Slack, and reference it explicitly when making product decisions.
Want a Persona grounded in your actual customer data?
PMRead ingests your customer interviews, feedback, and Slack threads — and generates PRDs backed by real evidence, not guesses.
Frequently asked questions
How many buyer personas should a product have?
2–4 personas covers most B2B products. One primary (your ICP), one or two secondary, and an optional anti-persona (who you're not building for). More than 4 usually signals unclear positioning rather than genuine user diversity.
What's the difference between a buyer persona and a user persona?
A buyer persona describes who makes the purchase decision — their goals, objections, and buying journey. A user persona describes who uses the product day-to-day. In B2C they're often the same person. In B2B they're often different: the buyer might be a VP of Engineering while the user is a developer.
How often should personas be updated?
Review personas at least once a year, or after any significant customer discovery sprint. Early-stage companies often discover their ICP is different from their original assumptions within 6 months. A stale persona is worse than no persona.
What data sources work best for building personas?
In priority order: customer interviews (most valuable), sales call recordings, support ticket themes, survey data, CRM data. Analytics can tell you what users do but not why they do it — pair quantitative data with qualitative interviews for the most useful personas.
Other free templates