The Operating Record
Commercial systems rarely fail because effort declines. They fail because the assumptions underneath the model change — how customers buy, where value is captured, what a partner will carry — while the commercial system keeps running on the old logic. By the time the numbers turn, the effort is usually still there. The architecture is what's out of date.
A company with no revenue. A category scaling through every stage. A mature business that no longer matched how customers bought. A market that didn't yet exist. Different industries, scales, and stages of a business's life — and different work every time.
What stayed constant was the approach: diagnose what actually changed, then rebuild the commercial system to match it — structure before execution, judgment before achievement.
Build from Zero
A tool that reduced mistakes in cancer treatment already worked — but a working product isn't a business, and there was no company, no market access, and no way in as an outsider. Bootstrapped from nothing into an ONC award-winning product with a marquee federal customer and steady service income, then handed to a new CEO who ran it without the founder — no customers lost.
Read the Operator Case Study: Building the Business Around the Opening →Category Scale
A mobility business rode a fast-growing market through emergence, scale, and maturity — and at each stage the instinct was to push harder on what had just worked, when the real move was recognizing the stage had changed and rebuilding the commercial model rather than throwing more effort behind the old one. Over seven years it grew many times over and took clear category leadership, holding and even improving margin through hypergrowth and a price war built to force a choice between share and margin.
Read the Operator Case Study: Leading a Category Through Every Transition →Enterprise Redesign
Each of these was a mature business whose commercial system no longer fit its reality — the way customers bought had changed, the structure had outgrown its design, or the market no longer matched the model. The hard part was rebuilding a system already carrying real revenue, without dropping that revenue or losing the people who ran it.
It looked like a sales performance problem, but the real issue was structural — the engine was built to close one-off transactions while customers were demanding an end-to-end service relationship. What made the shift hold was redesigning two things together — who owned the customer after the sale, and what people were paid to do — because on the old logic, quarterly targets kept pulling everyone back to the next deal.
Read the Operator Case Study: Rebuilding a Model That No Longer Matched the Buyer →It looked like a discounting problem, but every renewal, mid-contract change, and even expansion had become a fight over price — and the very opacity meant to protect margin was quietly inviting the attack. The fix ran the other way: make the value structure open, and set the price of every future change, expansion included, at the moment of signing — so customers stopped pushing on price, started weighing fit, and chose longer terms on their own.
Read the Operator Case Study: Redesigning Value Capture to Plug Margin Leakage →Running direct sales across dozens of small markets no longer paid for itself, so the whole operation moved to partner-led — the hardest part being the people: moving direct teams to the partners, funding retention to keep the ones who mattered, and handling separations where roles no longer existed. The design that protected the business was two distributors per market, not one — a prime to operate, a secondary as built-in insurance when a prime underperformed.
Read the Operator Case Study: When the Direct Model Stops Paying for Itself →The sales team was doing exactly what its structure asked — plenty of activity and pipeline — yet contribution per rep kept falling, because the business was organized around geography when it was really the type of account that drove the economics. It was rebuilt around that account logic within the same cost budget, and the lasting gain was the new way of planning, which outlived the reorganization itself.
Read the Operator Case Study: Organized for Activity, Not Return →Emerging Categories
In an emerging category, the product may not be the problem. The economics around it are still forming, and the way customers buy it doesn't yet exist. And in a partner-led business, the vendor doesn't own the customer — the partners do — so the category can only be shaped through them, and only when the partner has a real reason to lead it — in profit or in strategic position.
A software line sat inside a much larger partner-led business, and the partners deliberately kept it swappable — keeping the vendor replaceable was their leverage. It became the anchor only when standardizing on the platform was made more profitable for the partner than keeping it swappable — the economics were rebuilt so the partner led the platform, instead of being pushed to sell it.
Read the Operator Case Study: Turning Software Into the Platform Anchor →The AI category was real, but the way to buy it wasn't — and the partners who owned the customers earned their money on cloud, so no amount of extra incentive would move them. What moved them was strategic position, not price: cloud-plus-edge gave the partner a seat as the customer's AI architect that the cloud giants couldn't match — and the whole engine was built to help them claim it.
Read the Operator Case Study: Creating the Buying Motion in an Emerging AI Category →Across all of them — a business with no revenue, a category at scale, a mature model, a market yet to exist — the situation changed but the approach did not: diagnose what actually changed, then rebuild the commercial system to match it. That is the method.
See the Operating Method →