What an automation actually costs

A workflow is worth automating when it is repetitive, rule-based, and happens often enough that the time adds up. Everything else is a distraction.

The arithmetic is unglamorous: hours per week multiplied by fully loaded hourly cost multiplied by fifty-two. If that number is not several times the build cost within a year, do something else first.

We price implementation as a fixed fee rather than hourly, because hourly billing rewards slow work. You should know the number before the work starts.

Ongoing costs are usually small and belong to you: model usage, telephony minutes and the subscriptions you already pay for. We do not resell them.