Automation costs after launch: price completed work

Start with an operating worksheet

A workflow still needs attention after its first successful run. Estimate the cost of keeping completed work correct, recoverable and supported. This guide offers a planning worksheet, not a price quote or a forecast of savings. Check current rates and billing units with the actual providers before committing.

Separate one-off discovery, integration, testing and rollout costs from the recurring budget. Record what is included in support and what requires a separate change request. A low usage price says little about the total cost of an unreliable workflow.

Include the costs around execution

For a stated reporting period, list:

• Fixed platform subscriptions, minimum charges and user or connector licenses.
• Variable execution, document-page, message, storage and AI usage charges that apply to your chosen services.
• Monitoring, retained evidence, backups and access administration.
• Staff time reviewing uncertain items, correcting data, handling incidents and reconciling results.
• Maintenance for changing APIs, document formats, business rules and evaluation samples.
• Agreed support coverage, escalation and recovery exercises.

Avoid counting a cost twice when it is already included in a subscription or support agreement. Record the currency, applicable tax treatment, billing unit, source and date of each rate. Assign shared costs consistently and show assumptions rather than presenting an allocation as an exact supplier charge.

Use completed work as the denominator

Define what counts as an accepted completion. Count failed attempts and retries in usage costs, but do not count them as extra business completions. Include review effort for the same reporting period.

A useful operating measure is total attributable recurring cost divided by accepted completed items. Report total cost and volume alongside that ratio; if no items completed, the ratio is undefined. Keep one-off setup costs separate unless you state the period over which you allocate them.

Worked example with invented numbers

Suppose a hypothetical month has 1,000 accepted completed items, 120 EUR of platform and execution charges, 80 EUR of review effort and 50 EUR of maintenance. The attributable recurring total is 250 EUR, or 0.25 EUR per accepted item. These invented figures are arithmetic only, not SkepticFlow pricing, a vendor tariff or a client outcome. They omit one-off setup and any costs not explicitly listed.

Do not turn hours released into cash savings automatically. Explain whether staff capacity was reassigned, an expense was actually avoided or only a forecast changed. Compare quality and service outcomes with the recorded manual baseline as well as cost.

Agree limits and review changes

Estimate quiet, expected and peak volume, including increased exception rates. Assign an owner to spending alerts and define which work may pause at a budget limit. Provider budgets may only notify; confirm whether a separate technical limit is needed. A pause must preserve pending work and required human follow-up.

Review actual bills, completions, corrections and queue age together. Revisit the estimate when volume, provider rates, access, document types or support coverage changes. Agree an exit path, including ownership and export of permitted operational records.

Read next and sources

See choosing the first workflow and document exceptions.

Reviewed 21 October 2026. Microsoft's cost-model guidance and Cost Optimization checklist provide related planning principles. Provider-specific prices, commitments and legal terms must be checked separately.