Most companies think they need an AI strategy.
What they actually need is a redesign of how work happens.
That is the first thing worth saying plainly, because the market is already flooded with AI advice that mistakes the symptom for the disease. The symptom is that teams want better outputs, faster decisions, less manual work, and more leverage. The disease is that most companies are illegible to themselves.
Decisions live in meetings. Exceptions live in Slack. Ownership lives in tribal memory. Real process lives in the gap between what the system says is happening and what a few over-relied-on people know is actually happening.
Then leadership buys copilots, launches an AI initiative, and wonders why the output feels impressive and untrustworthy at the same time.
The model is not the first problem.
The company is.
The company is illegible
Most firms cannot see the true flow of work from customer request to internal decision to shipped result.
They do not know where ownership really sits.
They do not know which exceptions are routine and which are dangerous.
They do not know how many decisions made in meetings ever became durable state anywhere else.
They do not know how much of their operating rhythm depends on someone manually reconciling the gap between system truth and reality.
That kind of company can use AI.
It just cannot use AI well.
This is the hidden reason so much enterprise AI still feels like theater. The demonstrations are real. The capabilities are real. The disappointment is real too. Companies are trying to get machine leverage from work that does not yet exist in a machine-readable form.
They want systems that can reason over the business, but the business is scattered across calendars, chats, documents, tickets, spreadsheets, and oral history.
So the AI sees a version of the company.
It just is not the company.
That is why the output often feels slick but thin. The system is producing from partial state. It is reading the visible paperwork of the business while missing the hidden operating logic that experienced people carry in their heads.
That hidden logic is usually the whole game.
It tells you which customer exception matters, which dependency is political rather than technical, which project is marked green but is actually blocked, which system of record is aspirational rather than real, and which executive phrase actually means this has to ship by Friday.
Until that logic becomes explicit, AI does not transform the company.
It mostly reveals how badly the company needs redesign.
The best old idea in management is suddenly useful again
In the 1990s, business process reengineering started with a clean, brutal insight: stop optimizing departments and redesign work end to end.
A company does not create value through isolated functions. It creates value through flows.
Lead to close. Order to cash. Incident to resolution. Product idea to shipped capability. Customer problem to trusted outcome.
That insight was right.
What went wrong was what many companies did with it. Reengineering became famous for cost cutting, org trauma, and executive overreach. Some of that reputation was earned.
But buried inside the wreckage was a point that matters again, maybe more than it did the first time:
If you want step-change performance, you do not automate the mess. You rewrite the mess.
That was true in the age of ERP.
It is even more true in the age of AI.
The difference is that the substrate has changed. Today the modern firm has to become machine-readable. Work has to exist in a form that people, software, and AI can all act on from the same underlying state. Decisions have to survive the meeting where they were made. Exceptions have to be visible. Ownership has to be explicit. The live state of the company cannot remain trapped in side channels and human memory.
That is not a minor upgrade.
It is a redesign of the corporation’s operating grammar.
AI is the great centralizer
AI is often discussed as a productivity tool.
That is too small.
Structurally, AI is a centralizing force.
It concentrates intelligence, interface power, and workflow leverage into fewer layers. One good AI system can become the front door to search, writing, planning, coding, support, and eventually action. Whoever controls the model, the memory, and the workflow layer starts shaping what the organization sees and how the organization decides.
Inside a company, AI centralizes:
knowledge access
workflow routing
first-draft creation
management visibility
decision support
operating leverage
That is not a moral judgment. It is a structural one.
The best AI systems become the nervous system of the firm very quickly.
If the company is machine-readable, that is powerful.
If it is not, you get a polished hallucination machine sitting on top of operational confusion.
Crypto is the great decentralizer
Crypto is often described in the worst possible language.
Too much of the public story is still trapped in speculation, ideology, or tourist-grade futurism.
The serious story is simpler.
Crypto is a decentralizing force because it changes where trust lives.
It pushes ownership, settlement, coordination, and verification outward into networks rather than private ledgers controlled by single firms. It creates shared state, programmable assets, and verifiable execution across parties that do not need one institution to own the entire system of record.
In business terms, that matters because crypto is not mainly about coins. It is about trust architecture.
It changes how institutions can think about:
settlement
asset control
identity
shared state
multi-party coordination
provenance and auditability
That is why AI and crypto matter together.
AI centralizes intelligence.
Crypto decentralizes trust.
The next generation of institutions will need both.
Why these two forces belong in the same conversation
Most people write about AI and crypto separately.
That misses the actual story.
The future enterprise will have to use centralized intelligence on top of decentralized systems.
It will need AI to interpret complexity, route work, draft decisions, surface risk, and shorten cycles.
It will need decentralized infrastructure to verify, settle, coordinate, and preserve agency across networks.
One gives the firm a stronger intelligence layer.
The other gives it a more programmable trust layer.
Without AI, decentralized systems remain too complex for most institutions to use well.
Without decentralized trust, AI-era operating systems risk concentrating too much power into too few interfaces and platforms.
One solves the intelligence bottleneck.
The other constrains the trust bottleneck.
That is why I think these are the two most important technology forces of this era.
They solve opposite problems.
And serious companies now have to design for both.
Why I am writing this book
I am writing this because I sit at the intersection where AI and crypto stop being abstractions and become operating realities.
Most books about AI in business are written by one of three people: software vendors, consultants, or futurists who do not have to ship under pressure.
Most books about crypto are written by traders, protocol evangelists, or ideological decentralization purists.
That leaves a gap.
The interesting story is not what these technologies promise in theory.
The interesting story is what happens when they hit a real company with customers, deadlines, compliance obligations, product sprawl, handoffs, outages, and revenue targets.
That is where new operating models are either built or exposed.
I work close to that seam.
I see how AI changes the internal operating system of a firm. I see how crypto changes the external trust architecture that firm plugs into. And I see how quickly both of those forces expose whether the company actually understands its own work.
That is the book I want to write.
Not a book about prompts.
Not a book about hype.
A book about how companies redesign themselves so AI can become useful, and so decentralized systems can become usable.
The method: REWIRE
The framework I am building for the book is called REWIRE.
It is a modern reengineering method for AI-native firms:
Reframe around value streams
Externalize tacit work
Wire the system of record
Insert AI at decision edges
Reorganize around flows
Enterprise harden the new system
The point is simple.
Before you ask AI to run across the company, the company has to become legible enough for AI to read.
Before you let agents act, you need explicit state, explicit ownership, explicit permissions, and explicit fallback paths.
Before you celebrate automation, you need to know whether you are automating signal or automating noise.
That is the difference between transformation and theater.
What the next generation firm will look like
The firms that win this transition will not be the ones with the most AI subscriptions.
They will be the ones that learn how to centralize intelligence without centralizing fragility.
They will be the ones that learn how to decentralize trust without decentralizing accountability.
They will be the ones that make work machine-readable.
They will be the ones that treat hardening as part of the commercial product, not as cleanup after the demo.
They will be the ones that can answer basic questions from system state instead of from a meeting.
What is blocked this week.
Which accounts are at risk.
Which decisions were made.
Which dependencies are real.
Which workflows are healthy.
Which parts of the company still rely on memory instead of machinery.
That is where this is going.
The future enterprise will not just use AI.
It will be redesigned around the conditions that make AI useful.
And it will increasingly operate in a world where trust, value, and verification move through more decentralized rails.
That is why this is not just a story about tooling.
It is a story about the next institutional form.
The line I keep coming back to
Most companies do not have an AI problem.
They have an illegibility problem.
Until they fix that, they will keep asking machines to understand a business that even they cannot fully read.
If this idea resonates, subscribe.
I am developing this into a book on how to make AI actually useful in corporations by redesigning the work itself. In future essays, I will dig into the REWIRE framework, the relationship between AI and crypto, and what the machine-readable company looks like in practice.

Love this: “What the next generation firm will look like
The firms that win this transition will not be the ones with the most AI subscriptions.
They will be the ones that learn how to centralize intelligence without centralizing fragility.”
Brilliant! I'll read your book - and might use REWIRE for my client work with https://challenger-house.com/ as it neatly 'acronymitises' the work that needs to be done inside orgs.