Skip to the tool

Generate Software User Personas

An AI user persona generator for software: who pays, who uses it, what starts their search, and who it's not for.

User Personas4 questions

Who has the problem, and what you'd build. E.g. a meal planner for couples on different diets.

Who pays for it?
Does the person who uses it pay for it?

A parent paying for a child's app answers No.

How technical is the person who uses it?

It shapes their objections and what to ask them.

Your persona map appears here, weak points named. Free, no sign-up. AI can make mistakes: check before you act.

How It Works

1

Describe Your Idea

One sentence: who has the problem, and what you'd build.

2

Answer 3 Quick Picks

Who pays, whether the person who uses it pays, and how technical they are.

3

Get Your Persona Map, Plus the Pushback

The buyer, beachhead, jobs, who it's not for, and weak points with fixes. Download the PDF or JSON.

Where User Personas Sits in Discovery

Who is it for, and who isn't? User Personas names both for a software product. It needs no other Discovery tool first.

Use this when: You're about to scope features but can't yet say who you're building for.

Who it's for: Founders and product managers scoping a software product.

Personas That Change What You Build

Marketing persona tools often start with a made-up name and a stock photo. This user persona generator starts from jobs to be done and names who it's not for.

Jobs-to-Be-Done Over Demographics

Age and job title change no line of code. A job statement does: "when I get a client inquiry, I want to check availability instantly, so I can respond before they book someone else."

A Negative Persona Is Mandatory

Every result names one group it's not for. "We don't want to exclude anyone" is how products grow SSO, audit logs and admin dashboards before they have ten users.

Frequently Asked Questions

Sketch the person who uses your product by the job they need done, what starts their search and why they'd say no. Not a face on a slide.

The user persona uses the product; the customer persona pays for it. In B2C, often one person. In B2B they split: a support lead uses it, an operations VP pays.

Start with one. Founders with five "primary-ish" personas ship for none. The map names who pays, the group to win first and one group it's not for.

Specific enough to argue with. Made-up example, a dyslexia reading app: a parent pays, the child uses it, a teacher's note starts the search. Not for: schools.

No. It drafts hypotheses from one sentence and 3 picks, searches nothing and marks what it guessed. Ask real people the 3 questions it gives you.

Not by us. Your answers go to the AI for the run, then live only in this tab; a reload clears them. Download the PDF or JSON to keep the result.

Where To Next

Next discovery step:Market & Distribution

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.