Mihaela Cicvaric | September 4, 2026 | 19 min read
Mihaela Cicvaric | September 4, 2026 | 19 min read
Ready to launch?
Convert strategy into pipeline
Launch your first outbound campaign with verified leads, AI sequences, and multichannel outreach from one platform.
Claude Skills for Sales: Contact-Level Persona Targeting for Outbound in 2026
What is a persona definer for outbound sales
A persona definer is a framework, and in this case a Claude Skill, that identifies which specific contacts you should target within accounts that already fit your ideal customer profile. It’s the tool that answers the question every rep asks before sending a single email: who, exactly, should I be talking to?
Search “persona definer” and you’ll mostly find dictionary entries about literary characters or social facades. That’s not what we’re covering here. In outbound sales, a persona definer works at the contact level, helping you decide which role to target once you already know which companies matter.
- Buyer persona (sales context): a profile of the person at a target company most likely to buy, respond, or champion your product
- Persona definer (Claude Skill): an AI-powered framework that outputs a prioritized list of target roles, their pain points, and a recommended order of outreach
The skill itself is open-source and connects to lemlist MCP, so once you’ve defined your personas, you can move straight into lead search and campaign execution without switching tools.
Why contact-level persona targeting outperforms account-level outreach
Most outbound teams stop at the account level. They find companies that fit, then reach out to whoever pops up first in a search or CRM export. That first contact is rarely the right one, and it’s usually the reason a good ICP still produces flat reply rates.
Contact-level targeting means picking the person, not just the company, based on role, decision power, and how closely they feel the pain your product solves. Skip this step and even a well-built list lands in inboxes where no one has a reason to care.
Here’s what tends to happen once teams add persona definition before building lists: messaging becomes specific to what that person deals with day to day, and replies go up because the recipient recognizes their own problem in your first line, not just their company name.
ICP vs buyer persona for outbound
These two terms get used interchangeably, but they filter different things. Mixing them up is one of the more common reasons sequences underperform.
Company-level targeting with ICP
Your ICP (ideal customer profile) defines which companies deserve your attention. It filters by firmographic data: industry, headcount, revenue, tech stack, geography. If a company doesn’t clear this filter, no contact there belongs in your pipeline, no matter how good their title looks.
Contact-level targeting with buyer personas
A buyer persona narrows things further to the person at those companies you actually contact. It filters by role, seniority, decision authority, and pain alignment. Two people at the same ICP-fit company can respond completely differently depending on whether your product solves their problem or someone else’s.
When you need both working together
ICP without persona gets you the right company and the wrong inbox. Persona without ICP gets you the right title at a company that was never going to buy. You need both layers running at once.
Layer | What it filters | Example criteria | Question it answers |
|---|---|---|---|
ICP | Companies | Industry, headcount, tech stack, geography | Which companies fit? |
Buyer persona | Contacts | Title, seniority, pain points, decision role | Who at those companies do I reach? |
lemlist’s lead database lets you apply both filters at once, so ICP narrows the companies and persona filters narrow the contacts, all in one search.
Data points that make a buyer persona actionable for sales
A persona only helps if your team can act on it. A profile with a stock photo and an invented name like “Marketing Mary” tells an SDR nothing about what to write. Here’s what actually belongs in a sales-ready persona.
Job title, seniority, and reporting structure
“VP of Sales” and “Director of Sales” often sit in the same department but respond to different framing. A VP tends to care about pipeline velocity and revenue targets, while a Director often cares more about rep productivity and tool consolidation. Title also tells you whether this person can approve spend or has to escalate.
Pain points and buying triggers
Pain points shape what you say. Buying triggers, events like a new funding round, a leadership change, or a relevant job posting, shape when you say it. Mapping each persona’s top pain points alongside their triggers helps you time outreach instead of guessing.
Decision role in the buying committee
Not every contact plays the same role in a purchase, so it helps to tag each persona accordingly:
- Champion: believes in your product and sells internally on your behalf
- Decision-maker: holds budget authority and final sign-off
- Influencer: shapes the evaluation but can’t approve spend
- Blocker: can slow or stop a deal, often from procurement or legal
Champions get material they can forward internally. Decision-makers get ROI framing. Influencers get technical proof.
Preferred outreach channel
Some personas respond well to email, others to LinkedIn, others to a phone call. Channel preference belongs to the persona, not the campaign default. lemlist’s enrichment agents pull LinkedIn context and company data to populate these fields automatically, so you’re not researching each contact by hand.
How to identify and prioritize buyer personas in target accounts
Defining personas works best as a repeatable process, not a one-off brainstorm.
1. Map every role involved in the purchase decision
Start by listing every title that touches your buying process. Pull from closed-won deals: which titles showed up in those conversations, and who replied first? Cast wide before you narrow.
2. Score personas by decision power and pain alignment
Not every persona carries equal weight. A simple scoring rubric helps:
- Decision power: can this person approve budget without escalating?
- Pain alignment: does this person feel the problem daily?
- Champion likelihood: has this title historically advocated for products like yours?
- Reachability: can you reliably find verified contact info?
3. Assign each persona to a campaign tier
Once scored, group personas into tiers. Tier 1 gets multichannel sequences with manual personalization. Tier 2 runs automated sequences across fewer channels. Tier 3 gets email-only nurture, though even Tier 3 contacts can turn into champions later. lemlist’s multichannel campaign builder maps these tiers directly to sequence logic, so each one runs its own cadence from a single campaign.
How the persona definer Claude Skill works
The persona definer is a Claude Code skill, built by lemlist and listed on ColdIQ’s skill directory, that identifies and ranks buyer personas at the contact level.
What the skill outputs
Give it your product description and ICP context, and it returns target titles, decision power tags, and a pain hierarchy, essentially a targeting brief rather than a generic template. You can trigger it by asking Claude things like “who should I email” or “should I target VPs or Directors.”
How to install and run the skill
Getting it running takes about two minutes.
- Run the install command:
npx skills add l3mpire/claude-skills/persona-definer - Open Claude Code in your project; the skill is detected automatically
- Ask Claude a targeting question, or let it apply the skill when relevant
Pair it with lemlist MCP and you can move from persona map straight into lead search, enrichment, and campaign launch without leaving the workflow.
How to turn defined personas into persona-based outbound campaigns
A persona map is only a document until you turn it into lists, copy, and sequences.
Build persona-filtered lead lists
Use your defined titles and seniority levels as search filters, with each list mapped to one persona and one tier. lemlist’s contact database (over 450 million contacts) lets you apply ICP and persona filters together, returning verified emails and phone numbers that match both.
Match messaging to each persona’s pain hierarchy
Each persona’s top pain point becomes your opening line, and their buying trigger becomes your CTA hook. A single generic template across every contact is usually the fastest way to get ignored, even when the small differences (strategic language for a VP, tactical language for a manager) seem minor.
Launch multichannel sequences by persona tier
Higher-priority personas get more touches across more channels; lower-priority ones get lighter sequences. Every sequence should reflect the persona’s preferred channel. lemlist runs all these tiers from one campaign workflow with a unified inbox, so you’re not juggling separate tools for one outbound motion.
Validate personas with intent signals and engagement data
Personas start as hypotheses. Real data is what confirms or corrects them.
- Intent signals: job changes, tech stack shifts, funding rounds, and new hires show which personas are actively in-market right now. lemlist’s Intent Signal Agents track these events and add matching leads to campaigns automatically, with messaging tied to the specific signal detected.
- Campaign engagement data: open and reply rates by persona reveal which definitions actually hold up. If your Tier 2 persona consistently outreplies Tier 1, that’s worth promoting them. If an expected title never converts, it’s worth revisiting the definition. A quarterly review is a reasonable minimum.
Start building contact-level persona targeting today
The workflow, in short: define your ICP, define personas within those accounts, prioritize by decision power and pain alignment, build filtered lists, launch persona-based campaigns, and validate with engagement data.
The persona definer skill gives you the targeting brief. lemlist gives you the execution layer. Together they turn what used to be hours of manual research into a few minutes of setup.
👉 Start a 14-day free trial, no credit card required, cancel anytime.
FAQs about persona targeting for outbound sales
How many buyer personas does an outbound sales team typically define?
Most teams do well with two to five personas per ICP segment. Too many dilutes messaging and complicates campaign management, while too few leaves gaps in the buying committee.
Can you use the persona definer Claude Skill without lemlist MCP?
Yes. The skill runs as a standalone tool in any Claude Code project. Connecting it to lemlist MCP adds execution, like lead search and campaign launch, but isn’t required for persona definition itself.
What is the difference between a buyer persona and a user persona in B2B sales?
A buyer persona profiles the person who approves or champions a purchase. A user persona profiles the person who uses the product day to day. Outbound targeting relies on buyer personas, since you’re reaching the person with buying authority or internal influence, not necessarily the end user.
How often do outbound teams update their buyer personas?
A quarterly review works for most teams, or sooner if you notice a consistent shift in which titles reply or close. Stale personas tend to show up as declining reply rates before anyone notices why.
What is a persona definer
A persona definer is a framework that identifies and ranks the specific people you want to reach at your target accounts. It identifies and prioritizes buyer personas at the contact level for outbound targeting, answering questions like “who should I email,” “what role to target,” and “who is the decision maker.” (Persona Definer - Claude Code Skill | ColdIQ)
If you’ve searched for “persona definer,” you’ve probably seen dictionary results about public identities and literary narrators. Merriam-Webster defines persona as “a character assumed by an author in a written work” or “an individual’s social facade.” (PERSONA Definition & Meaning - Merriam-Webster) That’s not what sales teams are looking for.
In outbound sales, a persona definer answers a very specific question: once you know which companies to target, which person at each company do you contact first? It’s the bridge between account-level targeting and actually getting a reply.
The persona definer is designed to be used after your ICP is defined, because ICP determines which companies to pursue and persona determines which person at those companies to reach. (Persona Definer - Claude Code Skill | ColdIQ)
Why contact-level persona targeting outperforms account-level outreach
Most outbound teams identify companies that fit their ICP, then reach out to whoever shows up first in a search. The first contact at a company is rarely the right one. A well-defined ICP with sloppy persona targeting means your email lands in an inbox where no one feels the pain your product solves.
When you define personas before building lists, two things change. First, your messaging becomes specific to the problems that person actually experiences daily. Second, your reply rates go up because the recipient recognizes themselves in the email, not just their company.
Tip: Before you write a single email, ask yourself: “Does the person receiving this have the authority, the pain, or the motivation to act?” If the answer is unclear, your persona targeting is too loose.
How ICP and buyer persona work together
These two terms get used interchangeably, but they filter different things. Confusing them creates a targeting gap that wastes sequences and burns sender reputation.
Company-level targeting with ICP
Your ICP (ideal customer profile) defines which companies to sell to. It filters by firmographic data: industry, employee count, revenue, tech stack, geography. Think of it as the account-level gate. If a company doesn’t pass your ICP filter, no contact at that company belongs in your pipeline.
Contact-level targeting with buyer personas
A buyer persona defines which person at those companies to reach. It filters by role, seniority, decision authority, and pain alignment. Two people at the same ICP-fit company can have completely different responses to your outreach depending on whether your product solves their problem or their colleague’s.
Layer | What it filters | Example criteria | Question it answers |
|---|---|---|---|
ICP | Companies | Industry, headcount, tech stack, geography | “Which companies fit?” |
Buyer persona | Contacts | Title, seniority, pain points, decision role | “Who at those companies do I reach?” |
You can apply both layers simultaneously in lemlist’s lead database. ICP filters narrow the companies, persona filters (role, seniority, function) narrow the contacts, and you get a ready-to-sequence list in one step.
Data points that make a buyer persona actionable
A persona is only useful if your team can act on it. A two-paragraph profile with a stock photo and a made-up name (“Marketing Mary, age 34, loves yoga”) does nothing for an SDR writing a cold email. Here’s what actually belongs in a sales-ready persona.
Job title, seniority, and reporting structure
“VP of Sales” and “Director of Sales” often sit in the same department but respond to different value propositions. The VP cares about pipeline velocity and revenue targets. The Director cares about rep productivity and tool consolidation. Title also tells you whether this person can approve spend directly or will escalate to someone above them.
Pain points and buying triggers
Pain points determine what you say. Buying triggers determine when you say it. A buying trigger is an event (new funding round, leadership change, job posting for a relevant role, tech stack migration) that signals the persona is actively looking for a solution. Map each persona’s top pain points alongside the triggers that indicate urgency.
Decision role in the buying committee
Not every contact plays the same role in a purchase. It helps to tag each persona with one of four roles:
- Champion: believes in your product and sells internally on your behalf
- Decision-maker: has budget authority and final sign-off
- Influencer: shapes the evaluation but can’t approve spend
- Blocker: can slow or kill the deal, often in procurement or legal
Each role gets different messaging. Champions get enablement material they can forward. Decision-makers get ROI framing. Influencers get technical proof points.
Preferred outreach channel
Some personas respond well to email, others to LinkedIn, others to phone calls. Channel preference is a persona attribute, not a campaign default. Assigning channels per persona (rather than one cadence for everyone) typically improves response rates because you’re reaching people where they already pay attention.
lemlist’s enrichment agents pull LinkedIn context and company data to help populate these fields automatically, so you’re not manually researching each contact.
How to identify and prioritize buyer personas
Persona definition is a workflow, not a brainstorming session. Here’s how to move from a blank page to a prioritized persona map you can actually hand to your sales team.
1. Map every role involved in the purchase decision
Start by listing all titles that touch the buying process for your product. Pull from your closed-won deals: which titles appeared in those conversations? Which title initiated the first reply? Cast wide first, then narrow.
2. Score personas by decision power and pain alignment
Not every persona carries equal weight. Score each one on a simple rubric:
- Decision power: can this person approve budget without escalation?
- Pain alignment: does this person feel the problem your product solves on a daily basis?
- Champion likelihood: has this title historically responded to and advocated for your product?
- Reachability: can you reliably find verified contact info for this persona?
3. Assign each persona to a campaign tier
Once scored, group personas into tiers. Tier 1 personas get multichannel sequences with manual personalization (email, LinkedIn, calls). Tier 2 gets automated sequences across fewer channels. Tier 3 gets email-only nurture. Each tier reflects priority, not importance. Even Tier 3 contacts can become champions later.
lemlist’s multichannel campaign builder lets you map these persona tiers directly to sequence logic, so each tier runs a different cadence from the same campaign.
How the persona definer Claude Skill works
The persona definer is a Claude Code skill that identifies and prioritizes buyer personas at the contact level for outbound targeting. (Persona Definer - Claude Code Skill | ColdIQ) It’s open-source, built by lemlist, and available on ColdIQ’s skill directory.
What the skill outputs
The skill outputs target titles, decision power tags, and pain hierarchy. (Persona Definer - Claude Code Skill | ColdIQ) You provide your product description and ICP context, and the skill returns a ranked list of personas with recommended outreach order. Think of it as a targeting brief, not a generic template.
You can trigger it by asking Claude questions like “who should I email,” “define buyer persona,” “what role to target,” or “should I target VPs or Directors.” (Persona Definer - Claude Code Skill | ColdIQ)
How to install and run the skill
Getting started takes about two minutes:
- Run the install command in your terminal:
npx skills add l3mpire/claude-skills/persona-definer - Open Claude Code in your project. The skill will be automatically detected. (Persona Definer - Claude Code Skill | ColdIQ)
- Claude will automatically use the skill when relevant, or you can explicitly ask for it. (Persona Definer - Claude Code Skill | ColdIQ)
The skill pairs with lemlist MCP for end-to-end execution. Once you have your persona map, you can move directly into lead search, enrichment, and campaign launch without switching tools or tabs.
How to turn defined personas into outbound campaigns
A persona definition is a targeting document until you translate it into lists, copy, and sequences. Here’s how that translation works.
Build persona-filtered lead lists
Use your defined titles and seniority levels as search filters. Each lead list maps to one persona and one campaign tier. lemlist’s 450M+ contact database lets you apply these filters directly, so you get verified emails and phone numbers on leads that match both your ICP and persona criteria.
Match messaging to each persona’s pain hierarchy
Each persona’s top pain point becomes the opening line of your email. Their buying trigger becomes the CTA hook. Writing one generic template for all contacts is the fastest way to get ignored. Even small differences in framing (strategic language for VPs, tactical language for managers) change how the message lands.
Launch multichannel sequences by persona tier
Higher-priority personas get more touches across more channels. Lower-priority personas get lighter sequences. Every sequence reflects the persona’s preferred channel. lemlist lets you run all of these tiers from a single campaign workflow with a unified inbox, so you’re not managing five tools to execute one outbound motion.
Validate personas with intent signals and engagement data
Personas are hypotheses until real data confirms or contradicts them. There are two ways to validate.
Intent signals like job changes, tech stack shifts, funding rounds, and new hires confirm which personas are actively in-market right now. lemlist’s Intent Signal Agents track these events and automatically add matching leads to campaigns with messaging personalized to the specific signal detected.
Campaign engagement data reveals which persona definitions are actually accurate. If your Tier 2 persona consistently gets higher reply rates than Tier 1, promote them. If a title you expected to convert never replies, revisit the persona definition. Review these patterns quarterly, at minimum.
Start building contact-level persona targeting today
The workflow is straightforward: define your ICP, define personas within those accounts, prioritize by decision power and pain alignment, build filtered lists, launch persona-based campaigns, and validate with real engagement data.
The persona definer Claude Skill gives you the targeting brief. lemlist gives you the execution layer. Together, they compress what used to take hours of manual research into a few minutes.
👉 Start a 14-day free trial — no credit card required, cancel anytime.
FAQs about persona targeting for outbound sales
How many buyer personas does an outbound sales team typically define?
Most teams perform best with two to five personas per ICP segment. Defining too many dilutes your messaging and overcomplicates campaign management. Too few leaves gaps in your buying committee coverage.
Can you use the persona definer Claude Skill without lemlist MCP?
Yes. The persona definer skill runs in any Claude Code project as a standalone skill. Connecting it to lemlist MCP adds execution capabilities (lead search, enrichment, campaign launch) but is not required for persona definition itself.
What is the difference between a buyer persona and a user persona in B2B sales?
A buyer persona profiles the person who approves or champions the purchase. A user persona profiles the person who uses the product daily. In outbound, buyer personas drive your targeting because you’re trying to reach the person with buying authority or internal influence, not necessarily the end user.
How often do outbound teams update their buyer personas?
Review personas quarterly or whenever you notice a consistent shift in which titles reply, book meetings, or close. Stale personas lead to misaligned messaging and declining reply rates over time.
Content Marketing Manager @lemlist
Share this post