Published 21 November 2026 by the Scriptguru team
When a business asks what it costs to connect its systems or automate a process, it usually gets one number: the build price. That number matters, but it is rarely the whole cost, and it is often not the biggest one over three years. This guide breaks a typical project into the parts you will actually pay for, so you can compare quotes properly and budget without surprises.
The five parts of the cost
1. Working out what to build
Before anyone can give you a fixed price, someone has to understand the process: where the information arrives, which systems it passes through, who makes which decisions, and what goes wrong. Some firms do this for free and add it into the build. Others charge for a short assessment. We charge $2,500 for a two-week audit and credit it in full against the build, because a paid assessment gets done properly and you keep the findings even if you go elsewhere.
2. The build
This is the part everyone quotes. For a single connection between two systems, expect a few thousand dollars at the low end. For a proper system covering three to five connected processes in one area of a business, such as accounts or order handling, prices from agencies in the US and UK commonly run from the low tens of thousands upwards. Our own prices are public: a single integration from $6,000, and a connected system of three to five workflows from $12,000, typically $12,000 to $18,000.
What moves the price most is not the number of steps, but:
- How many systems are involved, and whether they have modern connections or need custom work.
- How many exceptions there are, and how carefully each one has to be handled.
- How messy the existing data is. Cleaning up duplicate customers or inconsistent product codes can take longer than the automation itself.
- How sensitive the data is, and the access controls and logging that follow from that.
3. Software licences
Most systems run on, or connect to, software you pay for monthly: your accounting package, Microsoft 365, a workflow tool such as Power Automate or Make, a hosting account. Some of these you already have. Some projects add a new subscription. Always ask for a list of every licence the finished system needs, and whether it will be in your name. It should be.
4. AI usage
If the system uses AI to read documents, sort emails or draft replies, you pay the AI provider for each use. For most small and mid-sized businesses this is modest, often tens of dollars a month rather than hundreds, because each task uses very little. But it grows with volume, and pricing models change. Ask for an estimate based on your actual monthly volume, and make sure the account is yours so you can see the bill directly.
5. Keeping it running
This is the cost most quotes leave out. Systems you connect to change, logins expire, providers retire old connections and AI models are replaced. Something has to notice when a workflow fails and fix it. You can handle this in-house if someone understands the system, or pay for a monthly care plan. Ours starts at $1,000 a month and covers monitoring, fixes and small improvements. Either way, budget for it: an automation that quietly stops is often worse than none at all.
A worked example
Take a 60-person distribution business where two people spend most of their week keying supplier invoices into the accounts system and chasing mismatches against purchase orders. The project: read invoices from the accounts inbox, match them to orders, send exceptions to a manager to approve, and post approved invoices to accounts.
| Item | When | Typical amount |
|---|---|---|
| Audit and fixed quote | Once | $2,500, credited against the build |
| Build: three connected workflows | Once | $12,000 to $15,000 in total |
| New software licences | Monthly | Often none, if it runs on tools already in use |
| AI document reading | Monthly | Usually tens of dollars, depending on invoice volume |
| Care plan (optional) | Monthly | From $1,000 |
These figures are illustrative, based on our own pricing. Your own quote depends on your systems and volumes.
How to tell whether it is worth it
Work out what the manual process costs you today. Count the hours each week, multiply by what those hours cost the business, and add the cost of mistakes: late-payment charges, wrong orders, time spent fixing errors. Then compare that with the build price spread over two or three years, plus the running costs.
If the numbers are close, the project probably is not worth doing yet. If the manual work is costing several times more than the system would, it usually is. And if you cannot put any figure on the manual work, that is the first thing to find out, before talking to anyone about building.
Common ways budgets go wrong
- Choosing on build price alone, then finding the cheapest quote left out exceptions, testing or handover.
- Automating a broken process. If the process itself is unclear, automation makes the confusion faster. Fix the process first.
- No owner after launch. Nobody budgets for upkeep, the system drifts, and the team goes back to doing it by hand.
- Building in someone else's accounts. If the supplier holds the logins, leaving them is expensive.
A good project should be able to show you, in writing, every cost you will pay in the first year. If a supplier cannot, keep asking until they do.