› Practical guide · Business case
AI automation cost and ROI: build the business case without fantasy numbers
An automation business case should expose its assumptions. Project price is only one line: integration access, review time, provider usage, monitoring, maintenance and change all affect the total cost. Benefits also need separation—released capacity is not automatically cash saved.
Written and reviewed by Agentary AI engineering
The short version
- Price the workflow against a written scope, acceptance criteria and integration boundary.
- Separate one-time implementation cost from provider, hosting, monitoring and change costs.
- Value released capacity conservatively and explain whether it becomes throughput, service quality or cash impact.
- Measure the baseline before building and compare the same metric after launch.
How this guide was produced
The framework reflects Agentary AI's current commercial model and the implementation boundaries demonstrated by its public workflows. The arithmetic examples are illustrative assumptions, not typical results or guarantees. A real proposal must use the client's measured volumes, labour assumptions, error costs and acceptance criteria.
What determines the cost of an automation
The visible number of steps is a poor proxy for effort. A five-step process may be straightforward when every system has a stable API, or complex when it involves email attachments, inconsistent spreadsheets, legacy access and several approval roles.
- Number and quality of integrations, including authentication and test environments.
- Data consistency, document variability and migration or cleanup work.
- Decision risk, approval roles, security review and audit requirements.
- Exception volume and the recovery paths required when a system is unavailable.
- Monitoring, alerting, documentation, training and support expectations.
- Provider usage, hosting, licences and third-party platform fees.
Agentary AI's current commercial starting points
| Engagement | Current price | Best fit |
|---|---|---|
| Probe | From €1,400 per project | One defined workflow with a written boundary and acceptance criteria |
| Operator | €3,200 per month | Ongoing delivery, monitoring and expansion across a prioritised roadmap |
| Autonomous | Custom | Higher-volume or complex operations with project-specific architecture and controls |
Prices are indicative, may exclude VAT and third-party costs, and are not binding until the scope, assumptions and responsibilities are agreed in writing.
Calculate total cost of ownership, not only build price
A useful annual model combines implementation, recurring service, provider usage, hosting and expected change. It should also account for the internal time required from process owners, reviewers, IT and security.
| Cost layer | Questions to answer |
|---|---|
| Implementation | What is designed, integrated, tested, documented and accepted? |
| Usage | Which model, email, OCR, storage or automation-platform fees vary with volume? |
| Operations | Who monitors runs, handles incidents and owns supplier changes? |
| Change | How often do forms, rules, APIs, prices or approval roles change? |
| Internal participation | How many hours will subject-matter experts and reviewers contribute? |
Released capacity is valuable—but it is not automatically cash
If a workflow removes repetitive handling, the organisation may use that capacity to process more volume, respond faster, reduce overtime, avoid a future hire or improve control quality. Those are different benefit types and should not be collapsed into a single guaranteed savings number.
Use the fully loaded hourly cost only when it is a reasonable approximation, and apply a conservative automation coverage factor. Keep revenue uplift, avoided loss and labour capacity as separate lines so decision-makers can challenge each assumption.
A transparent released-capacity formula
Annual released-capacity value = manual hours per week × active weeks per year × loaded hourly cost × realistically automatable share.
Illustrative example only: 12 manual hours per week × 46 active weeks × €25 loaded hourly cost × 50% in-scope coverage = €6,900 of annual released-capacity value. This does not mean €6,900 appears as cash; the organisation must decide how the capacity is used.
If the defined implementation cost were €1,400 and ongoing costs were €100 per month, the first-year cost would be €2,600. Under the illustrative assumptions, the simple first-year value-to-cost ratio would be 2.65. Taxes, financing, change cost and risk adjustments are excluded.
Never copy this example into a proposal as a forecast. Replace every input with the client's measured baseline and document who approved each assumption.
Choose one primary operational metric
| Workflow | Possible primary metric | Supporting measures |
|---|---|---|
| Lead qualification | Time to reviewed response | Edit rate, false routing, meeting conversion |
| Invoice reconciliation | Manual minutes per invoice | Exception age, correction rate, duplicate interception |
| Support triage | Time to correct routing | Reopen rate, escalation quality, reviewer effort |
| Reporting | Preparation time per cycle | Data completeness, correction count, delivery punctuality |
Questions to answer before approving the investment
- Is the current volume and handling time measured rather than estimated from memory?
- Which steps genuinely require judgment, and which follow stable rules?
- What happens when the model, provider or connected system is unavailable?
- Who owns the process, approves exceptions and accepts the release?
- Which costs vary with volume and which are fixed?
- What result would justify expansion—and what result would stop the project?
- How will the business use the released capacity if the workflow succeeds?
Questions about automation pricing and ROI
Why is there no fixed price for every automation?+
Integrations, data quality, risk, exception handling and acceptance criteria differ substantially. A responsible fixed price requires a defined workflow boundary and written assumptions.
Does Agentary AI guarantee savings?+
No. Estimates depend on client-provided baselines and assumptions. The project should define measurable acceptance criteria, but operational or financial outcomes cannot be guaranteed.
What third-party costs may apply?+
Depending on the design, costs may include AI model usage, OCR, email, storage, hosting, automation platforms, CRM or ERP licences and monitoring services. These should be itemised in the proposal.
When should a company not automate?+
Do not automate a process that is unstable, poorly owned, too rare to justify the effort, dependent on unavailable data or too risky for the available controls. Simplifying the process may be the better first step.