---
title: User Persona Generator @ Varstatt Discovery
url: https://varstatt.com/discovery/user-personas
description: Generate user personas tailored for software development. Technical proficiency, platform preferences, and development implications included.
section: AI Discovery Tools (https://varstatt.com/discovery)
step: 4 of 8
previous: Market Sizing (https://varstatt.com/discovery/market-sizing)
next: Feature Prioritization (https://varstatt.com/discovery/feature-prioritization)
---
# User Persona Generator
Generate user personas tailored for software development. Technical proficiency, platform preferences, and development implications included.

## Why Use This Tool

### 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.

## How It Works

1. **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.
2. **Deep-Dive on Your Primary User** — We'll explore their tech proficiency, daily workflow, current tools, device preferences, and pain points in detail.
3. **Define Secondary and Negative Personas** — Identify who else uses the product differently, and — critically — who you're explicitly not building for.
4. **Get Development Implications** — See what your personas mean for platform priority, onboarding depth, feature scope, and MVP decisions.

## FAQ

### Why do I need a negative persona?

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](/discovery/feature-prioritization).

### How it differs from marketing persona tools?

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](/principles/discovery/find-the-core).

### What are Jobs to Be Done (JTBD)?

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](/discovery/feature-prioritization).

### Are AI-generated personas reliable?

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](/discovery/market-sizing).

### What are development implications?

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](/production/mvp-in-6-weeks) build plan.
## Usage

This tool is an AI-guided chat — it requires a browser to use.

Prefill the conversation with your project context via URL:

- `https://varstatt.com/discovery/user-personas?context=I+am+building+...` (max 2000 chars)

Context carries forward across all discovery steps automatically once set.