Connections, exceptions and upkeep change the cost.
More connections, conditional paths and approval steps mean more work to design, test and support. Include software usage, human review and recovery when comparing the total commitment.
Start with a process brief. Separate setup from ongoing costs, and ask what could change the quote.
- Build: design, connections and testing.
- Run: software, usage and review time.
- Maintain: fixes, access changes and support.
- Recover: alerts, manual work and safe retries.
A complete process brief makes estimates comparable.
Describe one complete workflow.
Name the starting event, required inputs and expected result. Assign a person to check exceptions and own the outcome.
Include the awkward cases in the brief. Missing data, repeat requests and broken connections can add work to a simple process.
If you have not chosen a process, use our small business automation guide first. This guide helps price a process you have chosen.
Four questions for your brief.
- Which task is included, and which stays manual?
- Which tools must exchange information?
- Who approves changes before they reach a customer?
- What happens if a required step fails?
Three parts of an automation estimate.
Build
Map the process, connect tools and test the paths.
Run
Count software, usage and the time spent checking.
Maintain
Assign upkeep, recovery and future changes.
Separate the project from the software bill.
Ask what the setup fee delivers.
Setup may include mapping fields and connecting accounts. Include the tests and handover needed to run the process.
A ready-made connection can reduce some work. A custom one may need more work to build and maintain.
Ask for plain descriptions of what you receive. A demo alone does not show how the owner handles missing data or repairs.
Read the usage rules for the actual plan.
Zapier’s pricing page separates plans and features. Check features, billing terms and usage limits before buying. The headline price may not fit your process.
Zapier’s task documentation explains that successful actions count toward task usage. One request can include several actions. Count those steps when estimating the bill.
Other services can count use differently. Check each billing unit and what happens at the limit: extra charges, paused work or both.
- Estimate the normal path and busy periods.
- Include repeat runs and recovery actions.
- Check limits, alerts and upgrade rules.
Price the decisions the system cannot safely make.
Keep approval work visible.
A draft quote may need a person to check its scope. Budget their time even when the software prepares the draft.
Microsoft’s approvals documentation describes a workflow that waits for a human response. That step protects the customer promise. It still needs a reviewer who can respond.
Choose a simpler path when the rules are known.
AI agents can add model use and more checking. Clear rules may need a simpler, cheaper path.
“They're burning lots of tokens to go figure out what that task is.”
In Zapier’s account of his AI First interview, Foster compares set workflows with agents that choose their path. His distinction raises a cost question; it does not set your price.
Agree who watches the process after launch.
Tools change, account access expires and odd inputs arrive. Maintenance keeps the process useful beyond its first successful run.
Microsoft’s error-handling guidance includes failure paths and logging. Your tools may differ. The scope should still say how people detect and handle problems.
Make the support boundary clear.
Ask which fixes are included in support. Changes to the process may need a new quote; repairs should match the agreed scope.
- Name the person who receives failure alerts.
- Agree the support hours and escalation route.
- Keep account ownership and access documented.
- Describe how to turn the workflow off safely.
A manual fallback also has a cost. Someone needs access, instructions and time to finish the task by hand.
A fictional studio compares two scopes.
Imagine Elm Studio, a fictional service business. It wants to record each inquiry and notify the owner, who decides how to reply.
One proposal covers those actions and a failure alert. Another adds draft estimates and updates across several tools; the scopes differ.
Compare the same responsibilities.
Elm asks suppliers to name the outputs, checks and upkeep. It removes automatic estimates because the pricing rules are not settled.
Compare scope before comparing price.
Same task?
Confirm the starting event and expected result.
Same checks?
Include failures, approvals and duplicate handling.
Same support?
Check upkeep, ownership and the handover.
The owner uses the website cost planning tool for the separate website budget. Workflow costs need a separate estimate. The tool does not calculate an automation quote.
Compare the work behind each estimate.
Send the brief with test examples that contain no private customer details. Ask which uncertainties could change the work or ongoing bill.
Compare setup, software, checks and upkeep over an agreed period. Keep possible savings separate until a real trial supports them.
- What is included in setup and handover?
- Which software accounts does the business need?
- What usage assumption supports the estimate?
- Who reviews output and handles failed work?
- What changes require another quote?
Aim for a clear scope and a process you can maintain. Choose a small, safe version and review the work it creates.
Frequently asked questions.
What should our automation quote include besides the software subscription?
Look for process design, connections, testing, checking, handover and maintenance. Separate setup from recurring commitments so the quote shows who pays for the work after the first successful run.
Two suppliers automate the same form. Why might their estimates cover different work?
One may include validation, duplicate handling, failure alerts and support while the other covers only the normal path. Compare outputs and recovery responsibilities before treating the totals as equivalent.
How do we tell whether the trial reduced work rather than moving it?
Compare the whole task before and after, including review, corrections and upkeep. A faster automated step does not establish a saving if those other duties absorb the time it released.
Glossary.
- Billing unit
- The action or amount of use a provider counts when charging.
- Scope
- The work, checks and responsibilities included in an estimate.
- Manual fallback
- A documented way a person can complete the task when the automated path fails.
- Workflow automation
- The use of software to carry out connected steps when defined events or conditions occur.
- Branching rule
- A condition that sends a workflow down a different path and creates another case to design and test.
- AI agent
- A software system that uses a model to choose steps toward a task within its granted tools and limits.
Sources and method.
Provider documentation supports the examples of usage, approval and failure handling. The models and studio example are original illustrations; they do not set market prices or predict savings.
About Jake Tripp.
Jake Tripp is the owner of Still Matter. He helps businesses connect brand strategy, identity, websites, content and practical marketing systems.
He works on his own brands and client projects. His focus is clearer decisions and work that is easier to manage.
Here, he writes about useful websites and content your team can maintain.
Learn more about the author