Skip to main content
Create personas on the Personas page by clicking Create new. The flow is conversational — describe the person you want in your own words, and Percio fills in the rest. You can then edit any field before saving.

​
The conversation

Start with a one-sentence description. Examples:
  • “A 35-year-old bakery owner who uses Instagram on her phone to market her business.”
  • “A technical buyer at a 200-person SaaS company evaluating our platform.”
  • “A first-time mobile shopper who’s never used a subscription service before.”
Percio asks follow-ups — device usage, tech comfort, what they’re trying to accomplish, what frustrates them. Answer in plain language. When it has enough, it generates the full persona and shows you the fields.

​
Every field explained

​
Name and emoji

Used throughout the UI to identify the persona. A strong name and emoji make it easier to pick the right persona from the list and to scan past reports.

​
Occupation

The persona’s job or role. This anchors the persona’s worldview and the assumptions they bring to your product. Prefer specific (“Neighborhood bakery owner”) over generic (“Small business owner”).

​
Description

A 2–3 sentence background. Short enough to read at a glance, rich enough to establish context.

​
Main objective

The persona’s big-picture goal — what they’re ultimately trying to accomplish that your product might help with. 30–200 characters.

​
Device context

The primary device and usage context. “Desktop during work hours” is different from “iPhone while commuting” — Percio uses this to interpret what’s reasonable for the persona to do.

​
Tech expertise

A 1–5 scale:
  • 1 — struggles with anything beyond basic apps.
  • 2 — comfortable with familiar tools, cautious with new ones.
  • 3 — average consumer, figures things out with some effort.
  • 4 — comfortable with new software, explores UIs confidently.
  • 5 — power user, expects keyboard shortcuts and advanced features.

​
Focus areas

3–5 things this persona pays attention to when evaluating a product. Examples:
  • “Clear pricing and no hidden costs”
  • “Speed — I don’t have time to wait”
  • “Visual trust signals (reviews, security badges)”
  • “Mobile-first design”

​
Pain points

2–4 frustrations this persona brings to every interaction. Examples:
  • “Gets impatient with long sign-up forms”
  • “Distrusts ambiguous CTAs”
  • “Hates when fixes require calling support”

​
Behavioral traits

3–5 personality traits that govern how the persona reacts when something goes wrong. Examples:
  • “Abandons easily when confused”
  • “Reads every word before clicking”
  • “Skims headlines, ignores body copy”

​
Priority heuristics

The Nielsen heuristics this persona weights most heavily. A tech-anxious persona might over-index on Help users recover from errors; a power user might over-index on Flexibility and efficiency of use.

​
System prompt

The full prompt that governs how the persona evaluates a flow. Auto-generated from the other fields. You can edit it directly if you want total control.

​
Saving

Once the fields look right, save. The persona appears on your Personas page and is immediately available for test runs.

​
Editing later

Every field is editable after the fact. If reports from a persona feel off-target, tweak the focus areas, pain points, or behavioral traits — those have the biggest impact on what the persona flags.

​
What’s next