Mihaela Cicvaric | September 4, 2026 | 17 min read
Mihaela Cicvaric | September 4, 2026 | 17 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.
How to Use the Offer-Definer Claude Skill to Win More Deals
What is the Offer-Definer Claude Skill
The Offer-Definer Claude Skill is a free .md file that turns a raw list of product features into a single, outcome-focused offer statement. You attach it to a Claude conversation, tell it who you’re selling to, and it hands back a line of copy calibrated to that buyer’s role and seniority.
That last part matters. A Claude Skill isn’t a prompt you type from memory each time. It’s a structured instruction file (a text document written in Markdown) that you load into Claude so it follows a defined process instead of improvising.
- Claude Skill: a reusable .md file that encodes a specific workflow, so Claude repeats the same logic every time instead of generating something different based on how you happened to phrase the request
- Offer-Definer specifically: takes your product description or feature list, plus a target persona, and returns one outcome-framed offer ready to paste into an email
The Offer-Definer lives in the “Extrapolating” category of lemlist’s Claude Skills library, alongside the ICP Definer and Persona Definer. You can download it directly from GitHub or browse the full set on lemlist’s site.
Why most cold emails fail at the offer
Feature lists don’t create urgency
Most reps default to listing what their product does: automated sequences, built-in warm-up, AI personalization. The problem is that this hands the prospect a translation job. They have to figure out what any of that means for their day, and most won’t bother.
An offer does that translation for them. Instead of “automated sequences,” you say “your reps launch campaigns in minutes instead of hours.” Same feature, different framing, and now the prospect doesn’t have to do any work to see why it matters.
Generic prompts produce generic offers
You might wonder why you can’t just ask Claude to “rewrite my features as benefits” and skip the skill entirely. You can, and Claude will give you something. But without structured inputs (who the buyer is, their seniority, what proof to include), it tends to default to vague language that could describe almost any product.
The Offer-Definer avoids this by requiring specific inputs and following a fixed translation logic. It doesn’t just rephrase your features. It maps them to what a defined buyer actually cares about.
How the Offer-Definer skill turns features into outcomes
Feature-to-outcome translation
The mechanic is straightforward: each feature gets mapped to a business result the prospect recognizes. “Automated multichannel sequences” becomes “your reps cover more accounts per day without adding headcount.” The underlying capability hasn’t changed. The framing answers the question the prospect is silently asking, which is simply: what changes for me?
Persona and seniority calibration
The same feature reads differently depending on who’s on the other end. A VP of Sales usually cares about pipeline velocity and revenue per rep. An SDR Manager tends to care about daily rep output and ramp time. A founder often thinks in terms of revenue per headcount.
Input you provide | What changes in the output |
|---|---|
Persona (VP of Sales vs. SDR Manager) | The outcome shifts to match what that role gets measured on |
Seniority (IC vs. Director vs. C-suite) | Output leans tactical for ICs, strategic for execs |
Proof points (customer name, result) | Social proof gets woven in without inventing claims |
One-liner output with proof integration
The output lands as a single sentence, not a paragraph. It’s built to slot into an email between your opening line and your CTA, and the skill nudges you to include a real proof point (a customer name, a specific result) so it reads as credible rather than like a tagline.
How to set up and run the Offer-Definer skill in Claude
Step 1: Download the skill file from GitHub
Head to lemlist’s Claude Skills page, find Offer Definer under “Extrapolating,” and download the .md file. It’s one text file, nothing to install.
Step 2: Open a new Claude conversation
Start fresh so earlier context doesn’t interfere with the skill’s instructions. The free plan works fine, though Claude Pro or Team gives you a longer context window, which helps if your feature list runs long.
Step 3: Attach the file and add your inputs
Attach the .md file the same way you’d attach any document (paperclip icon on web, drag-and-drop on desktop), then include:
- Product description or feature list
- Target persona and role
- Seniority level (IC, Manager, Director, VP, C-suite)
- Any proof points you want folded in
Step 4: Review and refine
Check the output against what you actually know about your ICP’s pain points. You can ask Claude to swap the persona, tighten the wording, or change the proof point, all in the same conversation, without re-uploading the file.
Tip: Run the skill twice with two different personas (say, VP of Sales and SDR Manager) in the same session. Comparing the two outputs side by side is a fast way to see whether your offer actually shifts with the buyer, or just repeats itself in different words.
What the Offer-Definer output looks like
Here’s a simplified before-and-after using a generic feature set:
Raw input | Offer for VP of Sales | Offer for SDR Manager | |
|---|---|---|---|
Feature | Automated multichannel sequences, AI-personalized first lines, built-in warm-up | Sales teams add more pipeline coverage per rep by launching sequences in minutes instead of hours | Reps stop losing their first hour to copy-pasting follow-ups and start reaching live prospects earlier |
Notice the difference isn’t in the underlying feature. It’s in what each person is measured on, pipeline coverage for one, daily output for the other.
How to use the Offer-Definer output in cold outreach sequences
Placing the offer in a first-touch email
The one-liner has a specific home: after your hook (the line that earns attention) and before your CTA. Skip it, and the email jumps straight from “I noticed X” to “want to chat?” with nothing bridging the two.
You can paste the output into lemlist’s sequence builder, or, if you’re mid-conversation in Claude, push it to lemlist directly via MCP.
Adapting the offer across follow-ups and channels
The core offer stays fixed, but the format shifts depending on where it lands:
- Follow-up emails: open with a new angle, but keep the same underlying outcome
- LinkedIn messages: trim it down to one conversational line
- Cold call openers: drop the written polish, lead with the result out loud
lemlist’s multichannel builder lets you run all of these in one sequence, so the offer holds together even as the channel changes.
Where the Offer-Definer fits in your outbound workflow
Pairing with ICP Definer and Persona Definer
The Offer-Definer works best when its inputs are already sharp, and that’s where the earlier skills in the library come in. The ICP Definer narrows down which companies to target. The Persona Definer identifies which buyers inside those companies matter. Run them in order (ICP, then Persona, then Offer) and each output feeds the next.
Skip the first two, and the Offer-Definer still runs fine. It just works from your assumptions about the buyer instead of a structured read on who they actually are.
Feeding the output into campaign sequences
Once you have your offer, the Copywriting First Touch skill builds a full email around it. The Outbound Campaign Architect takes it further, designing a whole sequence. Or, if you’d rather stay in one place, lemlist MCP lets you go from offer to sequence to live campaign inside the same Claude conversation.
Turn your product into offers that book meetings
The Offer-Definer gives you a repeatable way to frame your product around what actually changes for the buyer, matched to the exact persona you’re reaching. Run it, get a calibrated offer, plug it into your sequence, and move on to the next campaign instead of rewriting your pitch from scratch.
FAQs about the Offer-Definer Claude Skill
Does the Offer-Definer work on Claude’s free plan?
Yes. Paid plans (Pro or Team) give you a longer context window, which helps if you’re pasting in a long feature list or running multiple personas in one session, but the free plan works.
Yes. Paid plans (Pro or Team) give you a longer context window, which helps if you’re pasting in a long feature list or running multiple personas in one session, but the free plan works.
Can the output be used for LinkedIn messages and cold calls?
Yes. The output starts as a written offer statement, but you can shorten it for LinkedIn or rewrite it in spoken cadence for a call. The underlying outcome framing carries over either way.
Yes. The output starts as a written offer statement, but you can shorten it for LinkedIn or rewrite it in spoken cadence for a call. The underlying outcome framing carries over either way.
How is this different from just asking Claude to “rewrite my features as benefits”?
A plain prompt gives Claude no fixed process to follow, so results vary and often default to vague language. The Offer-Definer requires specific inputs (persona, seniority, proof points) and applies the same translation logic every time.
A plain prompt gives Claude no fixed process to follow, so results vary and often default to vague language. The Offer-Definer requires specific inputs (persona, seniority, proof points) and applies the same translation logic every time.
Can the .md file be customized to match a company’s messaging style?
Yes. The file is open-source text, so you can open it in any editor and add your own positioning guidelines, banned phrases, or preferred proof points before attaching it to Claude.
Yes. The file is open-source text, so you can open it in any editor and add your own positioning guidelines, banned phrases, or preferred proof points before attaching it to Claude.
What is the Offer-Definer Claude Skill
The Offer-Definer is a Claude Skill that transforms product features into outcome-focused offers for outreach. (Claude skills for GTM engineering) In practical terms, it’s a free .md file (a Markdown text file) from lemlist’s open-source Claude Skills library that you attach to a conversation in Claude. Once loaded, it takes a product description, a target persona, and a seniority level, then returns a single, ready-to-paste offer statement calibrated to what that buyer actually cares about.
Claude Skills are structured Markdown files (.md) that contain detailed instructions, context, and best practices for a specific task. When you load a skill into a Claude conversation, it’s like handing an expert playbook to your AI. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) So while a one-off prompt produces whatever Claude improvises on the spot, the Offer-Definer follows a defined framework every time, and you get consistent, structured output instead of something generic.
The Offer-Definer sits in the “Extrapolating” category (Claude skills for GTM engineering) alongside related skills like the ICP Definer and Persona Definer. You can download it from GitHub or browse the full skills library on lemlist.com.
Why most cold emails fail at the offer
Feature lists don’t create urgency
Most reps default to listing what their product does. “Automated email sequences, built-in warm-up, AI personalization.” The problem is that this forces the prospect to translate capabilities into relevance for their own situation. Prospects rarely do that work, so the email gets ignored.
An offer does the translation for them. Instead of “automated email sequences,” it says something like “reps launch campaigns in minutes instead of hours.” The shift is subtle but it changes who carries the cognitive load.
Generic prompts produce generic offers
You might be thinking: “Why not just ask Claude to rewrite my features as benefits?” You can, and it will produce something. But without structured inputs (who the buyer is, their seniority, what proof points to include), Claude defaults to vague benefit language that could describe any product.
Think of it this way: a prompt says “write me a cold email.” A skill says “here’s our proven framework for cold emails, with persona research steps, subject line formulas, CTA patterns, and follow-up logic.” (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) The Offer-Definer works the same way. It requires specific inputs and follows a defined translation logic, so the output actually fits the buyer you’re reaching.
How the Offer-Definer skill turns features into outcomes
Feature-to-outcome translation
The core mechanic is simple: the skill maps each product capability to a concrete business result the prospect cares about. “Automated multichannel sequences” becomes “your reps cover more accounts per day without adding headcount.” The feature is the same. The framing is different because it answers the question the prospect is silently asking: What changes for me?
Persona and seniority calibration
The same feature gets framed differently depending on who reads the email. A VP of Sales cares about pipeline velocity and revenue per rep. An SDR Manager cares about daily rep productivity and ramp time. A founder cares about revenue per headcount and capital efficiency.
The Offer-Definer adjusts language, specificity, and outcome framing based on the role and seniority you provide:
Input you provide | What changes in the output |
|---|---|
Persona (e.g., VP of Sales vs. SDR Manager) | The business outcome shifts to match what that role is measured on |
Seniority (e.g., IC vs. Director vs. C-suite) | Tactical detail for ICs, business impact for execs |
Proof points (e.g., customer name, concrete result) | Social proof gets woven in without fabricating claims |
One-liner output with proof integration
The output format is a single statement you can paste directly into a cold email body. The skill also guides you to include real social proof (a customer name, a specific result), so the offer lands with credibility instead of reading like a marketing tagline.
This is worth emphasizing: the output is one sentence or a short statement, not a paragraph. It’s designed to slot into the middle of an email, after the hook and before the CTA.
How to set up and run the Offer-Definer skill in Claude
Each skill is a .md file you download and load into Claude. No code, no terminal commands, no npx (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide), just a file you attach to a conversation. Here’s the process:
1. Download the skill file from GitHub
Go to lemlist’s Claude Skills page and find the Offer Definer under the “Extrapolating” category. Click the download link to grab the .md file. It’s a single text file.
2. Open a new Claude conversation
Start a fresh conversation so prior context doesn’t interfere with the skill’s instructions. You can use the free plan or any paid plan. That said, Claude Pro or Team will give you longer context windows (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide), which helps if you paste in a large feature list.
3. Attach the .md file and provide your inputs
Attach the downloaded SKILL.md file to your message, just like you’d attach any document. On claude.ai: click the paperclip icon (📎) in the message bar, select your .md file, and hit send. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) On Claude Desktop: drag and drop the file directly into the chat window, or use the attach button. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide)
Along with the file, include:
- Product description or feature list that you want translated
- Target persona and their role (e.g., “Head of Demand Gen at a mid-market SaaS company”)
- Seniority level (IC, Manager, Director, VP, C-suite)
- Proof points you want included, like a customer name or a concrete result
4. Review and refine the output
Evaluate what Claude returns against your ICP’s actual pain points. You can ask Claude to adjust for a different persona, tighten the language, or swap the proof point, all without re-uploading the skill file. The skill stays loaded for the duration of the conversation.
Tip: Run the skill twice with two different personas (e.g., VP of Sales and SDR Manager) to see how calibration changes the output. It’s a quick way to sanity-check whether your offer resonates across buyer levels.
What the Offer-Definer output looks like
Here’s a simplified before-and-after to show how the skill translates raw features into persona-calibrated offers:
Raw feature list | Offer for VP of Sales | Offer for SDR Manager | |
|---|---|---|---|
Input | “Automated multichannel sequences, AI-personalized first lines, built-in email warm-up” | — | — |
Output | — | “Sales teams using [Product] add 40% more pipeline coverage per rep by running multichannel sequences that launch in minutes, not hours.” | “Your reps stop spending their first hour copy-pasting follow-ups and start hitting live prospects by 9:15 AM.” |
Notice how the VP version talks about pipeline coverage and team output, while the SDR Manager version talks about the daily rep experience. The underlying features are identical. The framing changes because the audience changed.
How to use the Offer-Definer output in cold outreach sequences
Placing the offer in a first-touch email
The offer one-liner fits in a specific spot: after the hook (the opening line that earns attention) and before the CTA (the ask). It’s the “why you care” bridge. Without it, the email jumps from “I noticed X about your company” to “Want to chat?” with nothing in between.
You can paste the output directly into lemlist’s sequence builder, or, if you’re already working in Claude, push it to lemlist via MCP from the same conversation.
Adapting the offer across follow-ups and channels
The core offer stays the same, but the format shifts by channel:
- Follow-up emails: lead with a new angle or consequence, but anchor on the same outcome
- LinkedIn messages: shorter, more conversational, typically one sentence
- Cold call openers: spoken cadence, so drop the written polish and lead with the result
lemlist’s multichannel campaign builder lets you run all of these variants in one sequence, so the offer stays consistent even as the channel changes.
Where the Offer-Definer fits in your outbound workflow
Pairing with ICP Definer and Persona Definer skills
The Offer-Definer works best when the inputs are already sharp. That’s where upstream skills come in. The ICP Definer defines and prioritizes Ideal Customer Profiles for outbound targeting. (Claude skills for GTM engineering) The Persona Definer identifies and prioritizes buyer personas for contact-level targeting. Each skill’s output feeds the next: ICP → Persona → Offer.
If you skip the first two, you’ll still get an output from the Offer-Definer. It just won’t be as precise, because the persona and seniority inputs will be based on your assumptions rather than a structured analysis.
Feeding the output into campaign sequences
Once your offer is defined, the downstream path is straightforward. The Copywriting First Touch skill writes a full first cold email around your offer. The Outbound Campaign Architect designs high-performance outbound sequences based on ICP and benchmark data. (Claude skills for GTM engineering)
Or you can use lemlist MCP to go from offer to sequence to live campaign in one Claude conversation, without switching tools. What MCP does is remove friction between thinking and execution. (Connect lemlist to Claude: Run Outbound Campaigns from Your AI)
Turn your product into offers that book meetings
The Offer-Definer gives your outreach a repeatable way to frame products around what changes for the buyer, matched to the exact persona you’re targeting. Instead of rewriting your pitch from scratch for every campaign, you run the skill, get a calibrated offer, and plug it into your sequence.
The full Claude Skills library has 38 skills across 6 categories (Claude skills for GTM engineering), all free and open-source. The Offer-Definer is one piece of a workflow that covers everything from ICP definition to campaign launch.
FAQs about the Offer-Definer Claude Skill
Does the Offer-Definer work on Claude’s free plan?
Yes. You can use the free plan or any paid plan. That said, Claude Pro or Team will give you longer context windows, which means better performance with complex skills. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) If you’re pasting in a long feature list or running the skill for multiple personas in one conversation, a paid plan helps.
Can the output be used for LinkedIn messages and cold calls?
Yes. The output is a concise offer statement that you can adapt to any outbound channel by adjusting length and tone. For LinkedIn, shorten it. For cold calls, rewrite it in spoken cadence. The core outcome framing stays the same.
How is the Offer-Definer different from asking Claude to “rewrite my features as benefits”?
Claude Skills are structured Markdown files that contain detailed instructions, context, and best practices for a specific task. When you load a skill into a Claude conversation, it’s like handing an expert playbook to your AI. Claude reads the instructions and follows them precisely, producing higher-quality, more consistent outputs than a generic prompt ever could. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) The Offer-Definer encodes a framework that requires specific inputs (persona, seniority, proof points) and follows a defined translation logic, so the output is calibrated to a real buyer.
Can the .md file be customized to match a company’s messaging framework?
The entire skills library is free and open source. (How to Use lemlist Claude Skills (.md Files) in Claude | Step-by-Step Guide) You can open the .md file in any text editor and modify the instructions to include your positioning guidelines, banned phrases, or preferred proof points before attaching it to Claude.
Content Marketing Manager @lemlist
Share this post