codel
← Back to the index

MKT-03 · SEC. 08 Market Research

Target User Segment Breakdown

Turn a rough audience description into grounded user segments with needs, objections, and buying triggers.

FORMAT
prompt
DIFFICULTY
beginner
TIME
10 min
TOOLS
universal
MODELS
any
COPIES
0 so far

When to use this

You have a vague sense of who your product is for ("small business owners," "freelance designers") and need it broken into real, distinct segments before you write copy, pick channels, or scope features.

The pattern

Pastes as plain text
Act as a user research analyst.

Break my target audience into 2-4 distinct segments (not invented personas with
names, actual behavioral or situational groupings). For each segment, give:

- WHO: what makes this segment distinct from the others (role, stage,
  context, not demographics alone)
- NEEDS: the specific problem this segment has that the product addresses
- OBJECTIONS: the real reasons this segment would hesitate or say no
- BUYING TRIGGER: the specific event or realization that makes this segment
  actually go looking for a solution now

Ground every claim in source material I provide or public sources you can
verify and cite, not recalled or invented specifics. Where evidence is
missing, label the claim HYPOTHESIS rather than presenting it as fact.

Do not fabricate quotes, statistics, or named sources. If you don't have
grounded evidence for a segment claim, say so plainly.

End with which segment to target first only when the available evidence
compares reach and need; otherwise give a conditional hypothesis and name
the data needed to rank the segments.

Start by asking me in one message for: (1) my rough audience, (2) what the
product does, (3) source material or permission to research public sources.
Wait for my reply before segmenting.

Real example output

Audience: freelance graphic designers
Product: automated invoicing and contract tool for freelancers

SEGMENT 1: New freelancers (0-2 years independent)
WHO: Recently left agency or in-house work, still building a client base
NEEDS: Look professional despite lacking a "business" setup, avoid getting
  burned by scope creep or non-payment
OBJECTIONS: Price sensitivity is high, likely to default to free templates
  or Google Docs until pain is acute
BUYING TRIGGER: First client who pays late or disputes an invoice, commonly
  reported as the moment freelancers start looking for formal tools

SEGMENT 2: Established solo freelancers (3+ years, steady client roster)
WHO: Already has a workflow, likely juggling 3-5 recurring clients
NEEDS: Reduce time spent on admin, not proving legitimacy anymore
OBJECTIONS: Switching cost from an existing spreadsheet or tool they've
  already customized, likely to resist unless the time savings is obvious
BUYING TRIGGER: Hiring a subcontractor or scaling past what manual tracking
  can handle

SEGMENT 3: Freelancers transitioning to a small studio (hiring 1-2 people)
WHO: Crossing from solo to managing others' invoices and contracts too
NEEDS: Consistency and audit trail across multiple people's work, not just
  personal admin anymore
OBJECTIONS: May already be evaluating full agency management software,
  this tool needs to look like it scales with them
BUYING TRIGGER: Onboarding first subcontractor or employee

RECOMMENDATION: HYPOTHESIS, not a validated ranking: test Segment 1 first
because it may have lower switching cost than established freelancers.
Verify relative segment size, acquisition reach, willingness to pay, and
the late-payment trigger before committing to this target.

Why it works

Forcing behavioral segments instead of named personas keeps the output grounded in real decision patterns rather than invented characters. Requiring "likely" or "commonly reported" language on inferred claims stops the model from presenting guesses as verified facts.

Related patterns

Entry MKT-03 · by codel · 2026-07-08 · CC-BY-4.0