
The AI infrastructure your business runs on
Rubrics, field notes, and positions on what it actually takes to run AI in production. Written for the people who have to own the result.
The build-versus-buy question is the wrong shape for the intelligence layer, because the real decision is which parts you can afford to have someone else own.
A five-dimension rubric to grade how ready your business actually is to run AI in production, and where the layer breaks first.
The gap between a demo that works and a system that runs is not the model. It is the four things nobody scoped.
Orchestration is presented as an architecture and is usually a workaround for a context problem that would be cheaper to solve directly.
Renting your intelligence by the seat is fine until it is the thing your business runs on. Then it is a liability.
Voice agents do not fail on comprehension. They fail on timing, and the budget is smaller than almost every architecture assumes.
Traditional monitoring asks whether the system responded. Agentic systems fail while responding perfectly, which is why most teams find out from a customer.
The phrase gets used to mean fine-tuning, and it almost never should. What most businesses need is context engineering, and it is a different budget.
The highest-return first deployment is almost never the customer-facing one, and the reason has nothing to do with caution.
You would not give a new hire admin credentials on their first day. Most agent deployments do exactly that, and call it an integration.
Token spend is the line item everyone models and the smallest one that matters. The costs that decide the business case sit somewhere else entirely.
Human-in-the-loop is not a safety blanket you add at the end. It is a design decision that determines whether the system saves anyone any time.
Retrieval is not a vector database problem. It is a content problem, and most teams discover that after they have bought the database.
Scoping a first AI system is mostly an exercise in saying no, and the things you refuse decide whether the thing you build ever ships.
An agent that is right most of the time and unpredictable the rest of the time is not a good agent. It is an unmanaged one.