Persona Library
Community-sourced UX research

Who actually uses these products,
and what made them stay.

Deep persona profiles for the tools that run modern work. Community-validated. Exportable. Open for contribution.

2
attioAPP-193
4 comments

The Attio Revenue Operations Lead

A revenue operations lead or head of sales operations at a Series A–C startup who chose Attio because legacy CRMs either cost too much (Salesforce) or think too rigidly (HubSpot). They build custom objects, design pipeline views, and create automations that match how their team actually sells — not how a CRM template assumes they sell. They think in data models, not contact records. They've realized that a CRM is only as good as the data in it, and their primary job is making sure the data stays clean and the team actually uses the tool.

Aha

It happened mid-workflow — the company is expanding from SMB to mid-market sales.”

riveAPP-190
4 comments

The Rive Interactive Animation Designer

A motion designer or creative developer who uses Rive to create animations that aren't just decorative — they're interactive. They build loading indicators that respond to progress, toggle switches that morph between states, onboarding illustrations that react to user input, and game-like UI elements. They think in state machines: idle, hover, active, success, error. They chose Rive because After Effects exports video, Lottie exports playback, but Rive exports interactive, state-driven animations that respond to runtime input.

Aha

Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about the state machine editor has a learning curve, especially for designers coming from timeline-based tools in two weeks.”

Recognize yourself in one of these?

Every field in every persona can be confirmed, corrected, or extended by real users. Your lived experience is more accurate than any researcher's archetype.

+ Contribute to a persona