Frequently asked questions about costs, timelines and ROI

The build costs €2,500 to €10,000 depending on integrations and how much validation is required. Operation costs €150 to €500 a month, with no minimum term. Model usage and infrastructure are billed separately, in accounts in your company’s name.

Between €2,500 and €10,000 to build and between €150 and €500 a month to operate. What moves it within that range is the tools, the information sources, the actions and the validation the process requires. Systems with an orchestrator and several agents are quoted per project.

A single-process workflow starts at around €2,500 to build, and those that touch several of your systems get close to €10,000. Monthly operation runs between €150 and €500.

The same as the rest of our agents, between €2,500 and €10,000 to build and between €150 and €500 a month to operate. On WhatsApp there are also two variable costs: the model calls in each conversation and the templates that Meta charges for separately.

It depends on the number of processes analyzed, the scope and the level of detail required.

It depends on three things: that the data exists, that access has been granted and that the task is well defined. With all three, a pilot in two weeks is realistic. If any of them is missing, the first part of the project is getting it.

Complex integrations, incomplete data, permissions, disorganized documentation and poorly defined processes.

Yes. It’s what we recommend. The pilot covers part of the problem with a metric agreed before starting. It’s paid, and its price counts toward the final project.

By comparing the total cost of the system with the gain it brings, in euros: new revenue or avoided cost.

When the expected benefit exceeds the cost of building, operating and maintaining the system over a reasonable time frame.

No. Model usage and infrastructure are billed separately, in accounts in your company’s name, so you see what you spend and it doesn’t go through us. Neither the build nor the monthly fee includes them.

Yes, and there are two separate ones. Model usage and infrastructure are paid by the client in accounts in its own name, and they go up or down with use. Monitoring and maintenance go in a monthly fee of €150 to €500, with no minimum term.

Not necessarily. It depends on scope, integrations and complexity. An agent can be simple and a conventional automation can be very complex.

Complex integrations, extensive rules, disorganized data, security, multiple systems and a high level of customization.

Yes. It can increase infrastructure, model, storage and operating costs.

Yes. Every call to the model has a price set by the provider, and that bill goes to the client’s account.

Yes. Repeated parts can be cached, smaller models used, the model chosen per task or less context sent. Every change goes through the test suite before it ships.

When the process, the integrations and the scope are defined well enough.

Yes, that’s how we work. There are four steps: Explore, which delivers a yes or a no, Prioritize, which picks the first case with its figure, Implement, which puts it into production with its test suite, and Optimize, which provides the data to decide the next step. Each one is decided with what the previous one delivered.

Yes. It lets you validate a hypothesis before committing to a larger investment.

First the concrete gain, in euros: new revenue or avoided cost. Then conversions, errors avoided, response times, capacity freed up and hours saved.

The work the monthly fee pays for, €150 to €500 with no minimum term: a weekly test run against the system in production, the test suite before every change and fixing whatever comes up. Within that range, the figure depends on complexity, integrations and how critical the process is.

Yes, by adjusting models, processes, prompts, infrastructure and integrations with real usage in view.

Yes. It can be calculated by combining infrastructure, model usage and the costs associated with the workflow.