sales-strategist
Expert sales strategy and operations guidance for B2B SaaS companies. Use when designing sales processes, implementing qualification frameworks (MEDDIC, BANT, SPICED), territory planning, forecasting, quota setting, compensation design, or optimizing pipeline velocity. Covers sales methodology, org structure, tech stack selection, win rate analysis, and deal acceleration strategies.
What this skill does
# Sales Strategist
Strategic sales operations expertise for B2B SaaS companies — from process design and methodology selection to compensation planning and pipeline optimization.
## Philosophy
Great sales organizations are built on **process, not heroics**. The best quota-crushing reps eventually leave, but excellent sales systems compound.
The best B2B sales strategies:
1. **Process before people** — A-players in a broken system lose to B-players in a great system
2. **Qualify ruthlessly** — Time is inventory; don't waste it on bad-fit deals
3. **Forecast with discipline** — Hope is not a strategy; data is
4. **Align incentives** — Compensation drives behavior, design accordingly
5. **Iterate constantly** — Sales is a science; run experiments, measure results
## How This Skill Works
When invoked, apply the guidelines in `rules/` organized by:
- `methodology-*` — Sales frameworks, qualification criteria, selling approaches
- `process-*` — Sales stages, exit criteria, deal flow management
- `planning-*` — Territory design, account planning, forecasting
- `ops-*` — Quota setting, capacity planning, tech stack, compensation
- `optimization-*` — Win rate analysis, deal velocity, pipeline health
## Core Frameworks
### Sales Qualification Frameworks
| Framework | Focus | Best For | Key Questions |
|-----------|-------|----------|---------------|
| **MEDDIC** | Deal qualification | Enterprise, complex sales | Metrics, Economic Buyer, Decision criteria, Decision process, Identify pain, Champion |
| **BANT** | Lead qualification | Transactional, high volume | Budget, Authority, Need, Timeline |
| **SPICED** | Discovery | Consultative sales | Situation, Pain, Impact, Critical Event, Decision |
| **SCOTSMAN** | Opportunity scoring | Mid-market | Solution, Competition, Originality, Timescales, Size, Money, Authority, Need |
| **CHAMP** | Modern qualification | SaaS, product-led | Challenges, Authority, Money, Prioritization |
### The Sales Pipeline Hierarchy
```
┌─────────────────┐
│ Closed Won │ ← Revenue
├─────────────────┤
│ Negotiation │ ← Contract stage
├─────────────────┤
│ Proposal │ ← Pricing/SOW
├─────────────────┤
│ Evaluation │ ← POC/Trial
├─────────────────┤
│ Discovery │ ← Qualification
├─────────────────┤
│ Meeting Set │ ← First meeting
└─────────────────┘
```
### Sales Motion by ACV
| ACV Range | Motion | Team Structure | Sales Cycle |
|-----------|--------|----------------|-------------|
| **<$5K** | Self-serve/PLG | No AEs, maybe Success | Days-weeks |
| **$5K-$25K** | Transactional | SDR → AE (1:4 ratio) | 2-6 weeks |
| **$25K-$100K** | Mid-market | SDR → AE → CSM | 1-3 months |
| **$100K-$500K** | Enterprise | SDR → AE → SE → CSM | 3-9 months |
| **>$500K** | Strategic | Named accounts, exec sponsors | 6-18 months |
### Pipeline Coverage Model
```
┌─────────────────────────────────────────────────────────────┐
│ PIPELINE MATH │
├─────────────────────────────────────────────────────────────┤
│ Target Revenue: $1M │
│ Win Rate: 25% │
│ Required Pipeline: $4M (4x coverage) │
│ │
│ Average Deal Size: $50K │
│ Deals Needed: 80 opportunities │
│ │
│ Meeting → Opportunity Rate: 40% │
│ Meetings Needed: 200 │
│ │
│ Response → Meeting Rate: 20% │
│ Outreach Needed: 1,000 responses │
└─────────────────────────────────────────────────────────────┘
```
### Comp Plan Architecture
```
┌─────────────────────────────────────────────────────────────┐
│ COMPENSATION STRUCTURE │
├─────────────────────────────────────────────────────────────┤
│ Role │ Base:Variable │ OTE Range │ Quota Multiple│
│ ───────────────────────────────────────────────────────── │
│ SDR │ 70:30 │ $70-100K │ N/A (activity) │
│ AE (SMB) │ 50:50 │ $100-150K │ 4-5x OTE │
│ AE (MM) │ 50:50 │ $150-250K │ 4-5x OTE │
│ AE (Ent) │ 60:40 │ $250-400K │ 3-4x OTE │
│ Sales Mgr │ 60:40 │ $200-350K │ Team rollup │
└─────────────────────────────────────────────────────────────┘
```
## Sales Technology Stack
| Layer | Tools | Purpose |
|-------|-------|---------|
| **CRM** | Salesforce, HubSpot, Pipedrive | System of record |
| **Engagement** | Outreach, Salesloft, Apollo | Sequences, cadences |
| **Intelligence** | Gong, Chorus, Clari | Call recording, forecasting |
| **Enrichment** | ZoomInfo, Clearbit, Apollo | Contact/account data |
| **Scheduling** | Calendly, Chili Piper | Meeting booking |
| **CPQ** | DealHub, PandaDoc, Proposify | Quotes, contracts |
| **Analytics** | Clari, InsightSquared, Atrium | Pipeline analytics |
## Anti-Patterns
- **Happy ears** — Believing what prospects say without validation
- **Demo-first selling** — Showing product before understanding pain
- **Single-threaded deals** — Only one contact at an account
- **Sandbagged forecasts** — Reps hiding deals to sandbag
- **Commission clawback abuse** — Punishing reps for customer churn they can't control
- **Territory chaos** — Unclear or overlapping territories creating conflict
- **Discounting addiction** — Training buyers to always ask for discounts
- **Vanity pipeline** — Inflated stages, zombie deals, false confidence
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.