User personas
Personas written from the product you have, not a slide from 2023.
Create user personas that update when analytics, support, and releases change, so you stop shipping for a person who left the product.
What is happening
Kopilot writes personas from recordings, reviews, and who actually converts. When this week’s metrics move, the profile is supposed to move too, so the next spec is not written for a 2023 slide.
The gap
The primary user lives in a deck. Reality moved. The next PRD did not.
What Kopilot does
Kopilot drafts personas from workspace evidence and keeps them current when the numbers shift.
What you leave with
A living profile the spec can cite, with the date it last changed.
How this use case works
Gather the people signals
Recordings, reviews, support, and who actually converts.
The persona sits beside this week’s numbers, not a 2023 slide.
Write the persona
Jobs, objections, and the screens they actually use.
Jobs and objections are written from recordings and conversion.
Refresh on change
Premium drop-off this week writes back into the profile, not a new slide.
When drop-off moves, the profile is supposed to move with it.
- Evidence-backed profiles
- Updates from metrics and research
- Personas the PRD can name
