How to Create a Customer Persona for B2B SaaS (With Template and Example)

Long before Anthropic's Claude became every knowledge worker's trusty consigliere, generations of marketers took their counsel from another Claude. His surname was Hopkins, and in 1923 this legendary ad man wrote a marketing manual our trade has treated as scripture ever since.

On page 71 of Scientific Advertising, Hopkins has you picture one passenger on an overnight sleeper train who swears by a rival brand of soap. What could you say to the man, he asks, to make him switch to your client's brand of soap?

Then he writes down one of the most fundamental rules in marketing:

Since then, no marketer worth their salt, whether selling soap bars, sports cars, or B2B SaaS, has started a campaign without pinning down their customer persona first.

Today, the customer persona is a document a whole team works from, the brief behind the copywriter's brief, the media buyer's targeting and the sales rep's script.

What has changed is how fast you can pin one down. With AI, a week's worth of customer persona research now takes minutes.

Ask a research agent about your buyer and it comes back with a long, confident report: market sizes, industry trends, a day in the life of a controller. Most of it reads like insight. Little of it will ever reach a landing page, an ad or a sales call.

So the hard part has moved from finding information to choosing it. That is why we built the WeGrowth customer persona template backwards, starting from what the customer persona has to feed: your customer journey, your messaging, your ad targeting and your offer. Each field asks a question one of those needs answered, and a fact that answers none of them stays out.

To create a customer persona:

1. Download the free WeGrowth customer persona template.
2. Fill in the nine buyer sections from your calls, tickets and CRM, or from your best guess if you have no customers yet.
3. Build your offer in the remaining seven sections.
4. Where you are torn between two answers, settle it with buyer interviews and your first campaigns.
5. Revise the customer persona as new evidence comes in.

This guide walks through every section of the WeGrowth template, using one fictional B2B SaaS buyer as a running example.

Describe the Buyer in the Template's First Nine Sections

The WeGrowth customer persona template is a Google Sheet with sixteen sections. The first nine describe the buyer and their company. The last seven describe your offer, written for that buyer.

AI takes much of the labor out of filling it in. It can transcribe and summarize your sales calls, pull the phrases buyers repeat across hundreds of tickets, sort competitor reviews into pros and cons, and draft each row of the sheet from what you give it.

On its own, though, it knows only what the internet knows about your buyer, and your competitors can ask it the same question. Build from that alone, and you end up saying what they say, to the same buyer.

Your own records hold what the internet does not: the calls, the tickets, the deals you won and lost. They show why buyers picked you or walked away, in their own words, and that is where your points of difference come from.

A SaaS company under a few million in ARR rarely has a research team, but once it has customers, it has a record of its conversations with them. Fill the sheet from it, and note what each source tends to skew toward.

• Sales call recordings and notes: triggers, objections, who joined the call, and the words buyers use for their problem. They skew toward deals that got as far as a call.
• Closed-lost and churn notes: what buyers tried before, what made them suspicious, and the alternative they picked. Your own team wrote these, so they reflect your side of the deal.
• Support tickets and onboarding answers: current tools, daily routines, and where work gets stuck. They skew toward problems.
• CRM records: company size, job titles, deal length, and who signed.
• Reviews of you and your competitors: outcomes and frustrations in the buyer's own language. They skew toward power users and strong opinions.
• Signup questions: on one WeGrowth engagement with an AI developer tool, a qualification survey in the signup flow collected user roles, primary pain points, and current software stacks.

A startup without customers has none of this yet, so its first customer persona is a best guess. Build it from the founders' own experience of the problem, a few conversations with people in the target role, and whatever the research agent turns up.

Where you are torn between two answers for a row, write both in. You will settle them once the sheet is filled.

The running example is illustrative. The product and the buyer are invented: an accounts-payable automation tool sold to wholesale distributors with 50 to 500 employees, and the financial controller who usually finds it first.

1. Niche

Who is this person at work, and how do they make decisions? The rows cover their title, goal and reporting line, how much budget they control, and how they think: their values, their appetite for risk, and how they like to learn and talk. Your tone of voice and your sales approach start here.

Pull most of this from the CRM and LinkedIn, and keep it short. Nielsen Norman Group notes that demographics "don't provide behavioral or attitudinal data."

A few rows do more work than the rest. Budget Authority tells you whether this person can sign or has to convince someone who can. People in Niche You Know turns the customer persona into a list of real people you can interview. Describe Themselves As captures their words for their own job, which is often the first line of good copy.

2. Company

This is your ICP, written for the company this persona works in. The rows cover industry, region, size and revenue, the team the buyer sits in and the budget it controls, the metrics you improve, and the tools the company runs today. Your account lists and ad targeting run on these rows, and the CRM fills most of them.

Alternative Solutions deserves care: list what the company uses today, including spreadsheets, manual work, and doing nothing. Those are the options your offer has to beat later on the sheet.

Example:

• A North American wholesale distributor with 80 to 300 employees.
• The AP team of two to four clerks sits in finance.
• Alternatives: typing invoices into the ERP by hand, an OCR add-on, or another hire.

3. Digital Footprint

Where does the buyer spend attention online, and what do they type when a problem gets bad enough to search? The rows list their networks, groups, communities and influencers, the searches they run, and the review sites they read, with the pros and cons they find there.

This section drives targeting and channel choices. The search queries and the pros and cons in reviews also give you the buyer's vocabulary. Sales calls surface some of it, and your competitors' reviews fill in the rest.

Example:

• Spends time on LinkedIn and in controller communities.
• Reads review sites before any demo.
• Cons in competitor reviews keep returning to the ERP sync.

4. Voice of Customer

What does the buyer say about their problem, in their own words? The rows collect their usual needs, objections and pain points, the themes in their support tickets, the moments the product clicks for them, and the reasons they buy from you or walk away. Most of your copy will borrow its language from this section.

The template labels this section "From Surveys, Calls Transcripts and Tickets," and that is where your call notes and tickets land. Paste in the phrases buyers repeat. Win Reasons and Loss Reasons come straight from your closed-won and closed-lost notes. The sections below draw on this one, so fill it before the Problems section.

5. Desired State

Where does the buyer want to be? Four rows answer it: the metrics they want to move, the business result they answer for, what success means for them personally, and how they want to feel once it is solved. Call recordings and reviews fill this section, and your headline and biggest claim will come from it.

Example:

• Month-end close in five days or fewer, with no late-payment fees or duplicate payments.
• Personally, no more weekends at month-end and a clean audit.
• They want to know what the company owes before the CFO asks.

6. Current State

Where is the buyer today? The rows describe the numbers they live with, the work that fills their week, the software they use, how they feel about it, and the people and sources that shape their thinking.

This is the "before" picture in your copy and the opening line of your outbound. Support tickets, onboarding answers, and call recordings fill this section.

Example:

• Close takes eight to ten days.
• Invoices arrive as PDFs and get typed into the ERP by hand.
• Approvals stall in email when a manager travels.
• Influenced by the CFO, the external auditor, and peers in controller communities.

7. Problems

What stands in the way? Up to eight rows list the obstacles between the current state and the desired state, written the way the buyer says them. Take the wording straight from your call notes and tickets. "Approvals sit in someone's inbox for a week" gives you far more to write from than "inefficient workflows."

Example:

• "We retype every invoice, and mistakes show up at close."
• "I can't see what we owe until the end of the month."
• "Approvals sit in someone's inbox for a week."

8. Frustrations Related to Problems

What makes the problems hurt? The rows capture what angers them about the problems, what they already tried that failed, what happens if nothing changes, what they fear and distrust, who or what they resent, and the market trends working against them. Closed-lost and churn notes fill most of it. This section supplies most of your objection handling.

Describe the cost of standing still as the buyer describes it. A deadline you invent here will turn up later as a false claim in your copy.

Example:

• Tried an OCR add-on that still needed every invoice checked.
• Fears a rollout that collides with month-end.
• Distrusts vendors who promise fully touchless processing.
• If nothing changes, the next step is another hire the budget does not cover.

9. Acquisition

How does this buyer come to buy? The rows trace the events that start a search, the signs that a buyer is close, how the decision moves through the company, what slows it down, and what they need to feel before they sign. They are the raw material for your customer journey map.

Call recordings and CRM deal history fill this section, including the sales cycle length and the contract terms buyers ask for. In B2B, the decision-making and approval rows usually name other people, and each of them may need a buyer persona of their own (more on that below).

Build Your Offer on What the Customer Persona Says

The template's second half turns the customer persona into an offer. Fill it in only after the first nine sections, and tie every row back to something above it. A promise that answers no problem on the sheet is a guess.

10. Bodacious Claim

Write one big claim aimed at the buyer's deepest desire, taken from the desired state. Aim for the boldest one this buyer will still believe.

Three things set that limit. The first is proof: the claim has to survive section 16. The second is how much the buyer already knows. Someone who has not yet tied their late closes to manual entry needs the problem named before a big promise means anything.

The third is how many similar promises they have heard. When rivals have worn a claim out, saying it louder gets you nowhere, and a narrower claim with proof behind it still gets heard.

Example: "Close the month without retyping an invoice." It stops short of "fully touchless," a promise this buyer has heard before and distrusts.

11. Promise

Promises are the specific commitments that make the claim believable. The sheet has room for nine, each one answering a problem or a fear from sections 7 and 8.

12. Transformation/Benefits

Benefits describe the move from current state to desired state, written in the buyer's metrics. Pair each benefit with the problem it removes.

Example:

• A close that drops from ten days toward five.
• A live view of payables at any point in the month.
• Clerks who review exceptions instead of typing.

13. Pricing

Three rows cover your price, the return that justifies it, and the guarantee that takes away the risk. Frame the return in the persona's own numbers, and point the risk reversal at their biggest fear. Price objections from your calls tell you which comparison the buyer is making.

Example:

• The ROI compares the subscription with the AP hire from the Implications row.
• The risk reversal answers the fear of a rollout during close: a pilot on one entity, finished before the next month-end.

14. Product/Solution Assumptions

How does the product deliver the transformation? The rows name the mechanism, the features and add-ons, and ideas for new ones, with each feature mapped to a problem.

The idea rows collect problems no current feature solves, which makes this section a short list for your roadmap. The word "assumptions" in the template is a reminder to test these rows with buyers.

Example:

• The mechanism is invoice capture with a direct ERP sync.
• A feature idea from support tickets: a close-week view that shows unapproved invoices by manager.

15. Points of Difference

List up to six reasons to pick you over the alternatives, each sorted as easier, faster, better, or cheaper. Compare yourself with the alternatives in the Alternative Solutions and Failures rows, including doing nothing. A difference only counts if this persona cares about it.

Example:

• Easier to run than the OCR add-on, because exceptions arrive as a short review queue.
• Faster than hiring, because it can be live before the next close.

16. Research/Facts

The last section asks one question: what data or research backs your promises? List the proof behind every claim and promise above: case studies, customer data, reviews, and references from similar companies. Any claim without proof here gets rewritten or cut.

Read the Finished Customer Persona Example

Here is the controller from the walkthrough, collected in one place.

• Who: the financial controller at a North American wholesale distributor with 80 to 300 employees, running an AP team of two to four clerks.
• Where they look: LinkedIn and controller communities, and review sites before any demo.
• Where they want to be: a month-end close in five days or fewer, no late-payment fees or duplicate payments, no more weekends at month-end, and a clean audit.
• Where they are: a close that takes eight to ten days, PDF invoices typed into the ERP by hand, and approvals that stall in email when a manager travels.
• Problems, in their words: "We retype every invoice, and mistakes show up at close." "I can't see what we owe until the end of the month." "Approvals sit in someone's inbox for a week."
• What they fear: a rollout that collides with month-end, and vendors who promise fully touchless processing.
• What they use instead: manual entry, an OCR add-on that still needed every invoice checked, or another hire.
• The claim: "Close the month without retyping an invoice."
• The benefits: a close that drops from ten days toward five, a live view of payables, and clerks who review exceptions instead of typing.
• The risk reversal: a pilot on one entity, finished before the next month-end.
• The proof: close-time data from pilot customers, and references from two distributors of similar size.

Let the Evidence Settle What You Are Unsure Of

A filled sheet is a set of guesses, some better supported than others. The rows where you wrote two answers are where research earns its time.

Evidence earns its place when it helps you choose between two plausible explanations. "They're busy" and "they care about ROI" fit every buyer you will ever meet, so they decide nothing.

CIA analyst Richards Heuer built a method around this idea, called Analysis of Competing Hypotheses. List the plausible explanations side by side, check each piece of evidence against all of them, and keep the explanation with the least evidence against it. Evidence that fits every explanation gets set aside, however much of it there is.

Here is how it works on the running example, with the evidence invented for illustration. What is the controller's main problem?

• Speed: invoice processing eats the team's time.
• Errors: manual mistakes surface at close and in the audit.
• Visibility: the CFO cannot see what the company owes.

Now check the evidence against all three.

• "We're swamped at month-end," from call notes, fits all three. It is the line everyone says, and it decides nothing.
• Demo requests spike in the weeks after audits. That fits errors. A speed problem would peak at month-end, and a visibility problem before board meetings.
• Trial users lean on the approval audit trail and barely touch bulk upload. That fits errors and counts against speed.

Errors has the least evidence against it, so it goes into the Problems section. The obvious customer persona would have led with speed. The evidence points to copy about a clean close instead.

Records tell you what happened. Interviews tell you why. Talk to people who made a buying decision in the last few months: new customers, prospects who chose a competitor, and customers who churned.

Nielsen Norman Group recommends starting with five or six interviews, analyzing as you go, and stopping when new interviews stop changing the picture. Bring the rows you are unsure of into these conversations.

Ask about what happened. Hypothetical questions ("would you use a tool that...") produce polite guesses.

• What was going on at your company when you started looking?
• What did you try before this, and why did it fall short?
• Who else was involved, and what did each of them need to see?
• What almost stopped the purchase?
• How would you describe the problem to a peer at another company?

Read the transcripts side by side and highlight the phrases buyers repeat. Copywriter Joanna Wiebe calls this message mining. A phrase that shows up in three or more conversations is a pattern worth building on. Patterns that split cleanly by job title are an early sign that you need a second customer persona.

Your first campaigns settle questions too. An A/B test between two headlines is a test between two explanations of the buyer. You can stop when the explanations would lead to the same decision. If both answers produce the same headline and the same targeting, separating them is money spent on curiosity.

Write a Buyer Persona for Each Role That Can Stall the Deal

Gartner found that B2B buying groups range "from five to 16 people across as many as four functions" (survey of 632 B2B buyers, 2024). A smaller SaaS deal may involve fewer people. It rarely comes down to one.

Start with the champion, the person who finds you and argues for you internally, and fill in the full template for them. Add another buyer persona only when a role needs a different message.

HubSpot learned this early. It built for two personas, "Owner Ollie," a small-business owner, and "Mary Marketer," a marketer at a 50 to 100 person company. "The more we tried to solve for both," cofounder Brian Halligan said, "the less we served either." HubSpot chose Mary.

In most B2B SaaS deals, two more roles qualify for a shorter persona:

• Economic buyer: owns the budget and the risk. In the example, the CFO has funded finance software before, only to see the team stop using it, and needs a payback period and references.
• Technical evaluator: owns integration and administration. In the example, the ERP admin needs integration documentation and proof that the tool will not add maintenance work.

Research often changes who you think is in the room. When Akeneo studied its buyers with the Buyer Persona Institute, it found buying groups of six to eight roles with one lead evaluator, and many prospects already owned a product in the category. Its sales development reps stopped explaining the category and went straight to evaluation criteria.

Role personas come with a caution. In the same Gartner survey, content tailored to individual relevance had "a 59% negative impact on buying group consensus," while content relevant to the whole group improved consensus by 20%. Use role personas to choose the proof each person needs, and keep one shared message about what the whole company gains.

See the Customer Persona Change Your Copy

Here is how the controller persona changes three pieces of copy for the example product.

Landing page headline

• Before: "AI-Powered AP Automation for Modern Finance Teams"
• After: "Get Supplier Invoices Into Your ERP Without Retyping Them"

The new headline comes from the Problems section and uses the buyer's own word for the work. More on the rest of the page in our guide to improving landing page conversions.

Ad angle

• Before: a list of features aimed at "finance teams"
• After: "Down an AP clerk? Keep month-end on schedule without a new hire."

The buying trigger becomes the hook, and the ICP sets the targeting. A paid media team can build audiences around the same trigger.

Outbound opener

• Before: "We help finance teams automate accounts payable."
• After: "Many distributors your size still type PDF invoices into the ERP by hand. Is that how your team handles it today?"

The opener names the current state and asks the buyer to confirm it. Gartner reports that 73% of B2B buyers actively avoid suppliers who send irrelevant outreach.

Use AI to Draft the Customer Persona and Interviews to Correct It

AI persona generators work from whatever you give them. A tool that reads your website describes the customer your positioning implies. That makes a fast first draft, and it shows you who your site is speaking to. What your buyers said on calls stays outside its view.

When Nielsen Norman Group compared AI-generated "synthetic users" with its own interview studies, the AI answers came out overly favorable and treated every need as equally important. A CHI 2024 study of 450 AI-generated personas found them believable, with biases in age, occupation, and pain points, and a strong tilt toward personas from the United States.

A workflow that uses AI well:

1. Generate a first draft from your site.
2. Correct it against your calls, tickets and CRM.
3. Where the draft and your records point different ways, write both answers into the row.
4. Settle those rows with five or six interviews, and keep the buyer's wording.

Persona AI by WeGrowth is free and handles the first step:

1. Enter your company name, your email, and the URL of your website or landing page.
2. Persona AI reads your site content and pulls out who it speaks to: their goals, challenges, and preferences.
3. Within seconds, you get a customer persona in the template's format, ready to download as a Google Sheet.

Keep the Customer Persona in Use After It Ships

Nielsen Norman Group's review of why personas fail names two common causes: teams create personas and never use them, and personas get built in isolation and imposed on everyone else.

Microsoft's early persona program worked hard against the first problem. Its personas appeared on posters, squeeze toys, beer glasses, and mouse pads, and each one had a real email address, used "to send feedback email to individuals on the development team who do good things for their users."

You do not need the beer glasses. You do need the customer persona in front of the people making decisions:

• Build it with the people who talk to buyers. Sales and customer success own the calls and will trust a customer persona they helped write.
• Put it where decisions get made: copy briefs, ad reviews, discovery call guides, and onboarding emails.
• Map it to the journey. Each stage of the SaaS customer journey puts a different role in front of you.
• Use it to tighten targeting. Clear triggers and objections keep spend on accounts that can buy, one of the levers for lowering customer acquisition costs.

Revisit the customer persona at least once a year, and sooner when you enter a new segment, when win rates shift, or when a new role starts appearing on calls.

A customer persona earns its keep when it changes what your team writes, targets, and says on calls. To get a first draft in front of your team, try Persona AI for free.