Custom API or Standard Integration?

There are only two real options when two systems need to talk: a standard, off-the-shelf connector (Zapier, Make, or a native integration) or custom API development. The right answer is almost always "start with the connector" — and only build custom when you hit a wall a connector genuinely can't get over. This guide gives you the decision rule and the realistic 2026 UK cost and time of each, so you don't over-engineer a problem a £20/month tool already solves.

The decision rule, in one line

Use a standard connector until you need custom logic, two-way sync, high volume, or authentication the connector can't handle. The moment you cross any one of those lines, you're into custom territory. Before that, you're paying for engineering you don't need.

When an off-the-shelf connector is the right call

Connectors like Zapier, Make and the native integrations baked into tools (your CRM's "connect to Stripe" button, for example) are reliable, cheap and quick. They're the correct choice when:

• The flow is one-way and event-driven — "new form submission → create a CRM contact", "new order → post to Slack".
• The data mapping is simple — fields line up, no heavy transformation.
• Volume is normal — hundreds or low thousands of events a month, not millions.
• Both apps are popular enough to already have a connector built and maintained for you.

If that's your situation, don't commission a build. A connector ships in an afternoon and someone else maintains it forever.

When you've outgrown the connector

You need custom API development once any of these are true:

• Custom logic — conditional routing, calculations, deduplication or data transformation that a no-code step can't express cleanly.
• Two-way sync — both systems must read and write, stay consistent, and handle conflicts. This is the single biggest jump in complexity.
• Volume and reliability — high throughput, retries, rate-limit handling and guaranteed delivery, where a missed event means lost revenue.
• Authentication a connector can't do — OAuth flows the platform doesn't support, signed requests, an internal or legacy API with no public connector at all.

These are engineering problems, not configuration problems. Forcing them through a connector tends to produce a fragile chain of zaps that silently breaks and loses data — expensive to debug, worse to discover late.

The decision table

A useful gut-check: if you can describe the whole flow as a single "when X happens, do Y" sentence, a connector probably covers it. The moment you need "…unless, and also, but only if" you're describing custom logic.

The hidden cost connectors carry

Connectors look free, and at low volume they nearly are — but the price isn't the whole story. Two things catch businesses out as they grow. First, task-based pricing scales with you: a flow that costs £20/month at launch can quietly become £200/month once it fires on every order across three apps. Second, you don't own the logic. When a connector vendor changes a step, deprecates an app or rate-limits your account, your integration is at their mercy — and debugging a no-code chain that silently dropped 40 records last Tuesday is its own special pain. None of this means connectors are wrong; it means the "free" option has a ceiling, and a custom build buys you ownership, observability and predictable cost above it. The skill is spotting when you're approaching that ceiling rather than crashing through it.

What each option costs in the UK (2026)

These are realistic, informed ranges — not a quote. The honest answer to "how much?" is always "it depends on scope", and the table below shows what it actually depends on.

What moves you up the range:

1. Scope — one endpoint and a handful of fields is cheap; orchestrating several systems with transformation in between is not.
2. Sync direction — one-way is straightforward; two-way (keeping both sides consistent, resolving conflicts) is the most expensive single factor.
3. Authentication — a well-documented public API with API keys is quick; bespoke OAuth, signed requests or an undocumented legacy system adds real time.
4. Volume and reliability — needing retries, queues, rate-limit handling and guaranteed delivery turns a script into proper engineering.

For a structured estimate against your own scope, our free API & database cost calculator turns "how much?" into an indicative UK range you can plan around.

The pragmatic path most businesses should take

1. Now: wire it up with a connector if one fits. Prove the workflow, capture the value immediately, spend almost nothing.
2. When justified: commission a custom API integration once volume, reliability or process complexity earns it — not before.

That sequence avoids two classic mistakes: paying for a custom build to solve a problem Zapier already handles, and bolting ever more zaps onto a process that outgrew them six months ago.

It's the same logic we lay out for CRMs in Salesforce Web-to-Lead vs a Custom Integration — start with the free, reliable option, upgrade only when the requirement genuinely changes.

Where JW Digital fits

When a connector stops being enough, we build robust third-party API integrations and database & API systems — two-way sync, custom auth, middleware, error handling and migration. Start with the cost calculator to size your scope, and tell us what you're connecting — we'll tell you honestly whether you need a build at all, and reply within 2 hours.