How to Create a Buyer Persona: 6 Steps Instead of Guesswork

Creating a buyer persona doesn't mean making up a name and picking a stock photo

Creating a buyer persona doesn't mean making up a name and picking a stock photo. It means understanding exactly when someone needs your product, what problem they're trying to solve, and what's holding them back from buying. As a solo founder, you don't need a market research budget for that — you need a clear structure and a few real conversations.

I used to think personas were something only big agencies bothered with. Wrong.

Buyer persona vs. target audience: what's the difference?

A target audience is a category. A buyer persona is a person. "Women aged 25-45 interested in fitness" is a target audience. "Sarah, 34, works full-time, wants to work out three times a week, but keeps failing because of lack of time and guilt" is a persona.

The difference sounds small, but it isn't. Demographic traits like age, gender, location, or income help you with media planning, but not with copywriting. A persona, on the other hand, describes behavior, motivation, and the exact moment someone starts actively looking for a solution. That moment — the so-called trigger — is what you actually need for your marketing.

If you've never systematically thought through your target audience, it's worth taking a step back first: roughly define your target audience, then build one or two concrete personas within that group. Together, the two give you a complete picture.

What building blocks a buyer persona for small SaaS products actually needs

A good persona for a small SaaS product needs three things: the trigger that makes someone start actively searching, the job they're actually trying to get done, and the objections holding them back from buying.

Take a scheduling tool for tradespeople I looked into closely: the trigger wasn't "wants to modernize" — it was very specifically the third double-booking headache in a month. The job-to-be-done wasn't "digitize," it was simply "no more double bookings, without having to double-check every appointment myself." That's the level of specificity you need to hit — not vague phrases like "increase efficiency."

What bugs me most about it: all those marketing persona templates online that ask what car your persona drives or what TV show they watch. For a micro-SaaS, that's a waste of time. Nobody buys an invoicing tool because they drive a BMW.

You're a solo founder, not a corporation with a media budget. You need focus, not completeness.

The trigger

Nobody buys software just because they feel like it. Something happens first: a customer complains, a spreadsheet gets too messy, a deadline gets closer. That moment is your trigger — and once you know it, you also know where and when to reach your audience.

Ask yourself: what happened right before someone started looking for a solution like mine?

The job-to-be-done

The concept comes from Clayton Christensen, and it's simple: people "hire" a product to get a job done. Nobody wants project management software — they want their team to stop using three different chats for one topic.

For every feature you build, ask: what job does this do for the user? If you don't have a clear answer, it's probably not a feature anyone actually needs.

The objections

Every potential customer has doubts before they buy. "Too expensive," "too complicated," "do I really need this," or "I'm already sort of managing this with Excel." You need to know these objections, or you won't be able to address them in your marketing.

By the way, you won't find the most common objections by thinking hard at your desk — you'll find them by listening. More on that in a moment.

Creating a buyer persona in 6 steps

Here's exactly how to do it, even with zero market research budget.

Step 1: Collect 5 to 10 real customer quotes

Before you write anything down, collect real statements. These can be forum comments, reviews of competing products, or questions from Facebook groups or Reddit threads related to your topic. What matters: these need to be real phrases from real people, not assumptions you dreamed up.

Copy the quotes word for word into a document. The exact language people use is pure gold later on. If someone writes "I'm sick of tracking all this by hand," that's a better headline template than any marketing copy you could come up with yourself.

Step 2: Have 3 to 5 short conversations

A 15-minute call with someone from your target audience often gets you further than weeks of desk research. Ask about the last time they tried to solve your problem. What did they try? What didn't work? What did they end up doing?

Avoid hypothetical questions like "Would you use something like this?" The answers are almost always overly optimistic and won't get you anywhere. Instead, ask about the past — about actual behavior.

Step 3: Identify the recurring trigger

Look through your notes and search for patterns. Does a specific trigger keep coming up? Maybe it's a team growing past a certain size, or a customer asking the same question for the third time.

If you find three or more people describing the same trigger, you've got something usable. One case is a coincidence. Three is a pattern.

Step 4: Write the job-to-be-done in one sentence

Write a single sentence following this pattern: "When [situation], I want [desired outcome], so that [deeper reason]." For example: "When my team grows past five people, I want a central overview, so I don't have to hunt for information across three different tools anymore."

This one sentence becomes the foundation for your landing page, your ads, and your emails. Everything you write afterward should tie back to this sentence.

Step 5: List the three most common objections

Go back through your notes and quotes. Which concerns keep coming up? Usually it's some combination of price, setup time, and doubts about whether the tool is really better than their current solution.

Write a short, honest answer to each objection. You'll need this later for FAQ sections, sales conversations, and objection handling in your ads.

Step 6: Bring it all together in a one-page template

Now pull everything together. A good buyer persona template for a small SaaS product fits on one page: name and role, the trigger from step 3, the one-sentence job-to-be-done from step 4, the top 3 objections with answers, a few real quotes, and the channels where this person gets their information.

That's enough. You don't need more, and more would only distract you.

Creating a customer avatar: a simple example

A customer avatar is essentially the same thing as a buyer persona, just often framed a bit more visually and vividly. For this example, let's take a fictional feedback-collection tool for small online shops.

See how concrete this gets? With a table like this in front of you, you're no longer writing an interchangeable landing page — you're writing one that speaks directly to this one person.

Where to find persona data without a budget

The best source for real persona data is language that already exists before you even asked. Comments under competing products, app store reviews, questions in niche forums. It's free, honest, and mostly unfiltered.

This is exactly where research often gets tedious. You scroll through forums for hours and still aren't sure whether the problem you found is big enough to build a business on. For this exact step, I use Starte.ai myself: instead of manually scrolling through forums, you can see what people in your niche are actually searching for and how large the estimated search volume behind it is — before you sink hours into collecting quotes.

Describing your ideal customer: turning the persona into a landing page

Describing your ideal customer ultimately means turning your persona into copy that speaks directly to that one person. The trigger from step 3 becomes your headline, the job-to-be-done from step 4 becomes your subheadline or hero line, and the objections from step 5 become your FAQ section.

Don't start your landing page with the product — start with the trigger. "Did you answer the same question in your support chat for the third time this week?" hits harder than "The best solution for customer support." The first sentence speaks to the situation your ideal customer is actually in; the second just talks about you.

Patrick McKenzie has often pointed out in his writing on pricing how much the customer's own language shapes the price they're willing to accept. When you speak your persona's language, you're no longer selling a feature — you're selling a solution to a problem that already has a name.

Common mistakes when creating a persona

The biggest mistake is inventing a persona at your desk without ever talking to real people. The result usually sounds like a cliché: "Marketing Manager Max, 35, likes efficiency." That helps no one.

Second common mistake: too many personas at once. For a small SaaS product, one — at most two — is enough to start. Every additional persona dilutes your focus, because you end up trying to please everyone and end up truly reaching no one.

A persona also isn't a one-time exercise you check off and never revisit. As your product evolves or you have new customer conversations, update your persona. What was true at the start might not quite hold up a few months later.

From persona to finished product

Once your persona is solid, you know not just how to write your copy, but also what you should actually be building. The job-to-be-done from step 4 is essentially already half of your product description.

This is exactly where a clear roadmap helps — getting you from idea to an actual MVP with the right feature scope for the exact persona you've just defined.

The bottom line

A buyer persona for a small SaaS product doesn't need a market research budget — it needs real quotes, a clear trigger, one sentence for the job-to-be-done, and three honest objections with answers. Talk to five people, collect their words, and turn that into your one-page template. Then write your next landing page not for "everyone," but for this one specific person.