Skip to content
← Back to Insights

Sales Process Design for B2B: A Practical Guide

Geometric stages beside a parallel buyer track

A good sales process is a short list of stages, each tied to something the buyer has done, written down so that anyone on your team can run it the same way. Designing one means deciding who you sell to, mapping how they really buy, setting 4 to 8 stages with clear exit criteria, and building those stages into your CRM and your coaching. This guide walks through each step, with a 90-day plan for founder-led and small to mid-sized firms in the UK.

Strategic-concierge
Build Capability for Sustainable Growth
Strategic Concierge helps businesses build, improve and embed the capabilities that support clearer direction, stronger execution and sustainable growth.

TL;DR

  • Design the process around buyer milestones (a confirmed meeting, a completed security review), not around what your reps do (a call made, an email sent).
  • Aim for 4 to 8 stages. More stages feel like more control but usually create friction and stalled deals.
  • Buyers now research alone and arrive late: in Europe, engagement with sellers happens later in the journey, so your process must work before a salesperson is involved.
  • Map first, then configure the CRM, then coach on quality (discovery depth, data hygiene) rather than activity volume.
  • Treat the first version as a draft and review it against won and lost deals every quarter.

Table of Contents

What a sales process is, and what designing one involves

A sales process is the repeatable sequence of steps that takes a prospect from first awareness to a signed contract and into delivery. It is not a methodology (the philosophy of how you sell) and it is not a playbook (the scripts, templates and objection handling that support each step). The process sits between the two: it defines the stages, who owns each, and what must be true for a deal to move on.

Design work covers five decisions:

  1. Who the process is for. Your ideal customer profile, and the buying group around it.
  2. What the buyer does at each point. The real journey, not the one you would like.
  3. Where the stages begin and end. Entry and exit criteria.
  4. How it is recorded. Pipeline stages, required fields and tasks in your CRM.
  5. How it improves. Review rhythm, win and loss data, coaching.

Skip any of these and the process becomes a diagram on a wiki that nobody uses.

Start from how your buyers buy

Most process design fails at the first step because it starts from the seller’s side. The evidence on European B2B buying says the seller’s side is the smaller part of the story.

According to 6sense research published in November 2025, buyer engagement with sellers in Europe happens later in the journey (58% in 2025, down from 67% in 2024), and average B2B buying cycles lengthened from 9.0 months in 2024 to 9.8 months in 2025. The same research reports that 61% of B2B buyers now prefer to buy without direct contact with a sales representative, and that roughly 75% of European buyers have settled on a preferred vendor before they speak to a sales team.

For a small firm, three design consequences follow.

  • Your first stage starts before the first conversation. If most of the decision is made in private research, your website, case studies, pricing clarity and referral reputation are part of the sales process. Design them as such.
  • The seller’s job shifts from controlling to guiding. The 6sense guidance points founders towards offering expert guidance through high-value content and self-serve resources, then personalising the interaction to each role in the buying group once you are engaged.
  • Hybrid journeys are normal. Buyers want to research independently but expect expert support at critical decision points. A process that relies only on vendor-led calls, with nothing for the buyer to read, test or share internally, adds friction.

If you want a practical example of making early-stage buyer research easier, look at how automated follow-up and content support help experienced buyers research on their own and still get relevant answers when they decide to talk to someone.

Remove the friction buyers name

A 2025 survey of 900 senior B2B buyers across Europe, reported by Netconomy, lists the top deal-breakers: lack of transparent pricing (39%), time-consuming reordering (35%), complicated approval processes (34%), hard-to-navigate self-service portals (33%) and slow vendor response times (24%).

Not all of these apply to a consultancy or professional services firm, but two translate directly:

  • Pricing transparency. Decide what you can publish: a price, a range, or at least the factors that move it. A buyer who cannot get a sense of cost will either guess high or move on.
  • Approval complexity. If a proposal needs three internal sign-offs on the client side, your process should give the champion what they need to run that internal process: a one-page summary, a clear scope, and an obvious next step.

Map the process you already have

Sales process mapping is the step that turns tacit habits into something you can change. Do it before you draw an ideal version.

A mapping session in four passes

  1. Pull the last 10 to 20 closed deals, won and lost. Include the ones that dragged. Use CRM records, email threads and calendar history.
  2. Write the timeline of each deal as buyer events. First enquiry, first meeting, stakeholder added, proposal requested, security or procurement check, verbal yes, contract signed. Ignore rep activity for now.
  3. Mark the points where deals stalled or were lost. Note what the buyer was waiting for, or what they were unsure about.
  4. Find the common spine. Which events appear in nearly every won deal, in roughly the same order? That is your draft process.

A flowchart is a good output format, because it forces you to show decision points: what happens if the lead is not a fit, if a new stakeholder appears late, if the buyer goes quiet. Monday.com’s guide to sales process flowcharts describes a process map as a visual diagram of the step-by-step journey from lead to loyal customer, which is a fair summary of what you are aiming for.

If you want to see how the same thinking applies after the sale, our guide to customer lifecycle management extends the map into onboarding, retention and expansion.

Set the stages: fewer, anchored to the buyer

The most common design error, according to the SalesGenie B2B sales process guide, is assuming that more stages mean more control. Its advice is that effective processes typically have 4 to 8 stages, each anchored to a verifiable buyer milestone rather than an internal one.

Here is a worked example for a founder-led professional services firm selling projects of five figures and above. Adapt the wording to your own market.

Stage Buyer-side exit criterion Typical owner
1. Qualified interest Buyer has agreed to a first meeting, and fits your ICP on size, sector and need Founder or business development
2. Discovery Buyer has described the problem, the cost of leaving it, and who else is involved Founder or senior consultant
3. Shaped solution Buyer has reviewed an outline approach and confirmed it addresses the problem Founder or senior consultant
4. Proposal and approval Buyer has a written proposal and has named the approval route and date Founder
5. Agreement Contract signed, start date and first deliverable confirmed Founder and operations
6. Handover Delivery team has the brief; buyer has met them Operations

Six stages, each ending in something a buyer has said or done. A rep cannot move a deal forward by making a call; the buyer has to do something.

Entry criteria matter as much as exit criteria

For each stage, write one line on what must be true to enter it, and one on what disqualifies the deal. Disqualification is where small firms gain the most time: most of us spend weeks on prospects who never had the budget, authority or urgency. A short qualification checklist at stage 1 (fit, need, timing, budget range, decision route) protects the rest of the process.

Five criteria for qualifying a sales opportunity

Allow for buying committees

The same SalesGenie guidance warns that forcing a linear process onto modern, larger buying committees leads to friction and stalled deals. In practice, add a parallel track: a “stakeholder map” field that records who is involved, what each person cares about, and whether you have met them. Stages stay linear; the account view is not.

Build it into the CRM

A process that lives only in a document will decay within a quarter. The aim is to make the CRM reflect the buyer’s progress with the least effort from your team.

The SalesGenie guidance offers a useful design rule: trigger CRM tasks from buyer-side exit criteria such as a confirmed meeting or a completed security review, not from rep activity such as “made a call”. That turns the CRM from a data-entry chore into a record of pipeline health.

A minimal configuration looks like this:

  • Pipeline stages that match your table exactly, with the exit criterion written in the stage description.
  • Required fields at stage change. For example, you cannot move to Proposal without a named decision-maker and an expected decision date.
  • A next step on every open deal, with a date. Apollo’s guidance on CRM hygiene includes the same expectation: every deal has a next step.
  • Loss reasons chosen from a short fixed list, so patterns are visible later.
  • Stage ageing alerts, so a deal that has sat in one stage for twice your average gets a conversation.

Most modern CRMs let you configure a pipeline of your own rather than use a default one, so you do not need a new system to start. If your current tool cannot enforce required fields or stage-based tasks, that is a sign to review it, not to add manual workarounds.

Measure quality, not just activity

Once the process exists, the temptation is to count calls and emails. Apollo’s guidance argues for competency gates over activity quotas: discovery call quality and CRM data hygiene are now treated as better predictors of success than raw activity. Measuring a rep by call volume alone is a legacy habit, and it can push buyers through a funnel rather than help them solve a problem.

For a small team, this translates into a few simple measures:

  • Stage conversion: the share of deals that move from each stage to the next.
  • Time in stage: where deals wait.
  • Discovery quality: a short scorecard reviewed on a sample of calls (was the problem quantified, were all stakeholders identified, was the next step agreed by the buyer?).
  • Data completeness: the share of open deals with every required field filled.
  • Win and loss reasons: reviewed monthly. Our guide to win-loss analysis sets out three formats that suit different team sizes.

A 90-day plan to design and embed the process

If you are a founder with a part-time sales function or a small team, this sequence is realistic.

Days 1 to 30: learn and map

  • Review the last 10 to 20 deals and draw the real timeline.
  • Write your ICP and the typical buying group in one page.
  • Draft 4 to 8 stages with entry and exit criteria.
  • Audit what buyers can find without talking to you: pricing guidance, case studies, a clear description of how you work.

Days 31 to 60: apply and configure

  • Configure the CRM pipeline, required fields and tasks.
  • Run the new stages on all live deals; reclassify them honestly, even if the pipeline value falls.
  • Write the playbook for each stage: questions, templates, proof points.
  • Start weekly pipeline reviews built around exit criteria and next steps.

Days 61 to 90: tighten and coach

  • Review stage conversion and time in stage for the first time.
  • Score a sample of discovery calls and give feedback.
  • Remove or merge any stage that nobody can define an exit for.
  • Set a quarterly review date, and put it in the diary now.

The structure mirrors the 30-60-90 framework that Apollo describes for onboarding new salespeople: learn, apply, accelerate. Apollo reports that the average SaaS ramp-up time rose 32% to 5.7 months in 2025, and that structured plans can cut new-hire ramp time by up to 34%. A documented process is what makes that kind of structured onboarding possible. For more on setting up a ramp that makes new sales hires productive sooner, see this piece on structured follow-up and early milestones.

One caution from the same guidance: do not treat the plan as a static checklist. The first 30 days should go into internalising product positioning and the ICP, otherwise later outreach fails to resonate and can damage brand trust.

Common mistakes in sales process design

  • Copying a seven-step textbook model. Generic lists (prospecting, preparation, approach, presentation, objections, closing, follow-up) describe a seller’s activity. They are a vocabulary, not a design.
  • Too many stages. If your team argues about whether a deal is in stage 5 or 6, you have too many.
  • Stages defined by rep behaviour. “Proposal sent” is a rep action. “Buyer has confirmed the approval route” is a buyer milestone.
  • Ignoring existing customers. Referrals and expansion often outperform cold outreach for small firms. Link the process to your customer success playbook so that delivery feeds the next sale.
  • Targeting too many accounts. If you sell to named accounts, size the list to what your team can actually work. Our article on account-based marketing strategy covers this.
  • No owner. Someone must be responsible for the process itself, not only for deals.

Where the sales process sits in the wider business

A sales process works best when it is one part of a coherent operating model: clear positioning, a defined offer, marketing that feeds it, delivery that justifies referrals, and reporting that ties them together. Our guide to building a business operating system in stages shows how the sales process connects to the other parts, and why it is usually better to build the pieces in order than all at once.

If you run a recruitment firm, the same logic applies, with its own twist: two-sided sales (clients and candidates) and heavy founder involvement. See digital foundations for recruitment businesses and scaling a founder-led recruitment business without scaling the founder.

Our perspective

We see the same pattern in small and mid-sized firms. The sales process exists, but only in the founder’s head, and every deal is run slightly differently. Growth stalls because the founder is the process.

Our view is that you do not need a large, complex design to fix this. You need a clear direction (who you sell to and why they buy), a small number of buyer-anchored stages, and a CRM that reflects them. Get that live in a month, then iterate. That is how we approach all capability work at Strategic Concierge: build a launch-ready foundation first, improve it against real results, and only then embed it so the team can run it without us.

We would also say this plainly: a process cannot compensate for an unclear offer. If buyers cannot tell from your site what you do, for whom and roughly at what cost, redesigning your stages will help less than fixing that. Start with the buyer’s view, and the stages follow.

— Chris

Getting help with the build

If you would rather not design this alone, our staged approach (Build, Iterate, Optimise, Embed, Grow) starts with a launch-ready foundation and can continue as ongoing managed support. The Managed Capability plan is priced at £999 per month, £2,850 per quarter or £10,000 per year; see the pricing page for the full list of options, or read how the method works. When you are ready to talk it through, book a discovery call.

FAQ

How many stages should a B2B sales process have?

Between 4 and 8 is a sensible range, according to SalesGenie’s guidance. Start at the lower end and add a stage only when you can define a verifiable buyer milestone that ends it. If you cannot name the exit criterion, the stage is not needed.

What is the difference between sales process mapping and sales process design?

Mapping records how deals actually progress today, from buyer events and rep actions. Design decides how they should progress: the stages, criteria, owners and CRM rules. Do the mapping first, because it shows where your current process loses time and deals.

What is the 30-60-90 rule in sales?

It is an onboarding framework in which the first 30 days are for learning product, process and ICP, the next 30 for applying that learning in outreach and discovery, and the last 30 for accelerating towards quota, as Apollo describes. It works best as a competency check, not a static checklist.

Do I need a CRM before I design the process?

No. Design the stages and exit criteria on paper first, using real past deals. Then configure whichever CRM you use so that it enforces them. Designing around a tool’s default pipeline usually produces stages defined by the software rather than by your buyers.

Sources

← Back to Insights