Pipeline Management
B2B Sales Process: How to Map Yours in 7 Steps
A process your team will follow starts from how your buyers actually decided, not from a template. Build yours from recent wins, with one owner, one buyer decision and a written handoff at every stage.
Key takeaways
- A B2B sales process is the sequence of stages, owners and handoffs a deal follows from first conversation to delivery; a sales methodology is how reps work inside it.
- Build the process from your last 10 won deals: events that recur in the wins become stages, and events common only in losses become warnings.
- Give each stage one buyer decision as its exit criterion and one owner, with evidence a colleague could check on the record.
- Write every handoff, SDR to AE and AE to customer success, as a checklist, and count it done only when the new owner books the next customer touch.
- Set discount approval bands with named approvers before a deal needs them, track handoff lag as a median, and review the whole map at 90 days.
A B2B sales process is the agreed sequence of stages a deal moves through, from first conversation to signed order and handoff to delivery, with one owner and one exit criterion at every stage. You can map yours in seven steps, starting from deals you already won. In Senitix CRM, you build your pipeline from the finished map.
This guide is for the sales manager, founder or sales ops lead who has to write it down. New to CRM? Start with our guide to what a CRM does for a sales team.
What is a B2B sales process?
Four terms get mixed up:
- Sales process: the stages, owners and handoffs your team follows to win a deal and pass it to delivery.
- Sales stages: the names of those steps in your CRM, usually one column each on the pipeline board.
- Sales methodology: how reps work inside each stage, such as the questions they ask and how they qualify. MEDDICC, SPIN Selling and the Challenger approach are methodologies, not processes.
- Sales process map: the one-page document that ties it together, listing each stage, the buyer decision that ends it, its owner and what the next person receives.
A process answers “what happens next, and who does it?” A methodology answers “how do we do it well?” The second needs the first to attach to.
Why write your sales process down?
Because in a B2B sales process a deal passes through many hands on both sides, and every step nobody wrote down is a place for it to wait. Forrester’s State of Business Buying, 2024 research, based on a survey of more than 16,000 business buyers worldwide, found that on average 13 people in the buying organization are involved in a purchase decision, and that 91% of purchases stall at some point.
An unwritten process breaks in three places: every rep runs a private version, a promise made in week two is gone by the kickoff call, and discounts get approved one deal at a time at quarter-end. A written map settles all three in advance.
How do you map a B2B sales process in 7 steps?
The seven B2B sales process steps, in order: reverse-engineer your last 10 wins, list the decisions your buyer makes, turn those decisions into stages with owners, write down every handoff, set quote and approval rules, decide what you will measure, and review the map at 90 days.
Step 1: Reverse-engineer your last 10 won deals
Owner: the sales manager or sales ops lead. Output: a dated timeline for each deal.
Pull your 10 most recent wins and five recent losses. Rebuild each from first conversation to signature using the record, the email thread and the calendar. Record events, not impressions: who joined from the buyer’s side and when, what they asked for, which documents changed hands and how long each silence lasted.
Lay the timelines side by side. An event that appears in eight of the 10 wins is a candidate stage or exit criterion. An event common in losses but rare in wins, such as a quote sent before anyone met the signer, is a warning worth writing down.
Step 2: List the decisions your buyer makes
Owner: the sales manager, with two of your strongest reps. Output: five to seven buyer decisions, in order, each written as the buyer would say it. A typical list:
- “This problem is worth solving this year.”
- “Your company is worth evaluating.”
- “Your solution fits, and this is who approves the spend.”
- “The commercial terms work for us.”
- “We will sign, and this is the path to signature.”
A decision earns its place only if a colleague who never spoke to the buyer could confirm it from the record: a written reply, a meeting with named attendees, a purchase order.
Step 3: Turn each decision into a stage with an owner
Owner: the VP of Sales or sales manager. Output: the stage list, each with an exit criterion, one owner and the evidence expected.
Give every buyer decision its own stage, ending when the decision is made; that is your exit criterion. Use your reps’ own words, keep to five to seven open sales stages, and give each a single owner. A stage with two owners has none.
No CRM field proves a buyer decided, so the exit criterion is a team standard that a manager checks, evidence in hand, in the weekly deal review. The CRM strategy guide covers which fields and reports to build on those stages.
Step 4: Write down every handoff
Owner: whoever hands the deal over, until the receiver accepts it. Output: a short checklist for each change of owner.
Many B2B teams have two: from the sales development rep (SDR) who qualifies an inquiry to the account executive (AE) who runs the deal, and from the AE to customer success after the close. A checklist to copy:
- SDR to AE: the problem in the buyer’s words; who else is involved, and in what role; the buyer’s timing and the reason for it; the lead source; and a first meeting on the AE’s calendar, not just a name passed along.
- AE to customer success: what was sold, line by line; anything promised outside the contract, such as a delivery date or training; who signs, who uses the product and who escalates; and the first date the customer expects something to happen.
- Acceptance: the handoff is done when the new owner has read the record and booked the next customer touch, not when the name on the deal changes.
Step 5: Set quote and approval rules before you need them
Owner: the sales manager and whoever owns margin, often the controller. Output: a one-page quoting policy. Fill in the brackets with your own numbers:
- A discount up to [X]% off list: the rep decides.
- Between [X]% and [Y]%: the sales manager approves.
- Above [Y]%, or payment terms beyond your standard: the controller or VP of Sales approves.
- Every quote has a version number and an expiry date, and the approved version is the one the customer receives.
Put a name beside each band, so no buyer waits while a rep hunts for an approver.
Step 6: Decide what you will measure
Owner: sales ops, or the sales manager on a smaller team. Output: a few numbers with written definitions, reported monthly.
- Stage conversion: of the deals that entered a stage in the period, the share that reached the next one.
- Median days in stage: measured on won deals, so you know what normal looks like at each step.
- Handoff lag: the date of the first customer success meeting minus the date the deal closed won.
Example: a team closes 12 deals in March, and the kickoff meetings happen 1, 2, 2, 3, 3, 4, 5, 6, 8, 9, 14 and 21 days after close. The median handoff lag is 4.5 days; the average is 6.5, pulled up by two deals that sat without an owner for two and three weeks. Report the median, and read those two deals line by line.
Step 7: Review the map at 90 days
Owner: the VP of Sales, with sales ops and two reps. Output: version two of the map, dated, with what changed and why.
Book the review the day your B2B sales process map goes live. At 90 days, look for:
- The stage where open deals wait much longer than won deals did.
- Exit criteria nobody records evidence for: either the criterion is wrong or nobody checks it.
- Handoffs that bounce back because the new owner lacked basic facts.
- Approval requests that are almost always granted, a sign the band is set too low.
Change only what the evidence supports, and keep the old version. If the map is part of a new CRM rollout, the CRM implementation guide shows where this work sits among the other steps.
B2B sales process example: a 15-person industrial distributor
Example: a hydraulic and pneumatic components distributor in Columbus, Ohio, sells to plants across Ohio, Indiana and Michigan. Its 15 people include three inside sales reps, six outside sales reps, two application engineers and two customer service reps. The company and every number here are illustrative.
Its last 10 wins showed a pattern: nine included a plant visit by an application engineer before the first quote, and seven needed a revised quote after the maintenance manager reviewed the spec. The resulting map:
| Stage | Buyer decision that ends it | Owner | What the next owner receives |
|---|---|---|---|
| Inquiry qualified | The plant confirms application, quantities and need-by date, and agrees to a visit | Inside sales rep | Qualification notes and a visit booked with the outside rep |
| Site assessment | The maintenance manager signs off on the written spec | Outside rep, with an application engineer | The spec sheet on the deal |
| Quote | The buyer accepts the quote or names the changes needed | Outside rep | The quote version sent and the buyer’s dated reply |
| Approval and terms | Purchasing agrees to price, freight and payment terms in writing | Outside rep | The quote version approved under the quoting policy, the only one the buyer sees |
| PO received | Purchasing issues a PO that matches the approved version | Outside rep | The PO on the record; the deal closes won |
| Customer service handoff | The plant confirms the delivery date and receiving contact | Customer service rep | A logged kickoff call listing every promise made during the deal |
The team split Quote from Approval and terms because the maintenance manager and purchasing decide different things, often weeks apart. The first handoff now counts only once the site visit is booked. The last row comes after the deal closes won, so in a CRM it is a task on the won deal, not a pipeline stage. A SaaS team fills the same columns with SDRs, AEs, a solutions engineer and customer success.
Which mapping mistakes should you avoid?
- Borrowing a generic stage list. The prospecting-to-close steps in many B2B sales process templates are things a rep does; they say nothing about where the buyer is.
- Mapping the process you wish you ran. A stage that none of your recent wins went through becomes a column reps skip.
- A map that never settles, or never changes. Change it weekly and no metric covers a full quarter; never review it and it drifts away from how buyers behave.
How do you set up the map in Senitix CRM?
A B2B sales process map works in any CRM. In Senitix CRM, you set up the stages from it yourself; nothing arrives configured.
- Pipelines and stages: deals move through your own stages on a list or Kanban board, and a team can run more than one pipeline as its sales motions diverge.
- Stage guidance: each stage can show guidance text and up to five key fields, so the exit criterion sits in front of the rep while they update the deal. It is shown, not enforced.
- Handoffs: qualifying a lead creates the contact, the account and the deal in one step, and notes, files and activities run down one shared timeline on the account, so the next owner starts from the history.
- Quotes and approvals: quotes are built from your catalog and kept as numbered versions, and a discounted quote can go through an approval process with named approvers.
- Automations and AI: a rule can create a kickoff task and notify customer service when a deal is won. Senitix AI, within a daily request limit per user, can summarize a long email thread for whoever takes over; nothing is sent or changed until that person confirms.
Start with the Senitix CRM overview to see how deals, stages and guidance fit together, then check the pipeline features for the detail. To test the map on live deals, the Free plan costs nothing for up to 2 users, with no time limit and no credit card. Compare plans on the Senitix CRM pricing page, or talk to the Senitix sales team about a larger rollout.
Frequently asked questions
How long does a B2B sales process take?
It depends on deal size, how many people the buyer involves and how they purchase, so an industry average says little about your team. Measure it: take your last 20 won deals and find the median number of days from the first qualified conversation to the signed order. Then do the same for each stage to see where the time goes.
How does B2B selling differ from B2C?
A B2B purchase is made by an organization: several people weigh in, the spend usually needs internal approval, and the order arrives as a purchase order or signed contract, followed by delivery. That is why a B2B sales process needs named owners, written handoffs and approval rules. A B2C purchase is usually one person deciding, often in one visit.
How is a sales process different from the buyer’s journey?
The buyer’s journey describes the purchase from the customer’s side: recognizing a problem, exploring options, choosing a supplier. The sales process describes your side: stages, owners and handoffs. A good map ties the two together by ending each stage on a buyer decision, so your deals move only when the buyer does.
Keep reading
Pipeline Management
Stalled Deals: How to Spot Them Early and What to Do Next
A fixed ‘30 days’ rule misreads your pipeline. Set your own per-stage baseline, run a three-touch revival plan, and record ‘no decision’ honestly.
Pipeline Management
What Is a Sales Pipeline? Stages, Examples, and How to Manage One
What a sales pipeline is, how it differs from a funnel, stages defined by buyer commitments, a worked B2B example, and the three metrics worth tracking.
Leads & Prospecting
Lead Scoring Model: How to Build a Rule-Based Score Your Reps Trust
A rule-based lead scoring model with a worked scorecard, the threshold sales will accept, and the quarterly back-test that keeps it honest.
Ready to grow with Senitix?
Connect with customers, win more deals and grow repeat business, all on one platform.
No credit card required.
