1. The task it handles
A chatbot that answers common questions from a fixed set of information is the simplest case. The work grows when the assistant must collect details from customers, qualify inquiries, look up live data such as order status or available appointments, or create requests in another system.
2. The information it answers from
An assistant that answers from your own content needs that content prepared: FAQs, policies, service descriptions, product data or internal documents. Organised, up-to-date sources take less work than scattered files with conflicting versions.
Someone also needs to own that content after launch. When prices, policies or services change, the assistant's sources must change with them.
3. Integrations with your systems
Reading or writing data in your website, booking system, CRM or other tools depends on what those systems support, usually an API. Each integration adds design, development and testing, and some older systems cannot be connected without changes on their side.
4. Languages and channels
Supporting Arabic and English, understanding dialects, and running the assistant on a website, inside a mobile app or in internal tools each add testing. Arabic needs particular care, because customers often mix dialect, Modern Standard Arabic and English in one message.
5. Running costs after launch
Unlike most website features, an AI assistant has costs that continue after it goes live:
- AI model usage, usually charged by the amount of text processed, so it grows with the number of conversations.
- Hosting for the assistant and for any document search it relies on.
- Updating content and instructions as your services change.
- Reviewing conversations to find questions it answers poorly.
How to keep the first version focused
- Start with one task, such as answering pre-sales questions.
- Use a limited, approved set of sources.
- Decide in advance when the assistant hands a conversation to a person.
- Test it on real questions before adding more features.
How Elite Solutions estimates an AI project
We first agree on the task and the sources the assistant may use, then check which systems it needs to connect to, and estimate the first version from that scope. Running costs are explained separately, so you know what continues after launch.