.png)
Personas were invented to create empathy at scale.
They worked. For a while. In a world where the person you were selling to had a stable role, a stable team, a stable set of problems, and a stable sense of who they were in relation to those problems.
That world ended.
Not gradually. Not theoretically. Structurally.
The agentic era didn't change what buyers do. It changed who they are in the process of becoming. And no persona model built on role, KPI, pain, objection, and tool has anything useful to say about a transformation that is happening to the buyer in real time — whether they asked for it or not.
The persona isn't outdated because it's old. It's outdated because it was built on a false assumption: that identity is fixed.
The False Assumption at the Center of Every Persona
Open any persona template. You'll find some variation of this:
Name. Title. Team size. Goals. Pain points. Objections. Preferred tools. A quote that sounds like no human has ever actually said.
This is a LinkedIn profile with a stock photo and a fake name.
It tells you where someone sits in the org chart. It tells you what they're measured on. It might tell you what they complain about on bad days.
What it doesn't tell you — what it was never designed to tell you — is what is being asked of them that their current identity cannot deliver.
That's the question the agentic era made unavoidable.
What Changed — And Why It Broke Everything
Every persona assumes the buyer is operating inside a stable system. The CRO runs forecast. The rep needs pipeline. The enablement leader builds programs. The RevOps person maintains the CRM.
Roles. Functions. Stable definitions.
The agentic era introduced a structural rupture into every one of those definitions simultaneously.
Leaders are now managing two incompatible operating systems at the same time.
Humans: emotional, nonlinear, meaning-driven, slow.
AI agents: fast, consistent, tireless, emotionless.
No management tradition prepared anyone for this. No business school curriculum. No coaching framework. No playbook.
The CRO who used to run forecast is now being asked to architect revenue capacity across a hybrid workforce of humans and agents — without any model for what that architecture looks like, what it requires, or who they need to become to build it.
The sales rep who used to own a territory is now drowning not because they are less productive but because the sheer volume of simultaneous context — multiple deals, multiple stakeholders, multiple narratives, multiple moments of truth — has exceeded what any single human can hold.
The enablement leader who spent a career building programs is now watching those programs fail not because the content is bad but because the system they were designed for no longer exists.
This is not a pain point. It is an identity crisis.
And you cannot sell to an identity crisis using a persona that assumes the identity is intact.
The Structural Problem With "Pain Points"
The standard persona says: find their pain point, offer relief.
This worked when the pain was localized. The CRM is too slow. The content is hard to find. The coaching is inconsistent. These are solvable problems that don't require anyone to become a different person.
The agentic era produced a different category of pain entirely.
It's not that something in the system is broken. It's that the system itself — the one that defined what the role meant, what success looked like, what skills were required — is being replaced underneath them.
You cannot relieve that pain with a feature. You can only resolve it by helping them cross from one identity into the next.
Which means your entire GTM motion — your discovery questions, your demo, your champion strategy, your DSR, your close — needs to be built around a completely different question.
Not: what is their pain?
But: who are they in the process of becoming, and what is blocking the transition?
A Persona Is an Identity Transition
This is not a reframe. It is a replacement.
The old model asked: who are they?
The new model asks: who is collapsing, and who is emerging?
Those are structurally different questions. The first produces a profile. The second produces a map — a map of the forces shaping their behavior, the deficits their current identity cannot resolve, the tension between the self they've built and the self the moment requires, the specific unlock that bridges that gap, and the cost of not crossing.
Five layers. One transition.
Layer 1: System Environment. What forces are shaping their behavior right now? Not their stated priorities — the invisible currents. Organizational physics. Emotional load. AI acceleration arriving faster than cultural adaptation. The system environment is what determines what is actually possible, regardless of what they say they want.
Layer 2: Capacity Deficit. What is the gap between what they are being asked to deliver and what their current identity allows? This is not a skill gap. It is a structural gap — the distance between the demands of the new world and the architecture of the old self. Capacity deficits cannot be closed by working harder. They can only be closed by operating differently.
Layer 3: Identity Tension. Who is collapsing? Who is emerging? This is where transformation lives. The CRO who built their identity around running tight forecasts and managing to number is being asked to become an architect of systems that generate capacity. Those are not the same person. The tension between them is real, uncomfortable, and the exact place where your category either lands or doesn't.
Layer 4: Activation Unlock. What specific capability does your category enable that bridges the identity gap? This is not a feature. Features live inside categories. The activation unlock is the thing that makes the identity transition possible — the new way of operating that the old category structurally couldn't provide.
Layer 5: The Stakes. What happens if they evolve? What happens if they don't? Legacy CROs who remain operators will be replaced by architects. Sales reps who remain quota carriers will be outperformed by agentic operators by orders of magnitude. Enablement leaders who remain content librarians will lose their seat at the table — permanently. The stakes are not hypothetical. They are already visible in every company that has run the transition and every company that hasn't.
Three Transitions, Fully Mapped
The CRO: From Operator to Architect
The old persona says the CRO runs forecast, owns revenue, wants predictability, hates surprises, uses dashboards.
This is accurate and useless.
The agentic reality is that the CRO is drowning in incoherence. Their GTM stack is fragmented. Their reps are using AI tools individually, inconsistently, in ways that don't compound. Their forecast is built on gut feel dressed up in spreadsheets. Their pipeline coverage masks execution gaps that no amount of additional pipeline will fix.
The capacity deficit is specific: they cannot create revenue capacity without burning people. The only lever they currently have is headcount. Add reps. Push harder. Raise quota. These levers have diminishing returns and they know it.
The identity tension is Operator versus Architect. The operator manages what exists. The architect designs for what's possible. The operator asks: how do I hit this quarter? The architect asks: what is the maximum revenue this system can produce, and what would it take to build that system?
The activation unlock is Revenue Capacity Design — the ability to look at the equation (Reps × Deals/Rep × Win Rate × ACV) and identify which lever is stuck, which intervention releases it, and how to measure the result with causation rather than correlation.
Legacy CROs fade. Architects rise. The question for your sales motion is not whether the CRO feels pain. It's whether they are ready to become the person who resolves it.
The Sales Rep: From Performer to Agentic Operator
The old persona says the rep needs pipeline, wants clarity, struggles to prep, hates admin.
Also accurate. Also useless.
The agentic reality is cognitive overload, emotional exhaustion, and AI acceleration that has added pressure without adding clarity. Reps are not failing because they are unproductive. They are failing because there are seventeen simultaneous conversations happening and they can hold the context of maybe three.
This is not a speed problem. Giving them a faster email tool doesn't solve it. Giving them a call transcription doesn't solve it. These are productivity interventions applied to a capacity problem.
The capacity deficit is that they cannot scale their preparation, their contextual awareness, or their in-moment intelligence beyond human limits. The deals are there. The buyers are there. The rep cannot be everywhere at once.
The identity tension is Performer versus Agentic Operator. The performer does the work. The agentic operator directs the system that does the work — and shows up to the human moments with everything the system has already prepared. These are not the same person. The transition requires a different relationship with time, with tools, and with what "doing the job" actually means.
The activation unlock is Context Intelligence — the ability to have the right information, the right coaching, and the right content surfaced automatically at the moment of execution, inside the workflow, without hunting.
Agentic reps will not slightly outperform traditional ones. They will operate at a different order of magnitude. The transition is not optional.
The Enablement Leader: From Content Librarian to Revenue Activator
The old persona says the enablement leader builds programs, manages the LMS, creates content, and prays that someone uses it.
This is not a persona. It is a job description for a function that has been structurally underfunded and organizationally undervalued for thirty years.
The agentic reality is that the enablement leader sits at the exact intersection of the two operating systems — humans and agents — and has neither the infrastructure nor the identity to bridge them. They know what the reps need. They cannot deliver it at the moment it's needed. They can prove adoption. They cannot prove causation. And without causation, they get cut first.
The capacity deficit is the inability to connect enablement actions to revenue outcomes. Every CRM has a field for content views. None of them have a field for which enablement intervention changed which deal. That gap is not a data problem. It is an architectural problem — one that cannot be solved inside a system designed for correlation.
The identity tension is Content Librarian versus Revenue Activator. The librarian organizes and delivers. The Revenue Activator identifies which lever is stuck and releases it in the moment the deal is live. Same underlying care for the rep. Completely different architecture. Completely different seat at the table.
The activation unlock is Revenue Proof — causal attribution from enablement action to revenue outcome. Not views. Not completions. Not adoption rates. The specific intervention that moved the specific deal.
When an enablement leader can walk into a budget review and say this coaching intervention on objection handling directly influenced $2.3M in closed revenue last quarter — they are not defending a budget. They are presenting a business case for expansion.
That is a Revenue Activator.
What This Means for How You Sell
If your buyer is in an identity transition, your entire sales motion has to shift.
Discovery is no longer about pain. It's about where the transition is stuck. What forces are shaping their behavior? What does their current identity prevent them from delivering? What have they already tried that failed — and why did it fail structurally rather than executionally?
The demo is no longer about features. It's about showing them the other side of the transition. Not what the product does. Who they become when the product is in place.
Champion activation is no longer about building a business case. It's about equipping your champion to help their colleagues cross the same transition they just crossed. The DSR is not a deal room. It's the activation surface the champion uses to sell the identity shift internally — complete with role plays for pitching to their CFO, their CRO, their IT team, each of whom is in a different stage of their own transition.
And the close is not the end of the sale. It is the beginning of the transformation. What you measure post-close is not adoption. It is how far along the identity transition each stakeholder has moved.
The Diagnostic
Before the next discovery call, ask yourself not what your buyer's pain points are but where they are in the transition.
Are they in the system environment phase — aware that forces are shaping their behavior but not yet able to name the capacity deficit? Then your job is to name it for them.
Are they in the identity tension phase — aware of the gap between who they've been and who they need to become, but paralyzed by it? Then your job is to show them the transition is survivable and who is already on the other side.
Are they in the activation unlock phase — ready to move, looking for the infrastructure that makes the transition real? Then your job is to get out of their way and let the product do the work.
Personas tell you who your buyer is.
Identity transitions tell you where they are in the process of becoming who they need to be.
The first is a profile. The second is a map.
In a stable world, profiles were enough.
The agentic era is not a stable world.
