What does AI automation cost to run each month?
Use $50–$500 a month as our planning band for typical small-business tools and model usage. It is not a quote, and it does not include the build, hardware, internal labor, or paid maintenance. Optional Managed Services starts at $1,500 a month, separately.
Budget four categories: model usage; software and hosting; your team’s review time; and maintenance. A low model bill can still sit underneath an expensive workflow if people spend hours correcting its output.
How do you estimate the model bill?
Count monthly runs, measure typical input and output, and apply the rates for the chosen model. Include repeated attempts, tool calls, and any paid search or document-processing features. A document’s page count alone is a rough proxy; test representative files.
Anthropic’s pricing documentation separates input, output, caching, and feature charges. Model choice and tokenizer also affect usage. Keep the date and model next to your estimate so someone can update it when a price or version changes.
Illustrative calculation: 1,000 runs using 10,000 input tokens and 1,000 output tokens each produce 10 million input and 1 million output tokens. At assumed rates of $2 and $10 per million respectively, that is $30 before other charges. These are example rates, not a quote for your workflow. Replace them with the current provider rates and measured usage.
What other software belongs in the budget?
List each subscription that the workflow depends on: automation platform, hosting, document extraction, storage, messaging, telephony, and any paid connector. Record the billing unit for each one. Seats, messages, minutes, documents, and executions can grow at different speeds.
Office AI licenses are a separate decision. Microsoft publishes per-user Copilot Business pricing and its subscription conditions. Compare the specific plan, existing license requirements, and commitment before budgeting. A seat that helps an employee and a workflow that moves work between tools may both be useful; do not count one as paying for the other.
Who reviews and maintains the system?
Name a workflow owner. Budget time for reviewing exceptions, checking outputs, handling access, and deciding what to do when something changes. Measure this during the pilot rather than assuming that every hour of manual work disappears.
Maintenance covers a different job: keeping integrations and models working, testing changes, and responding when a dependency fails. Your team can take that responsibility or buy support. Our optional Managed Services starts at $1,500 a month with no lock-in; the system remains yours. The written scope establishes what support covers.
What changes the monthly number?
| Cost driver | Measure | Question before launch |
|---|---|---|
| Volume | Runs, messages, calls, or documents per month | What happens in a busy month? |
| Document work | Length, extraction needs, and retries | Which difficult files cost the most? |
| Human review | Minutes per output and exception rate | Is preparation reduced after review is counted? |
| Dependencies | Subscriptions, model versions, and integration limits | Who sees an error or a price change? |
| Local hardware | Purchase, administration, backups, and electricity | Who maintains and replaces it? |
Set a spending threshold and an escalation owner. Decide whether the workflow pauses, falls back to a simpler route, or asks for approval when that threshold is reached. Include those decisions in the scope.
When is a workflow not worth automating?
When the value you can realistically capture does not justify the build, running costs, and review burden. Volume matters, but it is not the only test: a rare task can still be valuable if its delay or error cost is high.
For example, a task taking two hours a month at an assumed $40 an hour has at most $80 of monthly labor value before review. If software costs $50, only $30 remains before maintenance and build recovery. This illustrative case has little room for an $18,000 build. A simpler process change may be enough.
If growth could change the answer, record the trigger: transaction volume, time spent, or a recurring delay. Revisit when that trigger occurs. The ROI math guide explains how to keep capacity, cash savings, and revenue assumptions separate.
What belongs in a first-year budget?
Add the agreed implementation price, any discovery, hardware, twelve months of tools and usage, internal review time, and maintenance. Account for an audit credit only if its conditions are met. A ramp-up period means twelve months of costs may not produce twelve months of value.
Our audit is $3,500–$8,500 over 2 to 4 weeks; a sprint is $18,000–$60,000 over 4 to 12 weeks. You can go directly to a scoped sprint if a paid audit is unnecessary. The price list states the credit and support terms; the proposal guide shows what to compare before signing.
Basis and limits. The $50–$500 band is a first-party planning range for tools and model usage, not an all-in operating quote or a market survey. Worked examples are illustrative. Check current provider prices and test your own volume before committing.