>TL;DR. For about 80% of small businesses, an iPaaS (integration-platform-as-a-service) like Zapier, Make, or n8n covers your integration needs at $20–$300 a month — versus $5,000–$50,000 to build custom, plus ongoing maintenance. Custom only wins on high volume, deep compliance, or vendor APIs that don't exist. Compare options in our automation and integration directory.
The question shows up on almost every Stack Audit we run: "Should we just hire a developer to build this, or use one of those tools like Zapier?"
It's a fair question, and the honest answer is: it depends — but probably not on what you think. The difference between iPaaS and custom integration in 2026 isn't feature parity (the gap is closing fast). It's about who pays the maintenance bill in year two, who owns the knowledge when the developer leaves, and how often the logic needs to change. If you want the architectural foundation behind this decision, our systems integration guide is the pillar piece. This article zooms in on the platform-vs-custom call.
What's the actual difference between iPaaS and custom integrations?
An iPaaS is software you rent that listens for events in one system and pushes data to another, configured through a visual builder rather than code. A custom integration is software you (or a developer) write from scratch — usually Node.js or Python running on a server, talking to APIs directly — that does the same job but is owned and maintained by you.
The four iPaaS platforms an SMB will realistically consider are Zapier (the easiest, most polished, biggest connector library), Make (the most visual, best for branched logic), n8n (the most flexible, with a free self-hosted option), and Workato (enterprise-grade, custom pricing, only worth it past a certain size). Custom is everything else — usually a developer or agency writing connector code against the REST APIs of each tool you want to bridge.
The lines blur in one important place: self-hosted n8n. When you run n8n on your own server, you get the visual builder of an iPaaS plus the control and zero-marginal-cost economics of custom — without writing connector code. For technically-comfortable SMBs, this is increasingly the default answer. We'll come back to it.
The 4-question test: do you need iPaaS or custom?
Most build-vs-buy debates resolve in under five minutes if you ask the right four questions. We use this exact sequence on Stack Audits.
Question 1: Will the integration run more than ~50,000 operations a month?
Most SMB integrations sit under 10,000 ops/month. Below that, iPaaS is cheaper than custom by an order of magnitude. The break-even point — where custom code on a queue becomes cheaper than per-task iPaaS pricing — generally lands between 50,000 and 200,000 operations a month, depending on the platform and the complexity of each operation. Below the line, iPaaS wins on cost. Above it, the math starts favoring custom.
Question 2: Is the data sensitive enough that it can't leave your infrastructure?
If you're moving HIPAA-protected health information, controlled financial data, or anything covered under a strict data-residency contract, sending it through a third-party iPaaS may violate your obligations — even with the vendor's BAA in hand. Real options: enterprise-tier iPaaS (Workato, Boomi) with the right certifications, self-hosted n8n on your own infrastructure, or fully custom code on servers you control. Self-hosted n8n splits the difference well for most regulated SMBs.
Question 3: Are you tying together systems that don't have a connector — or don't have an API at all?
iPaaS platforms work because they ship pre-built connectors to thousands of SaaS tools — Zapier claims 8,000+ apps; Make and n8n are smaller but cover the major SMB stack. The trouble starts when you need to integrate a niche vertical tool that doesn't have a connector. If it exposes a public API, most platforms can hit it via a generic HTTP module, but the experience drops sharply. If it has no API at all (still common in industry-specific software), you'll need custom code.
Question 4: Will the integration logic change more than once a quarter?
This is the question that usually decides it. iPaaS wins on iteration speed. Changing a Zapier or n8n flow takes 10 minutes; changing a custom integration means a developer ticket, a code review, a deployment, and probably a $500 invoice. If the rules around how data should flow are still being figured out — and for most growing SMBs, they are — iPaaS lets you change them without paying somebody to change the code.
Scoring rule: if you answered "no" to Q1, Q2, and Q3, and "yes" to Q4, you want iPaaS. If you answered "yes" to two or more of Q1–Q3, you're looking at custom or hybrid.
The cost reality: $30/month vs. $20,000 to build
This is where SMB owners usually need a second cup of coffee. The cost gap between iPaaS and custom is large enough that "cheaper" is the wrong frame — order-of-magnitude cheaper is closer to the truth, at least for the volumes most SMBs operate at.
iPaaS, real 2026 pricing (verified against vendor pricing pages, April 2026):
- Zapier. Free tier 100 tasks/month. Professional $19.99/mo (annual) for 750 tasks. Team $69/mo for 2,000 tasks. Most SMBs we audit land between Professional and Team. Pricing at zapier.com/pricing.
- Make. Core $10.59/mo for 10,000 operations and unlimited active scenarios. Pro $18.82/mo. Teams $34.12/mo. Make's "operations" are smaller billable units than Zapier's "tasks" — a typical scenario run consumes 3–8 — so effective monthly cost is comparable to or lower than Zapier.
- n8n. Self-hosted Community Edition is free with unlimited workflows and executions; you pay only for the server ($5–$20/mo on a small VPS). n8n Cloud Starter is €24/mo (~$26) for 2,500 executions; Pro is €60/mo for 10,000. As of April 2026, n8n removed all active workflow limits across every plan.
- Workato. No public pricing; Standard editions start ~$833/mo (~$10K/year); Business deployments commonly $60K–$120K/year. Don't shortlist unless you've passed $20M revenue or you're in a regulated industry.
iPaaS spend for a typical SMB lands between $0 and $300/month total — even with multiple platforms in play.
Custom integrations, real 2026 pricing:
- Build cost: $5,000–$50,000 for the first version. A point-to-point integration between two well-documented APIs (HubSpot ↔ QuickBooks) might be $5,000–$10,000 with the right developer. A multi-system orchestration with branching logic, retry handling, and a queue lands closer to $30,000–$50,000.
- Maintenance: $500–$2,000/month equivalent, in either developer retainer or salaried time. APIs deprecate. Auth tokens expire. Schemas change. The integration that worked perfectly on launch day will break, on average, within 12–18 months — exactly the cost driver we cover in the $600,000 problem (forthcoming).
The maintenance line is what kills custom for most SMBs. The build cost is a bounded one-time expense; the maintenance bill is recurring, unpredictable, and almost always under-estimated. If you're going to build custom, budget for the second year as carefully as the first.
Heads up — this is a Stack Audit decision, not a Google decision. If you're stuck between an iPaaS and a custom build for a specific integration, book a free Stack Audit. Thirty minutes, one video call, no pitch — we tell you which way to go and why.
Where each option actually wins: 3 SMB scenarios
The four-question test gets you 80% of the way. The other 20% is recognizing the shape of the problem you have. Here are the three scenarios we see most often.
Scenario 1: iPaaS wins. Standard tools with well-built connectors. CRM ↔ accounting (HubSpot ↔ QuickBooks). E-commerce ↔ shipping (Shopify ↔ ShipStation). Support ticket → CRM enrichment (Zendesk → HubSpot). Volume well under 50,000 operations a month. Logic is "when X happens in A, do Y in B," with maybe one branch. Nobody on your team writes code professionally. Use iPaaS. Zapier or Make for non-technical owners; n8n for owners who like self-hosting.
For a head-to-head, our directory has live comparisons: Zapier vs. n8n, Zapier vs. Make, and Make vs. n8n.
Scenario 2: Custom wins. High-volume data (>100,000 operations/month) where per-task iPaaS pricing becomes punitive. Or a niche vertical tool: construction job-cost ↔ payroll, healthcare EHR ↔ billing under HIPAA, a legacy ERP with no public API. Or a unique business rule no platform can express cleanly. Use custom. Hire a developer or agency you trust, write it on your own infrastructure, budget for maintenance.
Scenario 3: Hybrid wins. Where most mature SMBs end up after running iPaaS for a year or two. Roughly 80% of the surface area runs on Zapier, Make, or n8n — the standard flows that change often. The other 20% — high-volume bulk sync, regulated patient-record sync — runs on custom code. The hybrid pattern is not a compromise; it's the right answer once you've grown past Stage 1.
The 2026 shift: AI-native iPaaS is closing the gap
Eighteen months ago, the line between iPaaS and custom was clear. iPaaS handled "if X then Y" automations; custom handled anything needing reasoning, classification, or natural language. That line has moved.
The platforms now ship native AI:
- Zapier Agents launched in beta in early 2026. Describe an outcome ("when a new lead comes in, research the company, score them, route to the right rep") and the agent stitches actions across Zapier's 8,000+ apps.
- Make introduced Maia, an AI assistant that builds whole scenarios from natural-language prompts, plus native AI modules for OpenAI, Anthropic, and Google models.
- n8n 2.0 shipped in January 2026 with native LangChain support, ~70 AI nodes, persistent agent memory, vector-DB support for RAG, and self-hosted LLM compatibility.
In practice: cases that required custom code 18 months ago — document classification, support-ticket triage, lead enrichment, multi-step agent workflows — now run inside iPaaS, often in an afternoon. The "custom is required for AI" rule of thumb is mostly false in 2026.
The market reflects the shift. Per Gartner's Market Share Analysis: iPaaS, Worldwide, 2024, iPaaS revenue hit $9 billion in 2024 — up 23.4% YoY — and Gartner forecasts the category will exceed $17 billion by 2028. Growth is driven by exactly the AI integration use cases that used to belong to custom development.
The honest comparison: Zapier vs. Make vs. n8n vs. Workato vs. custom
Vendor-aligned comparison articles usually rank whichever platform paid for the post. Here's the version we use internally with clients.
| | Zapier | Make | n8n (cloud) | n8n (self-hosted) | Workato | Custom | | --- | --- | --- | --- | --- | --- | --- | | Starting price | $0 free / $19.99/mo Pro | $10.59/mo Core | €24/mo Starter | $5–$20/mo (server only) | ~$833/mo | $5K–$50K to build | | Operations included | 750–2,000/mo | 10,000+/mo | 2,500–10,000/mo | Unlimited | 100K+/mo (custom) | Unlimited (you pay for compute) | | Scalability | Good to ~50K ops/mo | Good to ~100K ops/mo | Good to ~100K ops/mo | Excellent (limited by your server) | Excellent | Excellent (you build it) | | Learning curve | Lowest | Low–medium (visual canvas) | Medium | Medium–high (devops) | High (enterprise) | Highest (real code) | | Native AI | Zapier Agents (beta) | Maia + AI modules | 70+ AI nodes, LangChain | Same as cloud | Yes (enterprise) | Whatever you build | | Self-host option | No | No | No | Yes (free) | No | Yes (you must) | | Connector library | 8,000+ | 2,000+ | 400+ | 400+ | 1,200+ | None — you write each | | Best for | Non-technical owners; "just connect these two things" | Visual thinkers; complex branching | SMBs who want flexibility without devops | Technical SMBs; compliance-sensitive data | $20M+ revenue or regulated | High-volume; vertical-specific; no-API systems |
Three callouts that don't fit the table:
- Per-task vs. per-execution. Zapier counts every action as a task; n8n counts a whole workflow run as one execution. For multi-step workflows, n8n is dramatically cheaper per equivalent unit of work — sometimes by 10x.
- Connector quality varies. Zapier's are the most polished and best-maintained. n8n and Make are functional but occasionally lag on new API changes. Check connector quality before committing on a niche tool.
- Self-hosting has a price. "Free" n8n is only free if someone can keep a Linux server patched, monitored, and backed up. If that's you or someone on your team, self-hosting is the best deal in the market. If not, the cloud version is worth $24/month.
What we recommend by company size
The four-question test handles the technical decision. For the strategic decision — which platform should you commit to — company size is the cleanest predictor we've found.
Under 10 employees: Zapier or Make. You don't have time to debug connector code. You need something that works on the first afternoon. Zapier wins on connector breadth and ease; Make wins on price and visual flexibility. Pick one and start.
10–50 employees: n8n (cloud or self-hosted) is usually the right answer. This is where Zapier's per-task pricing becomes a real line item — $50–$150/month — and where n8n's flat per-execution pricing pays back fast. If anyone on the team can run a small server (or you have an MSP), self-hosted n8n at $20/month replaces a $200/month Zapier bill with no functionality lost. If not, n8n Cloud at €24/month is still cheaper than equivalent Zapier.
50–200 employees: hybrid stack. A primary iPaaS (usually self-hosted n8n for compliance and cost, with Zapier as a backup for connectors n8n doesn't have) plus a small inventory of custom integrations for high-volume or regulated flows. At this size you can justify a part-time integration owner — someone whose job includes "knows how the integrations work and what to do when one breaks." That person is the difference between a hybrid stack that scales and one that becomes a graveyard of forgotten Zaps.
200+ employees: you've outgrown the SMB framing here. Enterprise iPaaS (Workato, Boomi, MuleSoft) starts to make sense, but the criteria are different and the ROI math is sensitive to your compliance and volume profile.
The Monday morning recommendation
If you've read this far and want to actually move:
- Run the four-question test on your top integration need. Just the one. Volume, sensitivity, API availability, change frequency.
- If the answers point to iPaaS, pick the platform that fits your size band. Don't agonize. The choice is reversible; the time you waste agonizing isn't.
- Start with one connection. Run it for 30 days. Watch where it breaks and what you wish it did differently. Then add the next.
- Document the flow in a one-paragraph note. What it does, when it runs, what it touches, what to check if it stops. Without it, every integration becomes a black box six months later.
If you'd rather not figure out the iPaaS-vs-custom question alone, our team runs a free 30-minute Stack Audit. We run the four-question test on each integration in your stack and tell you plainly what to do. No pitch.
Frequently asked questions
Should an SMB use Zapier or custom code?
For roughly 80% of SMBs, Zapier (or a similar iPaaS like Make or n8n) is the right answer. Custom only wins when you're moving more than ~50,000 operations a month, you have data that can't legally leave your infrastructure, or you're integrating with a system that has no public API. The cost difference is significant — $20–$70/month for an iPaaS vs. $5,000–$50,000 to build custom plus ongoing maintenance — and iPaaS lets you change integration logic in minutes rather than on a developer ticket.
What's the cheapest iPaaS in 2026?
The cheapest iPaaS in 2026 is self-hosted n8n, free to run indefinitely on a small VPS that costs $5–$20/month. Among hosted options, Make Core at $10.59/month (10,000 operations) is the cheapest entry point, followed by n8n Cloud Starter at €24/month and Zapier Professional at $19.99/month (annual billing). All sit well below the $300/month most SMBs spend on integration platforms total.
Can n8n replace custom integrations?
In most SMB cases, yes. n8n's combination of a visual builder, full code-execution capability (drop into JavaScript or Python inside any workflow), self-hosting, and — as of n8n 2.0 in January 2026 — native AI and LangChain support, covers the majority of cases that previously required custom code. Exceptions: very high volume (millions of ops/month), tight sub-second latency, and systems with no API or no n8n connector.
When does custom integration make sense for SMBs?
Three specific cases: (1) you're moving more than ~100,000 operations per month, where per-task iPaaS pricing exceeds custom code on a queue; (2) the data is sensitive enough — HIPAA, financial, contractual — that it can't pass through a third-party iPaaS even with a BAA in place; (3) you need to integrate with a vertical-specific tool that has no public API. Outside these cases, custom is usually slower, more expensive, and harder to change.
How much does an iPaaS cost per month for a small business?
For most SMBs, expect $20–$300/month total on iPaaS — even with multiple platforms in play. A typical 10–50 employee company runs Zapier Professional ($19.99/mo) or Make Pro ($18.82/mo) for one or two flows, scales to Team or Pro pricing ($35–$70/mo) as volumes grow, and rarely exceeds $300/month unless transaction volume is unusually high. Self-hosted n8n at $5–$20/month for the server is the cheapest functional option for technical teams.
About the author. Alejandro Morales is a senior operations consultant and systems architect at STOA Digital Solutions. STOA helps SMB owners ($500K–$20M revenue) choose the right software, connect it, automate routine work, and build operations that don't depend on the owner being in every meeting. Based in the Triangle, NC; serving the US.
Sources cited.
- Gartner — Market Share Analysis: Integration Platform as a Service, Worldwide, 2024. iPaaS revenue and growth data.
- Zapier — Plans & Pricing. Current Zapier plan pricing and task limits, verified April 2026.
- Make — Pricing & Subscription Packages. Current Make plan pricing and operations allowances, verified April 2026.
- n8n — Plans and Pricing. Current n8n cloud and self-hosted pricing, verified April 2026.
- Workato — Pricing Model. Pricing model description (custom, sales-led).
- MuleSoft (Salesforce) — Connectivity Benchmark Report 2024. IT leader survey on data silos and integration challenges.
- n8n — n8n 2.0 release notes (January 2026). Native LangChain support, AI nodes, persistent agent memory.
- STOA Digital Solutions — operational observations from SMB Stack Audit engagements, 2024–2026.