---
name: user-persona-builder
description: "Builds a realistic one-page customer persona for a product or service, with the goals, frustrations and buying objections that product and marketing decisions can lean on. Use when a product or marketing team needs a single customer persona to guide design, messaging or targeting decisions. Do not use for market sizing or a segmentation study built from survey data. Related topics: ux, marketing, design."
---

# User Persona Builder

Builds a realistic one-page customer persona for a product or service, with the goals, frustrations and buying objections that product and marketing decisions can lean on.

## When to use

Use this skill when a product or marketing team needs a single customer persona to guide design, messaging or targeting decisions. Do not use it for market sizing or a segmentation study built from survey data.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Name the persona and write a one-line summary of who they are and what they are trying to get done.
3. Write each chosen element with a concrete situation or example rather than a trait list.
4. Add the buying role and decision process when the persona type is B2B.
5. Mark which details are assumptions to validate, then trim the whole thing to one page.

## Inputs

- **Product or service being sold** (free text, e.g. "B2B accounting software")
- **Target demographic** (free text, e.g. "Small business owners aged 35 to 50")
- **Persona type** (choose one: B2B (Business), B2C (Consumer))
- **Elements to include** (choose any: Demographics, Daily frustrations, Goals and motivations, Favorite brands, Buying objections)
- **Level of detail** (choose one: High-level overview, Extremely detailed story-driven profile)
- **Include a hypothetical quote from the persona** (choose one: Yes, No)

## Output

A one-page persona: name and summary, then one short section per chosen element, plus a quote when requested and a short list of assumptions to validate.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### User Persona Builder

Build one persona that a team could use to settle design and messaging arguments.

- Product or service being sold: {{Product or service being sold}}
- Target demographic: {{Target demographic}}
- Persona type: {{Persona type}}
- Elements to include: {{Elements to include}}
- Level of detail: {{Level of detail}}
- Include a hypothetical quote from the persona: {{Include a hypothetical quote from the persona}}

Give the persona a name, a role and a one-line summary first. Cover only the chosen elements, and make each specific enough to act on: a frustration should name the situation it happens in, and an objection should say what would overcome it. For a B2B persona include the buying role and who else signs off. Label anything invented from the demographic as an assumption to validate with real customers. If a quote is requested, write it in the persona's own voice. Keep the whole persona to one page.

## Pitfalls

- Describing a demographic average instead of a person, which gives the team nothing to design for.
- Listing objections without what would overcome them.
- Presenting invented details as researched fact.
