Overview
What are Personas?
A Persona is a detailed profile of one of your Ideal Buyer Personas (IBP): the responsibilities they carry, the KPIs they answer to, the frustrations that get in their way, the value proposition that lands with them, and the objections they tend to raise.
Personas are not just job titles. They are organised by department or function, and they capture decision-making influence, seniority, and the other attributes that shape how someone buys.
The point of a Persona is practical. When your Agents know exactly who they are writing to, your Contact discovery gets sharper, your qualification gets more accurate, and your outreach reads like it was written for one specific person rather than a list.
What makes up a Persona?
This is the part that trips people up, so it is worth being clear. A Persona is not generated from a single source. It is built by combining several inputs you have already defined during your deployment, and it then feeds several things downstream.
Here is the full picture:
The four inputs that define a Persona
1. The base Persona card. This is the starting point: a definition of the ideal buyer for this role, by definition. It describes who this person is before any of your company-specific context is layered on.
2. Your value proposition. The industries you serve, the verticals you sell into, and the challenges and pains your product or service actually addresses. This is what turns a generic role into a buyer who cares about your offering.
3. Your ecosystem and verticals. Each Persona is assigned to a vertical, and it inherits that vertical's fleshed-out challenges, pains, and KPIs. This is why the same job title can look different across two verticals: the context around them is different.
4. Manual input (optional). Each Persona card has a manual input field where you can add custom instructions. This is genuinely optional. Most customers leave it empty, because the three inputs above already produce a rich, accurate Persona. Reach for it only when you have a specific nuance the base definition cannot capture on its own.
Those four combine into a single per-vertical Persona: the finished profile you see on the Persona page, with its responsibilities, KPIs, frustrations, value props, and objections all fleshed out.
💡 If a Persona feels thin, the fix is rarely the "manual input" field
It is usually worth checking your value proposition and vertical definitions first, since those provide most of the context
What a Persona drives
Once defined, the Persona feeds three things:
Enriched Contact records: the Persona is what Contact Finder uses to discover the right people, and what Contact Qualification uses to score your existing Contacts as IBP Yes/No.
The Digital Twin: your AI strategy assistant draws on the Persona to reason about a specific Contact.
Plays: when a Play is drafted for a Contact, the Persona is what lets the copy flex to whoever it is being written for.
A common question: do Contact research Agents feed the Persona?
No, and this is worth understanding clearly.
You may have built one or more Contact research Agents to learn something specific about your Contacts, for example whether they have any active AI initiatives. These Agents are useful, but they are supplementary. Their output lands on the Contact record as enrichment. It does not feed back into the Persona definition.
So if you have built a Contact research Agent for your own purposes, that is completely fine. It sits alongside the Persona rather than inside it. The Persona itself is defined by the four inputs above.
When should I use Personas?
When you want to learn the responsibilities, KPIs, and pain points of a target Persona, especially within a specific industry/vertical.
When you need the specific value proposition for a specific Persona, at a glance
When you want to prepare for, or refresh on, objection handling
When you are onboarding to a new role, vertical, or Persona
Step-by-Step Guides
Accessing Personas in the Playbook
Use this process to learn about your target personas and prepare for outreach.
Navigate to Playbook >> Personas.
Select the Persona you want to learn about.
Review the Persona card, which includes:
Responsibilities of the persona
KPIs they care about
Common frustrations and pain points
The value proposition tailored for this persona and vertical
Typical objections and recommended objection handling strategies
Calibrated Questions
Tabs on the Persona page
Summary
For a quick refresher, read summary.
It's a high-level overview of the persona’s responsibilities, KPIs, frustrations, value propositions, objections, and how to address them.
Persona mapping
An extensive breakdown of the persona’s responsibilities, KPIs, frustrations, and value propositions. This is used by AI agents to further personalize specific contact research.
Responsibilities
The responsibilities are directly linked to the identified pain points, ensuring that the persona’s role and duties are clearly defined in relation to their challenges.
KPIs
The persona's KPIs are generated based on their responsibilities and pain points. These KPIs reflect the metrics by which the persona’s performance is measured, offering insights into what drives their decision-making and priorities.
Frustrations
Frustrations represent the challenges and obstacles that hinder the persona from achieving their KPIs. Understanding these frustrations is vital for crafting messages that address these pain points directly.
Value props
The value proposition is generated by an agent who assumes the persona's perspective, aligning the company's value proposition with the persona’s pain points, responsibilities, KPIs, and frustrations. This approach ensures a customer-centric value proposition tailored to each persona.
Objections/Concerns
These are potential objections or concerns that the persona might have are generated next. These are based on the previously identified fields and are essential for anticipating and addressing any potential barriers to engagement.
Objection addressing
With the same customer-centric approach as the value props, the persona agent suggests ways to address these objections or concerns, ensuring that responses are aligned with the persona’s needs and the overall value proposition.
Buyer journey info
This represents a detailed journey of the persona when procuring a solution similar to the company’s offerings based on the content of the value props field. It includes use cases that might trigger the persona to seek out a solution, providing valuable insights into the decision-making process.
Buyer journey use cases
The buyer journey use cases info represents the different use cases that could trigger the persona to look for a solution similar to the company’s offering based on the content of the value props field.
Pain points
A focused list of the persona’s main challenges and pain points.
Sales coach
Shows Calibrated Questions for this persona.
A calibrated question is an open-ended question salespeople use to engage prospects in a way that:
Shows deep understanding of their responsibilities, KPIs, pain points, and frustrations
Assumes they already have a plan in place (so they don’t feel cornered or judged)
Positions you as an industry peer, not “just another salesperson”
Lowers the prospect’s zone of resistance and encourages open dialogue
Why it works:
Builds credibility and trust by describing the challenge precisely
Makes the prospect feel respected (they’re not being told they’re doing something wrong)
Encourages them to share openly about their current approach and challenges
Plays
See which sales plays are attached to this persona. You can view play instructions and edit the play if needed.
Company profile
Read about the business description of the vertical this persona belongs to.
Also, you can see here what qualification & research agents are used for this vertical.
FAQ
What is a Persona card in Evergrowth?
A profile of a target buyer: their responsibilities, KPIs, frustrations, value proposition, and common objections. It is what helps you, and your Agents, tailor outreach and improve engagement.
What defines a Persona?
Four things combine into each Persona: the base Persona card, your value proposition, your ecosystem and vertical definitions, and an optional manual input. Most customers never need the manual input, because the first three already produce a rich Persona.
Do my Contact research Agents feed into the Persona?
No. Contact research Agents produce supplementary enrichment that lands on the Contact record, not on the Persona. They sit alongside the Persona rather than inside it. The only Persona-level settings of that kind are language and location.
How do I access Persona cards in Evergrowth?
Go to your verticals and expand the Personas menu. From there you can select and review any Persona relevant to your target audience.