Four stages. The third is where most of the budget goes, and most writing about AI skips it.
One task, stated so narrowly that you can tell whether it worked. "Answer customer questions" is not that. "Answer the eight questions that make up most of our enquiries, and hand the rest to a person" is. This conversation saves more money than any technical decision later.
Whatever the system answers from - your site, your policies, your product data - has to be found, split and checked for contradictions. If two documents disagree, the system will confidently pick one. Resolving that is part of the work, not a precondition for it.
Usually the larger half of the bill. Reading from your billing system, writing to your CRM, authenticating, handling the case where the other system is down. The model is a few lines; this is the project.
It needs hosting with root access, monitoring, a place for logs, a way to update the knowledge when your prices change, and somebody to look at what it got wrong. A system nobody reviews drifts quietly.
Said plainly, because a project that should not have started is the most expensive kind.
If the task is collecting five fields and emailing them somewhere, that is a form. An assistant in front of it adds cost, latency and a new way to fail.
A model cannot tell a customer your delivery time to Oman if nobody has ever written it down. Several projects are really documentation projects wearing a different hat.
Tax figures, dosages, legal deadlines. Retrieval reduces invention; it does not eliminate it. Those belong in a lookup with a deterministic answer, with AI at most helping you find the right row.
An AI system is not a thing you install and leave. If no one in the business will review what it said and update what it knows, it will be worse in six months than on launch day.
The detail on each, including where each one goes wrong.