Insights

Deep thinking on platform engineering, MRO data governance, and building software that lasts.

By Raghu Vishwanath, Managing Partner | August 2026 | 8 min read

In MRO master data, “identity” was always a description.

A line of text, typed by a human. Match the text, find the duplicate. Every deduplication tool ever pointed at an MRO catalog worked this way — and it was always the wrong model, because the description is the one field you cannot trust.

Two moments from a single afternoon make the point.

The Grounding Problem

On the layer between intelligence and the world.

A lone cloud-to-ground lightning bolt striking empty plains under a dark sky, the circuit closing between an enormous charge and the earth — potential finally doing work once it finds its path to ground.
The Open Circuit

Stack the voltage as high as you like — it does no work until it finds a path to ground....

Dark storm clouds gathering over open plains with a low horizon and no lightning, illustrating potential and ground that are not yet connected — the open circuit before the strike.
The Grounding Problem

A model can pass every exam and still mishandle one real file. The bottleneck was never intelligence — it's grounding,...

What Good Looks Like

The standard for master data, before the tools define it for you.

The Layer They Cannot Build

Why MRO master data governance can't be built from inside the incumbents' platforms.

Grooved brain coral — hero image for "The Identity MRO Never Had,"
The Identity MRO Never Had

In MRO master data, "identity" was always a description — the one field you cannot trust. Ark reads the part's...

Enterprise Data Engineering

The unglamorous engineering that makes AI agents work.

Builder's Log

Notes from 30 years of building software that lasts.

The swirling, weathered grain of an ancient twisted tree trunk filling the frame — endurance recorded in the wood of a tree that survived where others did not, a metaphor for staying with a platform long after the industry norm is to move on.
Why We Stay

Most software relationships end at go-live. We built the company around the opposite bet. Fifteen years in, two platforms deep,...

Fill-frame wind-rippled orange desert sand — the drift pattern that returns no matter how often the surface is cleared, a metaphor for master data that decays back after every cleanup.
The Revenue We Refused

The remediation contracts were there for the taking — large, repeatable, predictable. We stopped pitching them. Not because the work...

AI and MRO

What we learned building AI that understands MRO data

The Layers — MRO

Lessons from living inside the MRO data problem

painted hills detail, john day fossil beds national monument, oregon, usa
The Layers Don’t Lie

There's a moment in every long project when you realize you've stopped building what you set out to build. We...

Bluemind Thinking

Vision, philosophy, and the future of platform engineering

the-builder-who-asks-why
The Builder Who Asks Why

The builder who asks "why" isn't a new invention. Leonardo was one. The cathedral masters were. The architects of Uber's...

where-judgment-lives-in-code
Where Judgment Lives in Code

Philosophy is cheap. Everyone claims to ask "why." Every pitch deck mentions vision. Every engineering team says they care about...

assembly line for cars, ford motor company, usa. date: circa 1920s
The Deal That’s Expiring

Depth was your moat. AI is draining it. Your grandfather could learn a trade at eighteen and retire with a...

why-we-ask-why-2
Why We Ask “Why”

Five years ago, we took on an engagement that most product shops would have passed on — building a Super...

Ark Series

Data governance, MRO operations, and building foundations that last

preparing-for-eam-migration
Preparing For EAM Migration

Most CIOs underestimate data's share of migration budget. At least 25% — here's why your foundation determines success.

hidden-cost-of-MRO-duplicate-parts
The Hidden Cost of MRO Duplicate Parts

A major manufacturer discovered they had 50,000+ duplicate parts. Here's what it was costing them — and how they eliminated the problem in 60 days.

why-we-built-ark
Why We Built Ark

After two decades watching Fortune 500 companies waste millions trying to govern dirty data, we built something fundamentally different.