Sales system

The pipeline stage shows what we've done. The buying process shows what has actually changed on the customer's side.

This is the full picture of how to build a sales system that stays with the company. Not a method you buy off the shelf. A way of managing deals by where the customer is in their decision, not by how much activity the salesperson has logged.

I'm writing this for the owner, because a sales system isn't built in the sales department. It comes from the company's strategy, its culture and the way it wants to create value for customers. How salespeople then pick opportunities, run deals, handle price and treat customers is the leadership team's responsibility.
Part 1

Why your pipeline stages lie

The two processes don't line up

Your sales process has a few visible stages. Behind each one are steps the customer has to get through inside their own company before they can move on. You can't see most of them in your CRM.

In your system, the deal is past the presentation, past the proposal, maybe even in negotiation. Meanwhile the customer hasn't yet agreed on the problem, on who's involved in the decision, on the criteria, on the budget or on how it gets approved.

One stage of yours

  1. Proposal sent

What the customer has to get through behind it

  1. Agree the problem is worth solving
  2. Get everyone who has to decide to the table
  3. Agree on the selection criteria
  4. Defend it to their leadership
  5. Get comfortable with the risk and reach internal agreement

That's how much work can sit behind a single stage in your CRM. So you can't map stages to steps one for one; they don't line up.

Two sides of the table

The pipeline stage shows where we've logged the deal. What matters is where the customer is in their decision. That's why your CRM says “proposal sent” while the customer still doesn't know how they'll choose, who has to sign off, or whether they've even agreed internally on a solution.

When those two realities don't match, the salesperson pushes for the next step before the customer is ready. That's exactly where you lose time, trust and margin.

Knowing the stage isn't enough. You need to know the status.

To manage a deal, knowing its stage isn't enough. You have to read five things at once, as a chain in which each one explains the one before it, not as five separate warning lights.

Customer status

Where they are in their decision.

Buying process status

What their company still has to resolve.

Deal status

What's confirmed, what's blocking progress, and what the risks are.

Salesperson status

What they know, what they only assume, what they can do in this situation and where they need support.

Sales system status

Whether the company's strategy, rules, management and culture produce the behaviour we expect from salespeople, or get in its way.

The last question is the most important, and the owner is the only one who asks it: why is the salesperson acting this way, and what's driving it?

What's settled on the customer's side? Where is agreement still missing? Who decides? What don't we know yet? What do we only have second-hand? What is the salesperson just assuming? And what has to happen for the next step to make sense?

Part 2

What the system is built around

Not around the salesperson. Around the customer.

A sales system isn't built around what the salesperson wants to do. It's built around what the customer has to do to be able to decide and buy.

Activity isn't progress. A deal moves forward only when something demonstrably changes on the customer's side.

What the salesperson must have confirmed

Only then do checkpoints make sense: what the salesperson must have confirmed before the next step, before the proposal, before price, before negotiation, and before marking a deal ready to close.

A good system doesn't treat activity as evidence of progress. It shows the salesperson what evidence has to exist before the deal can move on.

Customer insight

The system rests on a deep understanding of the customer's buying process, where it stands right now, and what each stakeholder needs to resolve before they can move towards a decision.

The same sentence means a different need, concern or risk to different people. A salesperson who guesses what the customer is thinking gets it wrong cheaply at the first meeting and expensively when price comes up. Their job is to find out what each of those people needs to know, see or resolve to move forward.

Part 3

Who needs to know what

Salesperson

Even a well-designed process isn't enough if the salesperson can't read the reality of the deal.

They have to tell fact from assumption, a question from an answer, activity from real movement on the customer's side, and pressure to close from the customer's readiness to decide.

Sales manager

A manager's job isn't just to check when a deal will close. They have to see why it's stuck, what's still missing on the customer's side, and what the salesperson needs to handle better.

That turns the pipeline review from chasing dates into managing decisions and developing salespeople.

Owner and leadership team

The owner doesn't need to sell better than their salespeople. They need to build a system in which their salespeople can sell the right way.

That means being clear about which customers the company wants to win, what value it wants to create for them, where it wants to win, what behaviour it expects from salespeople, and what their managers judge them on.

A salesperson doesn't decide who the company's customers are, what behaviour it rewards, which deals to turn down or who's allowed to discount. That's company design, not their failure.

When the same problem keeps coming up across deals, it's no longer one person's problem. It's a signal that the cause lies higher up: in management, the rules, the culture, the sales process or the company's strategy itself.

When people keep making the same bad decision, I don't start by asking what's wrong with the people. I start by asking what in the company's system makes that decision the logical one.

Part 4

What stays with the company

The sales system is where the company's strategy and culture meet the customer. That's where you find out whether they exist at all.

Strategy translated into everyday decisions

It defines which customers we want to win, which problems we want to solve for them, what value we want to create, which deals we take and which we don't, where we invest our time, how we handle price, and where we'd rather say no.

Strategy sets where and how the company wants to win. Culture and management decide how people behave when the pressure for results arrives. The sales system has to carry both all the way to the customer.

So sales is the last mile, where you find out whether the company's strategy really works, and also the place where the customer's reality has to flow back into the strategy.

A system that stays with the company

A written, binding system that tells the salesperson where the customer is in their buying process, what the deal's status is, what they have and haven't confirmed, and what has to happen on the customer's side before the next step, the proposal, the price and the signature.

It also sets how the manager runs deals, what the leadership team tracks, who decides on discounts, where deals break down and which mistakes keep repeating in the team.

How the system learns

Won and lost deals both feed back into the system. Not as impressions, but as concrete findings: what happened on the customer's side, what the salesperson did, and what result it produced.

That way it's not just one salesperson who gets better. The sales system itself gets better.

Where the gap comes from

Why the two processes don't line up

The customer has their own path. Inside their company they have to

  • recognise the problem is worth solving
  • get the right people to the table
  • agree the criteria
  • and defend the decision.

There are tensions between those people that have nothing to do with you. A sales system can only be built on that path. Too often it's the other way round: stages from your own side of the table, and discounts to bridge the gap.

What it looks like in the company:

  • Every salesperson sells their own way. You have the training and the CRM, and margin doesn't move.
  • You close the biggest deals yourself. And most deals aren't lost to a competitor. They're lost to no decision.
  • You can't say which customers make you money and which cost you money.

Back to the problems →

Customer stakeholders

You never sell to just one person

Operations, engineering, finance, procurement. Each of them says something other than what they really want. The maintenance manager says: we need a reliable supplier. What they want: no call from the boss on Saturday asking why the line is down. The first can be compared on a price list. The second can't.

A sales system is built on a deep understanding of the customer's buying process, and of what each stakeholder needs to resolve to move towards a decision. It also sets what the salesperson must have confirmed before the proposal, before price, and before the next step.

When the same problem keeps coming back across deals, it's no longer one person's problem. That's when the owner needs to know what in the sales system is producing that behaviour: the rules, the management, or the strategy itself.

Back to Two sides of the table →

Want to know what in your sales system is holding growth back, and whether the cause is in the strategy, the management, the team or sales itself?