Quick Summary
- 1Most Indian businesses now run 800–900+ software tools, but fewer than 3 in 10 are actually connected to each other — the rest survive on manual exports, copy-paste, and end-of-day spreadsheet reconciliation.
- 2That gap isn't free: mid-size companies lose the equivalent of 20–30% of annual revenue to duplicated work, stale data, and missed follow-ups caused by disconnected systems.
- 3There are exactly two real paths to fixing it — no-code/low-code iPaaS platforms (₹1,500 to ₹4,00,000+ a month depending on scale) or custom-built middleware (₹1.5L–₹25L+ depending on complexity) — and picking the wrong one is the single most common integration mistake we see.
- 4This guide gives the honest 2026 cost breakdown for both paths and the decision framework we use with clients before recommending either one.
The bottleneck nobody budgets for
We get called in for a lot of reasons — a slow website, an app that needs building, a cloud bill that's out of control. But one problem shows up in almost every discovery call regardless of what the client thinks they're hiring us for: their tools don't talk to each other.
A lead fills out a form on the website. Someone manually copies it into the CRM. Someone else re-keys it into the accounting system when the deal closes. Inventory gets updated in the warehouse app but not in the e-commerce store until someone remembers to sync it. Support tickets reference an order number that the support team has to look up in a completely separate system. None of this shows up on a P&L line called "integration cost" — it shows up as headcount that never quite keeps pace with growth, and decisions made on data that's a day, a week, or a quarter out of date.
MuleSoft's 2025 Connectivity Benchmark put a number on this: the average organisation runs 897 applications, and only 29% of them are integrated. Everything else is a manual bridge — a person, a spreadsheet, or a nightly export nobody remembers setting up. Separately, Skopx and Netguru research on the operational cost of data silos puts the number for a mid-size company at $7.8M–$12.9M a year in duplicated work, missed correlations, and delayed decisions, and Cherry Bekaert's CRM/ERP research estimates the total drag at 20–30% of annual revenue for businesses running disconnected systems. For a ₹10 crore business, that's not a rounding error.
This is the third bottleneck we listed on our services page for a reason — disconnected tools and duplicate data quietly cap growth long before a founder or ops lead realises it's the actual constraint.
What "system integration" actually means in 2026
Strip away the vendor language and there are really three ways to connect two systems, and most businesses end up using a mix of all three as they grow:
- Point-to-point / manual: someone exports a CSV from System A and imports it into System B, or copies fields by hand. Zero setup cost, but it doesn't scale past a handful of records and it's where most of the $7.8M in silent cost hides.
- iPaaS (Integration Platform as a Service): a no-code or low-code tool — Zapier, Make, n8n, Workato, Boomi, MuleSoft — that connects pre-built "connectors" for popular apps (Salesforce, Tally, Shopify, HubSpot, QuickBooks) through a visual workflow builder. You configure triggers and actions; the platform manages the plumbing.
- Custom middleware: purpose-built integration code — usually a small service that listens for events from one system and pushes transformed data into another — written and owned by your engineering team or a partner like us. Full control, no per-task pricing, but you own the maintenance.
We wrote separately about the operational cost of skipping all three and staying on spreadsheets — see Spreadsheet Chaos vs API Automation — this article picks up from "we've decided to automate" and answers the next question: iPaaS or custom-built, and what does each actually cost in India in 2026.
iPaaS pricing in 2026: what the platforms actually charge
iPaaS pricing splits cleanly into two tiers, and the gap between them is enormous.
No-code / low-code tools (SMB and mid-market)
| Platform | Starting Price | Pricing Model | Best fit |
|---|---|---|---|
| Make | $9/month | Per-operation (task) volume | Simple, visual workflows; generous free tier |
| Zapier | $19.99/month | Per-task volume, per app pair | Non-technical teams, fastest to configure |
| n8n (cloud) | ~€20/month (~$22) | Per-execution, tiered plans | Teams wanting more logic control than Zapier |
| n8n (self-hosted) | Free (community edition) + server cost ~$5–7/month | Unlimited executions, you host it | Engineering-led teams, high-volume workflows, data residency |
| Boomi | $99/month + $0.05/message | Pay-as-you-go plus per-message fee | Hybrid cloud/on-prem, mid-market |
Enterprise iPaaS
| Platform | Typical Annual Cost | Best fit |
|---|---|---|
| Workato | $15,000–$50,000/year | Mid-market automation with governance needs |
| MuleSoft (Salesforce) | $80,000+/year | API-first enterprises with dedicated integration teams |
| Enterprise iPaaS (Informatica, etc.) | $50,000–$100,000+/year | Large enterprises, high connector/volume needs |
For most Indian SMEs and startups, the realistic starting point is Make, Zapier, or self-hosted n8n — not the enterprise tier. A self-hosted n8n instance connecting five or six common tools (CRM, accounting, e-commerce, a form tool, and Slack) typically runs ₹15,000–₹60,000 in setup effort plus a server bill of a few hundred rupees a month. That's the honest starting number most vendors skip past to sell you the enterprise platform.
Custom middleware pricing in 2026: what a built-to-order integration costs
Custom middleware makes sense when the workflow is too specific, too high-volume, or too business-critical for a no-code connector — bidirectional real-time sync, complex data transformation, or a legacy system with no API at all. Indian development rates for this work in 2026:
| Developer level | Hourly rate (USD) | Monthly (full-time) |
|---|---|---|
| Junior (0–2 yrs) | $10–$20/hr | $1,600–$3,200 |
| Mid-level (2–5 yrs) | $20–$40/hr | $3,200–$6,400 |
| Senior / specialised | $40–$80/hr (up to $100/hr for AI/ML-heavy work) | $6,400–$12,800+ |
| Integration scope | Typical timeline | Typical cost (INR / USD) |
|---|---|---|
| Simple two-system sync (e.g., form → CRM) | 1–2 weeks | ₹40,000–₹1,50,000 ($500–$1,800) |
| Multi-channel inventory / order sync (4–5 systems) | 3–5 weeks | ₹1,50,000–₹5,00,000 ($1,800–$6,000) |
| Custom middleware with legacy system + real-time bidirectional sync | 6–10 weeks | ₹4,00,000–₹12,00,000 ($5,000–$14,500) |
| Full CRM–ERP integration layer, enterprise scale | 3–6+ months | ₹20,00,000–₹80,00,000+ ($24,000–$95,000+) |
Ongoing maintenance for custom middleware typically runs 15–20% of the build cost annually — API versions change, authentication tokens expire, and source systems get upgraded out from under you. This is exactly the kind of work we cover under our standard 30-day post-launch window and monthly retainer plans, with under-4-business-hour response on critical integration failures — a broken sync between your store and your accounting system is a critical issue, not a backlog ticket.
Planning a Website? Don't Overpay or Underbuild
Most businesses overspend on features they don't need — or underspend and rebuild within a year. We help you scope it right from day one.
The decision framework: iPaaS, custom middleware, or both
We don't start an integration engagement by pitching a platform. We start by mapping the systems, the data volume, and how much the business actually loses when the sync breaks or lags. In practice, three questions decide it:
1. Do off-the-shelf connectors already exist for your systems?
If your CRM, accounting tool, and e-commerce platform are all mainstream SaaS products, Zapier, Make, or n8n almost certainly has a pre-built connector. Building custom middleware for a workflow an iPaaS tool already solves is the single most common way we see businesses overspend on integration.
2. What's your monthly transaction volume?
Under a few thousand events a month, per-task iPaaS pricing is cheap. Past roughly 20,000–40,000 executions a month, the per-task cost curve on Zapier or cloud n8n starts to cross over what self-hosted n8n or custom middleware costs to run — self-hosted teams report 80–90% lower costs at high volume because you stop paying per execution.
3. Is the workflow business-critical and does it need custom logic?
Real-time bidirectional sync, complex field mapping, conditional business rules, or a legacy system with no modern API (common with older Tally setups, on-prem ERPs, or manufacturing execution systems) push you toward custom middleware regardless of volume — no visual builder handles that reliably at scale.
Our default recommendation for most SMEs: start with self-hosted n8n or Make for the 80% of workflows that are standard SaaS-to-SaaS syncs, and reserve custom middleware for the handful of high-value, high-complexity connections — usually the ERP and the core CRM. This mirrors the pattern we cover in Event-Driven Architecture in India 2026, where a lightweight event bus often replaces a dozen brittle point-to-point connections.
A worked example: connecting Shopify, Tally, and a CRM
A mid-size D2C client came to us with a familiar setup: Shopify for the storefront, Tally for accounting, and a CRM for customer support — none of them talking to each other. Orders were manually re-keyed into Tally every evening; support agents had no order history without switching tabs three times per ticket.
We ran this as a two-week discovery-to-demo sprint: mapped the three data flows, confirmed Tally's API limitations (older on-prem installs often need a local connector agent rather than a direct API), and landed on a hybrid approach — n8n self-hosted for the Shopify-to-CRM sync (a standard connector, live in three days), and a small custom middleware service for the Shopify-to-Tally sync, because the client's specific GST invoice formatting rules weren't something a generic connector could handle. Total cost: roughly ₹2,80,000 build plus a ₹1,200/month server. The manual evening re-entry — about 90 minutes a day, five days a week — was gone in the first week.
Common mistakes we see before businesses call us
- Buying an enterprise iPaaS contract (Workato, MuleSoft) for a five-connector, SMB-scale problem — the governance and connector library aren't worth $50K/year until you're actually running enterprise volume.
- Treating integration as a one-time project instead of a maintained system — APIs deprecate, auth tokens expire, and a sync with no monitoring fails silently for weeks before anyone notices the numbers don't match.
- Skipping the data-mapping step — the technical connection is the easy part; deciding which system is the "source of truth" for each field (customer address, order status, stock level) is where projects actually stall.
- No error handling or alerting — a failed sync should page someone within minutes, not get discovered a month later during a reconciliation.
Working with us
System integration sits inside our Custom Software Development practice — the same team that builds workflow automation and custom CRM/ERP work runs our integration engagements, so the person mapping your data flows is the same person maintaining the sync six months later. We start every integration engagement with a fixed-scope discovery sprint that maps your systems, data volumes, and failure points before we recommend iPaaS, custom middleware, or the hybrid most businesses actually need. If disconnected tools are costing your team hours every week, book a free 30-minute consultation — we'll give you an honest read on what's worth automating first, with no obligation to hire us.
Related Articles
- [Business Automation] Spreadsheet Chaos vs API Automation: The Operational Cost Most Businesses Don't Measure
- [APIs] API Development Services in India 2026: REST, GraphQL and gRPC Done Right
- [CRM] CRM Software Development Cost in India 2026: Custom vs Salesforce vs Zoho
- [Architecture] Event-Driven Architecture in India 2026: Patterns, Cost & When to Use It
Pro Insight
Planning a cloud-native platform? Let's review your architecture for free.
At ZANISS SOFTWARES, we don't just build websites — we build growth systems.
- ✓SEO-first architecture
- ✓Conversion-focused design
- ✓High-speed performance
- ✓Scalable, future-proof code
📩 Response within 24 hours
