Budget for the whole workflow: setup, software, AI usage, review, maintenance and the cost of mistakes. Compare options using the same task volume and quality requirements before choosing a tool or accepting a quote.
AI automation costs depend on what the system must do and how much responsibility it carries. Drafting an internal summary has a different operating burden from changing customer records or sending messages. A useful estimate starts with that boundary.
This guide gives you a cost breakdown, a quote-comparison worksheet and a way to compare a pilot with your existing process. It does not present a universal price range. Use current supplier quotes and observed workload figures for your own estimate.
01 / Define what the price includes
Write one sentence describing the workflow’s trigger, inputs and output. Then list the systems it reads, the systems it changes and the actions a person must approve. Include what happens when information is missing or contradictory.
For example, a reporting workflow might collect figures from approved exports and assemble a draft. Reconciling conflicting totals, interpreting business performance and distributing the final report may remain separate tasks. A quote for collecting data should not be compared with a quote covering the entire reporting process.
Document the expected weekly volume, peak periods and review owner. Ask each supplier to price the same scope. If you have not chosen a candidate, start with the first automation project guide.
02 / Separate setup from running costs
| Category | What to include | Question to ask |
|---|---|---|
| Process preparation | Documenting steps, cleaning inputs, deciding exceptions | Who supplies the examples and decision rules? |
| Build and integration | Connections, validation, approval screens, tests | Which systems and actions are included? |
| Software and usage | Subscriptions, seats, workflow runs, model usage, storage | What happens when volume exceeds the plan? |
| Human review | Checking drafts, correcting errors, handling unusual cases | How much review is needed per item? |
| Maintenance | Monitoring failures, renewing access, changing rules | Who owns fixes and ongoing changes? |
Classify each amount as one-time, recurring or usage-based. Record the currency, billing interval and assumptions. A subscription billed annually may have a lower monthly equivalent but requires a different cash commitment from a monthly plan.
Check whether an existing application already includes the needed automation. An additional integration tool may be justified, but duplicating a built-in feature adds another system to maintain.
03 / Estimate usage from the actual workflow
Count the units a supplier bills. A business request can involve several workflow actions or several model calls. Reading a long document can consume a different amount of usage from classifying a short message. Retries and failed runs may also affect the bill, depending on the provider.
Ask for a small worked example using your intended workflow. Record which steps execute for a normal request and which execute when something goes wrong. Check current billing definitions in the provider’s own documentation instead of assuming every provider uses the same unit.
Prepare a normal-volume estimate and a busier-period estimate. If demand is uncertain, agree on a spending limit and a clear response when it is reached. A workflow that silently stops when a limit is hit creates an operational problem even if the software bill stays low.
04 / Price the work people still do
Measure review time during a pilot. Include opening the result, checking the source, making corrections and returning the item to its destination. Add exception handling separately so the same work is not counted twice.
Maintenance includes changes to input forms, business rules and connected systems. Someone also needs to notice failures, recover unfinished work and verify that a fix helped. Include that person’s time even if they already work for the business.
A draft counts as useful only when the reviewer can use it with an acceptable amount of checking and correction. Generating a result quickly is one part of the measurement.
Use the weekly time worksheet to subtract review, rework and upkeep from manual work. That gives a time estimate. It does not value customer experience, error consequences or the business’s alternative uses for that time.
05 / Compare quotes on the same basis
Put these questions next to every option, including building internally:
- What exactly is delivered, and how will acceptance be checked?
- Which subscriptions, usage charges and third-party services are excluded?
- Who owns the source, records and connected accounts?
- What support is included, and how are changes priced?
- How do retries, failures and duplicate requests get handled?
- Can the team export its data and return to the manual process?
Record each answer as included, excluded or unknown. Resolve unknowns before treating two totals as comparable. A low build quote with undefined support may produce a different operating commitment from a higher quote with an explicit handover and support scope.
For a reusable comparison, download the automation cost worksheet. Its fields are blank so you can use current quotes rather than a generic estimate.
06 / Make the pilot decision
For a chosen review period, add setup costs, recurring charges, expected usage and ongoing labor. Compare that with the current process over the same period. Keep forecast amounts separate from actual bills and observed labor.
setup + subscriptions + usage + review labor + maintenance labor
Check the assumptions that matter most. If the task occurs half as often as expected, does the project still make sense? If every output requires a longer review, is the original process faster? If the integration becomes unavailable, can the team keep serving customers?
A pilot can produce value by clarifying the process even when it does not justify a larger build. Record what worked, what needed correction and what would have to change before expansion. Time recovered is capacity; it becomes a revenue outcome only when the business actually uses it to produce one.
Common questions
What is the cheapest way to start?
Inspect the tools you already use and choose one bounded task. Compare the built-in option, a small integration and a custom build against the same requirements.
Should I use an agent to reduce costs?
Choose the level of autonomy from the task. An agent can introduce additional calls, testing and oversight. The agent-versus-workflow guide explains that decision.
When can I estimate a return?
After you have a comparable manual baseline, a complete cost estimate and pilot observations. Use a range of workload and review assumptions rather than presenting one forecast as certain.
How to use this guide
The categories and worksheet are original planning aids. They are not supplier quotes or evidence of Geronco client results. For project context, explore William’s AI strategy and implementation approach and selected work. Review current supplier pricing and usage definitions before making a purchase.