Research & Intelligence
User Persona Builder
Synthesizes qualitative and quantitative research into structured user personas with goals, behaviors, pain points, and jobs-to-be-done. Useful for product and marketing teams aligning on target users. Product managers scoping features, UX designers framing user flows, marketing leads shaping positioning, sales leaders training account reps, founders aligning the team on who they are building for. They either end up as marketing fiction ("Sarah, 34, drinks oat milk lattes") or they get buried in a deck that nobody reads. A good persona is concise, evidence-backed, distinct from adjacent personas, and answers the "what decisions does this change?" question. A structured builder takes whatever raw research is available and produces personas that are useful in design review, sales training, and copy decisions.
One-Time Purchase
$19.99
User Personas — Meridian Analytics
Product: Meridian Analytics — self-serve analytics platform for product teams Research base: 22 customer interviews, 180-response survey, the past 90 days of support tickets, website analytics. Intended audience: Product, marketing, sales Methodology: Behavioral clustering on usage data, validated against interview themes; jobs-to-be-done extracted from interview transcripts and ticket text.
Summary
Headline
Two personas account for ~83% of monthly active accounts and almost all of revenue. The Primary persona — an embedded data analyst on a product team — drives most expansion. The Secondary persona — a product manager who never logs into the analytics tool but consumes its output — is the buyer in roughly 4 out of 5 mid-market deals. A long tail of occasional users (executives, designers) was excluded because no product or copy decision changes when we account for them.
| Persona | Role in buying cycle | Product implication |
|---|---|---|
| Priya — Embedded Data Analyst | Hands-on user | Onboarding must reach value quickly |
| Marcus — Product Manager | Economic buyer | Copy must build trust in data quality |
| Long-tail users | Excluded | Avoid designing for edge-case visitors |
Persona Comparison
Primary Persona
Priya — Embedded Data Analyst
The hands-on user. Drives expansion.
Secondary Persona
Marcus — Product Manager
The consumer. Usually the buyer.
Primary Persona — Priya, Embedded Data Analyst
Goals (in priority order)
Pains
Jobs to be done
In her words
"My job got 40% better the day I could send the PM a link instead of a CSV."
Recommended positioning for Priya
Lead with the metric-layer story and the SQL-or-self-serve false choice. Priya doesn't need her tool sold to her — she needs ammunition for the conversation with her PMs and her manager. Marketing should produce one-page "send this to your PM" assets she can forward without editing.
Secondary Persona — Marcus, Product Manager
Goals
Pains
Jobs to be done
In his words
"I'm not trying to be an analyst. I just want to stop being wrong in front of the CEO."
Recommended positioning for Marcus
Lead with trust, not capability. Marcus doesn't want a more powerful tool; he wants to be confident the number is right. Marketing should emphasize metric governance, audit trails, and "the analyst signed off on this." Product should focus on the dashboard consumption experience — annotations, shareable views, comment threads — over query authoring.
Personas We Considered and Dropped
Why not include execs and designers?
Both groups appear in the data but neither changes any product or copy decision. Executives consume dashboards through Slack and email, not the product. Designers occasionally view dashboards but don't expand or churn accounts. Including them would dilute the focus on the two personas that actually drive growth.
What This Changes
Decisions this persona doc should drive
- Onboarding flow splits into Analyst track and PM track in the first signup step
- Pricing page hero copy speaks to Priya's pain; the second scroll speaks to Marcus's trust concern
- Sales discovery questions reordered to identify which persona is the economic buyer in the first call
- Roadmap quarterly review reviews each major initiative against both personas explicitly
This sample illustrates the skill's output format. Meridian Analytics is a fictional company used recurringly across these sample outputs. Real customer data and research findings are never included in sample outputs.
View full sample →
All sales final. No refunds on digital products.
Includes support for Claude Code, Codex, OpenClaw, and Google Antigravity in the same license.
Also in Customer & Product
Bundle price: $33. Compare this skill with the full workflow bundle or Pro access.
Best for
Product managers and UX designers framing a new feature where the team keeps disagreeing on who the user is, and founders aligning sales, marketing, and product on the same ICP narrative. Most useful when there is real research input — interview transcripts, support tickets, segmented usage data — to ground the personas in evidence.
Not ideal for
Personas built from no research at all — the output becomes marketing fiction (‘Sarah, 34, drinks oat milk lattes’) that nobody trusts or uses. Also a poor fit for highly fragmented audiences with dozens of micro-segments where personas flatten too much variance to drive useful decisions.
Included in this purchase
- Claude Code, Codex, OpenClaw, and Google Antigravity skill files.
- Setup guidance for the right adapter in your workspace.
- One-time license for the purchased skill version.
Setup
Plan for a short copy-and-configure setup in your preferred agent workspace. No custom integration is required for the skill file itself.
Related Skills
$19.99
One-time license
$19.99
One-time license
$19.99
One-time license
Future Updates
This purchase includes the current version of the skill. If you want future adapter updates — meaning compatibility and packaging updates as supported platforms evolve — plus new catalog additions included automatically, upgrade to Pro.