I meet with a sales leader and ask about his sales process. He opens his CRM and talks through the clearly defined stages running from lead generation through qualification, discovery, proposal, negotiation and close. Each opportunity has an owner, a value, an expected close date and a probability attached to it. To many, the business appears to have a structured way of selling.
Then the conversation moves from where opportunities sit to what actually happens inside those stages. What does a salesperson need to achieve during discovery? What needs to be understood before an opportunity is genuinely qualified? What must be true before a proposal should be produced? The answers are usually much less certain.
Ask several salespeople in the same team and the gap becomes clearer. One describes discovery as understanding what the customer is looking for. Another talks about identifying their challenges and presenting an appropriate solution. A third describes a much deeper conversation involving the underlying problem, its impact, commercial parameters, stakeholders, decision-making and an agreed reason to progress. All three are working within the same CRM stage called Discovery, but they are not following the same sales process.
This is one of the most common misunderstandings I encounter when discussing sales performance. An organisation believes it has a sales process because the stages of an opportunity have been defined. What it often has is a way of categorising opportunities as they move through the pipeline.
Those stages are useful, but they are just not the sales process.
Sales Stages Are Not a Sales Process
Sales stages answer an important question. They tell us where an opportunity currently sits in its progression through the pipeline.
That structure is necessary for managing a pipeline, but the labels themselves tell us very little about how those opportunities have been developed, or anything else about them for that matter. An opportunity can be moved into Proposal because the customer asked, “Can you send me a proposal?”, or because the salesperson has gone through a rigorous qualification process establishing a compelling reason for change, understood the commercial implications, mapped the decision process, determined investment parameters, and agreed the next step with the customer.
The CRM may treat those opportunities as equivalent. In practice, they are fundamentally different. One has progressed because quality interactions have been undertaken with the customer, while the other has progressed simply because somebody changed the stage in the CRM.
This distinction matters because sales stages can create an appearance of structure that does not exist underneath them. The pipeline looks orderly. Opportunities move from left to right, percentages increase and forecast values accumulate, but the quality of what has happened between those points may vary enormously.
A sales stage tells you where the opportunity is. It does not tell you what has happened to get it there.
A sales process needs to go further. It defines the activities, steps and outcomes required within and between those stages to progress an opportunity effectively towards a buying decision. Instead of simply identifying that an opportunity is in Discovery, it defines what needs to happen during Discovery and what must have been achieved before the opportunity should move on.
That distinction can sound semantic until you see what it produces in practice. If the organisation defines the stages but leaves everything underneath them open to interpretation, each salesperson has to fill in the gaps. They draw on previous jobs, past training, personal experience, instinct and whatever seems to work for them.
Over time, each salesperson develops their own version of the sales process. The stages remain consistent across the team, but the selling underneath them does not. The organisation has standardised the labels without standardising the substance. Variation exists, creating variable results.
What Actually Sits Beneath a Stage
The Discovery stage provides a useful example because almost every sales organisation has some version of it. Calling a stage Discovery creates an expectation that the salesperson will develop an understanding of the customer and their situation. It does not define what has to be learned, how deeply it needs to be understood, how the process should work, or what sufficient discovery looks like.
The first layer underneath the stage therefore must be its objective. What is this part of the sales engagement intended to achieve? If that objective is unclear, there is no common reference point against which the quality of the salesperson’s work can be judged.
A discovery objective might require the salesperson to develop sufficient understanding of the customer’s situation, reasons for change and ability to progress to determine whether there is a genuine opportunity worth pursuing. That immediately creates more clarity than the word Discovery alone. It still does not tell the salesperson what needs to happen to achieve it.
That is where the sales process becomes important. To achieve the objective of Discovery, the salesperson may need to establish how the conversation will work at the outset, create the conditions for an open discussion, use deeper questioning to move beyond the customer’s surface issues into the underlying reasons and impact, establish the investment parameters, understand how the decision will be made and agree what should happen next. These are the parts of the sales process that give Discovery substance. They define the work required rather than simply naming the stage in which that work supposedly happens.
Some parts of that process will contain further structure of their own. Exploring the customer’s situation may involve moving from the initial issue into its underlying causes and consequences, while understanding decision-making may involve identifying who is involved, their influence, the criteria they will use, how approval works and when a decision needs to be made. The sales process can therefore contain smaller processes within it, each contributing to the objective of the wider stage.
This structure is deliberate. A well-designed sales process gives the salesperson a clear path through the conversation, with each part building on what has been established before it. The salesperson guides the discussion, completes the work required at each point and only progresses when there is sufficient reason to do so. Customers may introduce information earlier than expected, but that does not require the salesperson to abandon the structure or allow the conversation to dictate the process.
That structure should not be confused with scripting. The process defines what needs to happen and provides a logical progression for achieving it. The salesperson still determines how to ask the questions, respond to what they hear, explore an issue more deeply and adapt their communication to the person in front of them. The sequence provides discipline, while the human interaction provides the flexibility.
Where Sales Methodology Fits
Once the process is clear, the salesperson also needs to know how to approach the work required within it. This is where sales methodology becomes important.
A methodology provides principles, frameworks and structured approaches that help salespeople sell effectively. Sandler, SPIN and Challenger are familiar examples, although each approaches selling differently and they do not all cover the same ground. An organisation may also develop its own methodology based on the way it wants customers to be engaged.
A methodology can itself contain a defined process and sequence. Within Sandler, for example, there are defined components covering areas such as bonding and rapport, up-front contracts, pain, investment and decision-making. Within an individual component there may be further approaches that guide how the salesperson works, such as moving from a surface problem into the underlying reasons and then its impact.
A methodology and an organisation’s sales process can therefore overlap significantly. The distinction is that the methodology provides a structured approach to selling, while the organisation’s sales process must define how selling actually works within its particular customer journey, market, commercial model and internal ways of working. A methodology may provide much of that process, but it does not automatically become the organisation’s sales process simply because people have been trained in it.
For example, a methodology may provide a structured progression for establishing how a meeting will work, uncovering the customer’s underlying problems, discussing investment, understanding decision-making and agreeing what happens next. Those steps may become part of the organisation’s sales process, but they still need to be deliberately integrated with its particular sales stages, customer interactions, qualification requirements and ways of working.
Nor does methodology necessarily map neatly to individual CRM stages. Building trust, agreeing how a meeting will work, exploring problems and confirming decision-making may happen across several interactions. In some organisations, the methodology will be integrated into an existing sales process. In others, the sales process itself may need to be redesigned around the methodology. What matters is that the two are deliberately connected rather than the methodology simply being taught alongside the way the organisation already sells.
This is where one of the most common failures in sales development occurs. An organisation trains people in a methodology but never determines exactly how it should operate within its market, customers, CRM stages, qualification requirements, commercial model and existing ways of working, nor redesigns its processes to accommodate it. People may have learned how to uncover problems more deeply, establish investment parameters, understand decision-making and secure clear next steps, but nobody has defined where those approaches belong, what good execution looks like or what needs to be achieved before an opportunity should progress.
Without that integration, the methodology remains something people have been trained in rather than the way the organisation sells. It sits alongside the organisation’s sales process instead of becoming part of its design. A Selling System closes that gap by deliberately integrating the methodology into the organisation’s unique way of selling, then connecting it to the behaviours, playbooks, capability, leadership, tools and reinforcement required to make it executable.
The value of those layers becomes most visible in a real customer conversation. A stage establishes where the opportunity sits, its objective defines what needs to be achieved, and the organisation’s sales process establishes what needs to happen. The methodology contributes the processes, principles and structured approaches that help the salesperson execute that work effectively. The playbook then turns that structure into practical options the salesperson can actually use.
Much like a sports playbook gives players practised options for situations they are likely to encounter, a sales playbook captures the questions, techniques, conversation approaches, third-party stories, objection strategies and examples relevant to the situations the team actually faces. If a customer gives a surface-level answer, challenges the price or is stalling, the salesperson has proven approaches to draw from rather than inventing a response in the moment. The structure becomes useful precisely when the salesperson needs it.
This is particularly valuable because much of what makes experienced salespeople effective has been accumulated over years. They develop a repertoire of questions, stories, techniques and responses through situations that less experienced people simply have not encountered yet. A well-designed playbook captures the best of that collective experience and makes it available across the team, while still leaving each salesperson to judge what to use, when to use it and how to express it with the customer in front of them.
Defining What Good Looks Like
Even with a process and methodology in place, another source of variation remains. Two salespeople can understand what they are expected to achieve and know the methodology they have been trained to use but execute both to very different standards. The organisation therefore needs another level of clarity about the behaviours that represent good execution.
Those behaviours need to be observable. Telling someone to “build trust” or “conduct strong discovery” provides little guidance because people can interpret those expectations differently. A more useful standard describes what a manager, coach or salesperson would actually expect to see happening.
During discovery, that might mean the salesperson does not accept the first problem stated without further exploration. They ask relevant follow-up questions, test assumptions, establish the impact of the issue and resist moving prematurely into presenting a solution. They confirm their understanding and establish whether the customer has a sufficient reason to continue.
The objective, process, methodology and behaviours now perform different but connected roles. The objective establishes what must be achieved, the process defines what needs to happen, and the methodology provides structured approaches for doing it well. The behaviours make the required standard visible in the way the salesperson actually executes.
This visibility matters because a standard that cannot be observed is difficult to coach, review or improve. A manager can give much more useful feedback on whether a salesperson explored the impact of a problem deeply enough than on whether they simply “did good discovery”. The same standard can then be used in coaching, opportunity reviews, call analysis and practice, creating a common understanding of what good selling looks like across the team.
The Difference Hiding Inside the Pipeline
Consider two opportunities sitting at the Proposal stage. Both have similar values, similar expected close dates and comparable probabilities recorded in the CRM. From a pipeline perspective, they may look to have progressed to the same level.
In the first opportunity, the salesperson has established why the customer is considering change and explored the underlying issues in enough depth to understand what is really driving the decision. The impact is understood, the commercial position has been discussed, the relevant stakeholders are known, and the decision process has been explored. The proposal is being produced because both parties have agreed there is sufficient reason to move forward.
In the second opportunity, the salesperson has had several positive conversations and understands broadly what the customer wants. The customer has expressed interest, asked about price and requested a proposal. Budget has been assumed from the apparent size of the business, the wider stakeholder group has not been explored, and the salesperson believes their main contact will “get it signed off”.
Both salespeople have followed the same visible progression. Both have moved from Discovery to Proposal. If the organisation’s process exists primarily as CRM stages, neither salesperson has necessarily done anything wrong.
The difference sits underneath the stage. One opportunity has progressed because detailed and valuable work has been completed. The other has progressed because the salesperson has interpreted the customer’s interest as sufficient evidence to move forward.
This is where apparently structured pipelines become unreliable. The problem is not necessarily that salespeople are deliberately ignoring the process. The process may never have defined the standard they were expected to meet.
Progression Needs a Standard
A well-designed sales process needs to distinguish between completing activity and achieving an outcome. Having a discovery meeting is an activity. Completing Discovery should mean something more.
The stage objective defines what that part of the engagement is intended to achieve. Exit criteria provide the evidence that enough has been achieved to justify progression. The two are connected, but they perform different roles.
A Discovery objective might be to establish sufficient understanding and qualification to determine whether there is a genuine opportunity worth pursuing. The exit criteria might require clarity and detail around the underlying problem, its impact, commercial parameters, decision-making, stakeholder involvement and an agreed reason to progress. The exact requirements will vary by organisation, market and type of sale.
The important point here is that progression is no longer determined solely by how the salesperson feels about the opportunity. There is a benchmark against which judgement can be made. Professional judgement remains important, but it operates inside a clearer set of expectations.
Without that standard, terms such as “qualified”, “strong opportunity” and “likely to close” can mean different things depending on who is using them. One salesperson may need substantial evidence before describing an opportunity as qualified, while another may reach the same conclusion because the customer has shown interest. Both then enter the same pipeline data.
When progression is based largely on individual interpretation, the pipeline becomes a collection of opinions rather than evidence of genuine advancement.
This also changes the quality of leadership conversations. Instead of asking only whether an opportunity has moved or when it will close, a manager can explore what has actually been established and what remains unknown. The conversation moves from confidence in the salesperson’s prediction towards confidence in the work that sits underneath it, and therefore confidence in the pipeline’s ability to predict deal closure.
The False Comfort of CRM Control
Modern CRM systems make it possible to create considerable structure around a pipeline. Required fields can be added, probabilities assigned automatically, activities recorded and dashboards built to show almost every aspect of opportunity movement. This visibility is useful, but it can also create a false sense that the sales process itself is under control.
A dashboard can show that an opportunity has been in Discovery for 21 days. It cannot tell you whether the salesperson has conducted good discovery unless the organisation has first defined what good discovery means and created a way of making the relevant information visible. Technology can record the standard, but it cannot invent it.
The same applies to qualification. A CRM field asking whether budget has been confirmed may produce a neat ‘tick in the box’. For one salesperson, that might mean they asked whether budget existed and the customer said yes. For another, it might mean they have discussed the likely investment, established where the funding will come from and confirmed who has authority to approve it.
The data appears consistent because both fields contain the same answer. The execution underneath the data is not. Without a common definition, the CRM simply gives different interpretations the same label.
This is why the CRM should support the sales process rather than be mistaken for it. Once the organisation has defined what needs to happen and what good looks like, technology can provide visibility, prompt required actions and support appropriate governance. Designing the CRM first reverses that logic.
The boxes across the top of the screen are therefore only the visible surface. The real work sits underneath them.
“Are We Turning Salespeople Into Robots?”
The more clearly an organisation defines its sales process, the more likely a common concern is to surface. Experienced salespeople are being employed because they know how to sell, so why prescribe how they should conduct every customer conversation? Taken too far, structure can appear to remove the very judgement and individuality that make strong salespeople effective.
That concern is only legitimate if the intention is to make everybody sell identically. However, that’s not the purpose of a well-designed Selling System. The goal is not identical selling. It is a consistently high standard of selling.
Two salespeople working within the same process should still sound different. They will use different language, build relationships differently, respond to body language differently and vary the pace of the conversation according to the person sitting opposite them.
They should also be able to follow and respond to what they hear. A customer may make an unexpected comment that deserves ten minutes of exploration, even though it was not part of the anticipated conversation. Another customer may answer the same issue clearly in thirty seconds and make further questioning unnecessary.
That is where human judgement sits. Curiosity, empathy, timing, communication style, commercial judgement and the ability to recognise what matters in the moment cannot be reduced to a flowchart. Nor should they be.
What should not depend entirely on personal preference is whether the salesperson establishes the things the organisation knows are critical to qualifying and developing a strong opportunity. Understanding the customer’s underlying problem should not be optional because one salesperson prefers to present early. Establishing how a decision will be made should not depend on whether someone happens to remember to ask.
The system therefore creates consistency in what matters while preserving freedom in how it is expressed. It defines the outcomes, process and standards that should hold across the team, then allows salespeople to exercise judgement within them. Flexibility exists within the process, not instead of it.
In fact, structure can accelerate expertise. A musician does not become more expressive by ignoring scales, timing and technique. Those foundations create a framework within which skill, judgement and eventually improvisation can develop. Selling is similar. When salespeople work within a common process, they can practise specific parts of it, receive meaningful coaching, compare approaches and progressively improve how they execute them.
Consider deep discovery. Without a common structure, one salesperson may ask a handful of questions before presenting, another may explore the problem extensively but avoid discussing investment, while another may never establish how the customer will make a decision. Each develops their own route through the conversation, and experience simply reinforces that route, whether it is effective or not.
A designed process gives them something better to develop against. The salesperson can become more skilled at moving from surface issues to underlying causes and impact, more confident discussing investment, more effective at understanding decision-making and better at gaining commitment to the next step. Managers can coach those skills against a common standard, and salespeople can practise and refine them rather than simply accumulating more years of doing things their own way.
Over time, the process becomes less something the salesperson consciously follows and more the foundation from which they sell. Expertise does not come from removing the structure. It comes from becoming increasingly skilled within it.
This can make the conversation less robotic rather than more. A salesperson who understands the underlying structure does not need to spend the meeting mentally searching for what they should do next. They can place more attention on the customer, listen more closely, notice hesitation, explore something unexpected and adapt their language without losing sight of what the conversation needs to achieve.
The structure sits underneath the interaction rather than dominating it. It gives professional judgement somewhere useful to operate.
The purpose of a Selling System is not to script the conversation. It is to provide enough structure that the salesperson can concentrate on having a better one.
Process Is Still Not the System
At this point, an organisation may have moved considerably beyond the stages in its CRM. It has defined what each stage needs to achieve, built a genuine sales process underneath those stages, selected or developed a methodology, established key behaviours and created practical guidance to help people execute. That is a substantial improvement.
It is still possible for execution to vary. A salesperson may understand the process but lack the capability to apply it under pressure. A manager may agree with the standard but focus pipeline reviews almost entirely on revenue, activity and close dates.
The process may be well designed while the CRM makes it difficult to follow. Training may introduce the methodology while subsequent coaching rarely refers to it. New people may be shown the documented approach but quickly observe that experienced colleagues work differently and nothing happens when they do.
Those are no longer process-design questions. They are questions about the wider system in which the process operates. Defining the intended way of selling and creating the conditions in which it is consistently executed are related, but they are not the same task.
This is where the distinction between process and Selling System becomes important. The process defines the work required to develop an opportunity effectively. The Selling System connects that process to the capability, leadership, culture and tools required to make it work consistently.
Execution is what we eventually observe in the field. It is the conversation with the customer, the way an opportunity is qualified, the quality of the questions asked, the decision process uncovered, the judgement applied and the next step agreed. It is where the five elements of the Selling System come together and where everything that has been designed either shows up or does not.
That is why a well-documented process can still coexist with inconsistent sales performance. Process is essential, but it is only one part of the system. Salespeople need the capability to execute it, leadership needs to coach and hold people accountable to it, tools need to enable it, and the culture needs to reinforce it as the accepted way of selling. Consistent execution occurs when those elements work together rather than independently.
Conclusion
The next time a sales leader says, “We have a sales process”, look beneath the stages. If the process consists primarily of labels such as Qualification, Discovery, Proposal and Close, the organisation has defined where opportunities can sit. It has not necessarily defined how they should be developed.
A genuine sales process goes deeper. It establishes what needs to happen within and between those stages, what each stage needs to achieve and what must be true before progression is justified. Methodology, expected behaviours and practical playbook guidance then give salespeople structured ways of executing that process well.
None of this requires salespeople to become identical. The organisation can standardise the parts of selling that materially affect opportunity quality while preserving the judgement, creativity and human interaction that strong selling requires. Consistency and individuality can coexist when the distinction between them is deliberately designed.
But process remains only part of the answer. The process can define the intended way of selling, yet whether that intention becomes consistent execution depends on the wider system around it: the capability of the people, the leadership they receive, the tools that enable them and the culture that reinforces the expected way of selling. That is the point at which process becomes part of something larger.
Sales stages tell us where the opportunity is. The sales process defines what needs to happen. The Selling System creates the conditions for it to happen consistently.