AI · Architecture · Clarity
I'm Saurav Bakshi. I write Architecture Speak on Substack — for the Technology Leaders, CDAIOs and Enterprise Architects now expected to have the AI answer no one wrote down for them. I turn the noise into what actually changes a decision you own.
Latest writing
In the workshop
Personal-capacity builds — the proof points behind the essays. Local-first by default; AI where it earns its place; opinionated about what an enterprise will adopt next.
Advisory
I partner with teams designing enterprise AI architecture — the systems, decisions, and tradeoffs of building on AI, designed for where things are heading, not where they have been.
Designing systems around intelligent, agentic services — where decisioning, automation, and orchestration are model-driven by default rather than bolted onto legacy flows.
Loosely coupled, cloud-native foundations and clean integration patterns — so the right capabilities plug in without the usual technical debt and bottlenecks.
Re-architecting the core stack so it can actually run on AI — clean data contracts, a decisioning layer, and the governance to deploy models safely inside a regulated enterprise.
Building on AI — and want a partner who's done the thinking?
Start a conversationWhy this, why now
Enterprise AI isn't short on information. It's short on information written for you — which leaves technology executives to turn it into a decision, alone.
For the whole of last year, while I was exploring enterprise AI, each attempt left me inundated with engineering frameworks, architectures and tools.
I struggled to find the information that would help CDAIOs and technology leaders make decisions about the use and governance of AI.
AI engineering matters, but enterprise strategy — and the decisions around it — travels well beyond engineering.
The information sits in silos. It is genuinely useful, but pulling it together takes time, and time is what decision-makers have least of.
I call it deciding in fog. You can move, but you cannot see far enough to be sure.
This is the situation most of us face. Finding clarity in it is my anchor and my mission — my attempt to gather, curate and present this knowledge as actionable insight.
Three goals
I strip the noise down to what truly touches the architecture and strategy — in the language CDAIOs and technology leaders actually speak.
Most AI writing explains what something is. The question that matters is what it changes: when a choice is forced, what tradeoff appears, and what breaks if you get it wrong.
Complexity isn’t avoided; it’s structured. I turn a moving, uncertain field into something a technology leader can hold, explain, and act on.
The newsletter
An architect's take on enterprise AI — the systems, decisions, and tradeoffs of building on it. Most weeks, straight to your inbox. No noise.
Get in touch
Working on a cloud, AI, or architecture challenge — or just want to compare notes? Drop me a line.
Send message