Three paths

Three paths. The Readout tells you which one fits.

Most firms sell the same engagement to every client. We work three different ways depending on what the business actually needs. The diagnostic names the path. Then we build it.

What makes this firm different

Most firms do one of these things. Big strategy firms write the deck and hand off implementation. AI boutiques sell their own methodology regardless of fit. Fractional operators execute but can’t diagnose. Solo guru-operators teach frameworks at scale but don’t build custom.

We do the three things that usually require three firms: executive-grade diagnosis, operator-grade strategy, and actual building. In one firm, with one team. The three-path structure is what makes that possible.

Path 1

Optimize

Who it’s for

Operators whose existing architecture is fundamentally sound but running below its ceiling. The business model works. The systems work. The team works. You just aren’t extracting the performance that AI-era tooling and operating practices now make possible.

What it looks like

Targeted work inside the existing architecture. Faster cycles. Leaner delivery. Better margins. Specific AI tooling integrated into specific workflows, not as theater, but because it moves a number that matters. Team practices tuned for the new pace.

Typical outcomes

Meaningful operational capacity unlocked without rebuilding anything structural. Margin improvement. Faster time-to-ship. Founder-dependency reduced.

Typical engagement

Three to six months, mostly alongside your team with focused sprints on specific workflows.

When Optimize is the wrong path

If the business model itself is what’s failing the AI era, Optimize just makes you more efficient at running the wrong architecture. That’s where Re-architect or The Parallel Build come in.

Path 2

Re-architect

Who it’s for

Operators whose business model needs reshaping for the AI era. Same company, same brand, same customers, different operating architecture underneath.

What it looks like

Structural work. How the company makes money, how it delivers, how it’s organized, how it uses tech, all of it on the table. We identify what stays, what changes, and what gets built new. Then we build it alongside your team, in sequence, so the business keeps running while it transforms.

Typical outcomes

A business that’s structurally competitive with AI-native challengers. Lower operational overhead. Defensible category position. Architecture that can absorb the next wave of AI capability without another rebuild.

Typical engagement

Six to twelve months. Real organizational work. Requires executive commitment and a team that can sustain the change while the rebuild is underway.

When Re-architect is the wrong path

If the existing business is structurally incompatible with where the category is going (not “could be adjusted” but “fundamentally wrong shape”), Re-architect becomes expensive surgery on a patient who needs a different intervention. That’s where The Parallel Build comes in.

Path 3

The Parallel Build

Who it’s for

Operators whose existing business is structurally incompatible with the AI-era version of the category. Running it down isn’t the move. Rebuilding in place is too expensive and too slow. Build the next version alongside, instead.

What it looks like

Two businesses, running in parallel for a defined period. The existing business keeps generating revenue and serving current customers. The parallel build is AI-native from day one: different architecture, different economics, often different team shape. Over time, the parallel build grows into the primary business. The original gets sunset, sold, or held as a cash-generating asset.

Typical outcomes

An AI-native business that would have been impossible to build inside the existing one. Market position in the next version of the category, not a retrofit of the last version. Optionality: run both indefinitely or transition on your own timeline.

Typical engagement

Nine to eighteen months, structured in phases. The most capital-intensive of the three paths. Also the one where the economics of the next five years make the biggest difference.

When The Parallel Build is the wrong path

If the existing architecture can be salvaged, building in parallel is over-investment. Cheaper to re-architect. The Readout tells you which.

Why diagnosis first

One-path firms find reasons their clients need the one path they sell. Optimize-only firms always recommend Optimize. Transformation firms always recommend transformation. AI-tooling firms always recommend AI tooling.

We run three paths so the recommendation can actually vary. If you only have a hammer, you can’t honestly tell a client whether they have a nail.

The Two Debts and our diagnostic frame are how we see clearly. They’re what decides the path. Every Readout runs through them.

How an engagement works

After the build: staying current

The build is finite. Staying current isn’t.

AI capability moves fast enough that an AI-native architecture needs regular updating to stay that way. New models change what’s possible. New tooling changes what’s economical. Practices that worked six months ago don’t anymore.

Some clients want an ongoing relationship to handle this. Less than a fractional CTO, more than an annual check-in. An operating partner who keeps the architecture current as the tools underneath keep changing.

Other clients want to build that capacity internally and take it over. Both are fine. The choice happens after the build, based on what your team is set up to handle.

Book The Readout

Two weeks. Five sessions. One honest recommendation.

A written diagnostic with a specific path recommendation. Starts at $10,000.

Book The Readout