How to write a sales SOP (and the SOTA framework that holds it together)
What is a sales SOP?
Short answer: a sales SOP (Standard Operating Procedure) is a written, repeatable, role-agnostic procedure for one recurring sales activity. A working sales operating system has 15–30 of them — covering everything from "how to enrol a prospect in a sequence" to "how to handle a churn-risk customer" to "how to run a weekly forecast call."
SOPs are what turn a sales playbook from a strategy document into an operating manual. The playbook says what we do. The SOPs say how.
SOTA — Situation, Objective, Tactics, Assessment — is the framework MAVEN uses to structure each SOP.
TL;DR — anatomy of a sales SOP
| Section | Content |
|---|---|
| Title | What this procedure covers |
| Owner | Who maintains it |
| Last updated | When was it last reviewed |
| Situation | Context — when this procedure applies |
| Objective | Outcome — what done looks like |
| Tactics | Step-by-step procedure |
| Assessment | How to know it worked |
| Linked artefacts | CRM views, templates, tools |
Each SOP is 1–3 pages. Not 20 pages. If it's 20 pages, it's a manual, not a procedure.
Why SOPs matter
Three concrete problems SOPs solve:
1. Onboarding speed. A new rep with 20 SOPs reaches independent productivity in 6 weeks instead of 12.
2. Quality consistency. Reps do not freelance the process. The CRM stays clean. The forecast stays defensible.
3. Coverage. When a rep is sick or on holiday, another rep can pick up their work without re-inventing the procedure.
Companies that operate without SOPs run on individual brain dumps. When the individual leaves, the brain leaves with them.
The SOTA framework
Each SOP has four sections:
S — Situation. When this procedure applies. The triggering event.
O — Objective. The outcome the procedure produces.
T — Tactics. The specific, ordered steps.
A — Assessment. How to evaluate whether the procedure was executed well.
A simple example — Sequence Enrolment SOP:
Situation: New prospect identified, fits ICP, contact data verified.
>
Objective: Prospect enrolled in correct persona-specific sequence with personalised first-line, expected to drive a discovery meeting within 21 days.
>
Tactics:
1. Verify ICP fit against checklist (link).
2. Confirm contact data via Apollo + manual LinkedIn check.
3. Choose sequence based on persona (table linked).
4. Write personalised first line — must reference a specific recent signal.
5. Enrol in sequence; set follow-up task for Day 10 review.
6. Log in CRM with source + sequence ID.
>
Assessment:
- Did the prospect receive the email within 30 minutes of enrolment?
- Was the first-line genuinely personalised (manager review on weekly sample)?
- Is the CRM record complete?
Three minutes to read. Clear enough to execute. Reviewable for quality.
The 20 SOPs every B2B sales team needs
The starter library:
| # | SOP |
|---|---|
| 1 | New prospect enrolment |
| 2 | First discovery call structure |
| 3 | Demo / pitch flow |
| 4 | Proposal generation + sending |
| 5 | Objection handling (top 5) |
| 6 | Stage advancement criteria |
| 7 | Forecast categorisation |
| 8 | Pipeline review prep |
| 9 | Weekly forecast call participation |
| 10 | Deal review escalation |
| 11 | Discount / pricing approval |
| 12 | Contract redline process |
| 13 | Vendor registration (GCC-specific) |
| 14 | Hand-off to Customer Success |
| 15 | Closed-lost retrospective |
| 16 | Re-engagement of closed-lost |
| 17 | Renewal motion |
| 18 | Upsell motion |
| 19 | Reference customer request |
| 20 | Out-of-office coverage |
Most teams have 5 of these documented and 15 in someone's head. The leverage is in writing them down.
How to write an SOP that gets used
Rule 1 — Two pages maximum. Beyond that, reps stop reading.
Rule 2 — Active voice, second person. "You enrol the prospect" not "The prospect is enrolled by the rep."
Rule 3 — Include screenshots. A picture of the CRM screen is worth 200 words of description.
Rule 4 — Link to artefacts. The SOP should not duplicate the sequence library, the playbook, or the CRM — it should link to them.
Rule 5 — Test before publishing. Have a new rep follow the SOP. If they get stuck, revise.
Rule 6 — Version explicitly. v1.0 → v1.1 → v2.0. Date every change.
Where SOPs live
| Tool | Pros | Cons |
|---|---|---|
| Notion | Easy to update + navigate | Search is mediocre |
| Guru | Best-in-class for sales | Cost; learning curve |
| Google Drive | Free | Hard to maintain version control |
| Confluence | Enterprise-grade | Heavy |
Notion is the modal answer for B2B teams under £10M ARR. Each SOP is a database entry with consistent structure.
Maintenance rhythm
| Cadence | Activity |
|---|---|
| Weekly | Add new SOPs as gaps emerge in pipeline reviews |
| Monthly | Update 2–3 SOPs based on rep feedback |
| Quarterly | Full review — archive obsolete, promote drafts |
| Annually | Comprehensive refresh + onboarding plan update |
A team that does not maintain SOPs loses them within 18 months. A team that maintains them quarterly has a permanent operating advantage.
For UAE & KSA teams
Region-specific SOPs that often get missed:
- Vendor registration SOP (KSA government). Step-by-step process for registering as a supplier with PIF entities or ministries.
- Arabic-language reply protocol. When to escalate a reply received in Arabic, who translates, response timeline.
- Ramadan modifications SOP. Adjusted cadence rules for Ramadan, including sequence pauses and meeting time windows.
- Multi-currency proposal generation. How to quote in AED/SAR vs. USD/GBP, FX lock conventions.
- Multi-threaded engagement. Standard procedure for engaging 2–3 stakeholders per account from outset.
- In-person follow-up protocol. When a deal warrants travel; how to budget and approve.
- Family business escalation. Standard process for surfacing patriarch / family principal stakeholders in GCC deals.
What MAVEN does about it
SOP library development is part of the Sales Process Program — the 90-day install includes drafting the foundational 15–20 SOPs and migrating them into the client's preferred tool. The SOTA framework is documented in the Sales OS Blueprint.
Book a virtual coffee if your team has playbook content but no procedure layer.
Frequently asked
SOP or playbook?
Both, layered. Playbook = strategy + content. SOPs = procedures for recurring activities. The playbook references the SOPs.
How long until SOPs are mature?
6–12 months from first draft to a working library. Faster than that often means incomplete coverage; slower means the maintenance cadence is broken.
Who writes SOPs?
The person doing the work, initially. Then the sales leader or RevOps reviews and standardises.
Can AI draft SOPs?
Yes, usefully. AI is strong at first-draft procedure documentation. Edit before publishing.
How do I know which SOPs to write first?
Watch where reps are getting stuck or asking the same question repeatedly. Those gaps are your SOP priorities.
Post 30 of our outbound + sales OS series.
Related reading
Level Up Your Sales Career
Join The Sales Development Society — weekly live coaching, proven templates, and a community of ambitious B2B salespeople going from entry-level to enterprise.
Join the CommunityReady to install your sales engine?
Book a 30-minute Virtual Coffee. No deck, no pitch — just an honest read of where you are.
Book a Virtual Coffee