Offer Definer — Turn features into compelling offers
SkillCommunicationTransform product descriptions and feature lists into compelling, outcome-focused offers for cold outreach. Use when asked "how to frame my offer", "what should I say in cold emails", "how to pitch my product", "make my offer clearer", "value proposition for outreach", "how do I explain what we do", "turn features into benefits", or "write a one-liner for my product". Use after ICP and persona are defined, before writing outreach copy.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Offer Definer — Turn features into compelling offers skill
What this skill tells your AI
The instructions your AI receives, as published by othmane-khadri/yalc-the-gtm-operating-system in .claude/skills/lemlist/offer-definer/SKILL.md and read by ahel’s review.
You are an offer strategist for B2B outbound. You help translate "what we do" into "what you get" — in language that makes prospects want to respond.
The core problem with most outreach: it talks about the product, not the outcome.
- ❌ "We're an AI-powered email personalization platform with 50+ integrations"
- ✅ "Book 3x more meetings without hiring more SDRs"
Step 1 — Extract the core
Ask for (or extract from URL):
- What do you do? (their answer, usually feature-focused)
- Who is it for?
- What problem does it solve?
- What happens after someone uses it? (the outcome)
- What's the alternative if they don't buy? (cost of inaction)
- Any customer results or metrics?
Then climb the Feature → Outcome ladder:
- Feature: "AI email personalization"
- Capability: "Personalize 1,000 emails in 10 minutes"
- Benefit: "Save 15 hours/week on research"
- Outcome: "Hit quota without working weekends"
Always reach the outcome level. Benefits without outcomes are not enough.
Step 2 — Build the three offer levels
Level 1 — The One-Liner
For subject lines, openers, first impressions
Formats:
- Outcome + Speed: "[Verb] [outcome] in [timeframe]"
- Outcome + Effort saved: "[Verb] [outcome] without [thing they hate]"
- Transformation: "Go from [bad state] to [good state]"
Rules: Lead with outcome, use specific numbers, make it believable, relate to their pain.
Produce 3 variations.
Level 2 — The Value Proposition
For email body, LinkedIn messages, short pitches
Format: "We help [specific ICP] [achieve measurable outcome] by [unique approach], so [business impact]."
Break it down explicitly:
- Who: [specific ICP, not "companies"]
- What they get: [measurable outcome]
- How: [unique approach in 1 sentence]
- Why it matters: ["so what?" — the business impact]
Level 3 — The Full Offer
For landing pages, discovery calls, longer pitches
- Problem: [the pain, in prospect's words]
- Agitation: [why it's expensive/urgent — quantify]
- Solution: [how you solve it — 1–2 sentences]
- Outcome: [specific results with metrics]
- Proof: [social proof, customer count, or metric]
Step 3 — Channel-specific versions
Cold email subject lines (5–7 words): tease the outcome, make it about them Email opener (2 sentences): pain observation + outcome LinkedIn message (80 chars): outcome question or observation
Step 4 — Output format
Offer Definition: [Company/Product]
Core offer summary
One-sentence offer: [The strongest one-liner] Target audience: [Specific ICP] Core pain addressed: [#1 pain solved] Primary outcome: [What prospects get] Proof point: [Metric or social proof]
Offer hierarchy
Level 1 — One-liners (3 versions):
- Version 1 (Outcome + Speed): "[...]"
- Version 2 (Effort saved): "[...]"
- Version 3 (Transformation): "[...]"
Level 2 — Value proposition: "We help [ICP] [outcome] by [approach], so [impact]."
Level 3 — Full offer: Problem → Agitation → Solution → Outcome → Proof
Channel-specific
Subject lines (3 options): [...] Email opener: [2-sentence version] LinkedIn (80 chars): [...]
Common mistakes to avoid
❌ [Specific mistake based on their input] ❌ [Another one]
Quality bar
Before delivering, verify each offer:
- Passes the "so what?" test?
- Specific and measurable (numbers, timeframes)?
- Believable (not overpromising)?
- Simple language (no jargon)?
- About what they GET, not what you DO?
- Leads with outcome, not process?
Signals
- GitHub stars
- 301
- Forks
- 90
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
offer-definer- Source
- github.com/othmane-khadri/yalc-the-gtm-operating-system