Early-Stage Sales Playbook

Founder-Led Sales

by LeadMagic · MIT license · ★ 62 on GitHub

Founder-Led Sales cover

Founder-led sales playbook for $0-5M ARR stages. Use when founder is primary seller, building sales process from scratch, transitioning from founder-led to AE-led, or designing demo/negotiation/close motions as a technical founder.

---
name: founder-sales
description: >-
  Founder-led sales playbook for $0-5M ARR stages. Use when founder is primary
  seller, building sales process from scratch, transitioning from founder-led to
  AE-led, or designing demo/negotiation/close motions as a technical founder.
license: MIT
compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
metadata:
  version: "1.1.0"
  author: LeadMagic
  category: founder-led
  tags: [founder, sales, demo, negotiation, closing, early-stage, b2b]
  related_skills: [sales-enablement, demo-scripts, pricing-strategy, sales-team-building, meeting-prep]
  frameworks:
    - "Jason Lemkin & Mark Roberge — From Survival to Thrival (Survival phase)"
    - "Mark Roberge — The Sales Acceleration Formula (founder-to-machine transition)"
    - "Pete Kazanjy — Founding Sales (founder-led sales stages)"

Overview

Founders who don't sell die. The mistake: thinking "I'm technical" or "I'll hire a VP of Sales to figure it out." You can't outsource the first $1-3M in revenue. You ARE the sales team until you've proven repeatability. This skill covers the entire founder-led sales motion — from first conversation to signed contract — with stage-appropriate tactics, discovery frameworks, demo architecture, negotiation, and the transition to your first AE.

Manual install (npx, ZIP)
Claude Codenpx skills add LeadMagic/gtm-skills --skill founder-sales -g -a claude-code
Claude Code (degit)npx degit LeadMagic/gtm-skills/skills/founder-led/founder-sales#main ~/.claude/skills/founder-sales
Claude.ai / desktopZip the folder and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md12.8 KB
Read SKILL.md here
LeadMagic/main1 file shown
SKILL.md
Show the full text273 lines

Founder-Led Sales

Overview

Founders who don't sell die. The mistake: thinking "I'm technical" or "I'll hire a VP of Sales to figure it out." You can't outsource the first $1-3M in revenue. You ARE the sales team until you've proven repeatability. This skill covers the entire founder-led sales motion — from first conversation to signed contract — with stage-appropriate tactics, discovery frameworks, demo architecture, negotiation, and the transition to your first AE.

When to Use

Trigger phrases: "founder-led sales", "I need to sell as a founder", "founder doing demos", "founder closing deals", "founder sales process", "I'm technical and can't sell", "transition from founder selling to AE", "first sales hire"

Authoritative Foundations

Jason Lemkin & Mark Roberge — From Survival to Thrival (Survival Phase)

Survival to Thrival defines Survival as $0–$2M ARR where the founder is the sales team. Lemkin's rule: close 10–20 deals yourself before any sales hire. Roberge's rule: document every step of those deals — the playbook you write here becomes the training material for your first AE. This skill covers the Survival phase. Load sales-team-building and pipeline-management when you enter Thrival.

Mark Roberge — The Sales Acceleration Formula

Roberge scaled HubSpot's sales org by treating sales as a science: measure conversion at every stage, hire for coachability over experience, and never delegate selling until the process is repeatable. The founder-to-AE transition in Phase 5 of this skill follows his documented-playbook requirement.

Pete Kazanjy — Founding Sales Stages

Kazanjy's framework defines three stages of founder-led sales:

  1. Proto-Sales ($0-500K): Discovery. You're learning what problems people pay for. Conversations > contracts. Every "no" teaches you something.
  2. Founder-Led ($500K-2M): Repeatability. You've found a repeatable problem→solution→value pattern. You're optimizing demo, discovery, and close.
  3. Founder-Led+ ($2-5M): Delegation. You're documenting your process so someone else can follow it. You're still the best seller but no longer the only seller.
SPIN Selling — Neil Rackham (Huthwaite Study)

The 35,000-call study proved top performers use questions differently:

  • Situation (10-15% for top performers vs 20%+ for average) — Get enough context
  • Problem (20-25% vs 15%) — Uncover pain they may not have articulated
  • Implication (30-35% vs 10%) — Make the pain cost real: "What happens if this continues?"
  • Need-Payoff (20-25% vs 5%) — Let THEM describe the value: "How would solving this change things?"
Winning by Design — SPICED
  • Situation: Current state, tools, team size, budget authority
  • Pain: What's broken, quantified when possible
  • Impact: What does the pain cost in dollars, time, or missed opportunity?
  • Critical Event: What makes this urgent NOW? (No CE = no deal timeline)
  • Decision: Who decides, what's their process, what are their criteria?
Leslie Venetz — Founder Buyer-First Outbound (Sales-Led GTM)

When the founder is doing their own outbound, stop pitching in TAM terms (your "1M potential prospects") and narrow to ICP, then to the small subset most likely to buy now, at the highest price, and renew — "you only need ~10 of ~380 to say yes." Apply the "Earn the Right" gate to every founder email (incl. VC outreach): say something relevant before any ask. Full playbook → references/leslie-venetz-buyer-first-outbound.md.

Step-by-Step Process

Phase 1: First Meeting — Discovery (30-45 min)

Your goal: Qualify OR disqualify. Not to sell. Not to demo. To decide if you should spend more time.

Structure:

  1. 3-minute opening: "Thanks for taking the time. To make this useful, let me share what I know and you correct me. Then we'll see if there's a fit."
  2. 20-minute discovery: SPICED framework. Start broad, narrow to pain.
    • "Walk me through how you handle X today" (Situation)
    • "What's the most frustrating part of that?" (Problem)
    • "What's that costing you — rough numbers?" (Impact)
    • "Why is now the right time to fix this?" (Critical Event)
    • "If we find a fit today, what happens next?" (Decision)
  3. 10-minute qualification decision — YOURS, not theirs. Ask yourself:
    • Can I solve their stated problem? (Problem fit)
    • Is the pain big enough to justify my price? (Value fit)
    • Is there a real timeline? (Timing fit)
    • Can they buy? (Budget + authority fit)
    • Do I WANT this customer? (Culture fit — trust your gut)
  4. 5-minute next steps: "Based on what you've shared, I think we can help with X and Y. Here's what a deeper look would involve..."

Red flags to disqualify fast:

  • No Critical Event ("we're just exploring")
  • No access to economic buyer ("I'll take it to my boss")
  • Pain is theoretical, not felt
  • They're collecting competitive pricing
  • They won't share numbers (budget, team size, current spend)
Phase 2: Demo/Deep-Dive (45-60 min)

Your goal: Show the specific value for THEIR situation, not a feature tour.

Structure:

  1. 3-min recap: "Last time we talked about X pain costing you Y. Today I'll show you exactly how we solve that."
  2. 35-min custom demo: Show ONLY what matters to their pain. Sequence:
    • Show the outcome first ("Here's what you'll see every morning")
    • Then show how to get there (minimal clicks)
    • Address their specific use case, using their data when possible
    • Pause after each major capability: "Is this what you were envisioning?"
  3. 10-min commercial discussion: Pricing, timeline, implementation.
    • "Typically companies your size start with X at $Y. Does that align?"
    • NEVER email pricing after the call. Discuss it live.
  4. 5-min close for next step: "It sounds like this would solve your problem. What needs to happen for us to move forward?"

Demo anti-patterns:

  • Starting with login screen (boring, generic)
  • Walking through every feature (you'll lose them)
  • "And over here we also have..." (no one cares about features they didn't ask for)
  • Letting them drive the demo ("can you show me X? and Y? and Z?")
  • No commercial discussion (the "I'll send pricing" trap)
Phase 3: Negotiation & Close

Chris Voss — Tactical Empathy principles:

  1. Mirroring: Repeat the last 1-3 words they said. "15% discount." "15% discount?" (pause — let them fill the silence)
  2. Labeling: "It sounds like budget is a real concern here." Let them confirm and explain.
  3. Calibrated questions: "How am I supposed to do that?" when asked for an unreasonable discount. Forces them to solve your problem.
  4. The Ackerman Model: Counter at 65%, 85%, 95%, 100% of your target — decreasing increments signal you're reaching your limit.

Founder-specific negotiation rules:

  • Never discount without a concession: annual prepay, case study, logo reference, faster implementation
  • "I can do X if you can do Y" — always conditional
  • Your first deal at any price point sets the anchor for all future deals
  • It's better to lose a bad-fit deal than win a bad customer
  • The best negotiation is having a pipeline — desperation leaks
Phase 4: Founder → AE Transition

When to hire your first AE:

  • You've closed 20+ deals yourself
  • You can predict close rates within 10% accuracy
  • You have a repeatable demo that works without you
  • Your calendar is the bottleneck (you're turning away qualified meetings)
  • You have 3+ months of pipeline to give them

Transition stages (Kazanjy):

  1. You lead, AE shadows (Weeks 1-2)
  2. AE leads, you're in the room (Weeks 3-4)
  3. AE leads alone, you review recordings (Weeks 5-8)
  4. AE owns pipeline, you do escalations only (Week 9+)

Documentation to create before hiring:

  • Discovery call script (your exact questions, in order)
  • Demo script (scene-by-scene, with talk tracks)
  • Objection playbook (top 10 objections with word-for-word responses)
  • Pricing and packaging guide
  • CRM entry standards (what goes where, when)
  • Qualification criteria (written, not in your head)

Output Format

FOUNDER SALES MOTION DOCUMENT

Stage: [Proto-Sales / Founder-Led / Founder-Led+]
Current ARR: $X

Discovery Framework:
- SPICED questions (customized to product)
- Qualification criteria (5-point check)

Demo Architecture:
- Opening hook (3 min)
- Core value demo (30 min, 5 scenes)
- Commercial discussion (10 min)
- Next-step close (5 min)

Pricing Tiers:
- Starter: $X/mo — for [persona], includes [features]
- Growth: $X/mo — for [persona], includes [features]
- Enterprise: Custom — for [persona], includes [features]

Negotiation Guardrails:
- Max discount: X%
- Concession menu: [options]
- Red-line terms: [non-negotiable items]

Transition Plan:
- AE hire trigger: [specific milestone]
- Documentation checklist: [items]

Implementation Checklist

  • SPICED discovery questions customized to your product
  • Demo follows outcome-first architecture (show result, then path)
  • Commercial discussion happens ON the demo call, never after
  • Negotiation uses conditional concessions ("I can X if you Y")
  • Qualification criteria written, not intuitive
  • Critical Event identified before any second meeting
  • AE transition documentation exists before first AE hire
  • Pipeline is 3x quota before hiring first AE

Quality Check

Before delivering, verify:

  • Output matches the user's stated request
  • Named frameworks or sources are reflected in the recommendation
  • The deliverable is specific enough for an agent to execute
  • Any assumptions, risks, or dependencies are explicit
  • No unsupported claims, invented facts, or private/internal references are included

Common Pitfalls

  1. Demoing too early. First meeting should be discovery, not demo. If you haven't identified a Critical Event, skip the demo. You'll waste time on tire-kickers. Fix: Require SPICED completion before scheduling demos.

  2. Emailing pricing. If you email pricing after the call, you've lost control of the conversation. They'll compare to competitors without your context. Fix: Discuss pricing live, anchoring on value delivered.

  3. Overqualifying on budget. "What's your budget?" is a lazy question that gets lazy answers. Most buyers don't know their budget for a new category. Fix: Qualify on pain impact. "What's this problem costing you?" — if the answer is 10x your price, budget exists.

  4. Hiring sales too early. Before you've proven repeatability, a sales hire is a research project you're paying for. They'll fail and blame the product. Fix: Close 20+ deals yourself first. Document everything.

  5. Discounting without concessions. Every discount without a trade trains buyers to ask for more. Fix: Always conditional. Always.

Execution Artifacts

  • references/framework-notes.md — Named frameworks and reference tables
  • templates/output-template.md — Deliverable shell for agent output
  • scripts/check-output.py — Lightweight deliverable validator
  • references/leslie-venetz-buyer-first-outbound.md — Founder buyer-first outbound, TAM→ICP narrowing, Earn-the-Right gate (Leslie Venetz)
  • pricing-strategy — Tier design, willingness-to-pay research, packaging
  • sales-enablement — Pitch decks, one-pagers, battlecards, demo scripts
  • demo-scripts — First demo, technical deep-dive, executive overview
  • sales-team-building — Hiring sequence, POD structures, compensation
  • meeting-prep — Account research, SPIN/MEDDIC prep, meeting briefs
1---
2name: founder-sales
3description: >-
4 Founder-led sales playbook for $0-5M ARR stages. Use when founder is primary
5 seller, building sales process from scratch, transitioning from founder-led to
6 AE-led, or designing demo/negotiation/close motions as a technical founder.
7license: MIT
8compatibility: Claude Code, Codex, GitHub Copilot, Cursor, Gemini CLI, OpenCode, Goose, Hermes, Windsurf, Zed
9metadata:
10 version: "1.1.0"
11 author: LeadMagic
12 category: founder-led
13 tags: [founder, sales, demo, negotiation, closing, early-stage, b2b]
14 related_skills: [sales-enablement, demo-scripts, pricing-strategy, sales-team-building, meeting-prep]
15 frameworks:
16 - "Jason Lemkin & Mark Roberge — From Survival to Thrival (Survival phase)"
17 - "Mark Roberge — The Sales Acceleration Formula (founder-to-machine transition)"
18 - "Pete Kazanjy — Founding Sales (founder-led sales stages)"
19 - "Winning by Design — SPICED discovery methodology"
20 - "SPIN Selling — Neil Rackham (35K-call Huthwaite study)"
21 - "Challenger Sale — Gartner/CEB (commercial teaching)"
22 - "Chris Voss — Tactical Empathy (negotiation)"
23 - "SaaStr/Jason Lemkin — Founder sales benchmarks"
24 - "David Skok — Sales learning curve"
25 - "Leslie Venetz (Sales-Led GTM) — Founder buyer-first outbound / TAM→ICP narrowing"
26---
27 
28# Founder-Led Sales
29 
30## Overview
31 
32Founders who don't sell die. The mistake: thinking "I'm technical" or "I'll hire
33a VP of Sales to figure it out." You can't outsource the first $1-3M in revenue.
34You ARE the sales team until you've proven repeatability. This skill covers the
35entire founder-led sales motion — from first conversation to signed contract —
36with stage-appropriate tactics, discovery frameworks, demo architecture,
37negotiation, and the transition to your first AE.
38 
39## When to Use
40 
41Trigger phrases: "founder-led sales", "I need to sell as a founder", "founder
42doing demos", "founder closing deals", "founder sales process", "I'm technical
43and can't sell", "transition from founder selling to AE", "first sales hire"
44 
45## Authoritative Foundations
46 
47### Jason Lemkin & Mark Roberge — From Survival to Thrival (Survival Phase)
48*Survival to Thrival* defines Survival as $0–$2M ARR where the founder is the
49sales team. Lemkin's rule: close 10–20 deals yourself before any sales hire.
50Roberge's rule: document every step of those deals — the playbook you write here
51becomes the training material for your first AE. This skill covers the Survival
52phase. Load `sales-team-building` and `pipeline-management` when you enter Thrival.
53 
54### Mark Roberge — The Sales Acceleration Formula
55Roberge scaled HubSpot's sales org by treating sales as a science: measure
56conversion at every stage, hire for coachability over experience, and never
57delegate selling until the process is repeatable. The founder-to-AE transition
58in Phase 5 of this skill follows his documented-playbook requirement.
59 
60### Pete Kazanjy — Founding Sales Stages
61Kazanjy's framework defines three stages of founder-led sales:
621. **Proto-Sales ($0-500K):** Discovery. You're learning what problems people pay for. Conversations > contracts. Every "no" teaches you something.
632. **Founder-Led ($500K-2M):** Repeatability. You've found a repeatable problem→solution→value pattern. You're optimizing demo, discovery, and close.
643. **Founder-Led+ ($2-5M):** Delegation. You're documenting your process so someone else can follow it. You're still the best seller but no longer the only seller.
65 
66### SPIN Selling — Neil Rackham (Huthwaite Study)
67The 35,000-call study proved top performers use questions differently:
68- **Situation** (10-15% for top performers vs 20%+ for average) — Get enough context
69- **Problem** (20-25% vs 15%) — Uncover pain they may not have articulated
70- **Implication** (30-35% vs 10%) — Make the pain cost real: "What happens if this continues?"
71- **Need-Payoff** (20-25% vs 5%) — Let THEM describe the value: "How would solving this change things?"
72 
73### Winning by Design — SPICED
74- **Situation:** Current state, tools, team size, budget authority
75- **Pain:** What's broken, quantified when possible
76- **Impact:** What does the pain cost in dollars, time, or missed opportunity?
77- **Critical Event:** What makes this urgent NOW? (No CE = no deal timeline)
78- **Decision:** Who decides, what's their process, what are their criteria?
79 
80### Leslie Venetz — Founder Buyer-First Outbound (Sales-Led GTM)
81When the founder is doing their own outbound, stop pitching in TAM terms (your "1M
82potential prospects") and narrow to ICP, then to the small subset most likely to buy
83now, at the highest price, and renew — "you only need ~10 of ~380 to say yes." Apply
84the **"Earn the Right"** gate to every founder email (incl. VC outreach): say
85something relevant before any ask. Full playbook →
86`references/leslie-venetz-buyer-first-outbound.md`.
87 
88## Step-by-Step Process
89 
90### Phase 1: First Meeting — Discovery (30-45 min)
91 
92**Your goal:** Qualify OR disqualify. Not to sell. Not to demo. To decide if you
93should spend more time.
94 
95**Structure:**
961. **3-minute opening:** "Thanks for taking the time. To make this useful, let me
97 share what I know and you correct me. Then we'll see if there's a fit."
982. **20-minute discovery:** SPICED framework. Start broad, narrow to pain.
99 - "Walk me through how you handle X today" (Situation)
100 - "What's the most frustrating part of that?" (Problem)
101 - "What's that costing you — rough numbers?" (Impact)
102 - "Why is now the right time to fix this?" (Critical Event)
103 - "If we find a fit today, what happens next?" (Decision)
1043. **10-minute qualification decision — YOURS, not theirs.** Ask yourself:
105 - Can I solve their stated problem? (Problem fit)
106 - Is the pain big enough to justify my price? (Value fit)
107 - Is there a real timeline? (Timing fit)
108 - Can they buy? (Budget + authority fit)
109 - Do I WANT this customer? (Culture fit — trust your gut)
1104. **5-minute next steps:** "Based on what you've shared, I think we can help
111 with X and Y. Here's what a deeper look would involve..."
112 
113**Red flags to disqualify fast:**
114- No Critical Event ("we're just exploring")
115- No access to economic buyer ("I'll take it to my boss")
116- Pain is theoretical, not felt
117- They're collecting competitive pricing
118- They won't share numbers (budget, team size, current spend)
119 
120### Phase 2: Demo/Deep-Dive (45-60 min)
121 
122**Your goal:** Show the specific value for THEIR situation, not a feature tour.
123 
124**Structure:**
1251. **3-min recap:** "Last time we talked about X pain costing you Y. Today I'll
126 show you exactly how we solve that."
1272. **35-min custom demo:** Show ONLY what matters to their pain. Sequence:
128 - Show the outcome first ("Here's what you'll see every morning")
129 - Then show how to get there (minimal clicks)
130 - Address their specific use case, using their data when possible
131 - Pause after each major capability: "Is this what you were envisioning?"
1323. **10-min commercial discussion:** Pricing, timeline, implementation.
133 - "Typically companies your size start with X at $Y. Does that align?"
134 - NEVER email pricing after the call. Discuss it live.
1354. **5-min close for next step:** "It sounds like this would solve your problem.
136 What needs to happen for us to move forward?"
137 
138**Demo anti-patterns:**
139- Starting with login screen (boring, generic)
140- Walking through every feature (you'll lose them)
141- "And over here we also have..." (no one cares about features they didn't ask for)
142- Letting them drive the demo ("can you show me X? and Y? and Z?")
143- No commercial discussion (the "I'll send pricing" trap)
144 
145### Phase 3: Negotiation & Close
146 
147**Chris Voss — Tactical Empathy principles:**
1481. **Mirroring:** Repeat the last 1-3 words they said. "15% discount." "15% discount?" (pause — let them fill the silence)
1492. **Labeling:** "It sounds like budget is a real concern here." Let them confirm and explain.
1503. **Calibrated questions:** "How am I supposed to do that?" when asked for an unreasonable discount. Forces them to solve your problem.
1514. **The Ackerman Model:** Counter at 65%, 85%, 95%, 100% of your target — decreasing increments signal you're reaching your limit.
152 
153**Founder-specific negotiation rules:**
154- Never discount without a concession: annual prepay, case study, logo reference, faster implementation
155- "I can do X if you can do Y" — always conditional
156- Your first deal at any price point sets the anchor for all future deals
157- It's better to lose a bad-fit deal than win a bad customer
158- The best negotiation is having a pipeline — desperation leaks
159 
160### Phase 4: Founder → AE Transition
161 
162**When to hire your first AE:**
163- You've closed 20+ deals yourself
164- You can predict close rates within 10% accuracy
165- You have a repeatable demo that works without you
166- Your calendar is the bottleneck (you're turning away qualified meetings)
167- You have 3+ months of pipeline to give them
168 
169**Transition stages (Kazanjy):**
1701. You lead, AE shadows (Weeks 1-2)
1712. AE leads, you're in the room (Weeks 3-4)
1723. AE leads alone, you review recordings (Weeks 5-8)
1734. AE owns pipeline, you do escalations only (Week 9+)
174 
175**Documentation to create before hiring:**
176- Discovery call script (your exact questions, in order)
177- Demo script (scene-by-scene, with talk tracks)
178- Objection playbook (top 10 objections with word-for-word responses)
179- Pricing and packaging guide
180- CRM entry standards (what goes where, when)
181- Qualification criteria (written, not in your head)
182 
183## Output Format
184 
185```
186FOUNDER SALES MOTION DOCUMENT
187 
188Stage: [Proto-Sales / Founder-Led / Founder-Led+]
189Current ARR: $X
190 
191Discovery Framework:
192- SPICED questions (customized to product)
193- Qualification criteria (5-point check)
194 
195Demo Architecture:
196- Opening hook (3 min)
197- Core value demo (30 min, 5 scenes)
198- Commercial discussion (10 min)
199- Next-step close (5 min)
200 
201Pricing Tiers:
202- Starter: $X/mo — for [persona], includes [features]
203- Growth: $X/mo — for [persona], includes [features]
204- Enterprise: Custom — for [persona], includes [features]
205 
206Negotiation Guardrails:
207- Max discount: X%
208- Concession menu: [options]
209- Red-line terms: [non-negotiable items]
210 
211Transition Plan:
212- AE hire trigger: [specific milestone]
213- Documentation checklist: [items]
214```
215 
216## Implementation Checklist
217 
218- [ ] SPICED discovery questions customized to your product
219- [ ] Demo follows outcome-first architecture (show result, then path)
220- [ ] Commercial discussion happens ON the demo call, never after
221- [ ] Negotiation uses conditional concessions ("I can X if you Y")
222- [ ] Qualification criteria written, not intuitive
223- [ ] Critical Event identified before any second meeting
224- [ ] AE transition documentation exists before first AE hire
225- [ ] Pipeline is 3x quota before hiring first AE
226 
227## Quality Check
228 
229Before delivering, verify:
230 
231- [ ] Output matches the user's stated request
232- [ ] Named frameworks or sources are reflected in the recommendation
233- [ ] The deliverable is specific enough for an agent to execute
234- [ ] Any assumptions, risks, or dependencies are explicit
235- [ ] No unsupported claims, invented facts, or private/internal references are included
236 
237## Common Pitfalls
238 
2391. **Demoing too early.** First meeting should be discovery, not demo. If you
240 haven't identified a Critical Event, skip the demo. You'll waste time on
241 tire-kickers. Fix: Require SPICED completion before scheduling demos.
242 
2432. **Emailing pricing.** If you email pricing after the call, you've lost
244 control of the conversation. They'll compare to competitors without your
245 context. Fix: Discuss pricing live, anchoring on value delivered.
246 
2473. **Overqualifying on budget.** "What's your budget?" is a lazy question that
248 gets lazy answers. Most buyers don't know their budget for a new category.
249 Fix: Qualify on pain impact. "What's this problem costing you?" — if the
250 answer is 10x your price, budget exists.
251 
2524. **Hiring sales too early.** Before you've proven repeatability, a sales hire
253 is a research project you're paying for. They'll fail and blame the product.
254 Fix: Close 20+ deals yourself first. Document everything.
255 
2565. **Discounting without concessions.** Every discount without a trade trains
257 buyers to ask for more. Fix: Always conditional. Always.
258 
259## Execution Artifacts
260 
261- `references/framework-notes.md` — Named frameworks and reference tables
262- `templates/output-template.md` — Deliverable shell for agent output
263- `scripts/check-output.py` — Lightweight deliverable validator
264- `references/leslie-venetz-buyer-first-outbound.md` — Founder buyer-first outbound, TAM→ICP narrowing, Earn-the-Right gate (Leslie Venetz)
265 
266## Related Skills
267 
268- `pricing-strategy` — Tier design, willingness-to-pay research, packaging
269- `sales-enablement` — Pitch decks, one-pagers, battlecards, demo scripts
270- `demo-scripts` — First demo, technical deep-dive, executive overview
271- `sales-team-building` — Hiring sequence, POD structures, compensation
272- `meeting-prep` — Account research, SPIN/MEDDIC prep, meeting briefs
273 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 62
Checked
Source
LeadMagic/gtm-skills ↗
Creator
LeadMagic · 129 listings
View creator

Similar skills

See all →

More from LeadMagic

SkillFirst-Party Analytics SetupLeadMagic/gtm-skills · by LeadMagicSet up first-party tracking and analytics — website pixels, conversion tracking, UTM architecture, cookie consent, server-side tagging vs client-side, 1P vs 3P data strategy, and identity resolution. Use when setting up tracking, implementing pixels, building attribution, or preparing for privacy-first measurement. Triggers on: "pixel", "tracking", "conversion tracking", "first-party data", server-side tagging", "UTM", "cookie consent", "1P vs 3P", "identity resolution", or any tracking implementation request.★ 62 GitHub starsSkillStrategic Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns strategic 1-to-1 ABM for 5-15 high-value accounts: account plans, custom microsites, executive engagement, direct mail, and board-level connections. Use when a named enterprise account justifies bespoke content and executive time, or when the user needs a strategic account plan. Triggers on: "1-to-1 ABM", "strategic ABM", "custom ABM", "key account marketing", "named account".★ 62 GitHub starsSkillCluster Account MarketingLeadMagic/gtm-skills · by LeadMagicRuns ABM at scale (1-to-few) for 15-50 clustered accounts: industry or persona clusters, semi-custom campaigns, and cluster-level content. Use when named-account ABM needs to reach more accounts without bespoke work per account. Triggers on: "1-to-few ABM", "ABM scale", "cluster ABM", "industry ABM".★ 62 GitHub starsSkillProgrammatic Account TargetingLeadMagic/gtm-skills · by LeadMagicRuns programmatic 1-to-many ABM for 50-200+ accounts: automated personalization, scaled outbound, intent-based targeting, and lookalike expansion. Use when ABM coverage must grow without adding headcount or when the user wants automated account-based outreach. Triggers on: "1-to-many ABM", programmatic ABM", "scaled ABM", "automated ABM".★ 62 GitHub starsSkillAccount Strategy DesignerLeadMagic/gtm-skills · by LeadMagicDesigns an account-based marketing program: tier selection, account scoring, channel orchestration, BDR alignment (account-based sales development), and a measurement framework. Use when the user is launching or redesigning ABM, choosing between 1-to-1, 1-to-few, and 1-to-many, or building a target account program. Triggers on: "ABM strategy", "account based marketing", "ABM playbook", "design ABM", "target accounts", "ABSD", "account based sales development", "Lars Nilsson".★ 62 GitHub starsSkillTarget Account SelectorLeadMagic/gtm-skills · by LeadMagicBuilds and tiers a target account list: fit and intent scoring models, tier assignment, and TAM segmentation. Use when the user needs to decide which accounts to target, score or tier an account list, or prioritize a TAM for ABM or outbound. Triggers on: "account selection", "target account list", "tier accounts", "prioritize accounts", "TAM segmentation".★ 62 GitHub stars