Seven Signs a Product Is Just AI Bolted On
How to spot AI bolted on to old software before you buy. Seven concrete signs a product wrapped a model instead of building AI-native around it.
Most "AI-powered" products are old software with a model stapled to the side. You can tell in about ten minutes if you know where to look. The AI does not touch the core workflow. It lives in a panel off to the right, generating text you copy and paste back into the real product. That is bolted on. AI-native means the model is load-bearing. Remove it and the product stops working. Here are the seven signs that separate the two.
The AI lives in a sidebar
Open the product. Where is the AI? If it is a chat panel bolted to the edge of a screen that worked fine before, you have your answer. Native products do not have an "AI section." The intelligence is spread through every action because every action was rebuilt to assume a model is present. A sidebar means someone shipped the old app first and added AI as a feature request later. That is the tell I look for before any other.
You copy and paste to use it
Watch the actual motion of using the feature. If the loop is: ask the AI, read the output, copy it, paste it into the form that already existed, the AI is a bystander. It is not doing the work. It is drafting suggestions for a human who still does the work. Native products close that loop. The model reads your data, acts, and the result lands where it belongs with no clipboard in the middle.
The data model has no memory of the AI
This one is under the hood but it shows. Ask how the product stores what the model produced. In bolted-on systems, AI output goes into a generic notes field or a blob nobody queries. In native systems, the model's work is structured, versioned, and tied to the record it changed. I wrote more about why the data model has to change if you want the technical version.
It breaks the same with or without AI on
Turn the AI off. Does the product still do its whole job? If yes, the AI was decoration. In a native product, turning the model off breaks the core loop because the loop was designed around it. That is not a bug. That is the point. AI-native beats AI bolted on precisely because the model is not optional garnish.
Every AI action needs a human to approve it, always
Guardrails are good. But there is a difference between a product that asks for approval on the decisions that matter and one that asks for approval on everything because it does not trust its own plumbing. Bolted-on AI makes you babysit because the surrounding system was never built to catch a model's mistakes. Native products put the checks in the right places and let the rest run. I care about where the guardrails go, not whether they exist at all.
The pricing page added "AI" and a higher tier
Follow the money. When AI shows up only as an upsell tier on a product that existed for years, the AI is a monetization move, not an architecture. The company found a model, wrapped a prompt, and charged more. Nothing underneath changed. A product built around a model does not have a "with AI" tier because there is no version without it.
The marketing says AI, the demo says forms
The loudest sign is the gap between the pitch and the product. The site says autonomous, intelligent, agentic. The demo shows the same dropdowns and text fields with a "generate" button added. If the language is doing the work the software should be doing, walk. What AI-native actually means is that the model changed the shape of the thing, not the copy on the landing page.
Why this matters when you buy
Bolted-on AI works in a demo and falls apart in production. It carries the cost of a model without the leverage of one. You pay for intelligence and get a fancy autocomplete. When I build something like CaseSolo for personal injury firms, the model is not a feature I added to case management software. The case management was rebuilt to assume a model does the intake, drafts the letters, and reads the records. Same with Ficary for bookkeeping. Test the product against these seven signs before you sign anything. The ones that fail will cost you twice: once for the license, once for the workflow you have to rebuild when it does not deliver.