Falnor / Guides

How process automation projects are priced, and what to ask before you sign

Automation pricing is hard to compare because providers price different things: a licence, an hourly rate, a build or an outcome. This guide explains the parts of a project price and the questions that reveal what you are really paying for.

Book a discovery call

The four parts of an automation project price

Mapping: writing down how one process really runs, its rules and its exceptions. A fixed fee, and you keep the map.
Build: the system for one named process, priced as a fixed amount agreed in writing before work starts.
First module or extension: an optional second piece once the first is proved.
Run and support: an ongoing fee for monitoring, changes and support, if you want it.

What drives the price

The number of systems the process touches.
How many exceptions and approval paths there are.
How much of the rulebook is written down today.
The volume and how risky a mistake would be.

Questions to ask any provider

Is the build a fixed price for a named process, or open-ended hours?
Do I own the system, its rules and its record, or do I rent them?
What do I see before it changes anything in my software?
What does it cost to run each month, and what is included?
What happens if I stop working with you?

How we do it at Falnor

We do not publish a price list, because the work differs. We map one process first, then you get the scope, timeline and fixed price in writing before anything is built, and the system starts read-only. To size the opportunity first, use the automation ROI calculator, and to compare with hiring, the automation vs hiring calculator.

Questions people ask

How much does process automation cost?

It depends on how many systems and exceptions the process involves. A good provider scopes one named process, then gives you a fixed price in writing before building. Use the ROI calculator to see whether the saving would cover it.

Is automation priced per hour or per project?

Both exist. Hourly work is open-ended. A fixed price per named process is easier to compare and puts the risk of overruns on the builder.

Do I pay a monthly fee?

Often for running and support. Ask what it covers and whether you own the system if you stop.

What does it cost to map a process?

It is usually a fixed fee, and you keep the map whether or not you build. Falnor agrees it in writing after the discovery call.