The patterns described in the previous three newsletter, activity that doesn’t produce proportional results, training that fails to embed, inconsistency that persists despite repeated intervention, have something in common. They are not random. They are not the result of an unlucky combination of individuals or an unusually difficult market. They are the predictable output of something already in place. Something that shapes how every opportunity is found, developed, and progressed, whether anyone intended it to or not.
In most organisations, nobody set out to build a system that produces inconsistent results. The system that exists was not designed. It accumulated. It emerged from individual habits, past experience, what got reinforced, what went unchallenged, and what became normal over time. By the time its effects are visible in pipeline data, forecast variance, and leadership fatigue, the system has been operating for years. The question is not whether it exists. It is whether it is working in the organisation’s interest.
Understanding this distinction between a system that happened and a system that was designed, changes how the performance problem is framed. It removes the search for the individual explanation and replaces it with a structural one. Not who is underperforming, but what the system is producing, and why.
A System Already Exists
Sales is already operating as a system in every organisation, regardless of whether that system has been consciously designed. Every team develops embedded patterns in how opportunities are found, how conversations are conducted, how decisions are navigated, and how outcomes are reached. These patterns are not written down. They do not appear in any process document or training manual. But they are consistently applied, and they consistently produce results, predictably good or predictably inconsistent, depending on how they were formed.
These patterns are built over time from individual experience, shaped by short-term outcomes, and reinforced by what gets accepted in the team environment. A salesperson who wins a deal by moving quickly and presenting early learns, from that experience, that speed produces results. A team whose pipeline reviews focus on volume and stage progression learns, from that environment, that those are the things that matter. Neither is following a designed approach. Both are responding rationally to the conditions around them. Over time, those rational responses become the system.
Because these patterns are consistently applied, they produce outcomes that are predictably inconsistent. What varies is not whether a system is present, but what that system was built from and what it is therefore designed to produce. The system that exists in most organisations was not built for consistent, high-quality execution. It was built from habit, preference, and the absence of a deliberate alternative. It is operating exactly as it was formed to operate. The results it produces are not a failure of the system. They are evidence that it is working.
This pattern is not always dramatic. One business had invested in designing a structured sales process specifically designed to ensure that pain, budget, and decision-making were fully understood before any solution was presented. The logic was sound. A demonstration that reflects exactly what the prospect needs is far more compelling than one that showcases what the product can do generally. Under pressure from a prospect wanting to see the product upfront to compare with others, one salesperson agreed to demonstrate before the groundwork had been done. The meeting went well enough. Nobody flagged it. Within a few months, demonstrating early had become what the team did. What had been lost was less visible than what remained. The salesperson was no longer positioned as someone who understood the customer’s situation. They had become one of several options in the market, with the decision left to a prospect who had never been properly guided to understand what they actually needed. The designed standard had been bypassed not through any deliberate decision, but because one exception went unchallenged long enough to become the norm.
Sales is already operating as a system. The only question is whether it has been deliberately designed.
What an Accidental System Produces
The clearest way to see how an accidental system operates is to follow two salespeople through the same opportunity. The company profile is comparable, the level of need appears similar, and the commercial potential is roughly aligned. Both opportunities enter the pipeline in much the same way. From that point, they begin to diverge in ways that will not be visible on any report until the results arrive.
One salesperson takes time at the outset to establish a clear foundation. The initial conversations are structured, but not mechanical. They create a level of comfort and alignment that allows for open discussion rather than guarded responses. The salesperson adapts their approach to the individual they are engaging, recognising differences in style, priorities, and communication preferences, and adjusts accordingly. This is not superficial rapport. It is used to create a more productive environment for the conversation. As trust develops, the customer becomes more willing to share context, challenges, and constraints that would otherwise remain guarded. This creates the conditions for a deeper and more accurate understanding of their situation.
From that point, the conversation moves beyond what is immediately presented. Rather than accepting surface-level problems, the salesperson explores why those challenges exist, what impact they are having, and what happens if they remain unresolved. As the engagement develops, that understanding is expanded. The salesperson builds a broader view of the environment in which the decision will be made, identifying who is involved, how decisions are reached, and what factors will influence the outcome. Assumptions are tested rather than accepted. Budget is explored as part of a wider commercial context, not treated as a simple yes-or-no question. By the time a solution is introduced, it is positioned against clearly understood issues. The proposal is specific rather than generic. Objections, when they arise, are fewer and more manageable, because the underlying concerns were explored earlier in the process.
The second salesperson approaches the same opportunity differently. The early conversations are less structured and more reactive. Rapport is approached uniformly, with little adaptation to the individual being engaged. The discussion is shaped largely by what the customer chooses to share, leaving the conversation led by the prospect rather than deliberately guided. Challenges are acknowledged but not explored in depth, and the interaction remains closer to the surface. As the opportunity progresses, gaps in understanding emerge. Budget is assumed rather than confirmed. The decision-making process is loosely understood, based on what has been stated rather than what has been tested. When a solution is presented, it reflects what has been heard but not necessarily what is required.
Because the conversation has remained at a surface level and followed the customer’s lead, the salesperson has done little to change how the opportunity is being evaluated. Their approach reflects what the customer has likely experienced with other suppliers. Similar questions, responses to stated needs, broadly comparable solutions. The salesperson becomes difficult to distinguish from the other options being considered. Without a clear understanding of the underlying problem and without a differentiated approach to solving it, the conversation shifts towards more transactional measures. Price, features, and commercial terms take on greater importance not because they are the most relevant factors, but because they are the easiest to compare. At this point, the salesperson is no longer shaping the opportunity. They are participating in a process being defined elsewhere.
Both opportunities sit in the pipeline. Both appear to be progressing. Both may be forecast to close. On the surface, they look the same. Underneath, they are fundamentally different. One is grounded in a clear understanding of the customer’s situation, with defined next steps and a structured path to decision. The other is built on partial information, assumptions, and a reliance on the customer to guide the process. Over time, the outcomes reflect these differences. One progresses with increasing certainty. The other becomes harder to predict, close dates shift, confidence erodes, and what initially appeared to be a similar opportunity reveals a very different level of strength.
The difference is not visible at the surface. It sits in how the opportunity was developed.
What a Designed System Produces
A designed system operates from a different starting point. Rather than emerging through individual behaviour, it is deliberately built. It defines what must be achieved at each stage of an engagement, creates shared standards for how those achievements are reached, and puts in place the reinforcement mechanisms that ensure the standard holds over time. The goal is not uniformity of style. It is consistency of outcome. Individual personality, relationship approach, and communication style remain entirely individual. What does not vary is the rigour with which each stage of the engagement is executed.
In a designed system, the behaviours demonstrated by the stronger salesperson in the previous example are not left to individual capability or preference. They are expected, trained, and reinforced as the standard for everyone. Initial conversations are approached with clear intent because the system defines what must be established at the outset. Discovery is conducted consistently, not because every salesperson has the same natural instinct for depth, but because the system has defined what depth means and holds people to it. Commercial understanding is pursued with the same discipline. Budget, decision-making, and stakeholder involvement are understood clearly, not assumed or left vague.
What sustains this consistency is not the process alone. It is the environment in which the process operates. Leadership reinforces the expectations of the system through what it inspects and what it accepts. Conversations are reviewed against how they were conducted, not just whether they progressed. Pipeline stages reflect the achievement of defined outcomes rather than the passage of time. What gets challenged in reviews defines what gets done in the field. Culture shapes what becomes normal. In a designed system, surface-level engagement and poorly developed opportunities are challenged rather than accepted, and over time that standard becomes the environment’s expectation rather than its exception.
The result is not rigidity. It is reliability. Opportunities are developed in a consistent manner across the team. Progression reflects genuine advancement rather than optimism. The pipeline can be trusted because it reflects a shared standard rather than individual interpretation. Performance becomes less dependent on which salesperson happens to be handling an opportunity and more reflective of how the system is operating as a whole. Individual capability still matters. It always will, but it is applied within a structure that ensures it contributes consistently rather than occasionally.
In a designed system, the exception becomes the standard. In an accidental one, the exception is all there is.
What Changes When You See It This Way
Recognising that sales is already operating as a system changes the nature of the problem entirely. The focus moves away from isolated interventions, whether increasing activity, investing in training, restructuring the team, and towards the underlying question of what the system is producing and why. Those interventions are not wrong. They are insufficient on their own, because they address the outputs of the system rather than the system itself. If the system remains unchanged, the same patterns will return regardless of how much effort goes into individual responses.
The question is no longer how to get individuals to perform better. It becomes what is shaping how selling happens in this organisation, and whether that is the result of deliberate design or accumulated habit. Why does increased effort fail to produce consistent progress? Why does training fail to stick? Why does variation continue to reappear even when the right actions appear to have been taken? These are not separate problems requiring separate answers. They are different expressions of the same underlying condition. A system that was never designed to produce anything different.
This is also the point at which the instinct to look harder at individuals begins to lose its logic. The individuals are not the primary variable. They are operating within a system that is shaping their behaviour, their habits, and their sense of what good looks like, whether anyone intended it to or not. Changing what they produce requires changing the conditions they are operating within. And changing those conditions is a design problem, not a people problem.
Conclusion
Every sales organisation already has a system. It is shaping how opportunities are found, how conversations are conducted, how deals are progressed, and what results are produced. The question has never been whether a system exists. It has been whether the system in place is the one the organisation would choose if it were being designed deliberately.
In most cases, the answer is no. The system that exists was not chosen. It was formed from individual preferences, unchallenged habits, and the absence of a deliberately designed alternative. It is producing the results it was always going to produce. Inconsistency is not a flaw in that system. It is the system working as it was formed to work.
Changing those results requires changing what produces them. Not more effort within the same system. Not more training applied to the same environment. A different system. One that was designed to produce something specific and built to sustain it. What that looks like, and what it takes to build it, is what the chapters that follow will address.
Sales is already operating as a system. The only question is whether it has been deliberately designed to produce the results you are getting.
