Sales SOP Examples: 5 Procedures That Make Revenue Repeatable

A sales SOP is a written procedure for one repeatable piece of your sales motion, and the five sales SOP examples below cover the pieces where revenue leaks first: lead intake, the discovery call, proposals and pricing, the handoff to operations, and follow-up. Each comes from documentation work with real teams, retold without names, and each follows a skeleton you can copy this week.

In founder interviews we ask one question: without you in it, what part of the business fails first? One founder with an eight-figure contract pending answered honestly: customer acquisition, because he is the storyteller who closes every large deal and none of it is written down. Talent closes deals; procedure is what makes them repeat.

Key takeaway: A sales SOP documents one revenue procedure: the trigger, the owner, the steps in order, and the decision rules for the judgment calls inside it. The five worth writing first are lead intake and qualification, the discovery call script, proposal and pricing anchoring, the sales-to-operations handoff, and follow-up cadence with pipeline hygiene. A sales playbook holds the strategy; SOPs hold the execution, captured from the rep who actually runs each one, not from memory.

What Is a Sales SOP?

A sales SOP is a standard operating procedure for a single repeatable sales task: what triggers it, who owns it, the exact steps in order, and what the right call looks like at each judgment point. It is not a script for charisma. It is the plumbing around the charisma, and the plumbing is where deals actually leak.

Salespeople resist procedure because it sounds like a leash on an art. But look at where revenue actually goes missing: leads logged nowhere, quotes that go out four days late, rush promises operations never heard about, deals that stall because nobody owns the next step. None of that is art. All of it is procedure.

When we document a process, we capture three things: the purpose, the decision points, and the step-by-step from the person who actually does the work. Sales SOPs live or die on the middle one, because selling is full of judgment calls, and an SOP that pretends otherwise gets ignored by Friday. The anatomy itself is nothing exotic: the same action headers and short steps you see in real SOP examples from other departments.

The deal is not repeatable until the way you closed it is written down.

Example 1: Lead Intake and Qualification

The first leak sits between "a lead exists" and "a real call is booked." One field services client we mapped ran intake through a call center with automated booking, and the automation happily overbooked slots because no step in the procedure checked capacity. The intake SOP names one system where every lead lands the same day, with its source recorded, a response window attached, and a capacity rule the scheduler cannot skip.

Qualification is the second half, and it is mostly disqualification rules. We watched a deal die in one meeting because the owner had never attended a single call and sent two managers to receive the proposal. No decision maker, no sale, and the team called it on the spot.

If the decision maker will not attend the next call, the lead is not qualified yet.

Qualification gates can be bolder than a question list. One consulting firm moved from $1,500 proposals to $20,000 engagements with a single intake change: charging $500 for the discovery deep dive, so prospects either self-selected out or took the work seriously. Before the gate, 90-minute calls went nowhere because nothing had been charged for.

Example 2: The Discovery Call Script

A discovery script is not a monologue. When we write one into an SOP, the script is written as spoken words, the way a person would actually say them. The procedure behind a good discovery call looks like this:

1. Open with one question. "Picture yourself a year from now. What would have to be true for you to feel genuinely satisfied with the progress of the business?" Then stop talking.
2. Hold through surface answers. The first ten minutes produce rehearsed material; the real vision arrives in bursts, so the instruction at this step is to wait.
3. Quantify the pain. Ask how long the problem takes, how often it happens, and how many people it touches. Minutes multiplied by frequency and headcount writes the business case for you.
4. Prescribe nothing. A prospect who has not sat in their current state will not value the fix and will not change. Diagnosis is a deliverable, so resist solving on the call.
5. Book the next step. A date on the calendar before you hang up, even if a partner still has to weigh in.

A script this open only works when reps have run it before a live prospect hears it, which is what mock call training is for: practice calls scored against a rubric before real customers do the scoring. At one staffing firm that trained this way, a brand-new rep placed 22 workers in her first ten days, more than some veterans had managed in two months.

Example 3: Proposal and Pricing Anchoring

We learned this procedure the expensive way. A client agreed on scope, received finished work for two roles, and balked at the invoice, because nobody had said the per-role price out loud since the first conversation. The internal retro was blunt: the expectation email was never sent, the pricing was never anchored in writing, and the communication gap cost real money.

No work starts until the price has been said out loud and confirmed in writing.

The SOP that came out of that retro has five steps:

1. Send the proposal fast. Same day or next morning. Speed is a differentiator, and a quote that takes a week signals how delivery will feel.
2. State price and unit. Per role, per phase, per month: name the unit in writing so the client is never doing mental math mid-relationship.
3. Send the expectation email. Before any work starts, restate scope, price, and timeline in one message the client can find later.
4. Restate it on the invoice. The first invoice is a pricing document, not just a bill: the expectation email with a total.
5. Update weekly. A short weekly note keeps the value visible between invoices, so the bill is never the first news the client gets.

The pattern generalizes past consulting. When a prospect is doing arithmetic in their head, the meeting has stopped being about their problem, and the fix is a procedure that puts the numbers in writing before work begins.

Example 4: The Sales-to-Operations Handoff

The most expensive leak comes after the close. At one staffing agency, sales and operations never met after onboarding, so reps filled rush orders willy-nilly without ever seeing the dispatch crew they were burning at 4:45 in the morning. The sale counted. The delivery suffered, and nobody upstream felt it.

A sale that operations cannot deliver is not revenue: it is a refund with extra steps.

A handoff SOP has two parts. The first is a required-fields record that travels with every closed deal:

• What was promised, in the customer's words
• Delivery date and any constraints sales agreed to
• Capacity confirmation: who in operations said yes, and when
• Account owner from this point forward
• Escalation path if delivery slips

The second part is human. One sales manager at that agency takes every new salesperson to a restaurant powwow with the dispatchers and the temp workers who fill their orders, because a rep who has met the crew stops promising what it cannot staff. Put the capacity check before the promise, not after the close, and the record becomes a formality instead of a fight. Everything after the handoff (complaints, escalations, save attempts) belongs in customer service SOP examples.

Example 5: Follow-Up Cadence and Pipeline Hygiene

Deals rarely die from a no. They die from vagueness, so the follow-up SOP exists to make vagueness impossible. Its first rule is the one that ends every good sales conversation: book the next call before hanging up, even when the prospect has to check with a partner. A kickoff on the calendar can be canceled; a vague follow-up just dies.

The cadence half of the SOP defines the touches: how many, how far apart, in which channel, and what each one says. The hygiene half defines stages, and the rule that keeps a pipeline honest is that stages flip on events, not feelings. In our own pipeline, a lead moves to the call-booked stage when a call is actually booked, and the software makes that move automatically, so the stage cannot drift from reality.

An open deal has a next step with a date; anything without one is a stalled deal miscounted as pipeline.

Run that rule across your pipeline once and the forecast will shrink. That is not bad news. That is the first accurate forecast you have had in a while.

---

How Is a Sales SOP Different from a Sales Playbook?

A sales playbook is the strategy layer: who you sell to, why you win, how the team is structured, and what good messaging sounds like. A sales SOP is the procedure layer: the exact steps for one repeatable task inside that strategy. The two answer different questions.

Most teams need both layers, but they fail in opposite directions. A playbook without SOPs reads beautifully and changes nothing on Monday morning. SOPs without a playbook execute crisply toward the wrong customers. If the strategy layer is your gap, start with what belongs in a sales playbook, then come back for the procedures that make it operational.

Turn These Sales SOP Examples into a First Draft This Week

Do not write any of these from memory. Record your best rep actually running the procedure: a real intake, a real discovery call, a real handoff conversation. Then pull the purpose, the decision points, and the steps out of the recording, because documentation built from reality gets followed, and documentation built from memory gets corrected in front of the new hire.

Draft one page with action headers, and hold it to the glance test: a reader should be able to glance at any single step and know what to do. The skeleton in how to write an SOP works unchanged for sales.

Be honest about what this costs. Every page you write has to be kept current, and the fastest way to kill a sales SOP is to document the whole motion as one giant file: rename a pipeline stage or change the pricing model and the entire thing goes stale in an afternoon. One page per procedure survives that; a single sales manual does not. And if your offer is still moving every month, write only intake and the handoff for now, because a discovery script for a pitch you are about to rewrite is documentation you will throw away.

Once revenue procedures are on paper, the same anatomy carries into HR SOPs for hiring and onboarding. Interview-first capture is the whole method we run at The Systems Effect: record the person who does the work, then reverse engineer the procedure from what they actually said and did.

Start with the seam that leaked most recently: the quote that went out late, the rush order nobody could staff, the deal that stalled without a date. Write that one procedure this week, one page. Hand it to your newest rep and watch where they hesitate, because every hesitation is your next edit.

Frequently Asked Questions

What should a sales SOP include?

A sales SOP should include the trigger that starts the procedure, the single owner who runs it, the purpose in one or two sentences, the steps in order, and the decision rules for the judgment calls inside it. Keep it to a page or two per procedure. The test is whether a new rep can glance at any single step and know what to do without asking anyone.

What is the difference between a sales SOP and a sales playbook?

A sales playbook is the strategy layer: target customers, positioning, team structure, and messaging. A sales SOP is the procedure layer: exact repeatable steps for one task such as lead intake, discovery, or the operations handoff. They are also written by different people, which is the practical tell: leadership decides the playbook, while the rep who runs the task dictates the SOP. If you only have time for one, write the SOPs first, because a new rep can run procedures without the strategy document but nobody can run strategy without procedures.

How do you document a sales handoff to operations?

Build a handoff record with required fields: what was promised in the customer's words, the delivery date, any constraints sales agreed to, a capacity confirmation from operations, and who owns the account from that point forward. Keep the record inside the system the deal already lives in, so nobody has to remember to copy it anywhere. Make the capacity check happen before the promise, not after the close. Then put sales and operations in the same room on a schedule, because the handoff document only works when the two sides actually know each other.

How do you write a discovery call script?

Write it as spoken words, the way a person would actually say them. Open with one question about where the prospect wants the business to be in a year, hold through the surface answers, quantify the pain in time and money, and prescribe nothing on the call. Budget 90 minutes with whoever owns the vision, because an hour is not long enough to get past the rehearsed answers. Close by booking the next step before you hang up, and rehearse the whole thing in mock calls before a live prospect ever hears it.