A direct answer
How much does business automation cost?
There is no price list on this site, and this page will not invent one. Cost follows the process: how tangled the steps are, how many tools must connect, how often a person must review an exception, and whether a tool you already have can do the job. Price and timing are discussed and agreed before any paid work begins. A short introductory conversation has no cost and no obligation.
Why a single figure would be misleading
The same word — invoices, orders, a dashboard — can mean very different work. One path may be a stable export and a comparison you already trust. Another may be a stack of exceptions and a decision that should stay with a person. A single figure would hide that difference, so I will not offer one. What I can do is name what changes the size of the work, using the way the homepage already talks about price.
The homepage says that price and timing for an Automation Opportunity Review are discussed and agreed before any paid work begins, and that how long the Review takes depends on the process. It also says you do not need a Review first. If the problem is already clear, we can talk about building it directly. A short introductory conversation is separate from the Review. It is a conversation about the process and whether working together makes sense. It has no cost and no obligation, and it is not a consulting session.
What actually changes the size of the work
How settled the process is. If you can walk through the steps, the people, and the constraints, the work has an edge. If the steps change every time, someone has to understand them before anything is built. That understanding is part of the work, whether it happens in a Review or in the first part of an implementation.
How many places the information touches. Moving approved fields from one sheet to one tracker is a smaller connection than a path that also crosses email and a filing rule. Each extra place is another match to define. Stopping the copy between tools gets smaller once the source is clear.
How often a person must look. A review folder for uncertain invoices is the right design, and someone has to open it. A queue nobody reviews is unfinished. The human check is part of the scope. What should stay manual is the list I use.
Whether a tool you already have can do the job. If it can, the honest next step may be setup, not a build. A small custom app is for the gap that remains. Choosing the ready-made path when it fits keeps the project smaller. When a custom micro-app makes sense is that decision, without a claim that custom work is the bargain option or the expensive one.
How you will know it is working. Testing against agreed examples is part of the work, as is a fallback so the team can still finish the task by hand. Skipping the test moves the surprise onto a live day. How to start without disrupting the team keeps that test in the plan.
None of these is a rate. They are the questions to answer before a price is discussed. The price is agreed for your process, not copied from a table. Bring one process: how it works, which tools it touches, and what you check. Please do not send passwords, payment details, or private customer documents with that description.
When it is not worth it
It is not worth paying for automation when the task is rare, when you cannot describe it, or when a tool you already have would remove the repetition once it is set up. It is not worth a build when the “project” is really a decision that must stay with you or with a qualified professional.
It is also not worth chasing a low figure for a fuzzy scope. A small, described process with a visible check is the thing to price. A promise of a number before anyone has understood the process is not a plan I will make.