Most n8n freelancers price by guessing. The usual guess is the salary math: take what you earned employed, divide by 2,080 working hours in a year, and charge that per hour. It feels fair. It undercharges you by about a third, and the third it skips is the part that keeps you in business.
The mistake is the denominator. You do not bill 2,080 hours a year. Nobody does. You bill the hours a client pays for — and the rest of your working time goes to sales, scoping, admin, learning the next n8n release, and the gaps between projects. A realistic billable share is around 60% of your working hours. On a 2,000-hour year that is 1,200 billable hours, and every rate you quote has to be built on that number, not on 2,080.
The rate, worked through
The calculator at fasttools.me/freelance-rate-calculator runs the same math in four steps — salary to hourly, billable capacity, tax adjustment, and take-home pay. Here is the shape of it, with example numbers so you can follow the logic:
- Start from the take-home you need, not the salary you had. Say the target is $72,000 a year in your pocket. That is the number the rate has to deliver, after tax.
- Gross it up for tax. Freelance income carries self-employment tax on top of income tax. At a combined 25% the gross you need is $72,000 ÷ 0.75 = $96,000.
- Divide by billable hours, not working hours. $96,000 ÷ 1,200 billable hours = $80 an hour. The same target divided by 2,080 would have given you $46 — and that is the gap that eats freelancers alive.
- Check the day rate. $80 × 8 = $640 a day. Quote n8n build work by the day or by the sprint, not by the hour: a client buys an outcome (a working workflow), and a day rate keeps the conversation on the outcome instead of the clock.
The numbers above are an example, not a prescription — run your own target through the calculator and it gives you your hourly rate, day rate, and invoice totals with the tax adjustment included. The point is the method: take-home first, tax second, billable hours third. In that order, and never the other way round.
Why n8n work breaks hourly pricing
n8n work has a property hourly billing punishes: the better you get, the faster you finish. Your tenth HubSpot-to-Sheets sync takes a quarter of the time your first one did, and hourly billing pays you a quarter as much for it. Three things fix that:
- Day rates for builds. A workflow that takes three days to build and test is three day rates, whether the nodes took you six hours or sixteen. The client pays for a working system, and your speed becomes your margin instead of your penalty.
- Retainers for maintenance. Workflows break — APIs change, credentials expire, a node deprecates in a 3.0 release. A monthly retainer for monitoring and fixes is steadier income than chasing the next build, and it is what the client actually needs after go-live.
- Separate the run cost from your fee. Client workflows run on the client's n8n Cloud account, not yours: n8n Cloud — Cloud is the version client work should run on, with the executions, support, and uptime a business depends on. Your fee is for the build; their subscription is their infrastructure. Never bundle the two into one number you have to defend later.
What worked
Billable capacity is the whole trick. The day you stop dividing by 2,080, your rate jumps to where it should have been — and clients rarely blink, because the number finally matches the value of the work.
Day rates end the clock-watching. Scoping a build as "three days" instead of "twenty-four hours" changes the negotiation from cost to outcome, and it is how n8n work should be sold.
The calculator keeps the math honest. Salary to hourly, tax-adjusted 1099 rates, day rates, take-home pay — it runs the full chain in one place, free, with no login and no tracking.
What broke — or rather, what is hard
The first rate always feels too high. $80 an hour feels like a lot when your last salary worked out to $46. It is not a raise — it is the same money, once tax and unbillable time are counted. The calculator shows the working, which is what makes the number believable to you first.
Retainers are a second sale. Clients who happily pay for a build will hesitate at a monthly fee for "keeping it running" — until the first time a workflow breaks at 2 a.m. Price the retainer against the cost of the breakage, not the cost of your time.
Scope creep eats day rates. "Just one more node" is never one node. A day rate needs a written scope with it: what the workflow does, what it does not do, and what a change costs. Without that, the day rate quietly becomes an hourly rate again.
Who it is for
This fits if you build n8n workflows for clients and you are still pricing off your old salary. It fits less if you are on a full-time salary already and freelancing on the side — then the calculator's salary-to-hourly page still helps, but the tax picture is different. It does not fit if you only sell fixed-price products: the math is for selling your time well, not for pricing a template.
The deal, plainly
The calculator is free: fasttools.me/freelance-rate-calculator — no login, no tracking, your numbers stay in your browser. And if you are setting up client work, run it on n8n Cloud
Charge for the outcome, not the hours. The hours were never the product.
Alfaz Mahmud Rizve — GTM & RevOps Architect. I build autonomous revenue systems for scaling agencies and SaaS: SEO & organic growth, high-speed Next.js apps, and self-healing n8n workflows. whoisalfaz.me
Top comments (0)