Files
claude-skills-reference/c-level-advisor/cro-advisor/references/sales_playbook.md
Alireza Rezvani e145ac4a1d Dev (#265)
* docs: restructure README.md — 2,539 → 209 lines (#247)

- Cut from 2,539 lines / 73 sections to 209 lines / 18 sections
- Consolidated 4 install methods into one unified section
- Moved all skill details to domain-level READMEs (linked from table)
- Front-loaded value prop and keywords for SEO
- Added POWERFUL tier highlight section
- Added skill-security-auditor showcase section
- Removed stale Q4 2025 roadmap, outdated ROI claims, duplicate content
- Fixed all internal links
- Clean heading hierarchy (H2 for main sections only)

Closes #233

Co-authored-by: Leo <leo@openclaw.ai>

* fix: enhance 5 skills with scripts, references, and Anthropic best practices (#248)

* fix(skill): enhance git-worktree-manager with scripts, references, and Anthropic best practices

* fix(skill): enhance mcp-server-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance changelog-generator with scripts, references, and Anthropic best practices

* fix(skill): enhance ci-cd-pipeline-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance prompt-engineer-toolkit with scripts, references, and Anthropic best practices

* docs: update README, CHANGELOG, and plugin metadata

* fix: correct marketing plugin count, expand thin references

---------

Co-authored-by: Leo <leo@openclaw.ai>

* ci: Add VirusTotal security scan for skills (#252)

* Dev (#231)

* Improve senior-fullstack skill description and workflow validation

- Expand frontmatter description with concrete actions and trigger clauses
- Add validation steps to scaffolding workflow (verify scaffold succeeded)
- Add re-run verification step to audit workflow (confirm P0 fixes)

* chore: sync codex skills symlinks [automated]

* fix(skill): normalize senior-fullstack frontmatter to inline format

Normalize YAML description from block scalar (>) to inline single-line
format matching all other 50+ skills. Align frontmatter trigger phrases
with the body's Trigger Phrases section to eliminate duplication.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* fix(ci): add GITHUB_TOKEN to checkout + restore corrupted skill descriptions

- Add token: ${{ secrets.GITHUB_TOKEN }} to actions/checkout@v4 in
  sync-codex-skills.yml so git-auto-commit-action can push back to branch
  (fixes: fatal: could not read Username, exit 128)
- Restore correct description for incident-commander (was: 'Skill from engineering-team')
- Restore correct description for senior-fullstack (was: '>')

* fix(ci): pass PROJECTS_TOKEN to fix automated commits + remove duplicate checkout

Fixes PROJECTS_TOKEN passthrough for git-auto-commit-action and removes duplicate checkout step in pr-issue-auto-close workflow.

* fix(ci): remove stray merge conflict marker in sync-codex-skills.yml (#221)

Co-authored-by: Leo <leo@leo-agent-server>

* fix(ci): fix workflow errors + add OpenClaw support (#222)

* feat: add 20 new practical skills for professional Claude Code users

New skills across 5 categories:

Engineering (12):
- git-worktree-manager: Parallel dev with port isolation & env sync
- ci-cd-pipeline-builder: Generate GitHub Actions/GitLab CI from stack analysis
- mcp-server-builder: Build MCP servers from OpenAPI specs
- changelog-generator: Conventional commits to structured changelogs
- pr-review-expert: Blast radius analysis & security scan for PRs
- api-test-suite-builder: Auto-generate test suites from API routes
- env-secrets-manager: .env management, leak detection, rotation workflows
- database-schema-designer: Requirements to migrations & types
- codebase-onboarding: Auto-generate onboarding docs from codebase
- performance-profiler: Node/Python/Go profiling & optimization
- runbook-generator: Operational runbooks from codebase analysis
- monorepo-navigator: Turborepo/Nx/pnpm workspace management

Engineering Team (2):
- stripe-integration-expert: Subscriptions, webhooks, billing patterns
- email-template-builder: React Email/MJML transactional email systems

Product Team (3):
- saas-scaffolder: Full SaaS project generation from product brief
- landing-page-generator: High-converting landing pages with copy frameworks
- competitive-teardown: Structured competitive product analysis

Business Growth (1):
- contract-and-proposal-writer: Contracts, SOWs, NDAs per jurisdiction

Marketing (1):
- prompt-engineer-toolkit: Systematic prompt development & A/B testing

Designed for daily professional use and commercial distribution.

* chore: sync codex skills symlinks [automated]

* docs: update README with 20 new skills, counts 65→86, new skills section

* docs: add commercial distribution plan (Stan Store + Gumroad)

* docs: rewrite CHANGELOG.md with v2.0.0 release (65 skills, 9 domains) (#226)

* docs: rewrite CHANGELOG.md with v2.0.0 release (65 skills, 9 domains)

- Consolidate 191 commits since v1.0.2 into proper v2.0.0 entry
- Document 12 POWERFUL-tier skills, 37 refactored skills
- Add new domains: business-growth, finance
- Document Codex support and marketplace integration
- Update version history summary table
- Clean up [Unreleased] to only planned work

* docs: add 24 POWERFUL-tier skills to plugin, fix counts to 85 across all docs

- Add engineering-advanced-skills plugin (24 POWERFUL-tier skills) to marketplace.json
- Add 13 missing skills to CHANGELOG v2.0.0 (agent-workflow-designer, api-test-suite-builder,
  changelog-generator, ci-cd-pipeline-builder, codebase-onboarding, database-schema-designer,
  env-secrets-manager, git-worktree-manager, mcp-server-builder, monorepo-navigator,
  performance-profiler, pr-review-expert, runbook-generator)
- Fix skill count: 86→85 (excl sample-skill) across README, CHANGELOG, marketplace.json
- Fix stale 53→85 references in README
- Add engineering-advanced-skills install command to README
- Update marketplace.json version to 2.0.0

---------

Co-authored-by: Leo <leo@openclaw.ai>

* feat: add skill-security-auditor POWERFUL-tier skill (#230)

Security audit and vulnerability scanner for AI agent skills before installation.

Scans for:
- Code execution risks (eval, exec, os.system, subprocess shell injection)
- Data exfiltration (outbound HTTP, credential harvesting, env var extraction)
- Prompt injection in SKILL.md (system override, role hijack, safety bypass)
- Dependency supply chain (typosquatting, unpinned versions, runtime installs)
- File system abuse (boundary violations, binaries, symlinks, hidden files)
- Privilege escalation (sudo, SUID, cron manipulation, shell config writes)
- Obfuscation (base64, hex encoding, chr chains, codecs)

Produces clear PASS/WARN/FAIL verdict with per-finding remediation guidance.
Supports local dirs, git repo URLs, JSON output, strict mode, and CI/CD integration.

Includes:
- scripts/skill_security_auditor.py (1049 lines, zero dependencies)
- references/threat-model.md (complete attack vector documentation)
- SKILL.md with usage guide and report format

Tested against: rag-architect (PASS), agent-designer (PASS), senior-secops (FAIL - correctly flagged eval/exec patterns).

Co-authored-by: Leo <leo@openclaw.ai>

* docs: add skill-security-auditor to marketplace, README, and CHANGELOG

- Add standalone plugin entry for skill-security-auditor in marketplace.json
- Update engineering-advanced-skills plugin description to include it
- Update skill counts: 85→86 across README, CHANGELOG, marketplace
- Add install command to README Quick Install section
- Add to CHANGELOG [Unreleased] section

---------

Co-authored-by: Baptiste Fernandez <fernandez.baptiste1@gmail.com>
Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Leo <leo@leo-agent-server>
Co-authored-by: Leo <leo@openclaw.ai>

* Dev (#249)

* docs: restructure README.md — 2,539 → 209 lines (#247)

- Cut from 2,539 lines / 73 sections to 209 lines / 18 sections
- Consolidated 4 install methods into one unified section
- Moved all skill details to domain-level READMEs (linked from table)
- Front-loaded value prop and keywords for SEO
- Added POWERFUL tier highlight section
- Added skill-security-auditor showcase section
- Removed stale Q4 2025 roadmap, outdated ROI claims, duplicate content
- Fixed all internal links
- Clean heading hierarchy (H2 for main sections only)

Closes #233

Co-authored-by: Leo <leo@openclaw.ai>

* fix: enhance 5 skills with scripts, references, and Anthropic best practices (#248)

* fix(skill): enhance git-worktree-manager with scripts, references, and Anthropic best practices

* fix(skill): enhance mcp-server-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance changelog-generator with scripts, references, and Anthropic best practices

* fix(skill): enhance ci-cd-pipeline-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance prompt-engineer-toolkit with scripts, references, and Anthropic best practices

* docs: update README, CHANGELOG, and plugin metadata

* fix: correct marketing plugin count, expand thin references

---------

Co-authored-by: Leo <leo@openclaw.ai>

---------

Co-authored-by: Leo <leo@openclaw.ai>

* Dev (#250)

* docs: restructure README.md — 2,539 → 209 lines (#247)

- Cut from 2,539 lines / 73 sections to 209 lines / 18 sections
- Consolidated 4 install methods into one unified section
- Moved all skill details to domain-level READMEs (linked from table)
- Front-loaded value prop and keywords for SEO
- Added POWERFUL tier highlight section
- Added skill-security-auditor showcase section
- Removed stale Q4 2025 roadmap, outdated ROI claims, duplicate content
- Fixed all internal links
- Clean heading hierarchy (H2 for main sections only)

Closes #233

Co-authored-by: Leo <leo@openclaw.ai>

* fix: enhance 5 skills with scripts, references, and Anthropic best practices (#248)

* fix(skill): enhance git-worktree-manager with scripts, references, and Anthropic best practices

* fix(skill): enhance mcp-server-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance changelog-generator with scripts, references, and Anthropic best practices

* fix(skill): enhance ci-cd-pipeline-builder with scripts, references, and Anthropic best practices

* fix(skill): enhance prompt-engineer-toolkit with scripts, references, and Anthropic best practices

* docs: update README, CHANGELOG, and plugin metadata

* fix: correct marketing plugin count, expand thin references

---------

Co-authored-by: Leo <leo@openclaw.ai>

---------

Co-authored-by: Leo <leo@openclaw.ai>

* ci: add VirusTotal security scan for skills

- Scans changed skill directories on PRs to dev/main
- Scans all skills on release publish
- Posts scan results as PR comment with analysis links
- Rate-limited to 4 req/min (free tier compatible)
- Appends VirusTotal links to release body on publish

* fix: resolve YAML lint errors in virustotal workflow

- Add document start marker (---)
- Quote 'on' key for truthy lint rule
- Remove trailing spaces
- Break long lines under 160 char limit

---------

Co-authored-by: Baptiste Fernandez <fernandez.baptiste1@gmail.com>
Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Leo <leo@leo-agent-server>
Co-authored-by: Leo <leo@openclaw.ai>

* feat: add playwright-pro plugin — production-grade Playwright testing toolkit (#254)

Complete Claude Code plugin with:
- 9 skills (/pw:init, generate, review, fix, migrate, coverage, testrail, browserstack, report)
- 3 specialized agents (test-architect, test-debugger, migration-planner)
- 55 test case templates across 11 categories (auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility)
- TestRail MCP server (TypeScript) — 8 tools for bidirectional sync
- BrowserStack MCP server (TypeScript) — 7 tools for cross-browser testing
- Smart hooks (auto-validate tests, auto-detect Playwright projects)
- 6 curated reference docs (golden rules, locators, assertions, fixtures, pitfalls, flaky tests)
- Leverages Claude Code built-ins (/batch, /debug, Explore subagent)
- Zero-config for core features; TestRail/BrowserStack via env vars
- Both TypeScript and JavaScript support throughout

Co-authored-by: Leo <leo@openclaw.ai>

* feat: add playwright-pro to marketplace registry (#256)

- New plugin: playwright-pro (9 skills, 3 agents, 55 templates, 2 MCP servers)
- Install: /plugin install playwright-pro@claude-code-skills
- Total marketplace plugins: 17

Co-authored-by: Leo <leo@openclaw.ai>

* fix: integrate playwright-pro across all platforms (#258)

- Add root SKILL.md for OpenClaw and ClawHub compatibility
- Add to README: Skills Overview table, install section, badge count
- Regenerate .codex/skills-index.json with playwright-pro entry
- Add .codex/skills/playwright-pro symlink for Codex CLI
- Fix YAML frontmatter (single-line description for index parsing)

Platforms verified:
- Claude Code: marketplace.json  (merged in PR #256)
- Codex CLI: symlink + skills-index.json 
- OpenClaw: SKILL.md auto-discovered by install script 
- ClawHub: published as playwright-pro@1.1.0 

Co-authored-by: Leo <leo@openclaw.ai>

* docs: update CLAUDE.md — reflect 87 skills across 9 domains

Sync CLAUDE.md with actual repository state: add Engineering POWERFUL tier
(25 skills), update all skill counts, add plugin registry references, and
replace stale sprint section with v2.0.0 version info.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* docs: mention Claude Code in project description

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* feat: add self-improving-agent plugin — auto-memory curation for Claude Code (#260)

New plugin: engineering-team/self-improving-agent/
- 5 skills: /si:review, /si:promote, /si:extract, /si:status, /si:remember
- 2 agents: memory-analyst, skill-extractor
- 1 hook: PostToolUse error capture (zero overhead on success)
- 3 reference docs: memory architecture, promotion rules, rules directory patterns
- 2 templates: rule template, skill template
- 20 files, 1,829 lines

Integrates natively with Claude Code's auto-memory (v2.1.32+).
Reads from ~/.claude/projects/<path>/memory/ — no duplicate storage.
Promotes proven patterns from MEMORY.md to CLAUDE.md or .claude/rules/.

Also:
- Added to marketplace.json (18 plugins total)
- Added to README (Skills Overview + install section)
- Updated badge count to 88+
- Regenerated .codex/skills-index.json + symlink

Co-authored-by: Leo <leo@openclaw.ai>

* feat: C-Suite expansion — 8 new executive advisory roles (2→10) (#264)

* feat: C-Suite expansion — 8 new executive advisory roles

Add COO, CPO, CMO, CFO, CRO, CISO, CHRO advisors and Executive Mentor.
Expands C-level advisory from 2 to 10 roles with 74 total files.

Each role includes:
- SKILL.md (lean, <5KB, ~1200 tokens for context efficiency)
- Reference docs (loaded on demand, not at startup)
- Python analysis scripts (stdlib only, runnable CLI)

Executive Mentor features /em: slash commands (challenge, board-prep,
hard-call, stress-test, postmortem) with devil's advocate agent.

21 Python tools, 24 reference frameworks, 28,379 total lines.
All SKILL.md files combined: ~17K tokens (8.5% of 200K context window).

Badge: 88 → 116 skills

* feat: C-Suite orchestration layer + 18 complementary skills

ORCHESTRATION (new):
- cs-onboard: Founder interview → company-context.md
- chief-of-staff: Routing, synthesis, inter-agent orchestration
- board-meeting: 6-phase multi-agent deliberation protocol
- decision-logger: Two-layer memory (raw transcripts + approved decisions)
- agent-protocol: Inter-agent invocation with loop prevention
- context-engine: Company context loading + anonymization

CROSS-CUTTING CAPABILITIES (new):
- board-deck-builder: Board/investor update assembly
- scenario-war-room: Cascading multi-variable what-if modeling
- competitive-intel: Systematic competitor tracking + battlecards
- org-health-diagnostic: Cross-functional health scoring (8 dimensions)
- ma-playbook: M&A strategy (acquiring + being acquired)
- intl-expansion: International market entry frameworks

CULTURE & COLLABORATION (new):
- culture-architect: Values → behaviors, culture code, health assessment
- company-os: EOS/Scaling Up operating system selection + implementation
- founder-coach: Founder development, delegation, blind spots
- strategic-alignment: Strategy cascade, silo detection, alignment scoring
- change-management: ADKAR-based change rollout framework
- internal-narrative: One story across employees/investors/customers

UPGRADES TO EXISTING ROLES:
- All 10 roles get reasoning technique directives
- All 10 roles get company-context.md integration
- All 10 roles get board meeting isolation rules
- CEO gets stage-adaptive temporal horizons (seed→C)

Key design decisions:
- Two-layer memory prevents hallucinated consensus from rejected ideas
- Phase 2 isolation: agents think independently before cross-examination
- Executive Mentor (The Critic) sees all perspectives, others don't
- 25 Python tools total (stdlib only, no dependencies)

52 new files, 10 modified, 10,862 new lines.
Total C-suite ecosystem: 134 files, 39,131 lines.

* fix: connect all dots — Chief of Staff routes to all 28 skills

- Added complementary skills registry to routing-matrix.md
- Chief of Staff SKILL.md now lists all 28 skills in ecosystem
- Added integration tables to scenario-war-room and competitive-intel
- Badge: 116 → 134 skills
- README: C-Level Advisory count 10 → 28

Quality audit passed:
 All 10 roles: company-context, reasoning, isolation, invocation
 All 6 phases in board meeting
 Two-layer memory with DO_NOT_RESURFACE
 Loop prevention (no self-invoke, max depth 2, no circular)
 All /em: commands present
 All complementary skills cross-reference roles
 Chief of Staff routes to every skill in ecosystem

* refactor: CEO + CTO advisors upgraded to C-suite parity

Both roles now match the structural standard of all new roles:
- CEO: 11.7KB → 6.8KB SKILL.md (heavy content stays in references)
- CTO: 10KB → 7.2KB SKILL.md (heavy content stays in references)

Added to both:
- Integration table (who they work with and when)
- Key diagnostic questions
- Structured metrics dashboard table
- Consistent section ordering (Keywords → Quick Start → Responsibilities → Questions → Metrics → Red Flags → Integration → Reasoning → Context)

CEO additions:
- Stage-adaptive temporal horizons (seed=3m/6m/12m → B+=1y/3y/5y)
- Cross-references to culture-architect and board-deck-builder

CTO additions:
- Key Questions section (7 diagnostic questions)
- Structured metrics table (DORA + debt + team + architecture + cost)
- Cross-references to all peer roles

All 10 roles now pass structural parity:  Keywords  QuickStart  Questions  Metrics  RedFlags  Integration

* feat: add proactive triggers + output artifacts to all 10 roles

Every C-suite role now specifies:
- Proactive Triggers: 'surface these without being asked' — context-driven
  early warnings that make advisors proactive, not reactive
- Output Artifacts: concrete deliverables per request type (what you ask →
  what you get)

CEO: runway alerts, board prep triggers, strategy review nudges
CTO: deploy frequency monitoring, tech debt thresholds, bus factor flags
COO: blocker detection, scaling threshold warnings, cadence gaps
CPO: retention curve monitoring, portfolio dog detection, research gaps
CMO: CAC trend monitoring, positioning gaps, budget staleness
CFO: runway forecasting, burn multiple alerts, scenario planning gaps
CRO: NRR monitoring, pipeline coverage, pricing review triggers
CISO: audit overdue alerts, compliance gaps, vendor risk
CHRO: retention risk, comp band gaps, org scaling thresholds
Executive Mentor: board prep triggers, groupthink detection, hard call surfacing

This transforms the C-suite from reactive advisors into proactive partners.

* feat: User Communication Standard — structured output for all roles

Defines 3 output formats in agent-protocol/SKILL.md:

1. Standard Output: Bottom Line → What → Why → How to Act → Risks → Your Decision
2. Proactive Alert: What I Noticed → Why It Matters → Action → Urgency (🔴🟡)
3. Board Meeting: Decision Required → Perspectives → Agree/Disagree → Critic → Action Items

10 non-negotiable rules:
- Bottom line first, always
- Results and decisions only (no process narration)
- What + Why + How for every finding
- Actions have owners and deadlines ('we should consider' is banned)
- Decisions framed as options with trade-offs
- Founder is the highest authority — roles recommend, founder decides
- Risks are concrete (if X → Y, costs $Z)
- Max 5 bullets per section
- No jargon without explanation
- Silence over fabricated updates

All 10 roles reference this standard.
Chief of Staff enforces it as a quality gate.
Board meeting Phase 4 uses the Board Meeting Output format.

* feat: Internal Quality Loop — verification before delivery

No role presents to the founder without passing verification:

Step 1: Self-Verification (every role, every time)
  - Source attribution: where did each data point come from?
  - Assumption audit: [VERIFIED] vs [ASSUMED] tags on every finding
  - Confidence scoring: 🟢 high / 🟡 medium / 🔴 low per finding
  - Contradiction check against company-context + decision log
  - 'So what?' test: every finding needs a business consequence

Step 2: Peer Verification (cross-functional)
  - Financial claims → CFO validates math
  - Revenue projections → CRO validates pipeline backing
  - Technical feasibility → CTO validates
  - People/hiring impact → CHRO validates
  - Skip for single-domain, low-stakes questions

Step 3: Critic Pre-Screen (high-stakes only)
  - Irreversible decisions, >20% runway impact, strategy changes
  - Executive Mentor finds weakest point before founder sees it
  - Suspicious consensus triggers mandatory pre-screen

Step 4: Course Correction (after founder feedback)
  - Approve → log + assign actions
  - Modify → re-verify changed parts
  - Reject → DO_NOT_RESURFACE + learn why
  - 30/60/90 day post-decision review

Board meeting contributions now require self-verified format with
confidence tags and source attribution on every finding.

* fix: resolve PR review issues 1, 4, and minor observation

Issue 1: c-level-advisor/CLAUDE.md — completely rewritten
  - Was: 2 skills (CEO, CTO only), dated Nov 2025
  - Now: full 28-skill ecosystem map with architecture diagram,
    all roles/orchestration/cross-cutting/culture skills listed,
    design decisions, integration with other domains

Issue 4: Root CLAUDE.md — updated all stale counts
  - 87 → 134 skills across all 3 references
  - C-Level: 2 → 33 (10 roles + 5 mentor commands + 18 complementary)
  - Tool count: 160+ → 185+
  - Reference count: 200+ → 250+

Minor observation: Documented plugin.json convention
  - Explained in c-level-advisor/CLAUDE.md that only executive-mentor
    has plugin.json because only it has slash commands (/em: namespace)
  - Other skills are invoked by name through Chief of Staff or directly

Also fixed: README.md 88+ → 134 in two places (first line + skills section)

* fix: update all plugin/index registrations for 28-skill C-suite

1. c-level-advisor/.claude-plugin/plugin.json — v2.0.0
   - Was: 2 skills, generic description
   - Now: all 28 skills listed with descriptions, all 25 scripts,
     namespace 'cs', full ecosystem description

2. .codex/skills-index.json — added 18 complementary skills
   - Was: 10 roles only
   - Now: 28 total c-level entries (10 roles + 6 orchestration +
     6 cross-cutting + 6 culture)
   - Each with full description for skill discovery

3. .claude-plugin/marketplace.json — updated c-level-skills entry
   - Was: generic 2-skill description
   - Now: v2.0.0, full 28-skill ecosystem description,
     skills_count: 28, scripts_count: 25

* feat: add root SKILL.md for c-level-advisor ClawHub package

---------

Co-authored-by: Leo <leo@openclaw.ai>

* chore: sync codex skills symlinks [automated]

---------

Co-authored-by: Leo <leo@openclaw.ai>
Co-authored-by: Baptiste Fernandez <fernandez.baptiste1@gmail.com>
Co-authored-by: alirezarezvani <5697919+alirezarezvani@users.noreply.github.com>
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
Co-authored-by: Leo <leo@leo-agent-server>
2026-03-06 01:35:45 +01:00

16 KiB

Sales Playbook

Frameworks for building, running, and scaling a B2B SaaS sales organization.


Sales Process Design

A sales process is a repeatable series of steps that takes a prospect from first contact to closed revenue. Without it, you have individual heroics, not a scalable machine.

The Core Funnel

Lead Generation → Qualification → Discovery → Demo → Trial / POC → Proposal → Negotiation → Close → Handoff

Each stage has a clear entry criterion, exit criterion, and owner.

Stage Definitions

Stage 0: Lead / Suspect

  • Entry: Contact exists in CRM with basic firmographic data
  • Owner: Marketing or SDR
  • Exit criterion: Meets ICP criteria (company size, industry, tech stack)
  • Action: Research, prioritize, add to outbound sequence

Stage 1: Prospecting / Outreach

  • Entry: ICP-qualified account, no contact yet
  • Owner: SDR or AE (depending on model)
  • Exit criterion: Meeting booked with a qualified contact
  • Action: Multi-channel outreach (email + call + LinkedIn), 8-12 touch sequence
  • Key metric: Meeting booked rate (benchmark: 2-5% of outbound contacts)

Stage 2: Discovery

  • Entry: First meeting confirmed
  • Owner: AE (SDR hands off or joins)
  • Exit criterion: Confirmed: pain, budget range, decision process, timeline
  • Action: Ask questions. Listen. Map the org. Don't pitch yet.
  • Key metric: Discovery-to-demo rate (benchmark: 60-80% proceed)

Discovery question framework:

Situation:    "How do you currently handle [problem area]?"
Problem:      "What's the impact when [pain point] happens?"
Implication:  "If this continues, what does that mean for [business goal]?"
Need-payoff:  "If we solved this, what would that be worth to you?"

Stage 3: Demo / Solution Presentation

  • Entry: Confirmed pain and fit from discovery
  • Owner: AE (+ SE for complex products)
  • Exit criterion: Prospect agrees to evaluate / trial; next step defined
  • Action: Show the workflow that solves their specific pain (not a feature tour)
  • Key metric: Demo-to-trial/proposal rate (benchmark: 40-60%)

Demo structure:

  1. Recap their pain (show you listened) — 5 min
  2. Show the "aha moment" (fastest path to value) — 10 min
  3. Walk the specific workflow they described — 15 min
  4. Handle objections, confirm fit — 5 min
  5. Define clear next step (date, owners, criteria) — 5 min

Never show features they didn't ask for. Every additional feature is noise until they have a reason to care.

Stage 4: Trial / POC

  • Entry: Prospect commits to evaluate with real data/use case
  • Owner: AE + CSM or SE
  • Exit criterion: Success criteria met, POC success confirmed
  • Action: Define success criteria upfront (in writing). Set a tight timeframe (2-4 weeks max).
  • Key metric: POC-to-proposal rate (benchmark: 50-70%)

POC setup requirements:

Before any POC:
  □ Signed NDA
  □ Written success criteria ("We'll move forward if X happens")
  □ Named champion who owns the evaluation
  □ Executive sponsor identified
  □ Defined timeline with end date
  □ Agreed next step if criteria are met

If you can't get written success criteria, you don't have a real opportunity. You have a "we'll see."

Stage 5: Proposal / Pricing

  • Entry: POC success OR strong discovery fit for simple products
  • Owner: AE
  • Exit criterion: Proposal received, timeline to decision confirmed
  • Action: Present in a live call, never email a proposal cold
  • Key metric: Proposal-to-negotiation rate (benchmark: 50-75%)

Proposal structure:

  1. Problem statement (their words, not yours)
  2. Proposed solution (mapped to their workflow)
  3. ROI summary (value delivered vs. investment)
  4. Pricing options (give 2-3 options; anchors the decision)
  5. Next steps with dates

Stage 6: Negotiation

  • Entry: Verbal intent to proceed, price/terms discussion begins
  • Owner: AE (+ VP Sales for large deals)
  • Exit criterion: Mutual agreement on terms; contract sent
  • Action: Never discount before they ask. Discount on scope, not on margin.
  • Key metric: Negotiation win rate (benchmark: 70-85%)

Negotiation principles:

  • Get something for everything you give. Discount → multi-year. Fast close → early pay discount.
  • Don't negotiate against yourself. Silence after an offer is not rejection.
  • Know your walk-away before you enter. If you don't have a BATNA, you have no leverage.
  • Legal/procurement delay ≠ deal death. Keep the champion engaged.

Stage 7: Close

  • Entry: Signed contract or PO received
  • Owner: AE
  • Exit criterion: Contract countersigned, kickoff date set
  • Action: Celebrate with the customer. Immediately introduce CSM.
  • Key metric: Average close rate (closed won ÷ all closed = won + lost)

Stage 8: Handoff to Customer Success

  • Entry: Deal closed
  • Owner: AE + CSM
  • Exit criterion: Customer has met their assigned CSM, kickoff scheduled
  • Action: Internal handoff call with AE + CSM. AE shares: deal context, key stakeholders, use case, success criteria, any promises made during the sale.

Handoff document (AE fills before first CS meeting):

Account: [name]
ACV: $X
Close date: [date]
Primary contact: [name, title, email]
Economic buyer: [name, title]
Use case: [specific workflow]
Success criteria: [what they said good looks like in 90 days]
Promises made: [anything specific committed during sale]
Risk flags: [competitive, budget, champion strength]

MEDDPICC Qualification Framework

MEDDPICC is the enterprise qualification standard. If you can't answer every letter, you don't have a qualified opportunity — you have a conversation.

M — Metrics

What is the quantified business impact? What does winning look like in numbers?

  • "What's the current cost of [the problem]?"
  • "How do you measure success in this area today?"
  • "If we achieve X outcome, what does that save or earn you?"

Red flag: No metrics = no business case = hard to get budget.

E — Economic Buyer

Who has final authority to approve the budget?

  • "Who else will be involved in the final decision?"
  • "Have you purchased solutions in this range before? Who approved that?"
  • "When we get to final terms, who needs to sign?"

Red flag: You only know the user buyer. Economic buyer hasn't engaged.

D — Decision Criteria

What factors will they use to evaluate and select a solution?

  • "What's most important in your evaluation?"
  • "How will you compare options?"
  • "What does the ideal solution look like to you?"

Why it matters: If you don't know their criteria, you're guessing what to prove. Define the criteria before you compete on them.

D — Decision Process

What are the steps from evaluation to signed contract?

  • "Walk me through your process from here to signed agreement."
  • "Does procurement get involved? Legal? InfoSec?"
  • "Have you purchased software at this price before? How long did that take?"

Red flag: No defined process = unlimited sales cycle.

P — Paper Process

What's the contract and legal process?

  • "Who manages vendor contracts on your side?"
  • "What's your standard MSA, or do you use ours?"
  • "How long does legal review typically take?"

Why it matters: Legal and procurement have killed many "done" deals. Start early. Route to your legal team simultaneously.

I — Identify Pain

What is the specific, felt pain driving this evaluation?

  • "What triggered this initiative now vs. six months ago?"
  • "What happens if you don't solve this in Q3?"
  • "On a scale of 1-10, how urgent is this for your team?"

Red flag: Pain isn't felt by the economic buyer. User pain ≠ budget authority.

C — Champion

Who will actively sell your solution internally when you're not in the room?

  • "Who else have you brought into this evaluation?"
  • "Can you help us get access to [economic buyer / IT / security]?"
  • "If the decision went the wrong way, who would be disappointed?"

Red flag: Your champion is enthusiastic but has no internal influence.

C — Competition

Who else are they evaluating? What's your position?

  • "Are you looking at alternatives?"
  • "What made you start with us?"
  • "Have you used [Competitor X] before?"

Why it matters: Knowing the competitive field tells you what you need to prove and what to neutralize.

MEDDPICC Scorecard

Letter Score 1 Score 2 Score 3
Metrics No numbers Approximate value Specific ROI model
Economic Buyer Unknown Named, not engaged Engaged directly
Decision Criteria Vague Partially defined Written, weighted
Decision Process Unknown Verbal description Steps confirmed, timeline known
Paper Process Unknown Basic awareness Legal contacts, standard process known
Identify Pain No urgency User-level pain Executive-level pain with consequences
Champion No advocate Friendly contact Actively selling internally
Competition Unknown Identified Position mapped, differentiation clear

Score each 1-3. Total 16+/24 = qualified opportunity. Under 12 = unqualified, do not forecast.


Sales Compensation Plans

Comp drives behavior. Design it precisely.

Base / Variable Split

Role Base % Variable % Rationale
SDR 60-70% 30-40% Activity-based, not purely revenue
AE (Inside Sales) 50% 50% Balanced risk/reward
AE (Enterprise) 55-60% 40-45% Longer cycle, higher base for stability
VP Sales 50% 50% Accountable for team results
CSM (retention focus) 70% 30% Less variable, stable relationship role
CSM (expansion focus) 60% 40% Expansion quota adds variable

Commission Structure

Standard AE plan:

Base: $80K
Variable: $80K (at 100% quota attainment)
OTE: $160K

Commission rate: OTE variable ÷ Quota
  If quota = $800K ARR: commission = $80K ÷ $800K = 10% of ARR closed

Accelerators (performance above quota):
  101-125% quota: 1.25x commission rate (12.5% of ARR)
  126-150% quota: 1.5x commission rate (15% of ARR)
  > 150% quota: 2.0x commission rate (20% of ARR)

Why accelerators matter:

  • They keep top performers motivated past quota
  • They make it possible for top reps to earn $200K+ (attracting talent)
  • They create the "make it rain" culture

SDR Compensation

SDRs are measured on output (meetings booked, pipeline created), not closed revenue.

Quota: 20 qualified meetings booked per month (or $X pipeline created)
Commission: $150-300 per qualified meeting held

Accelerators:
  If a meeting converts to closed won: Bonus $250-500
  If monthly meetings > 125% of quota: 1.5x rate on upside meetings

Clawbacks

A clawback recovers commission paid on deals that churn or are fraudulently closed.

Common clawback rules:

  • Full clawback if customer cancels within 90 days of close
  • 50% clawback if customer cancels within 91-180 days
  • No clawback after 180 days (AE shouldn't be penalized for future CS failures)
  • Clawbacks vest: pay commission immediately but apply against next quarter's payout if triggered

Why clawbacks matter:

  • Without them, reps are incentivized to close any deal, regardless of fit
  • With them, reps self-qualify more carefully

SPIFFs (Sales Performance Incentive Funds)

Short-term tactical incentives for specific behaviors:

  • $5K bonus for closing a new vertical deal this quarter
  • 1.5x commission on annual prepay deals in Q4
  • $1K for closing a deal in a new geographic territory

Use SPIFFs sparingly. Overuse trains reps to wait for the SPIFF before engaging.

Multi-Year and Prepay Incentives

Align rep behavior with company cash flow:

  • Multi-year deals: Credit full TCV against quota, pay commission upfront on TCV
  • Annual prepay: 10-20% uplift on commission rate
  • Monthly billing: Standard commission rate

Enterprise vs. SMB vs. Self-Serve Models

Self-Serve / PLG

Characteristics:

  • Product is the primary acquisition channel
  • Credit card required (no invoicing)
  • No human touch in the initial purchase
  • Sales engages only at enterprise signals (high usage, team expansion, compliance needs)

Funnel:

Website → Free trial / Freemium → Activation → PQL → Expansion → Enterprise

Key metrics:

  • Free-to-paid conversion rate (benchmark: 2-5% of signups)
  • Time to activation (first core action)
  • PQL → expansion conversion rate
  • NRR from self-serve base

Sales involvement triggers (PQL signals):

  • Team size > 10 seats
  • Usage spikes (power user patterns)
  • Feature limit hits on core features
  • Job title change (new economic buyer appears in account)

SMB Inside Sales

Characteristics:

  • ACV $5K-25K
  • 30-60 day sales cycle
  • Inbound-heavy or light outbound
  • SDR → AE → CS model
  • Phone + email + video; no in-person

Funnel:

Inbound/MQL → SDR qualifies → AE discovery → Demo → Proposal → Close

Key metrics:

  • MQL-to-SQL rate (benchmark: 15-25%)
  • SQL-to-close rate (benchmark: 20-30%)
  • Average sales cycle (30-60 days)
  • AE productivity: $600K-$1M quota per rep

Team ratios:

  • 1 SDR supports 3-4 AEs
  • 1 CSM manages $1M-2M ARR

Enterprise Sales

Characteristics:

  • ACV $50K+
  • 90-365 day sales cycle
  • Outbound prospecting + inbound from brand
  • AE + SE + executive sponsor model
  • Multi-stakeholder: champion, economic buyer, IT, legal, procurement

Funnel:

Account targeting → Executive outreach → Discovery → POC → Security review → Legal → Procurement → Close

Key metrics:

  • Deals in pipeline (volume matters less, quality more)
  • POC win rate (benchmark: 60-75%)
  • Average sales cycle (3-12 months)
  • AE productivity: $1.5M-$3M quota per rep

Team ratios:

  • 1 SE supports 3-4 AEs
  • 1 CSM manages $2M-5M ARR (named accounts, high-touch)

Sales Hiring and Ramp

What "Good" Looks Like by Role

SDR (entry level):

  • 1-2 years of outbound experience OR strong track record in customer-facing role
  • Resilient: rejection is the job
  • Coachable: SDR is a proving ground, not a final destination
  • Can write clear, concise prospecting emails without templates

AE (inside sales):

  • 2-4 years sales experience, preferably SaaS
  • Can articulate their process for a discovery call
  • Knows their numbers: quota, attainment, average deal size, sales cycle
  • Shows how they build pipeline (AEs who only work inbound are a risk)

AE (enterprise):

  • 4-8 years B2B sales, at least 2 in enterprise
  • Has closed deals > $100K ACV
  • Can name the stakeholders in a complex deal they navigated
  • Understands procurement, security review, multi-year contracts

VP Sales:

  • Has scaled a team from where you are to 2x your size
  • Can build a comp plan from scratch
  • Has hiring and firing experience
  • Revenue from a repeatable process, not personal relationships

Interview Process

3-stage process:

  1. Recruiter screen (30 min): Motivation, experience, logistics
  2. Manager interview (60 min): Structured questions on process, examples, numbers
  3. Panel / role play (90 min): Mock discovery call + debrief; team fit

Role play rubric:

  • Did they prepare (knew your product, your ICP)?
  • Did they ask before pitching?
  • Did they handle pushback without capitulating immediately?
  • Did they confirm a next step with a date?

Onboarding Structure (6-Week Ramp)

Week Focus Activities
1 Company, product, ICP Onboarding sessions, product sandbox, shadow AE calls
2 Sales process, tools, messaging CRM training, call review, write first prospecting emails
3 First outreach Send first sequences, book first meetings, shadow closes
4 Independent discovery Lead own discovery calls with manager reviewing
5 Full cycle Handle pipeline independently, weekly coaching
6 Quota-bearing 25% of quota expectation; full accountability begins

Performance Management

Clear standards, no surprises:

Month 3: 25% of quota expected. Miss by > 50% → performance conversation.
Month 4: 50% of quota expected. Miss by > 40% → PIP warning.
Month 5: 75% of quota. Miss by > 30% → formal PIP.
Month 6+: 100% of quota. Consistent miss → exit.

PIP (Performance Improvement Plan) — not for show:

  • Should include specific, measurable targets (not "improve attitude")
  • 30-60 day timeline
  • Weekly check-ins with manager
  • If targets aren't met: exit, no extensions
  • A PIP that doesn't lead to improvement or exit is a management failure

Rule: Low performers who stay cost you your top performers. They watch what you tolerate.