Short answer
We charge per project, not per month. The price is decided by four things: the condition of your data, the number of systems to connect, the acceptable error rate, and who maintains it afterwards. We look at a real sample of your data before quoting, because a quote given without looking is a guess. Scoping and the quote itself are not charged.
The four factors that decide the price
| Factor | Cheaper when | More expensive when |
|---|---|---|
| Data condition | Consistent format, digital, one source | Mixed formats, photographs of documents, sources that disagree |
| Integrations | Output lands in a file or an email | It must write into software with no documented interface |
| Error tolerance | A person reviews everything anyway | Output goes straight to a customer, or carries legal weight |
| Maintenance | Your team takes over after handover | We maintain it, under a separate agreement |
The first factor is by far the heaviest. On almost every project we have quoted, the price gap between clean data and scattered data was wider than the gap between two different feature scopes. That is explained in why your data is the hard part.
What a quote includes
Always included
- Scoping and the review of your data
- Build and testing
- A measured performance figure and the test set
- Launch and support through the first weeks
- Documentation, written for another developer
- Ownership of code, prompts and data
Quoted separately
- Hosting and monthly usage costs
- Third-party platform fees
- Maintenance after handover
- Changes requested after delivery
- Capturing data you do not have yet
A vendor who quotes without asking a single question about your data is guessing. You are entitled to ask which of the four factors is driving your number.
Describe the task in a few lines and attach two or three real examples. We reply with a range and the factors driving it, with no obligatory meeting.
Ask for a quoteWhy per project and not by subscription
A build has an end. Charging monthly for something that finishes puts both sides on the wrong footing: the vendor gains by dragging it out, the client pays for finished work. You get a scope, a price, a delivery and a handover.
Maintenance, if you want it, is a separate and explicit agreement. It does not start on its own, and you can end it without the system ceasing to be yours.
The quote that goes nowhere
Sometimes scoping ends with: this project is not worth doing. The volume is too low, a simpler tool solves it, or the data is not ready. We say so, and reaching that conclusion is not charged.
Turning down a project costs us one invoice. Delivering one that gets abandoned costs the relationship and the referrals behind it. See also when you do not need AI and what to ask before you sign.
Frequently asked questions
How much does a chatbot cost in Algeria?
It depends on the condition of your information, the number of channels and systems to connect, and who maintains it. We look at a real sample before quoting and charge per project, with monthly running costs stated separately.
Do you charge for a quote?
No. Scoping, reviewing a sample of your data and the quote itself are not charged, including when the conclusion is that the project is not worth doing.
Why do you not charge a monthly subscription?
Because a build finishes, and billing monthly for a finished thing creates the wrong incentive on both sides. Maintenance exists, but as a separate explicit agreement you can end.
What moves the price the most?
The condition of your data, by a wide margin. Documents in a consistent digital format cost a fraction of what photographs, mixed formats and contradictory sources cost.
Are running costs included?
No, they are quoted separately and stated in the proposal: hosting, model usage, and third-party platform fees such as WhatsApp. That way you can see what the system costs to build and what it costs to run.