01Three companies under one logo
The situation
A private equity backed enterprise software company approaching $1 billion in revenue has made three acquisitions in four years. The value-creation plan was underwritten on cross-sell. A platform brand launched eighteen months ago. Growth has slowed to single digits, and cross-sell is not landing.
What everyone thinks the problem is
The platform story isn’t landing. A second agency has been shortlisted to sharpen the narrative.
What the diagnostic surfaces
Three ideal customers, three pricing models, three sales motions. In shared accounts, the three products discount against each other. The company is competing with itself and calling it cross-sell. Each acquired product still runs its own roadmap. Ask the leadership team separately what the company is becoming and three confident, incompatible answers come back. “Platform” exists in the deck and nowhere in the company’s decisions. The choice was never made, so every function made its own.
The decision and its casualties
Leadership chooses the integrated platform, built around the one workflow where the company’s data advantage compounds. The casualties are named out loud. Standalone roadmaps end. One acquired product becomes a feature. Another is put on a divestment path. Sales compensation is rebuilt around platform deals, and a brand the company paid real money for is retired.
What the company now believes
“We are one platform for one workflow, and everything we build, buy and sell exists to compound it.”
What we carry through
The identity becomes a portfolio architecture and a naming logic. The platform story is rebuilt around the chosen workflow, and sales carries one company-level narrative with product stories inheriting beneath it. Pricing collapses to one architecture. M&A criteria shift from revenue-additive to platform-completing, and the investor story is rewritten around retention instead of the sum of three products. Even the sales copilot stops hedging.
The choice was never made. Every function made its own.
02The wrong engine
The situation
A satellite-data company operates a sixty-satellite constellation with daily revisit. Revenue is approaching $200 million. Two years ago it hired a software leadership bench to move up the stack, and the board has been sold an analytics-platform future. The logic is familiar. Software commands better economics and higher multiples.
What everyone thinks the problem is
The platform ambition needs a stronger product narrative. The market still sees a space company.
What the diagnostic surfaces
The executive team is not divided. Everyone agrees on the platform future, which is what makes the case hard. The analytics product churns against horizontal competitors who will always out-build it. Meanwhile the constellation holds pricing power. Renewals concentrate where the constellation is scarce, not where the software is rich. Launch cadence, tasking speed, calibration and the ground network renew at rates the software never touches. The operating advantage took years to build and cannot be replicated by hiring another software team. The founders solved an operating problem competitors still find brutal, and a decade of that knowledge is being treated as legacy rather than as the company’s right to win. The company has been executing, with discipline, an identity borrowed from an industry it is not in. A coherent choice, built on someone else’s source of advantage.
The decision and its casualties
The company is the constellation and its operation. Software exists to raise utilization, deepen exclusivity and speed tasking, not to chase seats. Analytics reaches the market through partners instead of competing with them. The casualties are real. The platform roadmap is cut, the analytics organization is refocused, seat-based pricing is abandoned, and some software revenue is deliberately handed to the partners who can grow it.
What the company now believes
“The future of this market belongs to whoever collects the most valuable observations at the speed customers require, not to whoever ships the most features.”
What we carry through
The company story is rewritten around operational advantage rather than software breadth. Product positioning re-establishes software as an extension of the engine, not an escape from it, and partner and investor narratives inherit the same logic. Capital reallocates from application headcount to capacity, M&A targets shift from app startups to sensor IP, and the numbers finally support the story being told.
A coherent choice, built on the wrong source of advantage.
03The pre-exit fork
The situation
A private equity backed claims technology company is in year four of its hold. It runs a large outsourced claims operation and sells a claims software platform, and the two divisions have grown into rival camps. During the hold, AI collapsed the cost of processing a claim. The board sees a fork. Wind down services and become the software company, or double down on operations and scale the services company. A process is eighteen months away.
What everyone thinks the problem is
“We need to pick a side, and start shaping the exit story around it.”
What the diagnostic surfaces
The interviews confirm the fork runs through the leadership team. The evidence dissolves it. Win and renewal analysis shows that the deals that outperform are neither software nor services. Where field teams improvised a bundle, software doing the processing with named experts accountable for the hard cases, renewals and pricing hold at levels neither division reaches alone. Nobody sells this offer deliberately. It exists only where improvisation put it. The founding story explains why. The founders were adjusters who built tools for their own casework, and the company was the fusion before an org chart split it into divisions. The fork the board is fighting over is an artifact of that org chart, not of the market.
The decision and its casualties
The company is neither camp’s candidate. It becomes the accountable-outcomes company. Software does the processing, experts underwrite the judgment, and customers buy resolved claims at unit economics, not seats and not headcount. The casualties land on both sides of the old argument. Seat-based platform pricing goes. Headcount billing goes. Tool-only customers stop being the target, and the services organization is rebuilt around judgment rather than volume.
What the company now believes
“AI has collapsed the price of processing and raised the price of accountability. In our category, whoever owns accountable outcomes owns the economics.”
What we carry through
The value-creation plan is re-underwritten around the unified offer, because the plan is the identity’s first customer. Pricing moves to outcomes and the metric set follows. M&A shifts from buying headcount or features to buying expertise and data. The company story, the sales narrative and the investor materials describe one company, the one the evidence kept choosing, and the exit narrative gets years to become true instead of months to sound true.
Neither future was right. The evidence had already built a third.