Engagement structure, not a price list

How AI agent work is priced

There is no universal price for an AI agent. Devs Group costs each engagement from the scope agreed in writing: the channels covered, systems integrated, the languages and hours of cover, and the acceptance testing required. A proposal separates setup work, third-party charges, usage and ongoing support, so the figures can be compared with another supplier's.

What drives the cost

Two projects that sound alike can differ sharply once these factors are written down. Ask any supplier to state each one.

Channels: every customer or staff channel adds build, testing and support surface. One channel is a smaller job than four.
Systems: each integration depends on supported access, the operations required (read, write or both), stable record identifiers and permission rules. A read-only lookup is not the same job as a write back into a booking record.
Languages and content: Arabic and English together mean terminology work, review by a speaker and test conversations in both, including mixed-language messages.
Hours of cover: staffed escalation hours in GMT+4, out-of-hours behaviour and escalation destinations.
Acceptance testing: the size of the test set, whether it includes failures, conflicting records and unavailable systems, and how long the limited release runs.
Ongoing operation: monitoring, knowledge updates, error review and the support arrangement after launch.
Third-party charges: platform subscriptions, telephony minutes, model usage and messaging fees, billed by their providers.

Indicative figures and delivery timelines

A range is only useful when it is tied to a defined scope and a date. Verified figures for the scope described here belong on this page, next to the assumptions they depend on.

Until then, ask for a written estimate against your own brief. A quote that will not separate setup, usage and third-party charges has not shown where your budget goes.

What an engagement includes

The proposal is the definitive list: anything not written there is excluded, however likely it seems.

Workflow design: the task, the permitted actions, approval boundaries and the escalation route.
An approved answer and offer library, with a named owner for price changes.
Integration with the agreed systems, at the agreed permissions, plus duplicate and failure handling.
Acceptance cases, a test record and a limited release before wider use.
Handover of configuration, connected systems and operating instructions, as stated in the proposal.

How paid discovery works

Some projects need scoping before anyone can quote implementation honestly: access unclear, several systems involved, or a workflow nobody has written down. A paid discovery step is quoted as a fixed fee before it starts, and produces something you keep even if you go no further: a written scope, a system and access map with the operations required, a dependency and risk list, an acceptance plan and an itemised estimate.

Discovery does not commit you to build. It gives you the material to decide whether the workflow is worth building, and us the material to price it.

What the buyer receives

Expect a proposal that states inclusions and exclusions, the access the client must provide, the acceptance criteria, the assumptions behind the estimate and the payment stages. At handover, expect the configuration, the list of connected systems with their permissions, the approved information sources and their owners, and the test record. The proposal should say which documents are delivered; ask before signing.

How change requests are handled

Scope changes are normal, silent scope growth is not. A change request is written down, estimated for its effect on cost and date, and approved before the work starts, so neither side discovers the price at the end. Adding a channel, a language, an integration or a volume band is a new estimate. Small text and answer-library updates belong in the maintenance arrangement if one is in place; if it is not, they are quoted like any other change.

Getting a figure for your case

Send the task, the channels, the systems and their owners, the languages, the staffed hours and the result you would use to judge the work. That is enough for a scoped estimate. Discuss your workflow on WhatsApp, email mail@devs.group, or call +971 58 514 6444.