Buyer persona template
Describe who brings a problem forward, who can approve the purchase, and who can stop it. Those roles may belong to three different people.
A buyer persona for the decision you need to understand
Use this template to understand the people involved in a purchase: the sponsor, approver and blocker may be different people. Record the role you need to check, rather than assuming one title makes every decision.
If your next decision is about how someone uses the product, use the user persona template instead. Company fit belongs in an ideal customer profile.
See the user persona templateEight blocks for a buying decision
Fill what you know, mark what you assume, and leave unknown details unknown.
| Block | What goes in it |
|---|---|
| Who signs | Who brings the problem forward, who approves the purchase, and who can stop it. Do not assume these are the same person. |
| What they are measured on | The outcome they are accountable for, with a source if you have one. |
| Trigger event | An event that may start a search for a new process. Record whether it actually happened. |
| Budget form | Card, team budget or purchase order, if known. Leave the amount unknown until you can check it. |
| Where they read | Where they found or shortlisted their current tool. A guessed channel is not a targeting fact. |
| Three objections | Reasons that could stop a purchase. Separate reported objections from sample concerns. |
| Who else is in the room | Other users, reviewers and approvers involved in the last purchase. |
| Do not contact | Who is outside this draft target, and what evidence would change that exclusion. |
Each block is a working statement, not evidence of purchase intent.
The template, as plain text
Paste it into a doc, or into your CRM as a note field. It is short enough to finish.
Free to copy, edit and download. No account or email is required. The blank template includes an evidence note; the filled example below is fictional.
BUYER — a role label 1. Who signs sponsor: ___ / approver: ___ / blocker: ___ 2. Measured on the outcome they are accountable for 3. Trigger event what changed, and whether it happened 4. Budget form card / team budget / purchase order / unknown 5. Where they read where they found or shortlisted a tool 6. Three objections 1) ___ 2) ___ 3) ___ (source or assumed) 7. Also in the room other users, reviewers and approvers 8. Do not contact who is outside the draft target, and why
Start with three fields you can use for a decision, and attach an evidence note to at least one assumption.
A worked B2B buyer persona example
Illustrative example: not a real customer, interview or generated report.
StockBridge is a fictional inventory tool for brands selling from more than one warehouse. The profile below shows how to fill in the template. Every detail remains an assumption until you check it.
| Block | Draft for this example | What would confirm or change it? |
|---|---|---|
| Who signs | An operations manager may sponsor the purchase; finance may approve it. Neither role is confirmed. | Ask who approved the last inventory-software purchase. |
| What they are measured on | Avoiding oversold orders during promotions is a proposed priority. | Ask for the last incident and how the team tracked its impact. |
| Trigger event | Opening another warehouse may expose gaps in the current stock spreadsheet. | Ask what changed before the team started looking for a new process. |
| Budget form | Unknown. Do not invent a monthly budget. | Ask whether the last purchase used a card, team budget or purchase order. |
| Where they read | Unknown. Do not treat a guessed newsletter as a targeting fact. | Ask how they found and shortlisted their current tool. |
| Three objections | Possible objections: migration interrupts orders; warehouse staff need training; another subscription needs approval. These are sample concerns, not quotations. | Ask what nearly stopped the previous purchase and record their own words with permission. |
| Who else is in the room | A warehouse lead may judge setup; finance may judge cost. | Ask whose approval or review was needed before signing. |
| Do not contact | For this scenario, a single-warehouse team with no stock-sync problem is outside the draft target. | Check whether that exclusion wrongly removes a customer with a similar problem. |
Keep the evidence beside the profile
Copy this note under any field you plan to use in an email. A believable story is still a story when its source is missing.
Field: Current statement: Status: assumed / reported by a participant / checked against an artifact Source and date: Contradicting detail: Question or check to run next: Decision changed: keep / revise / stop using this statement
For the example’s trigger, the status is assumed and the source is this illustrative scenario. There is no interview count, buyer quote or observed willingness to pay behind it.
Before you use the profile in outreach
Choose one statement you can check with an existing customer, a permitted contact record or a conversation. If you cannot confirm the trigger, write an exploratory question rather than asserting that the person has the problem. A role or company match does not establish purchase intent.
Prepare questions for a real buyer conversationThree passes
The same discipline as the product-side template: specific beats complete.
Start with what you know
Use a past deal if you have one. Otherwise label the first draft as assumed; do not invent a customer history.
Write the objections in their words
Record the actual objection with permission. Mark a paraphrase as a paraphrase, and a sample concern as assumed.
Add who it is not for
Name who is outside your draft target, then check whether the exclusion removes people with the same problem.
A first draft can be useful before it is verified, as long as the assumptions stay visible.
Buyer persona or user persona?
A buyer persona describes purchase roles and decisions. A user persona describes the task someone needs to finish inside the product. One person may hold both roles.
Choose the document by the next decision: buying roles here, usage tasks in the user template, company selection in an ICP.
Start with a draft, then check it
Describe what you sell in the free ICP and persona generator. Treat the output as research hypotheses, then replace assumptions with evidence you can name.
The public generator is a starting point for hypotheses. Full reports and real-contact matching are separate signed-in steps; check availability and limits in your account.