What do AI automation agencies charge, and when is building it yourself with n8n enough?

What do automation agencies charge?

In US dollars, BULDRR AI, which sells n8n services, publishes $400 to $1,200 one-time for a single workflow with 1 to 3 integrations, $1,500 to $4,500 for a multi-workflow build with one AI layer and 4 to 10 integrations, and $1,200 to $8,000 a month for an ongoing partner retainer¹. It bills AI model usage directly to the client without markup¹.

The Bet on AI rate card, updated on 20 September 2026 and based on invoices from 54 freelancers and agencies between January and June 2026, lists lead capture to a CRM at $900 to $1,800 on n8n and $650 to $1,400 on Zapier or Make, plus about $400 for an AI step. Retainers are $650 to $1,200 a month for a solo or small business and $2,500 to $6,000 for AI-agent work². It says Latin American and Southeast Asian work prices at roughly 35 to 55 percent of its table². The card contradicts itself in places, for example its summary retainer range differs from its tables, so use it as a rough guide only.

In India, SOT Labs, an automation studio in Jodhpur, publishes set-up from Rs 50,000 for operations automation and from Rs 60,000 for lead follow-up and CRM automation, plus Rs 6,000 and Rs 8,000 a month. Its retainers are Rs 40,000, Rs 80,000 (the middle one labelled most common) and Rs 1.5 lakh a month, all excluding 18 percent GST³. At about Rs 96.6 to the dollar (RBI reference rate, 9 October 2026), Rs 50,000 is about $520 and Rs 1.5 lakh is about $1,550⁶. All of these prices come from sellers, so treat them as asking prices.

What does it cost to do it yourself?

The software is cheap. n8n Cloud Starter is €20 a month billed annually with unlimited users and workflows, and Pro is €50⁴. Make lists $9 a month for 5,000 credits⁷, and Zapier Pro is $19.99 a month billed annually or $29.99 billed monthly for 750 tasks⁸.

Your own time is the larger cost. BULDRR's checklist for hiring an agency lists failure alerts and retry logic, staging tests, documentation and change requests as the things to ask about⁹. A first workflow is quick to build. Making it reliable is the slow part.

Is self-hosting n8n really free?

The Community Edition is free, but running it is not. n8n's own comparison says self-hosting needs technical expertise to install and configure, that you provide and manage the infrastructure, and that maintenance is your responsibility. Cloud is fully managed, with n8n handling hosting, updates and scaling⁵.

Estimates of that upkeep vary widely. Ali Farhat, founder of Scalevise, lists a full self-hosted programme at $1,150 to $2,000 or more a month, including $600 to $1,000 for 6 to 10 hours of DevOps maintenance, and describes one team spending 6 hours a week¹⁰. His list also includes compliance and audit preparation at $250 or more a month, which many small teams will not need. Take it as one practitioner's estimate. The point that holds is that the cost of self-hosting is time and ownership, not licences.

Does n8n's licence let someone build workflows for you?

n8n's licence, the Sustainable Use License, permits using and modifying the software for your own company's internal operations or for personal and non-commercial purposes, and sharing it only free of charge and non-commercially. Files marked as enterprise need an n8n Enterprise Licence¹¹.

A forum user reported in December 2025 that n8n's help centre had told them that running automations for clients fits internal business purposes if the clients never access the instance, and that reselling, white-labelling or giving clients direct access needs a commercial or enterprise licence¹². That is a report of a support reply, not a licence amendment. The cleanest arrangement is an instance in your own account, and a community answer on client work advises that clients connect their own accounts and that each client gets a separate n8n account¹³. Ask any agency which licence covers your arrangement.

When is DIY enough, and when should you hire?

Build it yourself when you need one or two workflows, a failure is cheap (an internal alert, a form to a sheet), someone on your team will own it, and you use n8n Cloud rather than self-hosting. Hire when a failure costs customers or money, the workflow touches customer data, several systems and an AI step are involved, or nobody wants to own updates, backups and monitoring.

A caution from outside n8n: press coverage of MIT's NANDA study says tools bought from specialist vendors or built through partnerships succeeded about 67 percent of the time, and internal builds about one third as often, while about 5 percent of AI pilots reached rapid revenue acceleration¹⁴. It is about company AI pilots, not n8n workflows, and the source is press coverage, so use it as a caution and not a rule.

If you hire, ask in writing for these:

• Admin access and the workflows in your own account at delivery⁹.
• Credentials stored in your accounts, with documentation for each workflow⁹.
• What is billed separately, such as fixes after an API change, testing and documentation⁹.
• Failure alerts, retry logic and a response time for fixes⁹.