You have a commercial system. Sales, marketing, product, customer success – the functions are staffed, the processes run, the quarter closes.
Of course you have a system.
But ask a narrower question. Not “do you have functions?” – what connects them? What decides how a lead becomes a commitment, where a trade-off gets resolved, how meaning survives a handoff from one function to the next? That connecting logic – not the functions, but the logic between them – is the actual system.
And that is the part almost no one has designed.
Stacking functions does not produce a system, any more than stacking organs produces a body. The organs matter, but what makes the body alive is the architecture between them – what connects to what, in what order, carrying what. A commercial system is the same. It is not the functions. It is how value moves across them, where it accumulates, and where it leaks.
And here is the uncomfortable part. That architecture always exists. It is operating in your organisation right now, shaping every handoff and every escalation. The only question is whether anyone chose it.
In most organisations, no one did.
It took shape on its own – through growth, through whoever was in the role at the time, through a hundred local fixes that each made sense and were never revisited. It works well enough not to demand attention. So it never gets any.
That is the difference between architecture and design. Architecture is the structure you have, chosen or not. Design is the act of choosing it deliberately. Every organisation has the first. Far fewer have the second – and the gap between them is where most performance problems quietly live.
You can see it the moment you ask the question honestly. Why does this decision escalate? Often the real answer is not “because it is complex”, but “because no one ever decided where it should sit.” Why is this trade-off fought every time? Because the boundary was never drawn. Why does that handoff keep dropping context? Because nobody designed what has to survive it.
These do not feel like design gaps. They feel like execution friction. But trace each one back and you arrive at the same place: a decision that was never actually made, now running as if it had been.
This is why adding more rarely fixes it. More training, more tooling, more process – each one lands on top of the inherited architecture and is shaped by it. The practice improves.
The whole behaves exactly as before.
The shift is not a project. It is a change in where you look. Stop asking only which functions are underperforming, and start asking which parts of how you operate were ever actually decided – and which you simply inherited and have been maintaining ever since. The first time you ask it honestly, the answer is usually unsettling: far less was designed than it feels like from the inside. Which parts of your commercial system are deliberately designed – and which have emerged implicitly over time?
This question closes a chapter of The Architecture of Commercial Performance, where the thinking behind it is developed in full.
