A sales SOP sets the minimum standards every deal must meet between enquiry and signed contract: how fast a lead is answered, what gets recorded, what evidence moves a deal to the next stage, how long it may sit there and how it is handed to delivery. This article answers one question: what should a sales standard operating procedure control, and what should it leave to the salesperson? Draw that line too tight and you script your best people into mediocrity. Draw it too loose and every deal depends on who happened to pick it up, and the forecast becomes a collection of personal opinions.
Standardise the decision points, not the conversation
Most companies that write a sales procedure start with the sales call. They produce a script, a list of discovery questions and an objection sheet. Experienced sellers ignore it, new ones read it aloud, and the close rate does not move.
The parts of selling that benefit from a procedure are the ones nobody enjoys and everybody forgets: replying quickly, logging what was said, following up on schedule, keeping the pipeline honest and handing the client over cleanly. That is where a 60-person company with flat revenue loses most of its deals. The conversation itself stays with the person.
Suppose a sales director pulls the last 100 enquiries. Say 22 waited more than a day for any reply, 18 had a first call but no logged follow-up within a week, and in several won deals the delivery lead had to ring the client to ask what was sold. If only a handful were lost on price or fit, the pattern would be plain: the leaks sit between the steps, not inside the selling.
Define each stage by what the buyer did
Most pipelines describe seller activity: called, emailed, proposal sent, followed up. Activity says nothing about whether the buyer is moving. You can send five proposals to a prospect who stopped reading after the first.
Define every stage by something the buyer did or confirmed instead. They attended a discovery call. They confirmed a budget range. They named the person who signs. They asked for a contract. Each of those can be checked, and each one changes the odds of closing in a way that "follow-up email sent" never does.
Expect the pipeline to look smaller once you apply this test. Deals that sat hopefully in late stages move back or drop out. The numbers were always that size; you are simply seeing them.
The stage table at the heart of the procedure
Write the procedure as a table first and add the prose afterwards. For a service firm selling engagements of a few thousand to a few hundred thousand, five or six stages are enough.
| Stage | Entry rule (buyer evidence) | Exit rule | Owner | Time limit |
|---|---|---|---|---|
| New enquiry | Form, call, chat or referral received | First reply sent and call offered | Whoever is on enquiry duty | Same working day |
| Qualified | Need, timeframe and decision maker confirmed on a call | Discovery meeting booked | Assigned rep | 5 working days |
| Discovery held | Buyer attended and described the problem in their words | Scope agreed verbally | Assigned rep | 10 working days |
| Proposal | Written proposal sent and a review meeting booked | Buyer feedback received | Assigned rep | 10 working days |
| Commit | Buyer has asked for a contract or terms | Signed agreement or recorded loss | Rep plus manager | 15 working days |
| Won or lost | Signature or explicit decision | Handover or loss reason logged | Rep | 2 working days |
The time limit is the column most firms leave out, and it does the most work. A deal that breaches its limit is not lost. It triggers a conversation between the rep and the manager, who either agree a dated next step or move the deal back a stage.
Imagine 70 open opportunities, 31 of them in the proposal stage. Apply the buyer-evidence test and say 12 stay in proposal, 9 move back to discovery and 10 close as lost because the buyer has not replied in six weeks. An illustrative weighted forecast of 410,000 might fall to 260,000. That lower figure is not bad news; it is the first forecast you could plan hiring against.
The six standards a sales SOP covers
Lead response
Set a maximum reply time for each lead source and name who covers it in and out of working hours. A web form enquiry should get a reply within minutes. If the team cannot meet that, the procedure says which automated reply goes out while a person catches up. On the levelpartner.ai platform the instant reply and the assignment to an owner can run as a workflow when the form is submitted, so the written procedure covers what the person does next.
Qualification
List the three or four facts you need before a lead becomes an opportunity: the problem, the timescale, who decides and a rough budget band. Do not script how to ask. Do say where the answers are recorded and what happens to a lead that fails, such as a nurture list rather than deletion. The guide to operational intelligence shows how a lead left waiting becomes an alert someone acts on the same day.
Meeting and proposal
State what must exist before a proposal goes out: a logged discovery call, confirmed scope and a named decision maker. Name the proposal template and who may approve a discount. Pricing errors happen here, so this is where a procedure earns its keep.
Follow-up
The follow-up cadence is the most valuable line in the whole document. Most deals that established firms lose are not lost; they are abandoned. Fix a cadence, such as day two, day five and day twelve after the proposal, with what each contact should contain, and let the system create the tasks.
Pipeline hygiene
The stage table covers when deals move. Add the rule for closing: a deal untouched past its time limit is either given a dated next step or closed with a reason. Use a fixed list of six to eight loss reasons chosen from a dropdown, because free-text reasons are unreadable in aggregate. After a quarter, a fixed list shows whether you lose to "no decision" or to price, which changes what you work on.
Handover to delivery
Specify the record the seller completes before a deal is marked won: what was sold, any non-standard promises, the client's stated goal and their main contact. If the delivery lead has to ring the client to ask, the handover failed.
What the written document contains
Around the table and the standards, a new hire needs a few short sections to follow it without asking.
- Purpose and scope: which enquiries it covers. New business usually gets its own procedure, separate from renewals and upsells.
- Definitions: what counts as a qualified lead, a decision maker, a proposal versus a quote. Most forecasting arguments start with these words.
- Handoffs: what must be written on the opportunity each time it changes hands, so nobody re-asks the buyer.
- Exceptions: who may override a rule, such as a strategic deal skipping a stage, and how the override is recorded.
The file itself, with its header, version and review date, follows the format in the SOP document guide.
A sales SOP example
Here is an inbound example for a 30-person mortgage brokerage. It is firm on standards and silent on technique.
Trigger: a new enquiry by web form, phone or introducer. Owner: sales manager. 1. The system sends an acknowledgement within 2 minutes and assigns the lead to the adviser on rota. 2. The adviser calls within 1 working hour; if there is no answer, the system sends a text with a booking link and creates a retry task for the next morning. 3. On first contact, record purpose, property value band, timescale and employment type. 4. If the enquiry is not a fit, tag it for nurture and close the opportunity with a reason. 5. If it is a fit, book the fact-find and move the opportunity to the booked stage. 6. Send the recommendation within 2 working days of the fact-find. 7. Follow up on day 2, day 5 and day 10 using the tasks the system creates. 8. On acceptance, complete the handover fields and mark the opportunity won. 9. Any opportunity past its stage limit is reviewed on Monday and either updated or closed. Done when: the case is submitted or the opportunity is closed with a recorded reason.
Nine steps, and none of them tells the adviser how to talk to a client.
Building the rules into the pipeline
A procedure that lives only in a shared drive decays within a quarter. Let the pipeline enforce as much of it as it can. Start with the business work, which no system does for you.
- Write the stage table on one page and agree it with every person who sells.
- Agree the buyer evidence each stage needs and the loss reasons you will use.
- Create the pipeline: open Opportunities, select Pipelines, select Create New Pipeline, enter the pipeline name and one stage per row of your table, then select Save.
- Create a field for each piece of buyer evidence: open Settings, go to Custom Fields, select + Add Field, choose the field type and select Next.
- Name the field, set the Object to Opportunity, turn on the required option under Additional Preferences where that field type offers it, then select Save.
- Create the time-limit alert: open Automation, select Workflows, select + Create Workflow and choose Start from scratch.
- Select + Add new Trigger, choose Stale Opportunities and give the trigger a clear name.
- Select Add Filters, set Duration in Days to the stage time limit, choose the pipeline under In Pipeline and the stage under Pipeline Stage, then select Save Trigger.
- Add the Add Task action, fill in Title and Description, choose the rep or manager in Assign To, set Due In, then save and publish the workflow.
- Repeat the trigger for each stage that has its own time limit.
- Re-stage every open opportunity against the new rules in one working session.
- Review the stalled-deal tasks together every week for the first eight weeks.
The stale count starts when the trigger is added, not from the date an opportunity entered its stage, so old deals will not all flag on day one. That is why step 11 matters. Any update or stage change resets the clock.
What most sales procedures get wrong
They document the whole sales methodology. How to run discovery, present and handle a price objection is a skill, learned through practice and coaching. Put it in a playbook. The procedure is narrower and more useful: it sets the floor nobody falls below.
They write for the best rep. Your top performer carries the rules in their head. The procedure exists for the new hire in month two and the steady rep who is good on calls but lets follow-up slip.
They set standards the team cannot meet. A one-hour response time with two advisers covering forty enquiries a day is fiction, and a rule everyone breaks teaches people the procedure is optional. Set the standard you can meet now, automate the gap and tighten it when the numbers hold.
Measuring compliance by how many fields are filled in. Reps learn to fill fields with anything. Count the opportunities that have a dated next step agreed with the buyer instead. That number tells you whether the procedure is alive.
The trade-off
A procedure built on standards gives up control of the conversation. If your close rate on qualified meetings is genuinely poor, it will not fix that; you need call review and coaching alongside it. It also adds a few minutes of logging to every deal. The return is a forecast you can hire against and a delivery team that starts knowing what was sold.
It is overhead for a firm with one seller and the managing director. It earns its keep from about three sellers upwards, or as soon as anyone outside sales relies on the forecast.
Running it each week and measuring it
Once it is in place, the manager needs about an hour a week: thirty minutes on deals that breached a time limit and thirty in a pipeline meeting where reps discuss only deals that changed stage or stalled. Track three numbers weekly: median reply time to new leads, the share of proposals followed up on schedule and the count of stalled deals.
Each quarter, check conversion between each pair of stages. Weak qualified-to-discovery conversion points upstream, at lead quality or reply speed. Weak proposal-to-commit points at scoping or price. The operational intelligence guide shows how to turn a weak conversion rate into an alert someone acts on, and the SOP training guide covers getting a team to adopt the procedure rather than tolerate it.
Frequently asked questions
What should be included in a sales SOP?
Reply times by lead source, the qualification facts to record, what must exist before a proposal is sent, the follow-up cadence, a stage table with entry rules, exit rules and time limits, loss reasons and the handover record. Keep sales technique in a separate playbook.
How many pipeline stages should a sales procedure have?
Five to seven for most service firms. Fewer hides where deals stall. More than seven usually means you are recording seller activity rather than buyer decisions, and reps stop updating the extra stages.
Should a sales SOP include a call script?
Usually not. Scripts suit very high-volume, low-value calls, but in considered services they make experienced sellers sound wooden. Specify the information to gather, not the words used to gather it.
How often should the sales SOP be reviewed, and who owns it?
The sales manager or director owns it, because they answer for the outcomes it protects. Review the stage rules quarterly against conversion data and change them only when the data shows a rule is wrong, recording the date each change took effect so reporting stays comparable.