Start here
AI Readiness & Roadmap
2–3 weeks
You know AI matters but every vendor pitch sounds the same.
- Current-state assessment
- Opportunity register
- Sequenced roadmap
How we work
We do not sell packages off a price list. Two projects that sound identical can differ several-fold depending on how many systems they touch and how clean the data behind them is. So we scope first, then quote — and once you have the figure, it is fixed.
What an engagement looks like
Start here
2–3 weeks
You know AI matters but every vendor pitch sounds the same.
Control the risk
3–4 weeks
AI is already in use and nobody is accountable for it.
Build it
4–12 weeks by scope
You are losing enquiries to voicemail and slow follow-up.
Grow the pipeline
4–8 weeks
Leads arrive and quietly go nowhere.
Timelines are typical and move with your systems. The fee is agreed after a scoping call and, for fixed-scope work, does not change afterwards unless you change the scope in writing.
How we contract
| Model | When we use it | How it works | What is good about it | What to watch |
|---|---|---|---|---|
| Fixed-scope engagement | Roadmap and governance work, where the deliverable is well defined. | A fixed fee agreed after scoping, invoiced 50% at start and 50% on delivery. | You know the cost before you commit and there is no meter running. | Scope changes are handled as a written change order, not absorbed silently. |
| Build engagement | Agent and automation builds, where integration effort is the main variable. | Phased fee against milestones, with the first phase deliberately small so you can stop after it. | You see working software before committing the bulk of the budget. | Integration effort is the biggest driver, so we scope it explicitly in phase one. |
| Retained AI team | After a build, when you want the thing tuned and extended without hiring. | A monthly retainer for an agreed number of days, reviewed quarterly. | Continuity, and someone accountable in month six when the vendor has usually gone. | We will tell you when you no longer need it. Retainers that outlive their usefulness damage the relationship. |
What shapes the quote
Worth reading before you agree a price. Reducing scope on the right axis is far more effective than negotiating the fee.
Costs more A legacy platform with no usable API, or four systems that each hold part of the truth.
Costs less A modern platform with documented APIs, or a workflow that touches one system.
Costs more Bilingual English and Arabic including mid-sentence switching, tested against real dialect.
Costs less A single language with a defined customer base.
Costs more Inventory or availability data that is not reliable enough to make promises from.
Costs less A single source of truth that is already accurate.
Costs more Health data, financial services, or a residency requirement that constrains the architecture.
Costs less General commercial data with no specific residency constraint.
Costs more Phone, WhatsApp, web and social all live from day one.
Costs less One channel first, widened after it has proven itself.
After go-live
The build is a one-off; these are the ongoing costs. We model them against your current cost per handled conversation during scoping — that comparison is the one that decides whether the project is worth doing at all.
Engagement FAQ
Because a number without a scope is misleading. Two engagements that sound identical can differ several-fold depending on how many systems they touch and how clean the data behind them is. We would rather spend thirty minutes understanding your situation and give you a real figure than publish a bracket you would have to unlearn.
For roadmap and governance work, usually within a couple of days of the discovery call. For builds it depends on how quickly we can confirm what your systems expose — that is the single biggest variable, and we would rather check than guess.
Fixed for fixed-scope work, and it does not move afterwards unless you change the scope in writing. Build work is quoted per phase, so you are never committing the whole budget on the strength of an estimate.
Look at the five drivers above before you agree a price — reducing scope on the right axis is far more effective than negotiating the fee. Starting with one channel, out of hours only, rather than everything at once, is the most common and most sensible reduction.
No. The 30-minute readiness call is free and carries no obligation. If we conclude you should not spend anything yet, we will say so on that call.
Then you have paid for a roadmap and saved a build, which is a good outcome. It happens roughly one engagement in six. We would rather deliver that finding than sell you something that will not work.
Yes, and we often recommend it. A single channel, out of hours only, is a real deployment with real evidence at a fraction of the full commitment. It makes the decision to widen much easier to justify internally.
Occasionally, where the outcome is genuinely measurable and both sides control their part of it. More often the attribution is too messy to be fair to either party, and a clean fee produces a healthier relationship. We are happy to discuss it.
AED for UAE clients, and we invoice elsewhere in the GCC in the appropriate currency. VAT is applied where it applies.
Thirty days from invoice. Fixed-scope work is split 50% at start and 50% on delivery; build work is milestone-based.
Thirty minutes on your systems and volumes and we can give you a properly grounded figure, rather than a bracket you would have to unlearn.
Altus AI concierge
Answers about our work — and books your call
Hello — I'm the Altus concierge. Ask me anything about AI adoption, governance, or the agents we build. If it's a fit, I'll set up a call with the team.
AI-generated. We store what you send so we can follow up. Privacy