Commercial by Design

Design: Commercial Architecture

Early in my building years I was handed a business that was really several companies wearing one parent’s name. It had been stitched together out of a handful of small acquisitions, all-in revenue somewhere around ten million dollars. One built governance software. One distributed corporate communications against two entrenched giants. One sold investor-intelligence services against a much larger data incumbent. The parent was a household name in its world and, quietly, the weaker player in the exact spaces these small businesses now competed in. On the org chart it looked like one company. It was not one company. It was a drawer full of assets somebody had bought and labeled a strategy.

You do not have to be a holding company to have this problem. Any company that has ever made a bolt-on acquisition, or built a second product, or hired a team to chase an adjacent buyer has faced the same fork, and most do not notice they are standing at it. When you add the second thing, are you building one cohesive commercial effort or several competing ones? The failure is quiet and it is common. Each product keeps its own pitch, its own list, its own rep, and the customer, who sees one logo, gets several disconnected companies knocking in sequence. So even if you are a single-product startup today and this story sounds like someone else’s problem, hold onto it, because the day you add the second product is the day it becomes yours.

The tell in our case was embarrassing once you saw it. Four separate reps, from four parts of the company, were all calling the same chief financial officer, the same general counsel, the same investor-relations officer, tripping over each other inside the same accounts. The buyer got four disconnected pitches from one logo, which is the exact opposite of the impression a combined company is supposed to make. We were not losing to the category leaders. We were competing with ourselves, in front of the customer, four times over.

The idea was not wrong, and that is the part worth sitting with. Anyone could see that the pieces were individually good and that a customer who bought all of them would be better served than by any single incumbent. The strategy on the slide was correct: one company, more complete than anyone else in the room. And the correct strategy on the slide changed nothing about what the customer experienced, because it had never been translated into how the company actually operated. A correct idea and a working company are not the same thing, and the distance between them is exactly the work most companies never do.

A commercial idea is not repeatable because it is correct. It becomes repeatable only when the decisions behind it are built into a structure the organization can execute the same way every time, whether or not the people who had the idea are in the room. That structure is what Commercial Architecture means, and it is worth saying plainly what it does. Commercial Architecture converts judgment into organizational capability. It takes what a founder or an operator knows and would otherwise apply case by case, in the room, on instinct, and turns it into choices a company can run without them. It is where Commercial Truth becomes something the organization can actually operate. Most companies never build it, because they believe a strategy is a set of good ideas. It is not. A strategy the organization cannot execute the same way twice is not yet a strategy. It is a collection of ideas waiting for an architecture.

Turning scattered assets into a single, more complete solution is not something a company announces. It is something it constructs, decision by decision, until the customer feels it. Positioning came first: one account, one relationship, every capability behind it, a promise a customer could understand and a single-product incumbent could not easily answer. Then segmentation, which is as much about what a company refuses as what it chases. Then the motion. The relationship manager became a generalist who carried the whole account and pulled in a specialist at the buyer’s real level of interest, so the customer got depth exactly when they wanted it and never again met four strangers from one logo. And underneath the motion, the roles that kept it alive: a farm system that promoted specialists up into relationship managers, so the talent renewed itself and the knowledge of how the whole thing worked stayed inside the company as people came and went. Each of those was a choice, made explicit, and wired into how the company ran on an ordinary day.

There is a piece of the architecture that companies leave out almost every time, and it is finance. Commercial architecture is not only how you sell; it is how you let the customer buy, and that is a commercial decision as much as a financial one. A company that is rigid about how a deal is shaped, because the standard terms protect a margin or flatter a metric, will lose deals it should win to a competitor willing to meet the buyer where they actually are. The architecture has to hold room for commercial creativity, and that means finance is not a downstream approver of deals. It is a co-author of the motion. When we designed how these accounts would be sold, the shape of the deal, the timing of the money, the way risk was carried, was designed with finance in the room, not handed to them afterward to bless.

Designing the buying, not just the selling, exposes something the market will later confirm, which is that there are really two motions, and they are not the same job. In the first, you are displacing an incumbent. The buyer already spends money on this; the budget line item exists. Your work is to prove you are better, to bring down the fear of switching, and to redirect a budget that is already flowing. In the second, there is no incumbent and no line item. Nobody is spending on this yet. The switch risk is lower, because there is nothing to switch from, but the harder job is to help a buyer create a budget that does not exist, to build the internal case that turns a niceto-have into a funded priority. Both are difficult and they are difficult in opposite directions, and a single company will often run both at once, displacing an incumbent in one segment while creating a category in another. An architecture that pretends there is one motion will be wrong for half its market. This is the first place the design starts pointing forward, because which motion a buyer requires is part of what has to fit them, and fit is something only the market can finish teaching.

None of what I just described was a person. It was structure, written down, staffed, and repeatable. It kept running as people joined and left. It took a business worth around ten million dollars to roughly three hundred and fifty million, and it survived any single departure, which is the part that matters most. But here is the thing that took the years to teach, and it is the reason this playbook exists. What got us to ten did not get us to twenty-five. What got us to twenty-five did not get us to fifty. What got us to fifty did not get us to a hundred. At every threshold the architecture that had been right became the architecture that was holding us back, and the company that could see it and rebuild kept climbing while the version of the company that could not stalled at the size of its last good idea. The method is what I pulled out of that climb. Architecture is where it is designed. It is not where it is proven, and it is not where it stops changing.

The reason good commercial ideas so often fail to become companies is not that the ideas are bad or wrong. It is that the logic stays where it was born, in the judgment of the people who had it. A founder who wins on instinct usually has a genuinely correct read of who buys and why and what makes a deal close, but it lives as instinct, an unwritten set of moves made without naming them, and instinct does not transfer. As the company grows, new people arrive without it and improvise their own, so execution varies by person and the results scatter, and everyone blames the new people. The idea was never the constraint. The constraint was that it was never converted into explicit choices, rules, roles, and mechanisms that someone other than its authors could run. The distinction underneath this is exact. Ideas do not scale. Judgment does not scale. People do not scale. Architecture scales. Everything that made the first success possible, the insight, the instinct, the particular people, is precisely what cannot produce the second one on its own. Only what has been converted into architecture repeats.

This is where the word architecture earns its precision, because it is constantly confused with the artifacts that describe it, and the confusion is expensive. Documentation matters, and it is where this has to start. Product does not begin engineering without a spec, and a commercial system should not begin scaling without its own written account of how it wins. So write it down: who the company sells to and who it refuses, why it wins, how a deal moves, who owns which call. That is the necessary first act. But it is only the first act, and here is where most companies stop and pay for it later. A document holds what a person did. It does not hold how they decided. The reasoning that produced the play, the read of the room that told a good operator to bend here and hold firm there, does not live in the steps. It lives in the person who wrote them, and when that person is not standing over the document explaining it, a new hire gets the moves without the meaning and runs them on the wrong situations with great confidence.

So Commercial Architecture is not the paperwork. It is the set of commercial decisions themselves, and the reasoning underneath them, made explicit enough that the company executes them the same way with or without the people who first made them. Capturing that reasoning is real work, and it does not happen through the written word alone. It happens when decisions are explained and not just announced. It happens in recorded working sessions where the thinking is spoken aloud. It happens in role-play, where a new person has to make the call and gets corrected on the reasoning, not just the outcome. It happens when the calls the best operators run are captured and turned into a living library, so the documentation is not a static description of what to do but a record of how it is actually done, and why. Enablement has a real part to play here, because enablement is what takes that content and makes it accessible, shareable, and teachable across a growing team. But enablement distributes the architecture; it does not create it. The architecture is the underlying decisions and the reasoning behind them. Confuse the document with the architecture, and a company will keep polishing artifacts while the thing they were meant to encode still lives in a few people’s heads.

So the law underneath this discipline is simple and unforgiving. Judgment builds the first success. Architecture builds every one after it. Strategy fails when it cannot become architecture. A company rarely dies from a shortage of good ideas. It dies because a good idea never became something other people could run, and so the company stayed the size of the people who had it. The distance between an idea and an operating system, between individual excellence and company capability, is not attitude and it is not effort. It is architecture, and it gets built on purpose or it does not get built at all.

Architecture can make the motion coherent. It cannot make it true. A design is a hypothesis about how buyers will behave, and it cannot confirm itself; that happens in the next discipline, where the design finally meets the thing it was built to predict.