Customer Personas: Simple Profiles That Shape Better Content
Customer personas are one-page profiles built from real calls, forms and reviews. Learn how they guide topics, tone and format for your content.

Customer personas are short profiles of the people who buy from you, written around what they need and what they ask before they decide. Ask three people on your team to describe your typical customer and you'll probably hear three different answers. I'm Marven Salgado, founder of Social Influence in Mascouche, and I often find that gap behind blog posts and service pages that aren't landing. A one-page profile built from real customer conversations closes it.
Customer personas for a small business: what they are and what they are not
A customer persona for a small business is a short profile of a recurring type of buyer, built from real needs, questions and objections, not a fictional biography with a made-up name and hobbies.
Many persona templates ask for age, income and a favourite podcast. Demographics tell you who buys. A useful persona also records why they buy and how they make the decision. You build it from patterns you already see, like the questions customers ask and the objections that come up, plus whatever your best buyers have in common. Once it exists, it guides what you write and the words you use. It can even tell you where your ads should run.
Some practical points:
- Start with two or three personas. With more than that, the team stops using them.
- Keep business buyers and household buyers apart: a property manager and a homeowner may buy the same service but decide differently.
- Consider a negative persona for people who are a poor fit, such as bargain hunters or industries you don't serve, so you stop spending time and budget on leads that won't go anywhere.
Customer persona raw material: calls, forms, reviews and sales conversations
The raw material for a customer persona is already in your business: phone calls, enquiry forms, online reviews, emails and the notes from sales conversations.
Read through them looking for what repeats, such as a question that comes up on call after call or an objection that keeps stalling sales. Write those down in the words the customer used. A review praising a contractor for showing up when they said they would tells you more about what this buyer values than any demographic field. Google Business Profile reviews are an easy place to start.
Respecting Loi 25 when you collect customer information
Loi 25 applies to Québec businesses of every size, so customer calls, forms, reviews and sales notes can't be used for persona work without some care.
I build consent into the intake form before I touch any data. The form says why the information is collected and that feedback may shape how the business talks to other customers like them; on calls, a short heads-up does the same job. Before any persona work starts, I strip names, phone numbers, email addresses and anything else that identifies a person, and keep only patterns such as the type of job or the reason for buying.
How I sort source material before using it:
| Source | What I keep | What I remove |
|---|---|---|
| Calls | General concerns | Names, phone numbers |
| Forms | Industry, goals | Addresses |
| Reviews | Common phrases | Usernames |
| Sales notes | Objections raised | Account details |
This is my working practice; for the legal side, check your own forms with whoever handles privacy in your business.
One-page personas a small team will actually use
A one-page persona is the kind a small team will open, because nobody flips through a ten-page document before writing a blog post or choosing an ad headline.
Keep it simple and visual. Give the buyer a short label, describe the situation they're in, and answer three questions:
- What keeps them up at night?
- What do they wish someone would just tell them straight?
- What would make them trust a small business over a big chain?
Below that, add phrases customers used and the questions they ask most often. I pin mine above the desk. When you're stuck on a headline, you look up, read the answers and write as if you're talking to one real person.
Persona-based content decisions for service pages and blog posts
A persona becomes a content decision when every topic you write about is matched to a decision the buyer is trying to make.
I pick topics by asking what question the persona needs answered before they'll pick up the phone or fill out a form. Take a Mascouche homeowner comparing contractors: the useful page for them explains what a fair quote looks like and what it should include. On a service page, the same thinking decides which questions get answered on the page itself, such as what affects the price or what happens on the first visit.
Tone and format come from the persona too. If your buyer talks plainly and reads on a phone between jobs, a long, formal page full of industry terms won't suit them. Read each draft against the phrases in the persona and ask whether that person would say it that way. When we handle SEO content writing for a client, every draft goes through that check before it's published.
Matching topics to what the buyer is trying to decide
Matching topics starts with naming the decision the buyer is stuck on, then sorting real customer questions by where that person is in the process.
I pull questions from past emails, calls and sales conversations and group them. Early on, a buyer wonders whether they need the service at all. While comparing options, they want to know what it costs and how to choose a provider. Once they're ready, the questions turn to booking and what happens next. An explanatory blog post fits the first group, a comparison or pricing page the second, and a service page with a clear way to get in touch the third.
Then I check each topic against three questions:
- Does it answer a question a customer actually asked?
- Does it move them closer to booking or buying?
- Does it remove a worry they haven't said out loud?
If a topic does none of these, I cut it, however good it looks as a keyword.
Personas, Google search and AI-generated answers
Personas help with Google search and AI-generated answers by pushing you to name real customer questions in the plain language people use when they search.
Google's AI Overviews and tools such as Gemini and ChatGPT now summarize answers instead of only listing links. Content written for a vague audience tends to stay general, and a general page gives a summary very little to work with. A page that states the question a real person asks and then answers it directly is easier for a reader to understand, and for an AI system too.
That's why I build personas from audience research: the questions customers type into a search bar or ask on the phone. The same idea is where we start when we work on being found on Google and cited by AI. Nobody can promise that a page will appear in an AI answer, but a page that answers a real question in plain language gives Google and AI tools something clear to work with.
Persona updates and separate French and English audiences
Personas need updating whenever your market or your customers shift, and if you serve both French and English speakers, each language group needs its own persona, researched in that language.
I review personas every few months and ask what has changed: new questions on calls, new objections, a service you've added or dropped.
In Greater Montréal it's tempting to merge French and English customers into one persona. Language shapes how people search and how they expect to be spoken to, and separate profiles keep you away from content that reads like a translation. Loi 96 has also reinforced the place of French in Québec business, which is one more reason to give your French content its own research.
When I build personas for bilingual clients, I compare how each group searches, what tone feels natural and which local references connect. A French-speaking buyer in Terrebonne may use different search terms and expect a different register than an English-speaking buyer in the West Island, even for the same service.
Persona checklist before your next piece of content
A persona checklist is a short set of questions I run every piece of content through before publishing, with the one-page profile beside me.
- Who is this for? Name the specific persona.
- What problem does it solve for them right now?
- Do the words match how that person talks?
- Does the format fit where they'll find it: a short post for Facebook or Instagram, or a longer page for someone comparing options?
- What should they do next, and does the content make that obvious?
It takes a few minutes and catches drafts that would otherwise just fill space. If you don't have a persona yet, start small. Pick your three most common customer questions, write down the words people use, and build one page in French and one in English. For help with the first one, you can request a proposal.