User Persona Generator
Generate 3 persona cards — primary, secondary, and negative — with software-specific attributes other tools miss. Technical proficiency, platform preferences, UI tolerance, and what it all means for your build.
Free, no signup required. Results in 2-5 minutes.
How It Works
Describe Your Product and Users
Tell us what you're building and who you think will use it. We'll start forming persona hypotheses from your input.
Deep-Dive on Your Primary User
We'll explore their tech proficiency, daily workflow, current tools, device preferences, and pain points in detail.
Define Secondary and Negative Personas
Identify who else uses the product differently, and — critically — who you're explicitly not building for.
Get Development Implications
See what your personas mean for platform priority, onboarding depth, feature scope, and MVP decisions.
Software-Specific, Not Generic Marketing
Most persona tools give you demographics and buying habits. This one gives you technical proficiency, device preferences, onboarding patience, and UI complexity tolerance — the attributes that actually change what you build.
The Negative Persona Saves You Months
Defining who your product is NOT for is the fastest way to control scope. "We are not building for enterprise IT teams" eliminates SSO, audit logs, and role-based access from your MVP. That's weeks of development saved.
Jobs to Be Done, Not Just Demographics
Each persona includes JTBD statements: "When [situation], I want [goal], so I can [outcome]." These drive feature prioritization better than age ranges and job titles ever will.
Frequently Asked Questions
The negative persona defines who you're NOT building for. "We're not building for enterprise IT teams" eliminates SSO, audit logs, and role-based access from your MVP. Without a negative persona, every feature request sounds reasonable. The same logic at feature level lives in Feature Prioritization.
Marketing tools give you demographics and buying habits. This gives you technical proficiency, device preferences, onboarding patience, UI complexity tolerance, and current tool stack. Every attribute maps to a build decision — not a marketing campaign. The principle behind tying personas back to the core offer is Find the Core.
JTBD frames user needs as: "When [situation], I want [goal], so I can [outcome]." It includes the trigger and desired end state, making it more actionable than goals alone. These statements drive feature prioritization better than age ranges and job titles, and feed naturally into Feature Prioritization.
They're hypotheses, not facts. The tool flags when personas are assumption-based and recommends validating with 3-5 user interviews. But hypothesis-level personas that change what you build are better than no user model at all. The numbers behind the personas come from Market Sizing.
Concrete build decisions driven by persona attributes. "Mobile-first — primary persona uses phone 80% of the time." "Simple onboarding critical — low tech proficiency." "Must integrate with Slack — both personas live in Slack all day." Each maps to a technical decision — and to a MVP in 6 Weeks build plan.
Where To Next
Next discovery step:Feature Prioritization
Principles behind it:Saying No, Context Over Purity
When you're ready to build:MVP in 6 WeeksPoC in 2 Weeks
Built & Maintained by Varstatt
Varstatt is a one-person product studio run by Jurij Tokarski, product engineer since 2011. These tools are free and open — no signup, no catch.