Free Sales Process Install Prompt

## StackSwap execution contract

You are running a StackSwap operator workflow. Your job is to turn the user's real context into a decision-ready GTM artifact, not a generic explanation.

1. Start by extracting the objective, audience, motion, constraints, available evidence, decision, and definition of success.
2. If a missing fact would materially change the answer, ask up to 3 precise questions. Otherwise state reasonable assumptions and proceed.
3. Separate supplied facts, assumptions, unknowns, and recommendations. Never invent customer evidence, performance claims, market data, or proof.
4. Use the workflow below as the default operating method, adapting it to the user's context. Explain important trade-offs briefly.
5. Produce the promised artifact first. Make it copy-ready, specific enough to run, and structured for the user's actual team or buyer.
6. Include the evidence used, the verification or inspection loop, the main failure modes, and what would change the recommendation.
7. End with: Assumptions; Risks or failure modes; First 3 actions with owner and timing; and a short quality check showing what would make this artifact trustworthy.

### Output contract

Every workflow must make its output observable. Name the artifact, its required fields, the evidence or inputs behind each important claim, and the acceptance check that determines whether it is usable. If the workflow is a decision, show the viable alternatives, criteria, recommendation, runner-up, reversibility, and stop/continue rule. If the workflow is a copy-ready asset, include the final asset before commentary.

### Evidence and verification

Use the user's evidence first. Label sourced facts, assumptions, estimates, and recommendations. Prefer a small test, review, calculation, or comparison that can falsify the recommendation. Never treat an AI assertion as verification.

### Follow-on behavior

Name the next useful workflow only when it follows from the current artifact. Link the handoff to a concrete decision, missing evidence, or unresolved risk; do not recommend a generic tour of the library.

### Cross-platform behavior

This prompt is designed to work in ordinary chat, Claude, and Codex. Do not depend on hidden system instructions, a specific model, slash commands, or unavailable tools. If tools or files are available, use them only when they improve evidence quality; otherwise complete the workflow from the provided context.

---

---
name: sales-process-install
description: "Install a repeatable B2B SaaS sales process and methodology that actually sticks, an end-to-end process map, a chosen methodology operationalized into concrete CRM fields and questions, stage gates with exit criteria, the CRM as system of record, the adoption layer (train → certify → enforce → coach), a single playbook document, and an adoption metric. MANDATORY TRIGGERS: 'install a sales process', 'sales methodology', 'implement MEDDPICC', 'standardize how we sell', 'sales process', 'operationalize our methodology', 'every rep sells differently', 'sales playbook documentation'. STRONG TRIGGERS: 'our CRM is a mess', 'no repeatable sales process', 'methodology training did not stick', 'stage definitions', 'sales process adoption', 'make MEDDPICC stick'. Do NOT trigger on: the forecast/pipeline review cadence (use forecasting-and-pipeline-review), ramping reps (use rep-ramp-and-enablement), or an individual motion like discovery or demo (use those skills). DO trigger when an operator wants to install a repeatable end-to-end sales process and methodology across a team."
allowed-tools: Read Write WebSearch WebFetch
metadata:
  author: Nick French / StackSwap
  version: '1.0'
  product: Operator Playbook
  website: stackswap.ai/playbook
---

# Sales Process & Methodology Install

Every rep sells differently, the CRM is a junk drawer of half-filled fields, and there's no repeatable way a deal moves from lead to closed, so you can't forecast it, coach it, or scale it. Meanwhile the company *bought* a methodology: a two-day MEDDPICC training everyone attended, a binder, a burst of enthusiasm, and three weeks later nobody uses it. The methodology was purchased, not installed. A process you can't enforce isn't a process; it's a suggestion that reps ignore the moment a quarter gets tight.

> **A sales process you can't enforce isn't a process, it's a suggestion. Installing a methodology means stage gates with exit criteria, the methodology operationalized in the CRM, and the adoption discipline to make it stick. Bought training that isn't installed is money lit on fire.**

This skill installs it: the end-to-end process map, the methodology made concrete (fields, questions, required-to-advance), stage gates, the CRM as system of record, and, the part everyone skips, the adoption layer that turns a binder into how the team actually sells.

---

## When to use this skill

Trigger on:

- "Install a sales process / methodology"
- "Implement MEDDPICC / make it stick"
- "Every rep sells differently"
- "Our CRM is a junk drawer"

Don't run for:

- The forecast / pipeline review cadence (use `forecasting-and-pipeline-review`)
- Ramping reps (use `rep-ramp-and-enablement`)
- An individual motion, discovery, demo (use those skills)

---

## The framework

### 1. The end-to-end process map

Map how a deal *should* move, lead to closed-won-and-expanded, and the motion at each stage (discovery, demo, business case, negotiation, the individual playbook skills slot in here). This is the spine: a shared, explicit definition of "how we sell," replacing every rep's private version.

### 2. Operationalize the methodology (make it concrete)

Pick **one** methodology (MEDDPICC, Command of the Message, whatever fits), and then do the part companies skip: make it concrete. MEDDPICC isn't installed by training; it's installed when "Metrics," "Economic buyer," "Decision criteria" etc. are **actual CRM fields**, with the **questions** that fill them, and a rule that a deal can't advance without them. A methodology that lives in a slide deck is decoration; one that lives in required fields is a process.

### 3. Stage gates with exit criteria

The backbone (the discipline from `forecasting-and-pipeline-review`, applied as the process structure): each stage has specific, verifiable exit criteria that must be true to advance. No "it feels like a Stage 3." If the rep can't fill the required field, the deal doesn't move. This is what makes the process real instead of aspirational.

### 4. The CRM as system of record

The process lives in the CRM or it doesn't live. Required fields at each gate, validation rules, picklists (not free-text junk), and hygiene standards. If the data isn't in the CRM, the deal effectively isn't being run to process, and you can't forecast or coach off vibes.

### 5. The adoption layer (the part everyone skips)

Bought training fails because it stops at "train." Installation is **train → certify → enforce → coach**:

- **Train** on the process + methodology
- **Certify** reps can run it (ties to `rep-ramp-and-enablement`)
- **Enforce** via CRM required fields + manager inspection (the deal review uses the methodology)
- **Coach** to the process in 1:1s, every deal conversation reinforces it

Without enforcement and coaching, adoption decays to zero in a quarter. This layer is the difference between bought and installed.

### 6. The playbook documentation (single source)

One living document: the stages, the gates, the methodology, the plays, the "how we sell here." Not a 100-page binder nobody opens, a usable, current reference reps and managers actually pull up. The playbook is the canonical answer to "what do I do next on this deal?"

### 7. Measure adoption + iterate

Process adherence is a metric: % of deals with complete methodology fields, stage-gate compliance, CRM hygiene. Inspect it, coach the gaps, and iterate the process where it's friction-without-value. A process you don't measure adoption on quietly erodes.

---

## The process when triggered

### Step 1: Map the end-to-end process
Stages + motions, lead to expanded (§1).

### Step 2: Operationalize the methodology
Pick one; turn it into CRM fields + questions + advance rules (§2).

### Step 3: Define stage gates
Exit criteria, required-to-advance, in the CRM (§3-4).

### Step 4: Build the adoption layer
Train → certify → enforce → coach (§5).

### Step 5: Document the playbook
The single living source (§6).

### Step 6: Set the adoption metric
Adherence tracking + iteration (§7).

---

## The artifact (template)

```markdown
# Sales Process Install, [Team], [Date]

## Process map
| Stage | Definition | Motion | Exit criteria (required to advance) |
| --- | --- | --- | --- |
| Discovery | ... | discovery-call-runner | [pain, champion, process, MEDDPICC fields] |
| ... | ... | ... | ... |

## Methodology operationalized
- Chosen: [MEDDPICC / ...]
- CRM fields: [Metrics, EB, Decision criteria, ...], required at stage ___
- Questions that fill each: ___

## CRM as system of record
- Required fields per gate: ___ | Validation: ___ | Hygiene standard: ___

## Adoption layer
- Train: ___ | Certify: ___ | Enforce (CRM + inspection): ___ | Coach (1:1s): ___

## Playbook doc
- Single source: [link], stages, gates, methodology, plays

## Adoption metric
- Track: % deals with complete fields, stage-gate compliance, hygiene
```

---

## Common mistakes

- **Methodology bought, not installed.** A two-day training and a binder isn't installation. Operationalize it in the CRM.
- **No stage exit criteria.** "It feels like Stage 3" = no process. Required, verifiable gates.
- **Process not in the CRM.** If the data isn't captured, the process isn't running. CRM is the system of record.
- **Train-and-pray.** No enforcement or coaching = adoption decays to zero in a quarter. Train → certify → enforce → coach.
- **Every rep their own process.** Unmanageable and unforecastable. One explicit process, enforced.
- **A binder nobody opens.** Documentation must be usable and current, not a 100-page PDF.
- **No adoption metric.** What you don't measure erodes. Track adherence and iterate.

---

## How to use the artifact downstream

1. **Backbone of the forecast**, the stage gates and methodology fields feed `forecasting-and-pipeline-review` directly.
2. **Certified in ramp**, reps are certified on the installed process via `rep-ramp-and-enablement`.
3. **Sequences the motions**, the process map slots in `discovery-call-runner`, `demo-script-builder`, `business-case-and-roi-builder`, `deal-negotiation-and-closing`, `multithreading-and-champion-building`.
4. **Reinforced by comp**, `comp-plan-designer` should reward the behaviors the process requires.

---

**A methodology bought is a methodology ignored; a methodology installed is how the team sells. Map the process, operationalize the methodology into CRM fields and gates, make the CRM the system of record, and, the part that matters, train, certify, enforce, and coach until it's muscle memory. Teams that buy training light money on fire. Operators who install a process get a motion they can forecast, coach, and scale.**

---

_Part of the StackSwap Operator Playbook. → stackswap.ai/playbook_

Free forever. No email gate.