Iron Goo
Two professionals compare six tagged boxes on a meeting room table, with one opening a metal toolbox.

Build vs buy AI automation: 6 options, dated price matrix

Atamyrat Hangeldiyev
Atamyrat Hangeldiyev
Systems Architect
January 18, 2026
On this page
AI & Automation

Say you run a hypothetical 40-person online retailer of spare parts. You have picked one job: answer or route 2,000 support emails a month, with six ways to automate it on the table. The build vs buy AI automation decision starts with a surprising number: at the assumed token volume, cheap models cost $0.80 a month. Choose by the billing unit, where the data sits, what transfers when you leave, and who gets paged when it breaks.

Six options compared for the same support inbox

Prices were read on 24 October 2026; check the vendor page before relying on them. Dollar amounts are USD, euro amounts remain in EUR, and annual billing prices are monthly equivalents with an annual commitment. Time estimates are planning assumptions, not measured delivery promises.

CriterionVertical SaaSNo-code platformSelf-hosted n8nAssistant builderCustom codeAgency
Time to first resultAssumption: days with usable help contentAssumption: days for a connected pilotAssumption: days with hosting skillsAssumption: hours for chat; days for event agentAssumption: 40 to 80 build hoursAssumption: weeks, scope dependent
Monthly cost for worked jobFin: $990 for 1,000 outcomes, plus helpdeskZapier: $129 annual billing or $193.50 monthly; n8n Cloud: EUR 20 annual billing; each plus $0.80 modelEUR 6.49 server + $0.80 model + assumed 2 to 4 upkeep hoursCopilot: two packs $400, or one pack plus reported pay-as-you-go about $390; five chat seats: $100 to $125, different job$0.80 model + EUR 6.49 server + maintenanceCodewave estimate: $1,000 to $3,500 retainer, plus agreed platform charges
Data control and residencyHelpdesk, AI service and contract dependentZapier: US; Make: US/EU with AI exceptions; n8n Cloud: FrankfurtChosen host; external AI receives requestsAzure geography or workspace terms; feature exceptionsChosen host plus model endpoint rulesUnderlying stack and contract decide
Lock-in and exit costHistory and tuning need separate checksZap JSON stays in Zapier; n8n JSON runs on n8nWorkflow JSON; connections need rebuildingMicrosoft solutions; chat instructions need separate captureRepository portable; API behavior still vendor dependentOwnership and handover clauses decide
Who maintains itVendor platform; you own content and rulesVendor platform; you own workflowsYou own patches and workflowsVendor service; you own agent configurationYour engineering teamAgency within contracted scope
Failure handlingVendor operation; spending and handoff controlsZapier autoreplay; n8n error workflowsYour error workflows and monitoringCopilot capacity enforcement can disable agentsYour retries, queue and alertsWhatever the service agreement specifies
Security review burdenVendor and helpdesk reviewPlatform plus AI provider reviewHost, runtime, patches and access reviewTenant, identity, knowledge and connector reviewApplication, secrets, dependencies and providersAgency access plus underlying vendors
Best fitStandard support processConnected applications and visible workflowsTeam with an available operatorHuman drafting or event-capable enterprise agentsUnusual rules and durable engineering ownershipCompany buying implementation and operation capacity

Treat data control and security review as separate criteria. Choosing a server location answers a storage question; it does not establish who patches the workflow engine or which model provider receives an email. If procurement needs evidence, use the automation governance and access rules checklist to turn a vendor questionnaire into checks someone can actually complete.

Vertical SaaS: Fin wins when support is already standardized

Wins when: Your existing helpdesk contains the customer history and the policies needed to answer repeat questions. A support-specific product removes much of the work of joining an inbox to a model and a ticket system. You still need to define which answers it may send and which requests require a person.

Fin charges $0.99 per outcome. Assume half of the 2,000 monthly conversations become billed outcomes: 1,000 multiplied by $0.99 produces a $990 monthly charge, plus your helpdesk costs. For a non-Intercom helpdesk, the minimum is $49 a month including 50 outcomes.

An outcome has a contractual definition, not your preferred interpretation of success. Fin includes a completed Procedure, including handoffs, and charges once per conversation; the charge is refunded if the conversation reopens. Read the Fin outcome definition and pricing before equating a billed outcome with a customer served entirely without human help.

Loses when: Your process depends on awkward internal systems or unusual approval rules that the product cannot express cleanly. It can also lose on cost when a simple, repeatable workflow attracts a substantial per-outcome bill. The $990 figure purchases a support product and its operation; comparing it directly with $0.80 of model tokens omits most of what you are buying.

For data residency, request the processing locations for both the helpdesk and the AI service. The price page alone does not establish a suitable region or explain every subprocessor. Ask separately what happens to conversation history, knowledge content and tuned behavior when you terminate the service.

Before buying, run an observable acceptance check: a known order-status question receives the right answer, a return outside policy reaches a person, and a reopened conversation behaves as the billing definition promises. Set spending alerts and limits before expanding access. A technically correct answer delivered outside your returns policy is still a support problem.

No-code platforms: Zapier vs Make vs n8n for AI workflows

Wins when: Your applications already have usable connectors and the job consists of recognizable steps. For the hypothetical retailer, assume four billable action steps per email: look up the order, generate a reply, post the reply or draft, and tag the ticket. That produces 8,000 action steps across 2,000 emails.

Zapier counts successful action steps as tasks; triggers and built-in Filter, Formatter and Paths steps do not count. Its Professional 5,000-task tier costs $89 a month with annual billing or $133.50 monthly, with tasks beyond the included 5,000 charged at a higher per-task rate through pay-per-task billing, up to the maximum task limit. The 10,000-task tier includes the assumed 8,000 tasks and costs $129 with annual billing or $193.50 monthly, before the separate model bill.

n8n Cloud charges per execution of the whole workflow regardless of its step count. Starter supplies 2,500 executions and five concurrent executions for EUR 20 a month with annual billing, so the assumed 2,000 runs fit. Pro supplies 10,000 executions for EUR 50 a month with annual billing; Business at EUR 667 a month is self-hosted only.

Make's Free plan includes 1,000 credits a month. Most module actions consume one credit, while its own AI provider can charge credits by token volume; bringing your own AI provider key uses one credit per operation. Make's paid prices are not listed here.

The meaningful Zapier vs Make vs n8n comparison therefore starts with an actual workflow diagram. Count billable actions for Zapier, inspect module and AI credit rules for Make, and count whole runs for n8n. A four-step job and a forty-step job can have the same execution count while producing very different task bills.

Data location depends on the platform and the AI connection

Zapier stores customer data in AWS US-East 1, with region-specific residency unavailable unless otherwise agreed. n8n Cloud stores hosted-plan data in Frankfurt, Germany. Neither statement establishes where an external model processes the prompt you send it.

You choose a US or EU data center when creating a Make organization. Make's help center says you cannot change the data center location after creating the organization. Some AI features route to the US or UK, and bringing your own AI connection removes Make's EU guarantee. Check the Make AI provider and data-zone exceptions against the exact feature you intend to use.

Retries can delay the first error email

Zapier autoreplay is available on all plans, including Free. It attempts up to five replays at intervals of five minutes, thirty minutes, one hour, three hours and six hours. The last attempt occurs about ten hours and thirty-five minutes after the first error.

Zapier sends no error notification email until that final attempt fails. Its autoreplay documentation therefore describes a potentially long silent window for an inbox that needs prompt responses. Autoreplay applies to errored runs, not safely halted runs.

Loses when: Connector behavior cannot express your business rules, or nobody owns the workflow after launch. Configure an independent backlog check if ten hours without an error email would breach your response target. In n8n, assign an error workflow through Workflow Settings and verify that a deliberately failed execution reaches the responsible person.

Self-hosted n8n: control comes with a patching job

Wins when: You need to choose the hosting location and have someone who can operate a networked application. n8n Community Edition is available without a software subscription under its Sustainable Use License; internal company automation appears to fit that use. Review the license separately if you plan to expose an instance to clients.

For the cost example, assume a EUR 6.49 monthly server, $0.80 in model usage, and two to four upkeep hours a month. The server figure comes from Hetzner's shared-vCPU offerings and excludes VAT. Those hours are a budgeting assumption, not a promise that patching and incidents stop after four hours.

Compared with n8n Cloud, the execution meter is no longer the central monthly charge. You take responsibility for availability, backups and upgrades, including monitoring whether executions are completing. Exported workflow JSON can move to another n8n instance, but credentials and environment-specific configuration still require work.

Loses when: Nobody has a named patching responsibility or the authority to interrupt service for an upgrade. Self-hosting changes who controls the server and who must repair it. It does not establish that the deployment is safe.

By our count, the GitHub Advisory Database published 21 critical and 58 high-severity advisories for the npm package n8n between 1 January and 24 October 2026. We queried the public advisory API separately for critical and high severity, filtered the results by publication date, and counted entries affecting that package. These are our counts, not figures published by n8n; the n8n security advisory list provides the underlying notices.

Do not read those totals as 79 vulnerabilities exploitable against every installation. Several required an authenticated user who could edit workflows, and some advisories state that n8n Cloud instances were affected too. On Cloud, applying the fix is n8n's job; on your own server, checking applicability and installing the fixed release belongs to your operator.

Before choosing self-hosting, require a successful backup restoration and a demonstrated alert from a failed workflow. Record who receives security notices and who installs urgent updates when the usual owner is unavailable. If those names are blank, n8n Cloud's higher subscription is buying a responsibility you have not staffed.

Assistant builders: separate chat seats from event-driven agents

Wins when: People need help reading material or drafting answers, or your selected agent builder supports the event that starts the job. GPTs, Claude Projects and the Gemini app are chat workspaces built around a person starting the work. Before relying on one for an arriving support email, check whether its scheduling or event features actually fit that job.

A custom GPT vs building on the API is therefore partly a trigger decision, as is Claude Projects vs a custom chatbot. Claude Pro and higher plans can schedule Cowork tasks to run on a timer (hourly at most) without anyone present, but a schedule is not an event trigger: it polls rather than reacting when an email arrives (Anthropic support). Scheduling is a Cowork feature, not Projects. My opinion is that a chat workspace is the wrong shape for this event-driven inbox job unless you deliberately keep a person as the trigger.

For five support staff, ChatGPT Business Standard seats cost $100 a month with annual billing or $125 with monthly billing. Those prices, and its two-seat minimum, come from OpenAI's help center. Claude Team Standard has the same per-seat prices for teams of two to 150; custom retention controls and audit logs are Enterprise features.

Gemini Enterprise Business starts at $21 per seat per month, so five seats start at $105 monthly. Standard and Plus prices are not published. Google's editions table, updated 22 October 2026, marks building custom no-code agents as a preview feature; confirm availability before depending on it.

Copilot Studio bills the unattended job in credits

Copilot Studio can support an event-triggered agent, including a job autonomously triggered by an incoming order. For the hypothetical email workflow, assume one generative answer at two credits and four agent actions at five credits each. That makes 22 credits per email, or 44,000 credits a month.

A prepaid pack supplies 25,000 credits for $200 a month, so the worked job requires two packs at $400 monthly. Alternatively, one pack plus linked pay-as-you-go would cost about $390: $200 plus 19,000 excess credits multiplied by the reported $0.01 rate. Licensing guides report that per-credit rate; it was not confirmed on Microsoft's own page.

Microsoft's own order-processing example bills only the agent actions. Triggers and other steps may also be billable, so the assumed 22 credits per email may undercount the complete workflow; test it with the usage estimator or a pilot. Other features have different meters, including tenant graph grounding at ten credits and agent flow actions at thirteen credits per hundred actions.

No-charge employee-facing use applies to Microsoft 365 Copilot licensed users acting under their own identity. The Microsoft 365 Copilot add-on costs $30 per user per month with annual billing. An autonomous agent triggered by an arriving email consumes credits.

One Copilot pack runs into enforcement around day 21

Assume 44,000 credits spread evenly across a 30-day month, with one prepaid pack and no linked pay-as-you-go. The 125% enforcement threshold is 31,250 credits: 31,250 divided by 1,466.67 credits per day is about 21.3 days. Custom agents are then disabled.

Microsoft's Copilot Credit rates and enforcement rules distinguish custom agents from agent flows: agent flows are blocked once prepaid capacity is fully consumed. Linked pay-as-you-go avoids prepaid overage enforcement by billing the excess to Azure. Set per-agent monthly limits in Power Platform admin center and test the notification route.

Regional settings have product-specific limits

Copilot Studio stores customer data in the selected Azure geography, with exceptions involving global metadata, external services and some Microsoft 365-powered features. Gemini Enterprise offers global, us and eu locations, plus in-country regions including Canada, India, Japan, Singapore and the UK through an allowlist arranged with the Google account team. Regional processing still has feature limits: some features are global-only, and Gemini 3.1 Pro supports US residency without EU residency support.

OpenAI has reported European residency options for new Enterprise and Edu workspaces and new API projects; that does not establish availability for ChatGPT Business. Claude's API defaults to global processing, with a US inference option carrying a 1.1 multiplier for Claude 4.6 and later. Workspace residency and API processing are separate procurement questions.

Loses when: You price five chat seats as though they perform the same unattended job as a triggered agent. It also loses when a required knowledge source, regional feature or export component is unavailable. Require a test initiated by an arriving email, without someone opening the chat, before accepting an agent-builder proposal.

Custom code: a tiny model bill still needs engineering ownership

Wins when: The workflow has unusual rules, your systems expose usable APIs, and an engineering team can own the service after launch. You control the repository and can make failure behavior explicit. That includes retry limits, duplicate prevention and a queue for work that could not be completed.

Assume 40 to 80 build hours for a bounded pilot. BetonAI reports a median implementation rate of $185 per hour from what it describes as a survey of 68 independent AI consultants conducted in May and June 2026, with no further detail published. These are independent consultant rates, not agency rates; applying the median to the assumed hours produces an illustrative $7,400 to $14,800 build allowance. This is arithmetic using an assumed scope and a reported rate, not a quote for your inbox.

The model allowance is much smaller. At $0.10 per million input tokens and $0.50 per million output tokens, both gpt-6-luna and Claude Haiku 5.5 produce the $0.80 calculation used here; Haiku's quoted rates apply to prompts up to 100,000 tokens. Hosting, retrieval tools and storage can add separate charges.

Regional requirements can change that line. OpenAI regional processing endpoints carry a 10% uplift for models released on or after 5 March 2026, while Claude's US inference option carries the multiplier described earlier. Choose the processing endpoint before approving the data flow.

Loses when: Ownership means “the developer who had time last month.” Your repository still depends on vendor interfaces and model behavior. A replacement model may require evaluation changes even when the API call looks similar.

OpenAI notified developers on 26 August 2025 that the Assistants API would be removed, then removed it on 26 August 2026. The replacement is the Responses API with the Conversations API, as recorded in OpenAI's API deprecation history. Anthropic promises at least sixty days' notice before retirement of publicly released models.

Those dates become maintenance work in your backlog. Budget an owner for dependency notices, replacement-model evaluation and release testing using the automation maintenance responsibilities. Owning code gives you more ways to respond; it does not cancel the vendor's calendar.

An agency: buy accountable capacity and specify the handover

Wins when: You have a clear job and somebody internally who can approve business rules, but lack implementation or operating capacity. An agency can build on any of the underlying platforms. Its fee buys labor and responsibility, while the platform's billing and residency rules continue to apply.

Codewave, an agency, puts typical small-business pilots at $1,500 to $8,000 and retainers at $1,000 to $3,500 a month, without citing a source. These are one agency's estimates, not a quote. Ask whether platform subscriptions, incident response and change requests are included.

Iron Goo builds and operates automations, and its operations automation engagements include an exit plan. If you hire us or another provider, ask exactly which workflows, configuration and logs transfer, in what format, and when. Put the answer in the agreement.

Loses when: “Managed” has no specified response time or you cannot recover the accounts needed to run the system. Require company-controlled vendor accounts where practical, and define how credentials are transferred or rotated. A retainer that covers improvements may still exclude an overnight outage.

For AI agency vs in-house build, compare available capacity against named responsibilities. Someone must approve policy changes, investigate failed runs and accept releases. Gartner's 25 June 2025 prediction that over 40% of agentic AI projects would be canceled by the end of 2027 concerns organizations at large; it is a prediction, not a measured failure rate for a company automating one inbox.

The worked monthly bill: one inbox, six billing units

Assume 2,000 emails, one workflow run per email, four billable actions per run, and 2,000 input plus 400 output tokens per email, including retrieved order and policy text. Assume 50% become billed outcomes, and five people need seats where a person operates the assistant. Every figure here depends on those assumptions.

One stream of support emails feeds six meters for outcomes, tasks, executions, credits, seats and tokens.

The incoming work stays the same while the billing unit changes. A seat buys access for a person; an execution pays for a workflow run.

Monthly model cost for the assumed email volume

monthly_model_cost = 2000 * ((2000 * 0.10) + (400 * 0.50)) / 1000000 = $0.80

The formula uses prices per million tokens and excludes retries or additional model calls. At $2 per million input tokens and $10 per million output tokens, the same token assumptions produce $16 monthly. Model choice changes the allowance, but neither amount describes the whole operating cost.

Option and meterEvery inputMonthly result and separate costs
Fin: outcomes2,000 emails × 50% × $0.99$990, plus existing helpdesk; $49 minimum includes 50 outcomes
Zapier: tasks2,000 × 4 = 8,000 tasks; Professional 10K tier$129 with annual billing or $193.50 monthly, plus $0.80 model
n8n Cloud: executions2,000 runs; Starter allowance 2,500; five concurrentEUR 20 with annual billing, plus $0.80 model
Self-hosted n8n: infrastructure and hoursAssumed EUR 6.49 server; assumed 2 to 4 upkeep hoursEUR 6.49 + $0.80 model + upkeep hours × your hourly cost
Copilot Studio: credits2,000 × (2 + 4 × 5) = 44,000 credits; 22 credits per email may undercount because triggers and other steps may be billableTwo 25,000-credit packs = $400; or one pack plus linked pay-as-you-go at the reported $0.01 rate: $200 + 19,000 × $0.01 = about $390
Chat assistants: seatsFive seats × $20 annual-billing equivalent or $25 monthly$100 or $125 monthly; Gemini starts at five × $21 = $105; human-triggered work
Custom API code: tokens and infrastructureFormula above; assumed EUR 6.49 server; 40 to 80 build hours × $185/hour median from BetonAI's survey of independent consultants$0.80 + EUR 6.49 monthly before maintenance; illustrative build $7,400 to $14,800
Agency: project and retainerCodewave's estimates (one agency, no source cited)$1,500 to $8,000 pilot; $1,000 to $3,500 monthly retainer; platform charges per agreement

The six meters produce eight rows because the platform category has multiple products, while assistant builders include both seats and event-driven credits. Human review time is omitted from these comparisons; use the full automation cost calculation to add it. That omission especially affects the seat-based option, where a person still starts and checks the work.

The exit test: require a file, a destination and a missing-items list

Before signing, ask three questions and record the answers in the purchase approval. Require a sample export where one exists. A screenshot of a workflow is documentation, but it cannot restart your inbox.

Exit doors show portable workflow boxes beside boxes chained to the platform they came from.

The useful distinction is whether the exported work can run at your next destination. A downloadable file can still depend entirely on the original platform.

  1. What file do you get? Zapier exports Zap JSON; n8n exports workflow JSON; Copilot Studio exports an unmanaged solution. Capture chat instructions and knowledge files separately. For custom code, require the repository; for an agency, specify deliverables in the contract.
  2. Where can it run? Zap JSON reimports into Zapier, with no documented cross-platform importer here. n8n JSON runs on another n8n instance, including your own server. Copilot solutions move between Microsoft environments; your repository still needs its runtime and integrations.
  3. What is missing? Check credentials, run history, knowledge sources, tuned prompts and environment configuration. For vertical SaaS, establish whether conversation history and tuning can be extracted. Treat every connection as needing reauthorization until a migration test proves otherwise.

Copilot Studio cannot export managed solutions, and some custom topics or knowledge sources may be absent when stored as separate resources or Dataverse tables. Its solution export limitations make a successful export insufficient evidence of a complete handover. Import into a separate environment and check the missing components.

For this inbox, finish the exit test with three controlled messages: an order-status request, a policy exception and a request whose order lookup fails. Verify the destination produces the expected answer or draft, routes the exception and alerts on the failed lookup. Keep the original service available until those checks pass and you have accounted for messages arriving during the switch.

Free ebook

Put your next steps in order

Build on what you have just read with a free ebook on semantic SEO and AI visibility. Get worked examples, decision rules, checklists and a do-this-week action in every chapter, plus a six-week plan for your site.

By signing up and confirming your address, you consent to receive the free ebook plus one email every two weeks with 3 or 4 new Iron Goo videos, guides and articles, and nothing else; unsubscribe any time with one click.

Related in AI & Automation

Ready to move?

Tell us where your business is today. A written assessment lands in your inbox within two business days.

Talk to us