Customer Persona Builder (JTBD)

When to use

Triggers:

"Build customer personas" / "Who is our customer?"
"ICP for [business]" / "Target market for [product]"
"Why do customers buy from us?"
"We keep pitching to the wrong people"
Before launching a new product, channel, or campaign
Before rewriting website / ad copy / sales scripts

Don't fire for:

Pure market sizing (use business-plan-writer-au or an ABS-data skill)
B2C consumer demographic analysis at population scale (marketing agency territory)
Persona work for a business with no customers yet (do customer discovery first; don't invent personas)

Why generic personas fail

Most AU SME persona docs read like:

"Sarah, 35, marketing manager. Lives in Melbourne. Drinks flat whites. Frustrated with manual reports."

This is worthless for decisions. It doesn't tell you:

When Sarah starts looking for a solution
What she tried first (and why it didn't work)
Who influences her buying decision
What stops her from saying yes
What language she actually uses when she talks about the problem

Useful personas are triggered buyer profiles, not demographic portraits. The format matters.

The Jobs-To-Be-Done frame

The best persona format for SMEs comes from Jobs-To-Be-Done (JTBD): customers "hire" your product to do a job for them. Personas are organised around the job, not the person's attributes.

For each persona:

The job — what the customer is trying to accomplish
The context — when/where/why the job becomes urgent
The struggle — what they're doing now that's painful
The desired outcome — what "done" looks like
The trigger — the specific moment they start looking
The constraints — budget, time, political, skills
The decision process — who decides, who influences, what the steps are
The language — the phrases they actually say

A single person might hire your product for different jobs on different days — so you might have multiple personas for the same demographic.

Step 1 — Ground the persona in real data

Before writing any persona, pull data. No fabrication.

From your CRM

Closed-won deals, last 12 months — what do they have in common? Industry, size, role, how they found you, deal value, sales cycle length
Closed-lost deals — same. What patterns appear in the losses?
High-LTV customers — who's stayed the longest and spent the most?
High-churn customers — who left fastest and why

From analytics

Top-converting pages — what content led to signup?
Top-engaged posts — which themes resonate?
Search terms driving traffic — what queries bring them?

From conversations

Sales calls (recorded, transcribed) — what phrases do prospects use?
Support tickets — what are the complaints and requests?
Exit interviews with churned customers — why did they leave?
Referral conversations — why do existing customers recommend you?

From external sources

Industry reports (ABS, IBISWorld, trade publications)
Review platforms — Google, ProductReview, Trustpilot for your business + competitors
Forums / community spaces — Reddit, LinkedIn groups, industry Slack, Facebook groups

Step 2 — Look for patterns, not averages

Personas are cluster patterns, not means. The operator who bought from you for reason A is a different persona from the one who bought for reason B.

Rule of thumb: if you can serve 2 buyers with the same messaging, they're probably one persona. If you need different messaging, they're different personas.

Most AU SMEs have 2–4 personas. One is usually "the best current customer" and another is usually "the persona you want more of but you're bad at attracting".

Step 3 — Write each persona using this format

[Persona Name — memorable, evocative, not a real person's name]

## The job
[In their words. What are they trying to accomplish when they look for us?]

## The context
When: [situational trigger]
Where: [what part of their life / business]
Why now: [what's changed recently]

## The struggle
[Current workaround or status quo. Why is it painful?]

Cost of the struggle:
- Time: [quantify if possible]
- Money: [if the pain has a dollar tag]
- Emotional: [stress, embarrassment, risk aversion]

## The desired outcome
What does "solved" look like for them? Be specific.

## The trigger
What specific event makes them start actively looking?
- [Event 1]
- [Event 2]

## The constraints
- Budget range: [what's realistic]
- Time: [urgency level, working days vs weekends]
- Politics / stakeholders: [who else needs to agree]
- Skills / capacity: [what they can and can't execute themselves]

## The decision process
- Decision maker: [role]
- Influencers: [roles]
- Typical sales cycle: [weeks]
- Key objections at each stage:
  - Early: [objection]
  - Mid: [objection]
  - Late: [objection]

## The language
Phrases they actually use:
- [verbatim phrase from a call / review / forum]
- [verbatim phrase]
- [verbatim phrase]

Phrases that turn them off:
- [jargon they don't trust]
- [sales-speak they ignore]

## Where they find us
- [specific channel 1]
- [specific channel 2]

## What makes them stay
- [retention hook 1]
- [retention hook 2]

## Representative customer(s)
- [real name anonymised or "Customer X"] — an actual current customer who exemplifies this persona

Australian-specific persona considerations

Trust signals that matter more in AU

Australian ownership / Australian-made
Local phone number (local area code over 1300/1800)
Identifiable real people on the team (not just a brand)
Specific references to AU regulations (Privacy Act, Fair Work, ATO)
Reviews on AU-specific platforms (ProductReview.com.au especially)

Regional variation

AU operators in different cities / regions differ more than the demographic averages suggest. Brisbane tradies respond differently to Sydney's; regional operators have different expectations of service times and local presence. Don't assume a Melbourne persona maps to Perth.

Industry-specific language

Trades, healthcare, professional services, retail, hospitality each have their own vocabulary. Personas should capture the actual phrases — e.g. a sparky says "SWMS" and "CoES", not "safety documentation" and "compliance certificate".

Timing patterns

AU SMEs have predictable busy / slow cycles:

EOFY (June / July) — financial services, accounting, tax advisors spike
Christmas period (mid-Dec to mid-Jan) — many B2B businesses shut down; B2C spikes
Footy finals, public holidays, state events — regional spikes

Persona triggers often map to these cycles. A persona who "starts thinking about bookkeeping in late April" is a very different beast from one who "starts in August".

Step 4 — Sanity-check each persona

Before using the personas:

Can your salesperson tell you one story about a real customer who matches this persona?
Can your marketing person write 3 email subject lines that speak to this persona specifically?
Can you point at 2–3 closed-won deals in your CRM that match this persona?

If you can't do all three for a persona, it's still hypothetical. Keep doing customer research until it's grounded.

Step 5 — Use the personas

Personas sit in a shared document. They're used to:

Test marketing copy: "would [Persona A] actually say this?"
Qualify leads: "does this inbound lead match any persona? Which?"
Prioritise product decisions: "which persona benefits from this feature?"
Channel selection: "where does [Persona A] actually spend time?"
Sales scripts: "for [Persona A], the opening hook is X; for [Persona B], it's Y"

Update them every 6–12 months, or when you land a new customer type that doesn't fit existing personas.

What this skill does NOT do

Invent personas for a business with no customers. Do customer discovery interviews first (that's a separate methodology — rough guide: 10–15 conversations before you have a single grounded persona).
Replace ongoing customer conversations. Personas are a snapshot; your actual customers keep evolving.
Generate fake-precise demographics. If the data doesn't support it, don't claim it.
Work at consumer-brand scale (e.g. a cereal brand with 20M customers) — different methodology with quantitative research + segmentation analysis.

Output format

Per engagement:

Persona document — 2–4 personas in the format above
Data appendix — the CRM / analytics / review-source data that grounded each persona
Messaging implications — 3–5 bullet points per persona on what this means for copy, channels, qualifying questions
Refresh cadence — when to revisit and why

Tier access

Base. Foundational for any business doing marketing or sales seriously. Pro-tier members get a persona workshop (2-hour facilitated session with THL) to ground the personas in CRM data.

Related skills

business-plan-writer-au — the Customer section uses these personas
au-cold-outreach-spam-compliant — outreach sequences customise per persona
customer-retention-churn-signals — the same customer mapping informs retention patterns
pricing-packaging-professional-services — packaging decisions key off persona preferences