System
/
Memory
/
Persona

Persona

One definition of the people who buy: the roles they play, the pains they carry, the objections they raise and who actually decides. Held as your GTM system's memory, so every rep and every agent reasons from one governed version, and that version improves as deals are won and lost.

Learning from every outcome
Finance VPs are the strongest senior persona
$214/day efficiency, double the $107 baseline
54.0% win rate, $29K ACV, 74-day cycle
Legal VPs convert worst of any senior persona
25.4% win rate across 70 opportunities
$91/day, 15% below the $107 baseline
Upgrade proposedv12v13
LEARNING
The memory upgrades
Memory
Persona
v13
Roles: Finance, Technology, Legal, Operations
Finance VP promoted to primary decision makerv13
Top objection: product and technical fit
Legal VP reclassified as secondary influencerv13
Seniority and function both shape win rate
Approve upgrade to Persona?
The current way > AI added on > AI-native

The moments your personas decide, and who's deciding them

The same definition gets used a dozen times a day, by people and by agents. What changes across these three columns is whether it is a slide each team half-remembers, or one governed version your whole system reasons from and sharpens with every outcome.

01 | The Current Way

02 | AI Added On

03 | AI-Native

A contact gets picked

Close enough on title

The list is built from job titles that look about right. Seniority stands in for influence.

More titles, faster

A data-enrichment tool appends richer title data. It still cannot say who decides.

Chosen by decision role

Contacts picked against the persona version your won deals support, and every rep and every agent works from that same version.

A message gets written

Last year's deck

Pains lifted from an enablement slide, written for a persona nobody has tested since.

Personalised, not relevant

First name, company name, a scraped detail. The argument underneath is unchanged.

Written from approved pains

The message draws on that persona's approved pains and objections, so a junior rep makes the same case a veteran would.

A meeting gets prepped

A profile and a hunch

The rep reconstructs who they are meeting ten minutes before, from whatever is public.

A tidy summary

A generated paragraph about the person. Nothing about what this role blocks or wants.

The system briefs the role

Prep states what this persona decides, what they push back on, and which proof has moved them in deals you already closed.

The buying group gets mapped

One champion, hopefully

Coverage is whoever replied. The missing role surfaces only once the deal is already closing.

Contacts, counted

A contact-listing tool lists everyone at the account. It cannot tell you which seat is empty.

The missing role, named

Coverage is checked against the personas this deal type needs, so an unmapped decision maker gets flagged while there is still time to find them.

The persona turns out wrong

The deck stays wrong

Nobody owns noticing. The persona in the deck is a year out of date, and every team is still pitching to it.

Wrong, personalised

The message is personalised with a first name and a company name. The definition underneath is still wrong.

Outcomes propose the new version

Won and lost deals show which roles decided. The updated persona takes effect once marketing and sales leadership have approved it.

Referenced by

Capabilities that reason with this memory

Sales

Meeting Prep

Active
Brief built for tomorrow's Acme renewal call
Pulled live deal state 1 hour before the meeting
Flagged two deals with no next step
Both stalled 14+ days since last activity
New stakeholder added to the buying group
CFO joined — added to the account brief
+
Objection playbook matched to the call
Pricing pushback: three proven responses surfaced
2 briefs ready for your review before 9am
SEE HOW IT WORKS

Sales

Qualification

Active
Fresh discovery call read against your criteria
Nine criteria checked, not the boxes the rep filled
Champion confirmed, decision process still inferred
Two answers proven, one assumption flagged for evidence
Three gaps named, with the questions that close them
Queued for the next call, before the deal moves stage
+
Hold at Discovery recommended, reason on record
Sufficiency not met; the manager sees the same evidence
Know which deals are real, and what to ask next
SEE HOW IT WORKS

Prospecting

Propensity

Active
Three accounts just moved into in-market
New funding and hires in the roles that feel this pain
Meridian Logistics jumps to the top of the list
Same profile as your last five closed-won deals, and hiring for the gap you fill
A contact at Northbridge is showing real intent
Visited pricing and a comparison page twice this week
+
Your ranked account list, ready for outreach
Who to call first, and the reason why
Priority accounts, ranked, before you start prospecting
SEE HOW IT WORKS
SEE ALL CAPABILITIES
Used by

Skills that use this memory

No items found.
SEE ALL SKILLS
The Platform

One system that understands, decides, acts and learns.

Every GTM signal flows through an AI-native operating layer into a system that runs on the surfaces your team already uses.

Explore the GTM System →
GTM Data & Knowledge
CRM · Emails · Calls · Marketing · Product · Support · Documents · Research
AI-Native Operating Layer
Context · Memory · Skills · Agents · Decision Traces
AI-Native GTM System
Understand
ICP Fit
Deal & Account State
Stakeholders
Risk & Health
Decide
Targeting
Pipeline & Forecast
Campaign Planning
Renewals & Expansion
Act
Outreach & Follow-up
Meeting Prep
CRM Updates
Alerts & Escalation
Learn
Upgrade ICP
Upgrade Messaging
Upgrade Playbooks
Upgrade Forecasting
Surfaces
CRM · Slack · Teams · ChatGPT · Claude · MCP · API
Output
Briefings · Artifacts · Alerts · Recommendations · Approvals · Actions

SEE WHY REVOPS + MARKETING LEADERS CHOOSE REVENUE LABS

The GTM teams that learn fastest will win. Build yours a system that learns.

An advantage competitors cannot buy back: years of success and failure, codified.

FAQ

What buyers ask

If it's not here, we'll answer it live.

Talk to us
What is a persona memory in an AI-native GTM system?

One approved definition of the people who buy: their role in the decision, their pains, motivations and objections, held as a versioned record. Unlike a note saved in a chat tool, it is systemic: every rep, capability and agent reads the same version, and won and lost deals feed back into it.

How is this different from title-based personalisation?

A job title tells you what someone is called, not what they decide. Persona memory holds buying role, responsibilities, pains, motivations, objections and buying context, so a message is built from what that persona cares about rather than from their signature block.

How should AI use buyer personas?

It should reason against them, not regenerate them. Agents read the approved persona version when selecting contacts, drafting a message or mapping a buying group, and every output can be traced back to the persona logic that produced it.

How do personas improve from sales outcomes?

Won and lost deals show which roles drove decisions and which objections really mattered. Persona Analysis surfaces where the current definition diverges from those outcomes and proposes an update, with the evidence attached.

Who approves changes to a persona?

You do. The system proposes; a person approves. Nothing changes until someone signs off, and edge cases stay a human judgement, which is what keeps the definition trustworthy enough for every team to work from.