Customer Persona Canvas

What You Get

Behavior-based customer personas that actually predict how someone will buy and use your product. No demographics (age, location, income). Instead: what they do every day, what frustrates them, what media they consume, their values, and the narrative of how they found you.

This is the method Hazel uses with every client: forget the stereotypes, understand the behavior.

The Prompt

I want to build behavior-based customer personas instead of traditional 
demographic ones. Help me create detailed personas based on actual 
behaviors, not age or income. Here's my business info:

BUSINESS INFO:
- What you sell: [product/service]
- Who's currently buying: [describe your actual customers]
- Who should be buying: [ideal customer]

CUSTOMER DATA (if available):
- Who are your best customers? [Type of person or behavior]
- What do they do for work / in their lives? [Specific roles, situations]
- What frustrates them? [Real problems they mention]
- How did they find you? [Path to purchase: referral, social, search, etc.]
- What do they read/watch/listen to? [Specific content, platforms]
- What do they care about? [Values, principles]
- What words do they use when they talk about their problem? [Language]

IF YOU DON'T HAVE DATA:
[Describe your assumptions about your customers based on who's reached 
out, who you think should use this, etc.]

OUTPUT: Create [2-3] detailed Customer Persona Canvases with these 
sections for EACH persona:

1. PERSONA NAME & HEADLINE
Give them a name. Write a headline that captures their core situation.
Example: "Carla, the freelancer drowning in admin work"

2. BEHAVIORAL DESCRIPTION
Not: "Female, 28, from Portland"
Instead: What's their day like? What do they do? What's their current 
situation? (3-4 sentences)

3. THE PROBLEM THEY HAVE
What's the specific frustration that led them to look for a solution 
like yours? What have they tried before? Why didn't it work?

4. WHAT THEY WANT
The specific outcome they're after. Not vague ("be successful"). 
Concrete ("spend less than 5 hours on invoicing each week").

5. VALUES & WHAT DRIVES THEM
What do they care about? What matters to them? (Autonomy, creativity, 
community, impact, security, efficiency, etc.)

6. MEDIA & COMMUNITY
What do they read? What podcasts do they listen to? What social 
platforms do they use? What communities do they participate in? 
What influencers or brands do they follow?

7. AN AVERAGE DAY
Paint a picture of their day-to-day. What's happening? What's the 
rhythm? Where do pain points show up? (100-150 words)

8. HOW THEY FOUND YOU
What's the journey that led them to discover your product/service? 
What was the trigger? What did they search for? Who recommended you? 
(Narrative format)

9. OBJECTIONS & HESITATIONS
What would make them NOT buy? What are they skeptical about? What 
reassurance do they need?

10. SUCCESS METRIC (FOR THEM)
How will they know it worked? What does the win look like? How will 
they measure it?

Make each persona feel like a real person. If I read these 3 personas 
out loud, your team should nod and say, "Yes, I know exactly who that is."

How to Use It

Step 1: Gather customer data if you have it—interviews, support conversations, sales call notes, form submissions. If not, use your best assumptions. Honesty matters more than perfection here.

Step 2: Paste your business info and customer data into Claude with the prompt above. Claude generates 2-3 detailed persona canvases.

Step 3: Read each persona to your team. Ask: “Do we have real customers like this? Do we want more of them?” This clarifies who you’re actually trying to serve.

Step 4: Use these personas in every decision. When you’re writing copy, designing a feature, or building a campaign, ask: “Which persona is this for? Does it solve their actual problem?”

Step 5: Update these quarterly. As you get more customer feedback, the personas get sharper. Add real quotes, refine behaviors, track what changed.

Example Output

# Customer Personas — [Your Business]

---

## PERSONA 1: CARLA, THE FREELANCER DROWNING IN ADMIN

**Headline:** Carla is a freelance copywriter drowning in admin tasks 
and wants to spend more time on actual writing.

---

### BEHAVIORAL DESCRIPTION

Carla is a 10-year freelancer who works from home and manages everything 
herself: client acquisition, project management, invoicing, taxes, 
contracts. She's good at her craft but hates the business side. She 
works 50+ hours a week but only 20 of those hours are billable—the rest 
is administration. She's constantly switching between platforms (email, 
spreadsheets, calendar, invoicing software) and nothing talks to each 
other. By 6pm, she's exhausted.

### THE PROBLEM THEY HAVE

Carla spends 15-20 hours per week on invoicing, follow-ups, contract 
tracking, and scheduling. She's tried three different project management 
tools, but they all require too much setup and she forgets to update them. 
Her clients are confused about project status. She's missed follow-up 
deadlines and lost money on invoices that didn't get sent. She feels 
guilty that she's not giving her best work because she's burnt out from 
admin.

### WHAT THEY WANT

A system that consolidates all client information in one place (projects, 
rates, contracts, deadlines) and requires minimal upkeep. She wants to 
spend 1-2 hours per week on admin, not 15. She wants to know which 
invoices are outstanding without checking three spreadsheets. Most 
importantly: she wants to trust that nothing will fall through the cracks.

### VALUES & WHAT DRIVES THEM

- **Autonomy:** She chose freelancing to be her own boss. She doesn't 
want to deal with corporate structure, but she also doesn't want 
business tasks to dominate her day.
- **Craftsmanship:** She cares deeply about the quality of her writing. 
When admin tasks take over, it feels like she's betraying what she 
actually good at.
- **Simplicity:** She's tool-fatigued. She doesn't want "powerful" or 
"feature-rich." She wants something that just works.
- **Control:** She wants visibility into her business. She doesn't trust 
"the algorithm" or black boxes.

### MEDIA & COMMUNITY

- **Podcasts:** Tim Ferriss, The Tim Ferriss Show (interested in 
delegation and systems), Lexical, Longform.
- **Social:** Twitter/X, occasionally LinkedIn. She follows copywriters 
and business efficiency experts.
- **Content:** She reads business blogs occasionally (Seth Godin, 
Dispatch), but mostly she's so tired she just watches YouTube videos 
while eating lunch.
- **Communities:** Freelance copywriter Slack groups. She'll ask questions 
about client management but rarely has bandwidth for deep community 
participation.

### AN AVERAGE DAY

Carla wakes up at 7am and checks email. Two client messages. She 
responds while drinking coffee, then moves into her first writing project 
at 9am. By 11am, she's interrupted by two new project inquiries. She 
stops writing to respond, opens her pricing spreadsheet to calculate a 
quote, and realizes she's missing one old client's rate. She searches 
her email for the old contract. 45 minutes gone. She gets back to writing 
at 12pm, works until 2pm, then switches gears to follow up with three 
clients who haven't paid invoices. She checks her spreadsheet, realizes 
one invoice from 6 weeks ago never got sent. She sends it with an apology. 
By 5pm, she's exhausted and hasn't made progress on her own business 
growth.

### HOW THEY FOUND YOU

Carla's fellow freelancer friend mentioned your product in a Slack group. 
She said, "This saves me 5 hours a week." Carla DM'd her for more details. 
Her friend sent a video walkthrough. Carla visited your website, read a 
case study about another freelancer, and signed up for the free trial. 
She wanted to test it on one client project before committing.

### OBJECTIONS & HESITATIONS

- "Isn't this going to take a long time to set up?" (She doesn't have 
time for onboarding.)
- "I'm only one person. Do I really need this?" (She underestimates 
how much she needs to optimize.)
- "Will my clients be able to see sensitive information?" (She worries 
about privacy.)
- "What if I stop using it? Will I lose my data?" (She wants an exit 
strategy.)

### SUCCESS METRIC (FOR HER)

By month 2, she's spending less than 2 hours per week on admin. She 
never misses an invoice deadline. She can tell a prospective client 
"here's where your project stands" without hunting through emails. She 
feels in control of her business, not controlled by it.

---

## PERSONA 2: JAMES, THE OPERATIONS MANAGER TRYING TO KEEP UP

**Headline:** James manages operations for a 15-person agency and is 
constantly putting out fires because systems are inconsistent.

---

### BEHAVIORAL DESCRIPTION

James is an operations manager for a small agency. He's responsible for 
timelines, quality control, client communication, and keeping the team 
accountable. He's not the founder—he reports to the owner—but he feels 
the stress of everything not being tracked properly. He's creating a lot 
of his own systems in Airtable and Google Sheets because the agency's 
tools don't talk to each other. He's constantly reminded of things he 
forgot. He feels like he's babysitting instead of strategizing.

### THE PROBLEM THEY HAVE

James spends 30% of his time chasing down information: "Where are we on 
Project X?" "Did client Y get their deliverable?" "What's our utilization 
rate?" He's built three different spreadsheets to track this, but the 
designers never update them, so the data is always stale. When a project 
slips, it's because no one saw the deadline coming. The founder is 
frustrated with "surprises." James feels blamed for things he can't 
control because people don't use the systems.

### WHAT THEY WANT

A single source of truth where all project info lives: client, timeline, 
deliverables, status, budget, who's responsible. He wants the team to 
naturally use it (because it makes their job easier, not because they're 
forced to). He wants to give his founder real-time visibility into 
operations without creating more work for himself. He wants to shift from 
firefighting to planning.

### VALUES & WHAT DRIVES THEM

- **Ownership:** He owns the problem even though he doesn't own the 
company. He wants to make things better.
- **Systems thinking:** He believes good systems create autonomy. Bad 
systems create chaos.
- **Visibility:** He hates surprises. He wants data that tells the truth.
- **Team effectiveness:** He cares about his team being able to do their 
best work without drowning in process.

### MEDIA & COMMUNITY

- **Podcasts:** Stuff You Should Know, The Indicator from Planet Money, 
business operations podcasts.
- **Social:** LinkedIn primarily. He follows operations and business 
efficiency accounts.
- **Content:** Blogs about operations management, Slack communities for 
ops managers, occasionally attends webinars on process improvement.
- **Communities:** Operations Manager Slack groups, industry-specific 
operations forums.

### AN AVERAGE DAY

James arrives at 9am. He checks Slack and sees the founder asking about 
Project Q status. He doesn't have a quick answer, so he spends 20 minutes 
messaging the project lead. The answer is unclear because the team is 
using three different ways to track time. He writes a report for the 
founder with his best guess. By 10am, he's already frustrated. He spends 
the rest of the morning trying to enforce a new time-tracking system (the 
third one). Two team members resist. He spends 30 minutes explaining why 
it's important. At 2pm, he finally sits down to strategize about 
utilization, but gets interrupted with a client escalation. A deliverable 
was late because no one saw the real deadline. He stays late to patch it 
up.

### HOW THEY FOUND YOU

James was in an operations manager Slack group and someone mentioned your 
tool. He read the reviews, was skeptical that it would work for an agency, 
but decided to request a demo. The sales team showed him how three other 
agencies use it and how it eliminated these exact problems. He got buy-in 
from the founder (cost was low relative to the problem). His job is to 
pilot it and prove ROI.

### OBJECTIONS & HESITATIONS

- "Will the team actually use it, or will I be updating it myself?" 
(Past tool experiences have been failures.)
- "Can it handle our specific workflow?" (Agency work is complex.)
- "How much time does implementation take?" (He's already overloaded.)
- "Can I export this data?" (He doesn't want to be locked in.)

### SUCCESS METRIC (FOR HIM)

In 3 months, he has one source of truth for all projects. The team 
naturally updates it (because it's easier than not). The founder can see 
real-time status without asking. He can tell the founder utilization, 
burndown, and cash impact with confidence. He spends 10% of his time on 
data collection instead of 30%.

---

## PERSONA 3: MAYA, THE DESIGN STUDENT BUILDING A PORTFOLIO

**Headline:** Maya is building a freelance design business and needs to 
learn the business side while she's still learning design.

---

### BEHAVIORAL DESCRIPTION

Maya graduated 8 months ago. She's taking on small design projects (logos, 
social posts, simple brand work) to build her portfolio while working a 
part-time retail job. She's charging $300-500 per project. She's 
technically competent but clueless about the business side: contracts, 
pricing strategy, taxes, payment terms. She's doing everything wrong but 
doesn't know it. She's scared to raise prices. She's given free work to 
friends. She's never had a client sign a contract. She's learning as she 
goes.

### THE PROBLEM THEY HAVE

Maya is underpricing her work. She's given free revisions to three clients 
who've taken advantage. She doesn't have contracts, so clients don't 
respect scope. She's not sure how to handle taxes as a freelancer. She's 
scared to bring up money with clients and often doesn't follow up on 
invoices. She's thinking about quitting because it doesn't feel like a 
"real business"—it feels like unpaid work with a small payment attached.

### WHAT THEY WANT

She wants to feel legitimate. She wants to know what she should be 
charging and why. She wants a simple system that makes her look 
professional to clients. She wants to understand the business fundamentals 
(contracts, pricing, invoicing) without reading a 300-page business book. 
She wants to know if freelancing can actually be a full-time career or if 
she should pursue something else.

### VALUES & WHAT DRIVES THEM

- **Legitimacy:** She wants to be taken seriously as a professional, not 
a hobbyist.
- **Learning:** She's still early-career and wants to grow. She'll invest 
in education.
- **Autonomy:** She chose freelancing to avoid corporate structure, but 
she wants it to be real.
- **Sustainability:** She's tired of barely scraping by. She wants a 
viable path to full-time income.

### MEDIA & COMMUNITY

- **YouTube:** Design education channels, freelance business channels 
(Millennial Money, etc.)
- **Instagram:** Design portfolio accounts, business accounts run by 
freelancers.
- **Podcasts:** The Goal Digger Podcast, How to Fail, freelance business 
podcasts.
- **Communities:** Design student communities, reddit (r/freelance), 
online courses.

### AN AVERAGE DAY

Maya works her retail job 1-5pm. During her 9-1pm shift, she's checking 
email for client messages. She has two pending projects. One client keeps 
asking for changes but hasn't paid the first invoice yet. She's scared to 
follow up. She goes home, updates her portfolio with a new case study, 
posts it to Instagram. She spends 30 minutes engaging with design 
communities on Reddit. She works on a personal design project (not paid) 
because it feels safer than reaching out to prospects. By 9pm, she feels 
busy but unproductive. She's made $0 today but spent 4 hours on design 
work.

### HOW THEY FOUND YOU

Maya saw an Instagram ad from you featuring a freelance designer's success 
story. The designer mentioned how much money she was losing by 
underpricing. Maya immediately thought, "That's me." She visited your 
website and saw a free guide about freelance pricing. She downloaded it, 
read it in one sitting, and signed up for your free trial. She wants 
validation that freelancing is worth pursuing.

### OBJECTIONS & HESITATIONS

- "Can I afford this? I'm not making much money yet." (Price sensitivity 
is real.)
- "Is this going to help me if I only have 2-3 projects a month?" (She 
worries the tool is overkill for her scale.)
- "Will this tell me what to charge?" (She wants answers, not more tools.)
- "What if freelancing doesn't work out? Will I waste money?" (Risk 
aversion.)

### SUCCESS METRIC (FOR HER)

In 6 months, she's raised her rates to $800-1200 per project. She has 
contracts that clients actually sign. She's collecting invoices on time. 
She knows what she should be earning and can see a path to full-time 
freelance income. She feels like a real business, not a hobby.

---

## HOW TO USE THESE PERSONAS

1. **Copy them into your team Slack or shared doc.** Everyone should 
read these and have a shared mental model of who you're serving.

2. **Reference them in every decision.** "Is this feature for Carla, 
James, or Maya?" If you don't know, you haven't thought about it enough.

3. **Use them for marketing.** Write copy that speaks directly to Carla's 
frustration, James's situation, or Maya's fear. Don't write for "everyone."

4. **Use them for product decisions.** If you're building a feature, ask: 
"Which persona uses this? Does it solve their actual problem?"

5. **Test your messaging.** Share your tagline or pitch with someone who 
resembles each persona. Does it land?

Want more methods? Browse the full library at hazelq.com/methods.

Built with Claude. Every prompt in this library has been tested in the latest Claude model.