"Add AI to it." It comes up in almost every scoping call now, and it almost never means the same thing twice.
A few years ago it usually meant a search bar running on embeddings, or a field that auto-generated a summary. Useful features. They are also not where the interesting products are any more.
What those products do is act. The AI takes data from one place, makes a decision, and produces an output without a person clicking anything. That is agentic AI, and building it is a different job from adding a feature.
The difference is architectural
Most teams treat AI as a layer to add once the product is built. The product exists, it works, and someone asks whether AI can go into one part of it. Sometimes that lands fine. More often the data model was never designed for it, the user flows do not accommodate it, and the result feels bolted on, because it was.
When AI is going to be core to how a product works, design for it in week 1. Where does the data come from? What decisions will the agent make? What happens when it is wrong, who reviews that, and how do they override it? Those questions need answers before anyone writes a line of code, and they are the same questions that decide where AI lives in your architecture.
The products where AI feels natural are the ones where it was planned from the beginning. The difference is visible the moment you use them.
A healthcare client with 6 hospitals
Their scheduling team was spending around 14 hours every week resolving conflicts. Who is available, which room, which regulation applies, which request takes priority.
