Scale · Process Docs & SOP Libraries

Write an SOP for New Pipeline Stage Rollouts

Document the exact change-management steps for adding, renaming, or retiring a pipeline stage so reporting doesn't break.

managerfounderAdvanced⏱ 6-10 hours of cleanup per botched rollout
When to use
Use any time you're adding a new stage (e.g., 'Mutual Action Plan Signed') or splitting an existing one. Pipeline changes silently corrupt forecast history — this SOP forces a checklist that protects historical reporting, exit-criteria definitions, and rep training before the change goes live.
The prompt
You are a RevOps director at a 50+ person digital marketing agency writing SOPs that survive employee turnover, tool migrations, and quarterly re-orgs.
Agency: [AGENCY_NAME] — [SERVICES] | Process: [PROCESS_NAME] | Owner: [OWNER] | Tools: [TOOLS_USED] | Trigger: [TRIGGER] | Current pipeline stages: [CURRENT_STAGES] | Proposed change: [PROPOSED_CHANGE] | CRM: [CRM] | Forecast cadence: [FORECAST_CADENCE]
Write the SOP that governs how a new pipeline stage gets proposed, approved, configured in the CRM, communicated to reps, and reflected in dashboards — with rollback steps if forecast accuracy drops more than 10% in the first 30 days.

- must follow the standard SOP shape: Purpose, Trigger, Owner, Steps (numbered), Inputs, Outputs, Escalation, Last Reviewed
- each step has a who/what/where — not just verbs (name the CRM screen and the field)
- no jargon a new rep wouldn't know — define "exit criteria" and "stage conversion rate" inline
- include explicit exit criteria for the new stage and how to map historical deals to it
- include a 14-day rep training plan with Loom + role-play requirements
- include a rollback section with the exact 4 actions to revert

SOP doc in markdown with the section structure above; include a sub-table for the change-approval RACI
Variables
  • [AGENCY_NAME] — Your agency name
  • [SERVICES] — Core services sold
  • [PROCESS_NAME] — Always 'Pipeline Stage Rollout'
  • [OWNER] — RevOps lead approving the change
  • [TOOLS_USED] — CRM + dashboard tool
  • [TRIGGER] — What event kicks this SOP off — e.g., 'VP Sales requests a new stage'
  • [CURRENT_STAGES] — Today's stages in order
  • [PROPOSED_CHANGE] — What you want to add/rename/retire
  • [CRM] — HubSpot, Salesforce, Pipedrive, Close, etc.
  • [FORECAST_CADENCE] — How often you forecast — weekly, monthly
Example input
Agency: Lattice Search — SEO + Content | Process: Pipeline Stage Rollout | Owner: Marcus Lee, Head of RevOps | Tools: HubSpot + Hex | Trigger: VP Sales requests a stage change in the quarterly QBR | Current stages: New, Discovery, Proposal, Negotiation, Closed Won/Lost | Proposed change: Add 'Mutual Action Plan Signed' between Proposal and Negotiation | CRM: HubSpot | Forecast cadence: Weekly Monday forecast call
Example output
# SOP — Pipeline Stage Rollout (Lattice Search)

**Purpose:** Add/remove HubSpot deal stages without corrupting forecast history.
**Trigger:** VP Sales submits stage-change request in #revops-intake.
**Owner:** Marcus Lee, Head of RevOps.
**Inputs:** Change request form, current stage conversion rates, last 4 weeks of forecast accuracy.
**Outputs:** Updated HubSpot pipeline, refreshed Hex dashboard, rep training Loom, rollback plan.
**Escalation:** CRO if forecast accuracy drops 10%+ in first 30 days.
**Last Reviewed:** 2026-05-25.

## Steps
1. Marcus drafts exit criteria for the new stage in Notion (must be objective, e.g., 'signed MAP doc in DocuSign').
2. Marcus runs HubSpot report to find open deals to remap.
3. CRO approves in #revops-intake thread.
4. Marcus clones the HubSpot pipeline as 'Sandbox' before editing production.
5. Marcus updates Hex SQL and verifies historical funnel still matches prior quarter (±2%).
6. Marcus records 5-min Loom; mandatory watch + 10-min role-play in next team meeting.
7. Go-live Monday 8am ET; daily forecast check for 14 days.

**Rollback:** Restore sandbox → revert Hex query → Slack #sales-team → re-train.
Pro tips
  • Always test in a CRM sandbox before changing production — it's the #1 lesson from blown forecasts.
  • Make exit criteria objective (signed doc, paid invoice) not subjective ('seems engaged').
  • Keep a changelog inside the SOP itself so future RevOps hires understand why stages exist.
Works with
ClaudeChatGPTGemini
Done with prompts? Time to install the system
Book a STAOS call
Related prompts