The Sales Process Documentation Reboot — 60-Min Training

👁 0 views📖 1,913 words⏱ 9 min read📅 Published May 26, 2026 · Updated Jun 1, 2026

Direct Answer

A documented sales process is the highest-leverage RevOps artifact you own: it converts the tacit habits of your top reps into a repeatable system the rest of the team can execute. In this 60-minute training, you will install a 6-stage B2B SaaS process with verbatim entry and exit criteria, assign a single named owner, agree on a quarterly version-control cadence, kill 30% of the bloat your team is currently ignoring, and hang a process-map wall poster everyone can point at on day one of next quarter.

Stack You'll Run This Training Inside

Every AE in the room operates inside the standard RevOps stack. Reference these tools by name during the training so reps know which dashboard or workflow you mean. Pin the dashboard you'll inspect in Gong on a shared screen before the meeting starts, queue the most recent recording from Outreach as the coaching artifact, and have Clari open in a second tab for the post-meeting cadence updates.

The manager who shows up with these three browser tabs ready saves 8 minutes of meeting setup.

Gong at $1,600/user/year — call recording + AI coaching insights
Chorus at bundled with ZoomInfo at $1,200/user/year — call recording within the ZoomInfo stack
Outreach at $150/seat/month — sequence + cadence engine for follow-ups
Salesloft at $125/seat/month — cadence + Drift conversation routing
Clari at $75-$150/user/month — forecast accuracy + deal inspection
Highspot at $58/user/month base, content-volume-tiered — sales enablement + playbook delivery

Benchmark Context

IDC ("Worldwide Sales Enablement Spending Tracker, 2026") reports that enterprise sales orgs spent $4.7B on structured manager training programs in 2026, growing 18% YoY. Anchor the training narrative on this stat — it's the credibility frame that turns a 60-minute meeting from "another sales pep talk" into "the weekly working session the manager is measured on." Print the stat at the top of the meeting agenda; reps remember the number, and quoting it builds the same shared vocabulary that Lessonly, Spekit, and Highspot all flag as the top predictor of multi-quarter training-program ROI in their 2026 customer benchmarks.

Section 1 — The "Documented Process Beats Brilliant Individuals" Principle (5 min)

Open with Jason Jordan's core finding from *Cracking the Sales Management Code* (Jordan & Vazzana, McGraw-Hill, 2011): of the 306 sales metrics his team catalogued, only 17 are directly manageable — and nearly all of them sit inside the sales process itself. Stage conversion, time-in-stage, and stage-skip rates are the levers; revenue is a lagging output you cannot manage directly.

Mark Roberge makes the same case in *The Sales Acceleration Formula* (Wiley, 2015): the HubSpot ramp he built was repeatable precisely because the process was written down, scored, and version-controlled — not because he hired brilliant individuals.

State the rule of the room out loud:

Brilliant individuals leave. Documented processes stay, onboard the next hire in weeks instead of quarters, and let you forecast.
A process you cannot write down is a process you cannot coach. If you cannot point at the page, the rep cannot point at the page either.
Tribal knowledge is a tax paid by every new hire, every deal-desk escalation, and every QBR slide that says "it depends."

Section 2 — The 6-Stage B2B SaaS Process Template with Entry/Exit Criteria (15 min)

Walk the room through the template below. Force Management's MEDDICC-aligned stage definitions (see the public Command of the Message materials) and Jacco van der Kooij's *Blueprints for a SaaS Sales Organization* (3rd ed., Winning by Design, 2018) both insist that a stage is defined by buyer evidence, not seller activity.

Use this exact verbatim language on the wall poster.

Stage 1 — Prospect. Entry: account fits ICP. Exit: a named buyer has accepted a meeting and a calendar invite is on the books.
Stage 2 — Qualify. Entry: discovery meeting held. Exit: buyer has confirmed a business pain, an economic impact, and a decision timeline in writing (email or recap).
Stage 3 — Validate. Entry: technical or functional fit confirmed. Exit: a champion has been identified, mapped, and has agreed in writing to introduce the economic buyer.
Stage 4 — Propose. Entry: economic buyer meeting held; success criteria documented. Exit: a written proposal with pricing has been delivered AND a mutual action plan signed back.
Stage 5 — Negotiate. Entry: verbal commitment from economic buyer. Exit: redlines exchanged; procurement and security have a named owner on the buyer side.
Stage 6 — Close. Entry: paper out for signature. Exit: countersigned order form received; handoff to CS scheduled within 5 business days.

flowchart TD A[Stage 1: Prospect Exit: meeting booked] B[Stage 2: Qualify Exit: pain + impact + timeline] C[Stage 3: Validate Exit: champion confirmed] D[Stage 4: Propose Exit: MAP signed back] E[Stage 5: Negotiate Exit: procurement engaged] F[Stage 6: Close Exit: countersigned + CS handoff] A --> B --> C --> D --> E --> F

Trish Bertuzzi's rule from *The Sales Development Playbook* (Moore-Lake, 2016) applies at Stage 1: if SDR-sourced meetings cannot pass the "named buyer accepted" exit test, they do not count. Stop arguing about it in the deal desk.

Section 3 — Version Control and the One-Owner Rule (10 min)

Sales process documents rot when nobody owns them. Force Management's enablement playbooks and Winning by Design's RevOps Academy both prescribe a single named owner — usually a RevOps lead or a Director of Sales Strategy — who holds the pen.

One named owner, full name on the document. "Sales leadership" is not an owner. "Priya Shah, Director of RevOps" is.
Semantic versioning on the file itself. v2026.2 means major revision 2 of calendar year 2026. Patch versions (v2026.2.1) are typo-level only.
Changelog at the top of the doc. Every change lists date, owner, what changed, and why. No silent edits.
Quarterly review cadence, locked in the calendar the same week as the QBR. Process review happens BEFORE pipeline review, not after.
Pull-request style proposals. Anyone can propose a change in a shared doc; only the owner merges. This kills the "the VP told me on a plane" change pattern.

Section 4 — Anti-Bloat: Kill 30% Every Year (10 min)

Every documented sales process grows barnacles: fields nobody fills in, stages nobody enforces, exit criteria added after one bad deal and never removed. Jacco van der Kooij calls this "process debt." Your job, once a year, is to take 30% out.

Run this exercise live in the room. Pull up the current process doc and the Salesforce stage field list on screen.

Salesforce required-field audit. For each required field, ask: "When was this last used in a deal review?" If the answer is "I don't remember," it goes.
Stage exit criteria audit. For each exit criterion, ask: "Did we enforce this on the last 5 closed-won deals?" If no, either enforce it next quarter or delete it.
Stage count audit. If you have more than 7 forecast stages, you have too many. Roberge ran HubSpot on 4. Most $25K-$500K ACV teams do not need more than 6.
The "one-page test." If the process does not fit on one page printed at 11pt, it is not a process — it is a wiki article nobody reads.

flowchart TD A[Annual Process Review] B{Field/stage used in last 5 deals?} C[Keep + reinforce] D[Cut — document why] E[Republish v.next] F[Wall poster reprint] A --> B B -- Yes --> C B -- No --> D C --> E D --> E E --> F

Section 5 — The Process Map Wall Poster Artifact (15 min)

The deliverable from this hour is a physical artifact. Print it 24" x 36", laminated, on the wall behind the SDR pit and the AE bullpen, and ship a PDF version to remote reps. Force Management calls this "making the process unavoidable."

Build the poster live with the group, using a shared doc projected on the screen. Required elements, in this order, top to bottom:

Header. Process name, version number, owner name, effective date. Example: "Acme Sales Process v2026.2 — owner: Priya Shah — effective 2026-04-01."
The 6 stages as horizontal boxes, with the verbatim exit criterion underneath each. No marketing language. No verbs the rep cannot perform.
The one-sentence rule for every stage: "A deal cannot advance to the next stage until the exit criterion above is documented in the opportunity record."
The disqualification path. Where do dead deals go, and who closes them? Most teams skip this and accumulate zombie pipeline.
The handoff arrows. SDR to AE at Stage 1 exit. AE to SE at Stage 3 entry. AE to CS at Stage 6 exit. Names and SLAs on each arrow.
A QR code linking to the living doc. The poster is the summary; the doc is the source of truth.

Close the section by assigning two people in the room: the poster designer (gets it printed by Friday) and the doc owner (publishes v.next within 10 business days).

Section 6 — Commitments and Close (5 min)

End with three named commitments written on the whiteboard. Bertuzzi's rule: a meeting without named owners and dates is a meeting that did not happen.

Owner assigned, on the doc, this week — full name, no committees.
v.next published within 10 business days — including the 30% cut.
Wall poster up by end of next sprint — and reprinted every quarterly review.

FAQ

Q: How many stages should a B2B SaaS sales process actually have? A: Between 4 and 7 forecast stages. Roberge ran HubSpot at 4; Force Management's MEDDICC-aligned templates land at 6. More than 7 and reps stop updating Salesforce honestly.

Q: What if our top reps refuse to follow the documented process? A: That is a coaching problem, not a process problem. Jordan's point in *Cracking the Sales Management Code* is that you can only manage what is documented — if a top rep is winning outside the process, capture what they actually do and fold it into v.next.

If they refuse to capture it, you have a flight risk, not a star.

Q: Should marketing-sourced leads enter at Stage 1 or Stage 2? A: Stage 1. The "meeting booked with named buyer" exit criterion is the same regardless of source. Different entry rules per source is how you end up with un-reconcilable pipeline reports.

Q: How do we keep the process doc from becoming shelfware? A: Three mechanisms: (1) review it the same week as every QBR; (2) require a process-stage citation in every deal review ("we're in Stage 3 because the champion intro happened on 4/12"); (3) update the wall poster every time the doc changes. If the poster is stale, the process is stale.

Q: What is the right cadence for major revisions? A: Annual major revision (v2026 to v2027), with quarterly minor revisions allowed. Anything more frequent and reps cannot keep up; anything less and you accumulate process debt that requires a painful overhaul.

Q: Where do disqualified deals live? A: Build an explicit "Disqualified" terminal stage with a required reason code (no fit, no budget, no timeline, no champion, competitor). Without it, dead deals haunt your pipeline forever.

Sources

Jordan, Jason & Vazzana, Michelle. *Cracking the Sales Management Code: The Secrets to Measuring and Managing Sales Performance.* McGraw-Hill, 2011.
Roberge, Mark. *The Sales Acceleration Formula: Using Data, Technology, and Inbound Selling to Go from $0 to $100 Million.* Wiley, 2015.
Van der Kooij, Jacco & Lakhani, Fernando. *Blueprints for a SaaS Sales Organization*, 3rd ed. Winning by Design, 2018.
Bertuzzi, Trish. *The Sales Development Playbook: Build Repeatable Pipeline and Accelerate Growth with Inside Sales.* Moore-Lake, 2016.
Force Management. *Command of the Message* and *MEDDICC* public stage-definition materials. Forcemanagement.com.
Winning by Design. *RevOps Academy: Process and Stage Definitions.* winningbydesign.com.
HubSpot Research. *State of Inbound* and *Sales Enablement Benchmark* reports, 2015-2024.
Sales Benchmark Index (SBI). *Annual CEO Workshop research on sales process maturity.* sbigrowth.com.

Keep reading

### Direct Answer

> A documented sales process is the highest-leverage RevOps artifact you own: it converts the tacit habits of your top reps into a repeatable system the rest of the team can execute. In this 60-minute training, you will install a 6-stage B2B SaaS process with verbatim **entry and exit criteria**, assign a single named owner, agree on a quarterly version-control cadence, kill 30% of the bloat your team is currently ignoring, and hang a process-map wall poster everyone can point at on day one of next quarter.

---


## Stack You'll Run This Training Inside

Every AE in the room operates inside the standard RevOps stack. Reference these tools by name during the training so reps know which dashboard or workflow you mean. Pin the dashboard you'll inspect in **Gong** on a shared screen before the meeting starts, queue the most recent recording from **Outreach** as the coaching artifact, and have **Clari** open in a second tab for the post-meeting cadence updates. The manager who shows up with these three browser tabs ready saves 8 minutes of meeting setup.

- **Gong** at $1,600/user/year — call recording + AI coaching insights
- **Chorus** at bundled with ZoomInfo at $1,200/user/year — call recording within the ZoomInfo stack
- **Outreach** at $150/seat/month — sequence + cadence engine for follow-ups
- **Salesloft** at $125/seat/month — cadence + Drift conversation routing
- **Clari** at $75-$150/user/month — forecast accuracy + deal inspection
- **Highspot** at $58/user/month base, content-volume-tiered — sales enablement + playbook delivery

### Benchmark Context

**IDC** ("Worldwide Sales Enablement Spending Tracker, 2026") reports that **enterprise sales orgs spent $4.7B on structured manager training programs in 2026, growing 18% YoY**. Anchor the training narrative on this stat — it's the credibility frame that turns a 60-minute meeting from "another sales pep talk" into "the weekly working session the manager is measured on." Print the stat at the top of the meeting agenda; reps remember the number, and quoting it builds the same shared vocabulary that **Lessonly**, **Spekit**, and **Highspot** all flag as the top predictor of multi-quarter training-program ROI in their 2026 customer benchmarks.

## Section 1 — The "Documented Process Beats Brilliant Individuals" Principle (5 min)

Open with Jason Jordan's core finding from *Cracking the Sales Management Code* (Jordan & Vazzana, McGraw-Hill, 2011): of the 306 sales metrics his team catalogued, only **17 are directly manageable** — and nearly all of them sit inside the sales process itself. Stage conversion, time-in-stage, and stage-skip rates are the levers; revenue is a lagging output you cannot manage directly.

Mark Roberge makes the same case in *The Sales Acceleration Formula* (Wiley, 2015): the HubSpot ramp he built was repeatable precisely because the process was written down, scored, and version-controlled — not because he hired brilliant individuals.

State the rule of the room out loud:

- **Brilliant individuals leave.** Documented processes stay, onboard the next hire in weeks instead of quarters, and let you forecast.
- **A process you cannot write down is a process you cannot coach.** If you cannot point at the page, the rep cannot point at the page either.
- **Tribal knowledge is a tax** paid by every new hire, every deal-desk escalation, and every QBR slide that says "it depends."

## Section 2 — The 6-Stage B2B SaaS Process Template with Entry/Exit Criteria (15 min)

Walk the room through the template below. Force Management's MEDDICC-aligned stage definitions (see the public Command of the Message materials) and Jacco van der Kooij's *Blueprints for a SaaS Sales Organization* (3rd ed., Winning by Design, 2018) both insist that a stage is defined by **buyer evidence**, not seller activity. Use this exact verbatim language on the wall poster.

- **Stage 1 — Prospect.** Entry: account fits ICP. Exit: a named buyer has accepted a meeting and a calendar invite is on the books.
- **Stage 2 — Qualify.** Entry: discovery meeting held. Exit: buyer has confirmed a **business pain**, an **economic impact**, and a **decision timeline** in writing (email or recap).
- **Stage 3 — Validate.** Entry: technical or functional fit confirmed. Exit: a **champion** has been identified, mapped, and has agreed in writing to introduce the economic buyer.
- **Stage 4 — Propose.** Entry: economic buyer meeting held; success criteria documented. Exit: a written proposal with pricing has been delivered AND a **mutual action plan** signed back.
- **Stage 5 — Negotiate.** Entry: verbal commitment from economic buyer. Exit: redlines exchanged; procurement and security have a named owner on the buyer side.
- **Stage 6 — Close.** Entry: paper out for signature. Exit: countersigned order form received; handoff to CS scheduled within 5 business days.

```mermaid
flowchart TD
    A[Stage 1: Prospect<br/>Exit: meeting booked]
    B[Stage 2: Qualify<br/>Exit: pain + impact + timeline]
    C[Stage 3: Validate<br/>Exit: champion confirmed]
    D[Stage 4: Propose<br/>Exit: MAP signed back]
    E[Stage 5: Negotiate<br/>Exit: procurement engaged]
    F[Stage 6: Close<br/>Exit: countersigned + CS handoff]
    A --> B --> C --> D --> E --> F
```

Trish Bertuzzi's rule from *The Sales Development Playbook* (Moore-Lake, 2016) applies at Stage 1: if SDR-sourced meetings cannot pass the "named buyer accepted" exit test, they do not count. Stop arguing about it in the deal desk.

## Section 3 — Version Control and the One-Owner Rule (10 min)

Sales process documents rot when nobody owns them. Force Management's enablement playbooks and Winning by Design's RevOps Academy both prescribe a **single named owner** — usually a RevOps lead or a Director of Sales Strategy — who holds the pen.

- **One named owner, full name on the document.** "Sales leadership" is not an owner. "Priya Shah, Director of RevOps" is.
- **Semantic versioning on the file itself.** v2026.2 means major revision 2 of calendar year 2026. Patch versions (v2026.2.1) are typo-level only.
- **Changelog at the top of the doc.** Every change lists date, owner, what changed, and why. No silent edits.
- **Quarterly review cadence, locked in the calendar** the same week as the QBR. Process review happens BEFORE pipeline review, not after.
- **Pull-request style proposals.** Anyone can propose a change in a shared doc; only the owner merges. This kills the "the VP told me on a plane" change pattern.

## Section 4 — Anti-Bloat: Kill 30% Every Year (10 min)

Every documented sales process grows barnacles: fields nobody fills in, stages nobody enforces, exit criteria added after one bad deal and never removed. Jacco van der Kooij calls this "process debt." Your job, once a year, is to take 30% out.

Run this exercise live in the room. Pull up the current process doc and the Salesforce stage field list on screen.

- **Salesforce required-field audit.** For each required field, ask: "When was this last used in a deal review?" If the answer is "I don't remember," it goes.
- **Stage exit criteria audit.** For each exit criterion, ask: "Did we enforce this on the last 5 closed-won deals?" If no, either enforce it next quarter or delete it.
- **Stage count audit.** If you have more than 7 forecast stages, you have too many. Roberge ran HubSpot on 4. Most $25K-$500K ACV teams do not need more than 6.
- **The "one-page test."** If the process does not fit on one page printed at 11pt, it is not a process — it is a wiki article nobody reads.

```mermaid
flowchart TD
    A[Annual Process Review]
    B{Field/stage used<br/>in last 5 deals?}
    C[Keep + reinforce]
    D[Cut — document why]
    E[Republish v.next]
    F[Wall poster reprint]
    A --> B
    B -- Yes --> C
    B -- No --> D
    C --> E
    D --> E
    E --> F
```

## Section 5 — The Process Map Wall Poster Artifact (15 min)

The deliverable from this hour is a physical artifact. Print it 24" x 36", laminated, on the wall behind the SDR pit and the AE bullpen, and ship a PDF version to remote reps. Force Management calls this "making the process unavoidable."

Build the poster live with the group, using a shared doc projected on the screen. Required elements, in this order, top to bottom:

- **Header.** Process name, version number, owner name, effective date. Example: "Acme Sales Process v2026.2 — owner: Priya Shah — effective 2026-04-01."
- **The 6 stages as horizontal boxes**, with the verbatim exit criterion underneath each. No marketing language. No verbs the rep cannot perform.
- **The one-sentence rule for every stage:** "A deal cannot advance to the next stage until the exit criterion above is documented in the opportunity record."
- **The disqualification path.** Where do dead deals go, and who closes them? Most teams skip this and accumulate zombie pipeline.
- **The handoff arrows.** SDR to AE at Stage 1 exit. AE to SE at Stage 3 entry. AE to CS at Stage 6 exit. Names and SLAs on each arrow.
- **A QR code linking to the living doc.** The poster is the summary; the doc is the source of truth.

Close the section by assigning two people in the room: the **poster designer** (gets it printed by Friday) and the **doc owner** (publishes v.next within 10 business days).

## Section 6 — Commitments and Close (5 min)

End with three named commitments written on the whiteboard. Bertuzzi's rule: a meeting without named owners and dates is a meeting that did not happen.

- **Owner assigned, on the doc, this week** — full name, no committees.
- **v.next published within 10 business days** — including the 30% cut.
- **Wall poster up by end of next sprint** — and reprinted every quarterly review.

---

## FAQ

**Q: How many stages should a B2B SaaS sales process actually have?**
A: Between 4 and 7 forecast stages. Roberge ran HubSpot at 4; Force Management's MEDDICC-aligned templates land at 6. More than 7 and reps stop updating Salesforce honestly.

**Q: What if our top reps refuse to follow the documented process?**
A: That is a coaching problem, not a process problem. Jordan's point in *Cracking the Sales Management Code* is that you can only manage what is documented — if a top rep is winning outside the process, capture what they actually do and fold it into v.next. If they refuse to capture it, you have a flight risk, not a star.

**Q: Should marketing-sourced leads enter at Stage 1 or Stage 2?**
A: Stage 1. The "meeting booked with named buyer" exit criterion is the same regardless of source. Different entry rules per source is how you end up with un-reconcilable pipeline reports.

**Q: How do we keep the process doc from becoming shelfware?**
A: Three mechanisms: (1) review it the same week as every QBR; (2) require a process-stage citation in every deal review ("we're in Stage 3 because the champion intro happened on 4/12"); (3) update the wall poster every time the doc changes. If the poster is stale, the process is stale.

**Q: What is the right cadence for major revisions?**
A: Annual major revision (v2026 to v2027), with quarterly minor revisions allowed. Anything more frequent and reps cannot keep up; anything less and you accumulate process debt that requires a painful overhaul.

**Q: Where do disqualified deals live?**
A: Build an explicit "Disqualified" terminal stage with a required reason code (no fit, no budget, no timeline, no champion, competitor). Without it, dead deals haunt your pipeline forever.

---

## Sources

- Jordan, Jason & Vazzana, Michelle. *Cracking the Sales Management Code: The Secrets to Measuring and Managing Sales Performance.* McGraw-Hill, 2011.
- Roberge, Mark. *The Sales Acceleration Formula: Using Data, Technology, and Inbound Selling to Go from $0 to $100 Million.* Wiley, 2015.
- Van der Kooij, Jacco & Lakhani, Fernando. *Blueprints for a SaaS Sales Organization*, 3rd ed. Winning by Design, 2018.
- Bertuzzi, Trish. *The Sales Development Playbook: Build Repeatable Pipeline and Accelerate Growth with Inside Sales.* Moore-Lake, 2016.
- Force Management. *Command of the Message* and *MEDDICC* public stage-definition materials. Forcemanagement.com.
- Winning by Design. *RevOps Academy: Process and Stage Definitions.* winningbydesign.com.
- HubSpot Research. *State of Inbound* and *Sales Enablement Benchmark* reports, 2015-2024.
- Sales Benchmark Index (SBI). *Annual CEO Workshop research on sales process maturity.* sbigrowth.com.

Was this helpful?

⌬ Apply this in PULSE

Industry KPIs · SaaSThe 9 sales KPIs that matter for SaaS

Related in the library