FAQ: B2B Sales Process

A sales process is a designed path along which you lead the client from first contact to the purchase decision. It has stages, criteria for moving between them, and clear rules about what should happen at each step.

A set of activities is a situation where salespeople do things (they call, write emails, go to meetings) but nobody knows why in that order or what should come out of it. Everyone works their own way. One calls, another writes, a third waits. Results depend on individual talent, not on the way of working.

The key difference: a set of activities cannot be improved. Because you don’t know what to improve. If you don’t know at which stage you lose clients, you don’t know what to change. A process gives you that knowledge. You see that 60% of deals die after the proposal is sent. And you can ask: why. And do something about it.

A company with a set of activities says “sales aren’t going well.” A company with a process says “we lose clients at stage three because the proposal doesn’t address their problem.” That is the difference between frustration and diagnosis.

There is no single universal template, but in the B2B service companies I work with, the process usually consists of four to six stages.

Identification. Someone shows up: from a referral, a cold email, the website, LinkedIn. This is a raw contact that is not yet a lead.

Qualification. You check whether this contact fits your client profile. Do they have a problem you solve. Do they have a budget. Are you talking to a decision maker. If they don’t pass qualification, you let them go.

Diagnosis. A conversation in which you try to deeply understand the client’s situation and make them feel understood. You don’t present. You ask, listen, take notes. This is the stage that separates good sales from average sales.

Proposal. You present a solution tailored to what you learned. Not a generic offer. A proposal that answers the specific problem of this specific client.

Decision. The client makes a decision. Your role is to help them make it: answer their doubts, address the risks, agree on terms.

Closing. The contract, formalities, handover to delivery.

These stages may have different names in your company. They may be merged or split. What matters is that they exist, that they are named, and that everyone who sells knows what happens at each of them.

Don’t start with tools. Don’t buy a CRM. Don’t look for templates online. Start by answering one question: what does the client’s journey look like from the moment they show up to the moment they sign the contract?

Take a sheet of paper. Or a whiteboard. Draw that journey. Not the ideal one, not the textbook one. The one that actually happens in your company. The client calls. What do you do? You set up a meeting. What do you say there? What happens after the meeting? Do you send a proposal? When? Based on what?

Most business owners I work with do this for the first time and discover they can’t describe their own process. Because there isn’t one. There is improvisation, which usually looks a little different every time.

Once you draw that journey, you will see the stages emerge naturally. Give them names. Define what has to happen for a deal to move from one stage to the next. And start using it.

It doesn’t have to be perfect. The first process will be simple and imperfect. That’s fine. What matters is that it exists. Because only once it exists can you improve it. You can’t improve something that isn’t there.

Three signals.

First: you can forecast. If you know you have 15 deals at the proposal stage and historically you close 30% of them, you know you will close roughly 4 to 5 deals. If you can’t say that, the process isn’t working or you aren’t measuring.

Second: a new person can get up to speed. If you hire a salesperson and after two weeks they know what to do, the process works. If after two months they are still improvising and “learning,” there is no process.

Third: you know where you lose clients. Not a general “sales aren’t going well.” Specifically: “we lose 40% of deals between diagnosis and proposal.” That gives you a stage of the process worth working on. You can check why it happens and what to change.

A process that works doesn’t have to deliver 100% conversion. None does. But it gives you control. You know what is happening, why, and where to step in. That is the fundamental difference between a company that manages its sales and a company that hopes sales will somehow work out.

A funnel is a model. It describes a shape: many contacts at the top, few clients at the bottom. It says that at each stage some people drop off. That is useful as a way of thinking about proportions.

A process is an instruction. It says what you do at each stage. How you qualify. How you run the discovery call. When you send the proposal. What happens afterwards.

You can have a funnel without a process: you see contacts dropping off, but you don’t know why. And you can have a process without a funnel: you know what to do, but you don’t measure the proportions.

The ideal situation is both at once. The process tells you how to lead the client. The funnel tells you how many clients you lose at each step and whether that is normal.

In B2B service companies the funnel is usually narrow. You don’t work with thousands of leads. You work with a dozen or so, sometimes a few dozen. And that is exactly why the process matters more than the funnel. Because with a small number of deals, every process error costs proportionally more.

Don’t tell them to stop improvising. Give them something better.

Salespeople who have sold their own way for years won’t accept an imposed process unless they see it helps them. Saying “from now on we do it this way” without explaining why ends in resistance or in filling the CRM with fiction.

Start with one element. Not the whole process at once. Qualification, for example. Say: “before we spend time preparing a proposal, let’s check three things: whether the client has a budget, whether we are talking to the decision maker, and how urgent the need is.” That is concrete, simple, and delivers results right away. After a week the salesperson sees they are no longer wasting time on pointless proposals.

Then add the next element. A weekly pipeline review. 30 minutes. You go through the deals and agree on next steps. Salespeople start to see that this structure helps them sell and isn’t bureaucracy.

And most important: involve the team in building the process. Don’t impose it from above. Ask: “how do you run a conversation with a new client? What do you do after the meeting? When do you let go?” Draw out what they do well and call it the process. People accept rules more easily when they helped create them.

The stages, yes. The style, no.

The process says: at the first meeting we do a diagnosis, not a presentation. That is a rule that applies to everyone. But how the salesperson runs that diagnosis (which questions they ask, in what order, in what tone) can be their own space, although it is also worth standardizing needs discovery.

An analogy: in a hospital, every surgeon operates according to the same protocol. Preparation, disinfection, the order of steps, post-operative checks. But the surgical technique (how they hold the scalpel, how they react to a complication) is individual.

Sales is the same. The process defines what and when. The salesperson decides how. This is not a limit on creativity. It is the frame within which creativity makes sense.

One caveat: this works on the condition that the stages and criteria are actually followed. If one salesperson qualifies strictly and another “takes everything,” you don’t have a process. You have one salesperson with a process and another without.

Start with your reality, not with a textbook.

The sales process in a software house looks different than in a marketing agency. The sales cycle is different. The number of decision makers is different. The way the solution is presented is different. A process taken from a book on SaaS sales won’t work in a company that sells consulting services for PLN 200,000.

A practical method: take the last three deals you won. Write down step by step what happened from first contact to signing the contract. Where the client came from. What happened at the first meeting. How many meetings there were. When the proposal appeared. Who made the decision. How long it took.

Then take three deals you lost. Write them out the same way. Compare. Where are the differences? At which stage did the lost deals fall out? What didn’t you do that you did in the won ones?

Your process will emerge from that comparison. Not a theoretical one. Yours. Based on how your clients actually buy. Then you name it, write it down and start applying it consistently.

Designing the process is a matter of days. Implementing it is a matter of months.

Writing down the stages, qualification criteria and proposal template can be done in a week. But paper accepts anything. The problem starts when the process has to come alive in daily work.

Realistically: you need two to three months for the process to start working. For salespeople to apply it. For the CRM to reflect reality. For the weekly pipeline review to be a habit, not a duty.

And another three months to see results. Not because the process is slow. Because the B2B sales cycle takes weeks or months. A deal that enters the pipeline in January closes in March or April. Only then do you have the data to judge whether the process works.

Companies that want to see results in two weeks usually get discouraged and go back to improvising. Companies that give the process six months never go back. Because they see the difference.

Because a CRM is a tool, and a process is a way of thinking and acting.

A CRM records what you do. It doesn’t tell you what you should do. You can have the most expensive CRM on the market and still have no process. Salespeople will enter contacts, move statuses and generate reports that mean nothing. Because there are no rules that define what the status “in progress” means, when a deal should move forward and when it should be closed.

I run into this again and again. A company buys a CRM for tens of thousands a year. Spends three months implementing it. Six months later nobody enters data, or they enter whatever. The pipeline is fiction. The reports show numbers, but nobody trusts them.

The problem isn’t the CRM. It’s that the CRM was implemented before the process. And a CRM without a process is the most expensive address book you can buy.

The right order: first the process (stages, criteria, rules). Then the CRM as a tool that supports that process. The CRM should reflect your way of working, not the other way around.

Through one shared point: the definition of a lead.

In most B2B companies I work with, marketing and sales live separately. Marketing generates “leads”: contacts, downloads, webinar sign-ups. Sales gets those leads and complains they are weak. Marketing complains that sales doesn’t close. Nobody is right and everybody is right at the same time.

The problem is that nobody has defined what “a lead ready for a sales conversation” means. Marketing thinks someone who downloaded an e-book is a lead. Sales thinks a lead is someone who wants to buy this month. Those two definitions have nothing in common.

The solution: agree on the criteria together. What has to happen for a marketing contact to go to a salesperson? For example: a client from the right industry, of the right size, who has shown specific interest (not just downloaded a PDF, but visited the pricing page and came back three times in a week).

Once that definition exists, marketing knows what to deliver. Sales knows what to expect. And the mutual blaming ends.

A fix, when the goal of the process is right but the execution falls short. For example: the qualification stage is well designed, but salespeople skip it. That is not a process problem. That is an implementation problem. You fix execution, not architecture.

A change, when the process doesn’t match how your client buys. For example: you designed a five-stage process with two discovery meetings, and clients make the decision after one. The process is too heavy. Or the reverse: you have a three-stage process, and clients need four meetings and three decision makers. The process is too light.

Signals that you need a change, not a fix: conversion keeps falling despite good activity. Clients drop off at a stage that used to work. The market has changed: a new type of client, a new competitor, a new way of buying has appeared.

The rule: fix every quarter. Change every year or two. The process should evolve with the company. What worked with 10 clients a year doesn’t have to work with 40.

Qualification is the moment you decide whether a given contact deserves your selling time. It is the entry gate to the process. And it should sit as early as possible.

In practice, qualification is a few questions the salesperson asks at the start: on the first phone call or in the first minutes of the meeting. Does the client have a problem we can solve. Do they have a budget. Are they ready to make a decision within a reasonable time. Am I talking to the person who can make that decision.

If the answers to those questions don’t fit, the deal is out. Before you spend hours preparing a proposal nobody will buy.

Where in the process: between identification and diagnosis. A contact has appeared (identification). You check whether it fits (qualification). If yes, you move into the discovery call. If not, you say thank you and move on.

Companies that don’t qualify lose the biggest resource in sales: time. Salespeople spend weeks talking to people who will never buy. The pipeline is full of deals that look promising but have no chance of closing. And nobody understands why conversion is so low.

Qualification isn’t being picky. It is respect for your own time and for the time of the client who really needs you.

Don’t design it from the company’s side. Design it from the client’s side.

Most sales processes are designed from the seller’s perspective: what I do at stage one, what I do at stage two. But the client doesn’t think in your stages. The client thinks in their own questions. “Do these people understand my problem?” “Does this solution make sense?” “How much does it cost?” “Can I trust them?” “What happens if it doesn’t work?”

A good client journey answers those questions in a natural order.

First contact: the client wants to know whether it is worth talking. Show that you understand their situation. Don’t talk about yourself.

Discovery call: the client wants to know whether you understand their problem. Ask, listen, don’t present.

Proposal: the client wants to know how you will solve it and how much it costs. Answer both questions at once. Don’t hide the price.

Decision: the client wants to know whether they are making a good decision. Address the risk. Show what happens after the contract is signed. Give them a sense of security.

Every stage of your process should answer the question the client has in their head at that moment. If your process talks about something other than what the client is thinking about, you lose them. Not because they don’t want to buy. Because they don’t feel guided.