There is no useful universal automation price
An email-routing workflow and an invoice process touching several controlled systems are not comparable simply because both use automation. A credible quotation states what will be built, the assumptions behind the price, what is excluded and what ongoing charges remain.
Foxbyte does not publish an invented universal automation price list here. Its fixed website-design packages are a different commercial offer, not a benchmark for AI or workflow implementation. For automation, the useful starting point is a bounded requirement that can be assessed and quoted.
Separate the implementation price from running costs
Compare one-off discovery, build, testing, training and handover with recurring platform licenses, usage, hosting and management. Also identify costs your own team retains: preparing content, agreeing processes, authorising access and reviewing exceptions.
A subscription may grant access to a tool without including custom workflow design or managed support. Conversely, a build quotation may exclude the tool’s recurring fees. Ask who holds each account, who pays renewals and what happens when a usage allowance is exceeded.
The principal scope drivers
Workflow count and variation
One workflow with many departments, exceptions or approval paths can be more involved than several simple independent flows. Define the trigger, result and permitted variations. Avoid pricing an undefined list of “all other processes” as though it were fixed scope.
Systems and supported integrations
List every source and destination system, available interface, connection owner and authentication method. A supported connector can differ from custom API work or a desktop sequence. Include time for permissions, a safe test route and unavailable-system behaviour. Do not assume that owning a software license grants every integration entitlement.
Document and data quality
Structured form data usually requires different preparation from varying scans or inconsistent spreadsheets. Representative samples should include errors and unusual layouts, not only the cleanest examples. Clarify who corrects historical data, defines master references and resolves duplicates.
Approval rules and separation of responsibility
Identify who can submit, review, approve, reject or change a record. Include delegates, absent approvers, escalation and cancellation. A system with several roles and material decisions needs more than a diagram with one approval box.
Testing and acceptance
The scope should include ordinary cases, invalid inputs, duplicates, unavailable integrations, permission failures and controlled retries. Agree how acceptance is demonstrated and who signs it off. An untested connection should not disappear inside a line labelled “integration complete”.
Training, documentation and support
Specify users to be trained, administrator handover, operating notes and the maintenance arrangement. New workflows, changed requirements and vendor/API changes may be separately chargeable. Define the difference between correcting an in-scope defect and adding a new capability.
Ask for an explicit licensing and usage schedule
Microsoft distinguishes user and capacity licensing for Power Automate; other Microsoft subscriptions provide limited included capabilities. Premium connectors, unattended automation and additional capacity can have separate entitlement requirements. Verify the actual proposed deployment rather than assuming every Microsoft 365 user already has every necessary license. Microsoft: Power Automate license types.
For an API-priced component, ask which unit is billed, expected volumes, retry behaviour, budget limits and who receives usage alerts. Record the supplier’s billing currency and quotation date. Where a Kenyan quotation includes foreign-currency services, clarify the conversion basis and any separately confirmed tax treatment; this guide supplies neither an exchange-rate forecast nor a tax assumption.
Compare two quotations using the same worksheet
Deliverable
Question to resolve: Which exact workflow and outcome are included?
Connections
Question to resolve: Which systems, interfaces and environments are included?
Inputs
Question to resolve: Which layouts, records, volumes and languages are supported?
Exceptions
Question to resolve: Which cases pause, retry or return to a person?
Fees
Question to resolve: What is one-off, recurring, usage-based or third-party?
Acceptance
Question to resolve: Which tests and approval determine completion?
Ownership
Question to resolve: Who controls accounts, workflow definitions and documentation?
Changes
Question to resolve: What needs a new estimate and approval?
A cheaper headline can reflect omitted support, different volumes or a narrower integration. Resolve those differences before comparing totals. Avoid treating an expensive proposal as proof of better quality; ask for the specific work and evidence behind it.
Use a pilot to reduce uncertainty, not hide missing scope
A bounded pilot can test a difficult input or connection before a wider commitment. Specify the pilot’s samples, outputs, review criteria and what is reusable afterward. It should end with an explicit decision to proceed, revise or stop, rather than an assumption that production is already accepted.
For example, an illustrative invoice pilot may cover one intake channel and a small agreed range of document layouts, ending at human review. Adding more layouts, integration destinations or automated write actions is then visible as a scope change. This is an example of scoping, not an offered fixed-price pilot or a client result.
Make the business case without inventing returns
Estimate current handling effort, rework and waiting separately. Then measure the implemented process using the same definitions, including review effort and failed cases. Recovered staff time may improve service or capacity without directly reducing payroll cost.
Record assumptions and uncertainty. A business case should not assume that every minute saved becomes cash, that all exceptions disappear or that customer demand stays constant. Decide which outcome actually matters: speed, consistency, control, capacity or a combination.
What to bring to a consultation
Prepare a process outline, approximate activity volumes, the systems involved, required roles and a few safe representative examples. Describe sensitive data rather than submitting it through a public form. Mention deadlines and dependencies, and explain one case that routinely goes wrong.
This gives AI Business Automation a concrete requirement to scope. Read which workflows to automate first and AI versus rules-based automation before comparing implementation approaches.
Request a scoped automation discussion