Most sales teams have a process. Fewer have procedures. The gap between the two is where deals stall, reps improvise their way through discovery calls, and the forecast misses by double digits. Sales procedures are the written instructions that turn a sales strategy into something a new hire can actually execute. Without them, the process is a diagram on a whiteboard.
This guide covers how to design, document, and enforce sales procedures for a B2B team, from lead generation through post sale follow up and renewal.
Key takeaways
- Procedures translate a high-level sales process into concrete steps a rep follows from first touch to expansion, and they’re what makes stage-by-stage tracking mean anything.
- Documenting what your team does today comes before designing what it should do. You can’t fix a process you’ve never written down.
- Procedures that match how buyers actually evaluate produce more predictable revenue and faster ramp for new reps, and they give you metrics worth reviewing.
- CRM configuration, email sequencing, and commission tools such as incentX enforce procedures better than reminders do.
- Review procedures twice a year, in January and July, against real sales performance data.
What sales procedures are
A sales procedure is a step-by-step instruction that tells a rep what to do at a given stage: who does it, when, in which system, and what to do when the situation isn’t standard. It’s the operating manual sitting underneath the process diagram.
Three terms get used interchangeably and shouldn’t be. The sales process is the sequence of stages from prospecting to close, the what. The procedures are the written instructions inside each stage, the how. The methodology, MEDDIC or SPIN or Challenger, is the approach a rep takes to questioning and positioning, the why.
A discovery call procedure looks like this: in a scheduled 30 minute call, open with a two minute agenda review, work through the qualification questions in the MEDDIC order, log responses in CRM during the call rather than after, send a recap email within two hours, and book the next step within three business days.
Written at that level of detail, procedures produce the same customer experience across phone, email, and video, and across SDR, AE, and account manager. That consistency is most of what people mean when they call a sales organization well run.
Why written procedures matter in B2B
The case for documentation isn’t philosophical. Four things change when procedures exist in writing.
Rework drops. Without defined steps, reps redo work other reps already did, chase leads nobody dispositioned, and rebuild the same proposal from scratch. Sales management gets a lot easier when the answer to what happens next is written down.
Onboarding gets shorter. A new hire following a documented playbook doesn’t have to reverse engineer what the top rep does, and the top rep doesn’t have to explain it eleven times.
Forecasting improves, because CRM gets updated at defined trigger points instead of the night before the pipeline review. Organizations with structured forecasting land within 5 to 10 percent at the top quartile, against 15 to 25 percent for average teams.
Margins hold. A procedure that defines discount approval thresholds is the only thing standing between a quarter end and a deal priced below cost.
Durhamlane built structured SDR cadences on top of sales engagement software to systematize outreach and coaching, which is a reasonable picture of what this looks like in practice.
Procedures also interact with pay. Clear steps plus transparent commission and rebate accounting cut down disputes, because a rep who can see the transactions behind a payout stops filing tickets about it.
Process, procedures, and methodology side by side
| Term | Definition | Analogy |
|---|---|---|
| Sales process | The sequence of stages from lead generation to post sale follow up | Roadmap |
| Sales procedures | Written instructions for what a rep does inside a stage | Turn-by-turn directions |
| Sales methodology | The approach to qualifying, questioning, and handling objections, such as MEDDIC, Challenger, or SPIN | Driving style |
All three operate at once. A SaaS company selling into enterprise runs MEDDIC as the methodology, has eight stages in the process, and writes the qualify stage procedure as: complete the MEDDIC checklist in CRM within 24 hours of the discovery call, and if no economic buyer or decision criteria can be identified, disqualify with a stated reason. Drop any one layer and the other two stop working. The process gives direction, the methodology shapes the conversation, and the procedure is what makes it happen the same way twice.
Define the process before writing the procedures
Procedures attach to stages, so the stages have to exist first. Most B2B processes run seven stages, with an eighth for expansion. What matters more than the count is that each stage has an exit criterion someone can check.
- Lead generation and prospecting: inbound, outbound, and referral sourcing against the ideal customer profile.
- Qualification: fit judged on budget, authority, need, and timeline.
- Discovery: pain points, goals, stakeholders, and constraints.
- Solution presentation or demo.
- Proposal and negotiation, including pricing, terms, and objections.
- Closing: agreement, approvals, signature.
- Onboarding and implementation, with handoff to post-sales.
- Expansion and renewal.
Build the stage definitions from your own closed deals over the last 6 to 12 months, not from a template. The point of the exercise is finding where the funnel leaks. A common pattern is a large share of deals reaching proposal and never advancing, which usually traces back to a pricing conversation that should have happened during discovery. That’s a fixable procedure gap, and you only see it by reading your own pipeline history.
Procedures for each stage
What follows is the working detail: what a person does, and what the system does, at every stage.
Prospecting
Prospecting procedures are mostly about volume floors and routing rules, since both are easy to state and easy to audit.
- A daily SDR floor: set explicit minimums for call attempts, personalized emails, and social touches, and review connect rates and meetings booked weekly rather than monthly.
- Target lists refreshed weekly from CRM, an industry database such as ZoomInfo or LinkedIn Sales Navigator, and inbound. Every lead tagged with its source, without exception, or attribution is guesswork later.
- Routing: inbound demo requests assigned to the territory AE within one business hour. Outbound leads grouped by vertical and assigned weekly.
- A first outreach cadence spanning 7 to 10 business days across channels, with templates stored in the sales engagement platform rather than in individual drafts folders.
The purpose of the list criteria is to keep reps working accounts that match the ideal customer profile instead of whoever answers the phone.
Qualification and discovery
Qualification decides where the team spends its time, so the criteria have to be written down and recorded, not carried around in memory.
- Criteria: budget confirmed or a funding timeline identified, a named decision maker, a stated problem, and a decision window. Under MEDDIC, also capture metrics, decision criteria, economic buyer, and champion. Every field logged in CRM during the first call.
- Call structure: agenda sent ahead, five minutes of context, the bulk of the time on open questions, a summary read back, and an explicit next step agreed before the call ends.
- Disposition rules: unqualified leads closed out the same day with a stated reason such as no budget until the next fiscal year, wrong segment, or no problem to solve. Those reasons are what make pipeline analysis possible.
- Qualified opportunities get the next demo or technical session booked within three business days.
Script the framework, not the wording. A rep should be able to reorder questions to fit what the account has already told you.
Demo and solution presentation
Confirm attendees 24 hours ahead and send an agenda. Set up the demo environment with data that resembles the account: their vertical, their use case, field names they recognize. A generic feature tour is the most common way this stage fails.
Run 30 to 45 minutes: recap what discovery turned up, present the two or three value drivers that matter to this account, walk through the relevant functionality live, quantify the return in their numbers, and close with a decision timeline. Send the recap the same business day with the recording, the outcomes, the decision criteria discussed, and the next meeting already on the calendar. Reference the specific problems the buyer described rather than the feature list, and use a customer story where you have one that fits.
Objection handling
Objections are where undocumented teams improvise and deals go quiet. The framework is short: listen without interrupting, ask a clarifying question, acknowledge the concern, respond with evidence or a reframe, then confirm the objection is actually resolved rather than assuming.
Write pre-approved responses for the five to seven objections you hear most. In B2B those are usually budget locked until the next fiscal year, an incumbent competitor, bad timing, integration or technical risk, insufficient internal buy-in, and price against perceived value.
New objections go into a shared knowledge base, reviewed monthly by managers and folded into training. Objections involving commercial terms, custom SLAs, or legal risk should have a named escalation path to sales engineering, finance, or legal rather than a rep improvising a commitment.
Comp design belongs in this conversation. When commission rules pay on margin or deal quality rather than gross revenue, the rep has a reason to resolve an objection instead of discounting past it.
Closing and contracts
- Ready to close means all of: business case confirmed, decision maker identified, budget approved, target close date inside 30 days, and terms drafted. Anything short of that is still in negotiation.
- The sequence: share the proposal, review terms live rather than by email, negotiate, collect internal approvals from finance and legal, then send for signature.
- Follow up within 24 hours of sending a contract, then at agreed intervals until it’s signed or declined, logging the reason for each delay.
- Discounts above the threshold route to finance. Legal redlines stored centrally, contract versions tracked.
- Before final sign-off, confirm the deal is configured correctly in the compensation system: product, margin, term. Custom terms should trigger a commission eligibility review rather than surfacing as a payout surprise a month later.
Handoff, follow up, and expansion
The first 90 days set up everything that follows: welcome email within 24 hours, implementation kickoff within seven business days, and check-ins at 30, 60, and 90 days against adoption rather than sentiment.
The internal handoff is the part most often skipped. Discovery notes, proposal detail, negotiated exceptions, and the success metrics the buyer agreed to all move from sales to customer success, along with a clear statement of who owns what. Expansion conversations trigger off usage thresholds, delivered return, or a customer milestone, with account plan reviews between CS and sales each quarter. Referral and case study requests come after a documented result, not before.
Relationship work in this phase is what produces renewals and customer loyalty. It also needs to pay. Tracking incentives on renewals and expansions accurately is what keeps reps engaged with an account after the initial close.
Matching procedures to the buyer’s journey
Buyers don’t move through stages in order, particularly in committee driven B2B purchases. Procedures still have to map to what the buyer is doing, or reps end up pushing a proposal at someone still deciding whether the problem is worth solving.
| Buyer stage | Internal stage | Procedure focus |
|---|---|---|
| Problem recognition | Lead generation | Educational outreach, not a pitch |
| Research | Prospecting, initial contact | Insights and relevant content |
| Evaluation | Discovery, demo | Tailored presentation, return quantified |
| Selection | Proposal, negotiation, closing | Objection resolution, contract execution |
| Implementation | Onboarding | Adoption support, success metrics |
| Renewal | Expansion | Usage triggers, account planning |
Early on, the procedure should keep reps in a teaching posture. Later it shifts to return calculations, competitive comparison, and written decision criteria. Refresh the mapping twice a year using win and loss interviews, since the way a given market buys changes faster than most playbooks get updated.
Tools that enforce the procedure
A procedure that lives in a document gets followed for about a month. A procedure built into the system gets followed indefinitely.
In the CRM, that means required fields per stage, exit criteria that block advancement, and automated reminders tied to stage age rather than to whether a rep remembers. In the sales engagement layer, it means email sequences, dialer logging, and routing rules that apply the cadence without anyone deciding to.
On the compensation side, incentX reads transaction-level ERP data to calculate commissions, rebates, royalties, trade promotions, and billbacks against the rules your procedures define. It connects to Salesforce, Oracle NetSuite, SAP, Sage, and QuickBooks, and reporting shows reps the specific transactions behind a payout.
Integration is what makes the whole arrangement hold. If CRM, ERP, and the incentive system share data, a change to the process shows up in compensation and reporting without a manual reconciliation step. One caution: reps are already carrying more tools than they use. Consolidate where you can, and prefer platforms that integrate natively over adding another point solution.
Measuring and auditing the process
A handful of metrics tell you whether the procedures are working.
- Lead response time, measured from form fill to first contact attempt. Inbound leads worked within the hour convert at meaningfully higher rates than ones worked the next day.
- Stage conversion rates, to find the weakest transition. Lead to qualified and demo to proposal are the usual culprits.
- Win rate. SaaS new business typically runs 20 to 30 percent, enterprise 15 to 25 percent, and expansion deals 40 to 60 percent.
- Sales cycle length, tracked separately by segment. SMB, mid-market, and enterprise cycles are different animals and averaging them hides the problem.
- Forecast accuracy, measured against what actually closed.
- Process compliance. Stage exit criteria compliance of 80 to 90 percent is the target in well-governed organizations.
Run the audit every January and July. Compare what reps actually do against what the document says, then sit down with frontline reps and managers to find the steps they skip and why. Usually the skipped step is one that costs 20 minutes and produces nothing. Read the win and loss data for patterns, build an improvement backlog, fix the top three to five items, and update the training material before the quarter starts rather than mid-quarter.
Include marketing in the review. Lead quality and messaging determine whether the early stage procedures work at all, and sales can’t fix a qualification problem that starts in a campaign.
Common questions
How often should we update our sales procedures?
Formally twice a year, in January and July. Update sooner when a metric moves sharply, such as a drop in close rate or a spike in no-decision outcomes. Involve frontline reps every cycle, because they’re the ones who know where the document and reality have diverged.
Who should own the documentation?
Sales leadership or revenue operations, with input from marketing, customer success, and finance. Name one process owner rather than assigning it to a committee. Whoever owns it also needs to coordinate with whoever owns comp, since a procedure change that affects deal structure or pricing has to reach the commission rules in the same cycle.
How detailed should procedures be?
Detailed enough that a new rep can follow the timelines, systems, and templates without asking. Not so detailed that judgment is prohibited. Mark the non-negotiables explicitly, such as logging calls the same day, and mark the flexible parts, such as how discovery questions get ordered. A procedure nobody follows is worse than no procedure, because it makes the audit meaningless.
Can SMB and enterprise share the same procedures?
They can share the stage framework. They shouldn’t share the procedures inside it. Enterprise deals need stakeholder mapping, multi-threading, longer follow up cycles, and additional approvals that would only slow an SMB deal down. Maintain two variants: a short path with fewer touchpoints, and a multi-threaded path with formal business case and champion development steps.
How do commissions fit in?
The comp plan should pay for the behavior the procedure requires. If the procedure demands documentation, margin discipline, and full qualification before advancing a deal, and the plan pays flat on booked revenue, the plan wins and the procedure gets ignored. Keeping the two in sync is easier when commission rules run off the same ERP and CRM data the process does. Change a close-plan rule to require finance sign-off on discounts above 15 percent, and the commission logic can pick up the change rather than waiting for a spreadsheet update, which is also what keeps pipeline coverage honest.
