User Persona Builds

Persona documents grounded in CRM data, customer interviews, product usage cohorts, and support tickets - not invented from a marketing offsite. Each persona carries Goals · Pains · JTBD · Tools, with a backing data pill so PM sees the cohort behind every claim.

What the managed workflow does

Pulls 4 sources per persona

CRM segment + role mix, transcribed interviews scoped to that segment, product-usage cohort signal, and per-segment support-ticket patterns - every persona claim is anchored to data.

Builds 3 archetype-named personas

The Operator · The Builder · The Founder - archetypes that the team can hold in their head, not 'Persona A · Persona B · Persona C' that nobody uses six months later.

Captures Goals · Pains · JTBD · Tools

Each persona carries the four sections PM and design need - top-2 Goals, top-2 Pains, a single JTBD verbatim, and the tool stack they actually live in.

Updates on signal change

When the CRM segment shifts, when interview themes drift, when usage cohort behavior changes - the persona doc updates with diff highlights, so it doesn't rot in Notion.

3 personas · 4 sections each · backed by 412 interviews

3 PERSONAS · 4 SECTIONS · 412 INTERVIEWS BACKING

Inputs synthesized

CRM segment · firmographic + roleCustomer interviews · transcribedProduct usage cohort · DAU + WAUSupport tickets · per-segment patterns

What lands per cycle

3 personas · archetype-namedGoals · per personaPains · per personaJTBD + tools · grounded in usage

Inputs synthesized

CRM segment. Firmographic + role data - company stage, ARR band, industry, ICP fit. Drives the persona segment line and grounds the demographic claims.
Customer interviews. Transcribed interview corpus scoped per persona - so the JTBD verbatim is from the actual cohort, not a paraphrase.
Product usage cohort. Behavioral cohort per persona - what they actually do in-product, claimed pains checked against observed activation, retention, and feature engagement.
Support tickets. Per-segment ticket patterns surface the chronic pain points - what each persona struggles with at scale, not what one customer mentioned once.

What lands per cycle

3 archetype-named personas. The Operator · The Builder · The Founder - names that travel into the team's vocabulary and stick across cycles.
Goals + Pains. Top-2 each, evidence-anchored, with the source artifact one click away from each line.
JTBD verbatim. Single best-quote articulation of the job each persona is hiring the product to do - pulled from interview transcript with attribution.
Tools + stack. What each persona actually lives in - pulled from CRM enrichment + integration usage signal - so positioning lands inside their workflow.

What you get, every week

Personas that don't rot

Updated on signal change with diff highlights - the persona doc is a continuous reflection of who your customers are, not a six-month-old offsite artifact.

Cross-functional vocabulary

PM, design, marketing, and sales all reference the same archetype names - 'building for The Operator' is a one-liner everyone can hold.

Defensible positioning

Every persona claim is sourced. When marketing asks 'why is this messaging right for The Founder', the answer is the cohort and interviews behind the persona.

See this in your industry