Updated September 28, 2026 | 12 min read
Updated September 28, 2026 | 12 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.
Persona Definer: The Free Claude Skill for Contact-Level Outbound Targeting (2026)
Last week I watched a rep send a perfectly written cold email to a CFO. The pitch was about developer productivity tooling. The CFO had zero reason to care, and the email died in silence. The company was a fit. The person was not.
That gap, right company but wrong inbox, is where most outbound campaigns quietly fail. I’ve seen it happen dozens of times, and fixing it always comes down to the same thing: defining who you should reach at a company before you hit send.
In this post, I’ll show you exactly how to build contact-level persona targeting for outbound using a free Claude Skill, and how to connect that targeting directly to lead search and campaign execution in lemlist (rated 4.6/5 across 2,000+ reviews on G2 and other platforms).
Why most outbound lists still target the wrong person
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.
A buyer persona (in a sales context) is a profile of the person at a target company most likely to buy, respond, or champion your product. A persona definer, specifically the Claude Skill we’ll walk through, is 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. lemlist’s own outbound-campaign-architect skill, for example, benchmarks sequence design against empirical lemlist data from hundreds of thousands of campaigns (GitHub - l3mpire/claude-skills · GitHub), and the pattern is consistent: contact-level specificity lifts reply rates more than any copywriting tweak alone.
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 built these as paired tools. The Claude Skills library covers ICP definition, list building, copywriting, campaign design, CRM hygiene, and more (GitHub - l3mpire/claude-skills · GitHub). The ICP Definer skill defines and prioritizes which companies to target; the persona definer skill (covered below) defines which people at those companies to reach. Use them in sequence: ICP first, then persona.
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.
👉 Already know your ICP? Start a 14-day free trial to build persona-filtered lead lists now.
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.
But knowing the title tells you nothing without knowing what that person is measured on. That’s where pain points come in.
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.
Still, two people with the same title and the same pain point can play completely different roles in a purchase decision. I’ve watched a Director of Ops champion a deal while a VP of Ops in the same org tried to block it. So you need to know where each persona sits in the buying committee.
Decision role in the buying committee
Not every contact plays the same role in a purchase, so it helps to tag each persona accordingly.
A champion believes in your product and sells internally on your behalf. A decision-maker holds budget authority and final sign-off. An influencer shapes the evaluation but can’t approve spend. A 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.
Once you know the role, the last question is how to actually reach that person. And the answer varies by persona, not by campaign.
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 you rank them.
Ask four questions for each persona. Can this person approve budget without escalating? Does this person feel the problem daily? Has this title historically advocated for products like yours? Can you reliably find verified contact info for them?
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.
4. Re-score personas quarterly using engagement data
Personas decay. The title that replied well six months ago may not reply the same way today. Set a quarterly review to compare reply rates and conversion rates by persona. If your Tier 2 persona consistently outreplies Tier 1, promote them. If an expected title never converts, revisit the definition.
Before the skill: other ways teams build buyer personas
Not every team uses a Claude Skill for this. Some approaches are worth knowing, if only to understand what the skill replaces.
Stakeholder interviews with existing customers remain one of the most reliable ways to learn who actually drives purchase decisions. If you have five closed-won accounts, ask the AE who they talked to first, who pushed the deal forward, and who almost killed it. Spreadsheet-based scoring, where you manually list titles and rate them on decision power and pain alignment, works for small teams that run fewer than a few hundred outbound contacts per month. Generic persona-builder templates (HubSpot’s free tool, Xtensio, and similar) produce a structured profile, but they’re built for marketing, not outbound sequencing.
All of these work. They’re also slow, manual, and disconnected from your lead database. The persona definer skill doesn’t replace the thinking behind them. It compresses the execution.
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.
ColdIQ’s listing confirms the skill is meant to be used after your ICP is defined (Persona Definer - Claude Code Skill | ColdIQ): ICP determines which companies, persona determines which person at those companies. That sequencing matters. Running the persona definer without a clear ICP produces generic role lists instead of targeted ones.
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 like 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. You can also pair this with the companion skills in the same library (like the company-finder or outbound-analyst skills) to automate parts of the validation loop rather than running it manually.
Campaign engagement data tells you which definitions actually hold up. Open and reply rates by persona reveal where your targeting is accurate and where it’s off. 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.
Over to you
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 on the team formally flags the problem. Set a calendar reminder. By the time the data is obvious, you’ve already wasted weeks of outbound on the wrong contacts.
Share this post