Free Sales SOP Template
A sales SOP that keeps the pipeline honest — stages, exit criteria and a clean handoff.
Part of our free sop templates.
Your download has started.
Didn’t start? Retry the Word file or get the PDF.
1.Title Block & Document Control
| SOP Title | {{SOP Title}} |
|---|---|
| SOP ID | {{SOP ID}} |
| Version | {{Version}} |
| Effective Date | {{Effective Date}} |
| Review Date | {{Review Date}} |
| Document Owner | {{Document Owner}} |
| Approver | {{Approver}} |
Keep this block on page one so anyone can audit the document at a glance. Set a Review Date 6–12 months out and assign a single Document Owner who is accountable for keeping it current.
2.Purpose
State in one or two sentences why this procedure exists and what result it delivers when followed correctly.
Write the “why”, not the steps. Example: “This SOP ensures every customer refund is processed accurately, within policy, and within two business days.”
3.Scope
Define which teams, locations, systems, and situations this SOP applies to — and explicitly note what it does not cover.
Naming the boundaries prevents the procedure from being applied to the wrong cases. List any exclusions on their own line.
Pipeline Stages & Exit Criteria
| Stage | Definition | Exit criteria (to advance) | CRM status |
|---|---|---|---|
| {{New / Lead}} | {{Captured but not yet worked}} | {{Contact attempted within SLA}} | {{Status value}} |
| {{Qualified}} | {{Fit and intent confirmed}} | {{Need, authority, timeline known}} | {{Status value}} |
| {{Proposal}} | {{Solution and price shared}} | {{Quote sent and acknowledged}} | {{Status value}} |
| {{Won / Lost}} | {{Closed outcome}} | {{Signed, or lost reason recorded}} | {{Status value}} |
Define what each stage means and the single thing that must be true to advance. Stages without exit criteria are why pipelines inflate — a deal should only move when the criterion is met and the CRM is updated to match.
4.Definitions & Abbreviations
| Term | Definition |
|---|---|
| {{Term}} | {{Plain-language definition}} |
| {{Abbreviation}} | {{What it stands for}} |
Only define terms that could be misread by someone new to the process. If there are none, keep this section and write “None” — auditors expect it to exist.
5.Roles & Responsibilities
| Role | Responsibility |
|---|---|
| {{Role}} | {{What this role is accountable for in this procedure}} |
| {{Role}} | {{What this role is accountable for in this procedure}} |
Assign responsibilities to roles, not named individuals, so the SOP survives staff changes. Keep each role to one or two lines.
6.Prerequisites, Materials & Equipment
- {{Access or permission required before starting}}
- {{Tool, system, or login needed}}
- {{Material or document that must be on hand}}
List everything that must be ready before step one. A short checklist here prevents half-finished runs.
7.Safety & Compliance
Note any safety precautions and the regulations or internal policies this procedure must comply with.
If this procedure has no safety or compliance angle, keep the section and write “N/A”. Reference the specific policy or regulation by name where one applies.
8.Procedure (Step-by-Step)
| Step | Action | Owner | Expected Result |
|---|---|---|---|
| 1 | {{Start with a verb — one action per step}} | {{Role}} | {{What “done right” looks like}} |
| 2 | {{Next action}} | {{Role}} | {{Expected result}} |
| 3 | {{Next action}} | {{Role}} | {{Expected result}} |
Aim for roughly 5–15 numbered steps. Begin each with a verb, keep it to one action, and make the Expected Result observable so anyone can confirm the step is complete.
9.Quality Checks & Acceptance Criteria
- {{Measurable check that confirms the work was done correctly}}
- {{Second acceptance criterion}}
Write 2–4 checks that are measurable — a reviewer should be able to answer each with a clear yes or no.
10.Troubleshooting & Exceptions
| Failure scenario | What to do | Escalate to |
|---|---|---|
| {{Common thing that goes wrong}} | {{Corrective action}} | {{Role / contact}} |
| {{Edge case}} | {{How to handle it}} | {{Role / contact}} |
Capture the failures you have actually seen. Naming the escalation point keeps exceptions from stalling.
11.Related Documents & References
- {{Form, checklist, or policy this SOP relies on}}
- {{Upstream or downstream SOP}}
Link the forms, policies, and adjacent SOPs a reader will need next.
12.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | {{Effective Date}} | {{Document Owner}} | Initial release |
| {{Version}} | {{Date}} | {{Author}} | {{What changed}} |
Update this table every time the SOP changes. The v1.0 row is pre-filled as an example.
13.Approval
Both sign-offs confirm the procedure is accurate and authorised for use.
A worked example for a B2B SaaS sales team, from inbound lead to an accepted opportunity.
1.Title Block & Document Control
| SOP Title | Inbound Lead-to-Opportunity |
|---|---|
| SOP ID | SALES-006 |
| Version | 1.0 |
| Effective Date | June 1, 2026 |
| Review Date | December 1, 2026 |
| Document Owner | Sales Operations Manager |
| Approver | VP Sales |
2.Purpose
This SOP ensures every inbound lead is contacted fast, qualified consistently, and either advanced to a clean opportunity or disqualified with a reason — so reps spend time on real deals and the pipeline stays trustworthy.
3.Scope
Covers inbound leads (demo requests, trials, contact forms) from capture to an accepted opportunity owned by an Account Executive. It does not cover outbound prospecting (SALES-002) or renewals, which the Customer Success team handles.
Pipeline Stages & Exit Criteria
| Stage | Definition | Exit criteria (to advance) | CRM status |
|---|---|---|---|
| New | Lead captured, not yet worked | First touch within 1 business hour | Lead · New |
| Working | Outreach in progress | Two-way conversation booked | Lead · Working |
| Qualified | Fit + need + timeline confirmed | BANT-lite captured; AE accepts | Opportunity · Discovery |
| Disqualified | Not a fit or no intent | Disqualify reason recorded | Lead · Disqualified |
4.Definitions & Abbreviations
| Term | Definition |
|---|---|
| MQL | Marketing Qualified Lead — meets the agreed scoring threshold |
| SQL | Sales Qualified Lead — accepted by sales as worth pursuing |
| BANT-lite | Budget, Authority, Need, Timeline — the minimum qualification captured |
| SLA | Service Level Agreement — here, the time to first contact a lead |
5.Roles & Responsibilities
| Role | Responsibility |
|---|---|
| SDR / BDR | Works the lead, qualifies, and books the meeting |
| Account Executive | Accepts or rejects the qualified lead and runs the opportunity |
| Sales Operations | Owns lead routing, the CRM stages, and the SLA report |
| Sales Manager | Coaches on disqualifies and approves exceptions |
6.Prerequisites, Materials & Equipment
- CRM access with the inbound lead queue and routing rules
- Current qualification (BANT-lite) questions and call script
- Calendar/booking link for handoff meetings
- Email sequences and the disqualify-reason picklist
7.Safety & Compliance
Honor consent and privacy law (GDPR/CCPA): only contact leads who opted in or have a lawful basis, include an opt-out in every email, and follow the data-retention policy. Do not buy or import lists that violate the marketing policy. Record contact preferences in the CRM and respect do-not-contact requests.
8.Procedure (Step-by-Step)
| Step | Action | Owner | Expected Result |
|---|---|---|---|
| 1 | Lead lands; CRM routes it to the right SDR by territory | Sales Operations | Lead owned within minutes of capture |
| 2 | Make the first contact attempt within 1 business hour | SDR | Call/email logged; SLA met |
| 3 | Run the qualification questions on the call | SDR | BANT-lite captured in the CRM |
| 4 | Book the discovery meeting and hand off to the AE | SDR | Meeting on the AE’s calendar with notes |
| 5 | AE accepts the lead or sends it back with a reason | Account Executive | Opportunity created, or lead recycled |
| 6 | If not qualified, disqualify with a reason and nurture | SDR | Disqualify reason set; lead added to nurture |
9.Quality Checks & Acceptance Criteria
- First-touch SLA (1 business hour) met for inbound leads
- Every qualified lead has BANT-lite fields completed
- Accepted opportunities have a next step and a date
- Every disqualified lead has a reason recorded — none left blank
10.Troubleshooting & Exceptions
| Failure scenario | What to do | Escalate to |
|---|---|---|
| Lead not routed or owner unclear | Claim it, then fix the routing rule | Sales Operations |
| AE and SDR disagree on qualification | Use the written exit criteria; log the call | Sales Manager |
| Duplicate or existing account | Merge in the CRM; route to the current owner | Sales Operations |
11.Related Documents & References
- SALES-002 Outbound Prospecting SOP
- Lead scoring and routing rules
- Discovery call script
- Disqualify-reason definitions
12.Revision History
| Version | Date | Author | Summary of change |
|---|---|---|---|
| 1.0 | June 1, 2026 | Sales Operations Manager | Initial release |
13.Approval
How it works
- Preview the sales SOP, including the pipeline-stage and exit-criteria table.
- Download Word/PDF, or copy the text to paste into Google Docs.
- Define your stages and exit criteria, set your approval thresholds, and tailor the qualification questions to your market.
Frequently asked questions
What should a sales SOP include?
A sales SOP should define the pipeline stages and the exit criteria to advance each one, the qualification standard, CRM hygiene rules, and discount/approval thresholds, plus how leads are routed and handed off. This template includes a pipeline-stage table and a worked lead-to-opportunity example on top of the standard SOP sections.
What are pipeline stage exit criteria?
Exit criteria are the single condition that must be true for a deal to move from one stage to the next — for example, “a discovery meeting is booked” or “BANT-lite is captured.” Defining them stops the pipeline from inflating with deals that look further along than they are. The template asks for an exit criterion on every stage.
What is the difference between a sales SOP and a sales playbook?
A sales SOP is the procedure — the repeatable steps, stages, and rules for working a deal consistently. A playbook is broader coaching content: messaging, objection handling, and tactics. Many teams keep the SOP as the system of record and link the playbook from it.
How does a sales SOP keep the CRM clean?
By tying each pipeline stage to an explicit exit criterion and a CRM status, and by requiring a reason on every disqualified lead, the SOP makes the CRM reflect reality. The template’s stage table and quality checks are built around exactly that discipline.