How to price n8n and Make automation work

Short answer

Use a fixed fee for a clearly scoped build, a monthly retainer for support and changes, and think about value-based pricing when the client can name what the automation saves them. Hourly is simplest, and also the model that punishes you for being fast.

The four models

Fixed fee per project

You quote one price for a defined outcome. It works when the scope is clear: "when a Shopify order is paid, create a row in Sheets and send a Slack message". It goes wrong when the client adds things as you go. Write what is in scope and what is not, and say how change requests are handled.

Hourly

Easy to explain and easy to compare. The weakness is that your income is tied to your speed. If a build you have done ten times takes you two hours, hourly pay shrinks while the value to the client stays the same.

Monthly retainer

A recurring fee for monitoring, fixing breakages and small changes. Automations break: an API changes, a token expires, a field is renamed. A retainer pays you for being the person who notices. Define response time and what counts as a small change.

Value-based

You tie the price to what the work saves or earns. One common rule of thumb in freelance advice is a share of the first-year savings, with figures often given as 25 to 50 percent. That number is a rule of thumb from advice articles, not a standard. It only works if the client can state the saving and trusts the estimate.

What other guides claim for n8n

LearnForge published an n8n freelancing guide on July 7, 2026. It claims first projects of $500 to $1,500, hourly consulting of $60 to $120, and retainers of $500 to $2,000. These are that site's claims, and the page gives no data source for them. Use them as a rough picture of what sellers say, not as market rates. Your own rate depends on your niche, your location and how bad the client's problem is.

The n8n license point most pricing guides skip

n8n is source available under the Sustainable Use License, and there are limits on how you can use it commercially. Based on n8n's license documentation, here is how it applies to consultants:

• Providing consulting services related to n8n, such as building workflows, is listed as allowed.
• Setting n8n up or maintaining it on a company's own internal server is listed as allowed.
• White-labeling n8n and offering it to your customers for money, or hosting n8n and charging people to access it, is listed as not allowed.

This changes your pricing. Price the build and the support, not access to the tool. If you want to sell hosted n8n, read the license and n8n's commercial options first. This is not legal advice. Check the current text before you structure a deal.

Make has its own plans and terms. Check them as well, since a client may need their own Make account, and operations are billed by Make.

Include running costs

Spell out who pays for:

• the automation platform plan (client or you)
• third-party API fees
• hosting, if any
• your time for monitoring

Many disputes come from a client who thought "automation" meant free forever. Put a line in the quote.

A simple way to quote

1. Write down the trigger, the steps and the result in plain words.
2. List the accounts and access you need from the client.
3. Estimate your hours, add time for testing and handover.
4. Add a buffer for unknowns. Say it is a buffer.
5. Offer two choices: a fixed build, or build plus a monthly plan.

Offering two options often makes it easier for a client to pick one than to say yes or no to a single quote. We have no test data on that, so try it and see what your clients do.

When you subcontract

If you take work from an agency or a partner program, the price is split. A common approach in subcontracting advice is to negotiate your margin before you start. Ask what the client pays, what the agency takes, and what costs come out first. Our own model is explained in white label and partner programs.

A worked example of the arithmetic

The numbers below are made up to show the method. They are not market rates. Say a client wants new Shopify orders copied into a spreadsheet and a Slack message sent to the fulfilment person.

• You estimate 3 hours to build, 1 hour to test, 1 hour for handover and notes. That is 5 hours.
• At your own hourly rate, multiply by 5. Add a buffer of one more hour because the client's data has odd cases. Say so in the quote.
• Support: you expect about 1 hour a month for small fixes and watching for failures. That becomes your monthly plan price, using the same rate.

Now compare with the value side. If the fulfilment person spends 20 minutes a day copying orders by hand, that is a few hours a month the client no longer pays for. You do not need to promise a saving. You can ask the client what that time costs them and let them tell you. Their answer tells you whether a higher fixed fee is realistic.

Write the assumptions in the quote, for example the number of orders a day. If volume doubles, the price may need to change, and the client should know that from the start.

Raise prices as you learn

If everyone says yes right away, you are probably too cheap. Raise the price on the next quote and see what happens. Keep notes on how long each build took, so you can price the next similar one.

Where this applies to store work

Shopify store care is priced differently, because the work recurs. See Shopify store care retainers.

Where to find clients to price for

Pricing is only useful when someone asks for a quote. See getting your first automation clients without Upwork.

If you want someone else to handle quotes and billing

Thomas Partners brings client work and runs the client side, including billing. The partner keeps 90% of the profit after itemized, documented costs, and if there is no profit, there is no fee. You can apply here whenever you like.

See also: Error handling for client automations in n8n and Make.