"How much does this cost" is usually the first question and the hardest one to get a straight answer to. Automation pricing varies wildly because the work itself varies wildly, one integration between two tools is a different job than an entire operational system. But "it depends" isn't useful to anyone trying to budget, so here's what actually drives the number, and real figures instead of a vague range.
What actually drives the price
Number of connected tools. A workflow that moves data between two tools is simpler than one coordinating five. Each extra connection is another set of edge cases: what happens when a field is empty, when an API is slow, when two systems disagree about the same record.
How much logic is involved. Moving data from A to B is cheap. Deciding what to do with that data, routing it differently based on conditions, transforming it, validating it, handling failures gracefully, is where the real work is. A workflow that just copies data is a different project than one that makes decisions.
How reliable it needs to be. A personal automation that emails you a weekly summary can fail quietly and you'll notice eventually. A workflow that processes client payments or sends invoices cannot fail quietly. Building in proper error handling, alerts, and retry logic takes real time, and it should, because the cost of it failing is higher.
One-off build versus ongoing system. A single workflow solving one problem is a fixed, scoped project. An operational system with multiple interconnected workflows, documentation, and a support period behind it is a bigger undertaking, and priced accordingly.
What this actually looks like in numbers
I price in fixed packages rather than hourly, specifically so you know the cost before anything starts. As a reference point:
A single focused workflow (one problem, cleanly scoped) starts around €497. Support included: 14 days.
A few connected workflows working together, more integration points, starts around €897. Support: 21 days.
A full operational area built and connected, documentation and a screen recording walkthrough included, starts around €1,497. Support: 45 days.
An entire business infrastructure, mapped, built, and documented from the ground up, starts around €3,997. Support: 60 days.
These are fixed prices, agreed before work starts, not estimates that grow as the project goes. What changes the price within each tier is scope: more tools, more logic, more edge cases to handle properly.
What's usually missing from a cheaper quote
The lowest quote you get is rarely the same scope as the highest one. Common things left out of a cheap quote: documentation of how the system works, a support period after delivery, proper error handling so the workflow doesn't fail silently, and ownership of what gets built (some cheap builds run inside the builder's own account, which means you're locked in).
None of these show up when you're comparing numbers on a call. They show up three months later, when something breaks and there's no one to call, or when you realize you don't actually control what you paid for.
What drives the price down, legitimately
The honest ways to spend less: a smaller, more focused scope (automate one thing well instead of everything at once), being clear about your process before the project starts (ambiguity costs time), and not needing every edge case handled if the workflow is low-stakes and internal-only.
The dishonest way costs are cut is by skipping error handling, skipping documentation, or building it in a way that locks you into paying the same person forever. Worth asking about directly if a quote looks unusually low.
If you want a real number for your specific situation instead of a general range, book a free discovery call and I'll scope it honestly, including telling you if it's smaller (and cheaper) than you think.