Custom integrations connect tools that don't talk to each other: small pieces of software that move data between systems such as your CRM, accounting package, booking system or WhatsApp. You need one when staff copy the same information between systems by hand and no ready-made connector does the job reliably. It replaces retyping with an automatic, logged transfer.
Every growing business ends up with a stack of tools chosen at different times by different people. Each is fine on its own. The cost hides in the spaces between them: the spreadsheet someone updates every Friday, the invoice raised from details in an email, the customer whose address differs in three places.
How do you know you need an integration?
If the same piece of information is typed into more than one system, you have an integration problem. The more often it happens and the more it costs when someone gets it wrong, the stronger the case.
Common signs:
- A team member spends part of every day exporting from one tool and importing into another.
- Customer details differ between your CRM, accounts and support inbox.
- Reports need someone to combine three exports in a spreadsheet first.
- Mistakes such as a wrong invoice amount or a missed booking trace back to manual copying.
- A tool you rely on has an export button but no live connection.
Count the hours. Multiply the weekly time spent on manual transfers by a loaded hourly cost and by 52. That annual number, plus the cost of errors, is what an integration competes against.
Can't an off-the-shelf connector do this?
Often it can, and you should try that first. Native integrations and no-code automation tools handle simple, one-direction transfers between popular apps well.
| Situation | Off-the-shelf connector | Custom integration |
|---|---|---|
| Popular apps, one direction, standard fields | Usually fine | Overkill |
| Data must sync both ways without overwriting | Fragile | Better |
| Business rules (routing, approvals, calculations) | Limited | Built to fit |
| High volume, where per-task fees add up | Gets expensive | Fixed build cost, lower running cost |
| One side is a custom or legacy system | Often impossible | The usual answer |
| Data is sensitive and must stay in a controlled place | Adds another processor | You control where it flows |
The same build-or-buy logic applies here as to software generally. Our guide to custom software vs off-the-shelf SaaS sets out the decision in more detail.
What does a custom integration actually involve?
Four parts: connecting to each system, translating the data, applying your rules, and recording what happened. The connecting is rarely the hard part.
- Connections. Most modern tools offer an API, a documented way for other software to read and write their data. Think of it as a service counter with fixed rules about what you can ask for and in what format. Older tools may only offer file exports, a database, or an email inbox to read from.
- Translation. One system's "client" is another's "contact" plus "company". Dates, currencies, phone formats and tax codes all need converting.
- Rules. Which record wins if both systems changed? Should a won deal create an invoice automatically or wait for approval? These decisions are business decisions, not technical ones.
- Logging and alerts. Every transfer should be recorded, and failures should alert a person rather than vanish.
GRWW's own Ops Console is an example of this in practice: its lead centre pulls in website form submissions and Meta lead-ad enquiries automatically, and those leads flow on into the CRM pipeline, proposals and invoices. The value isn't any single connection. It's that nobody types a lead's details twice.
What patterns do integrations follow?
Most integrations are one of three shapes, and picking the right one avoids a lot of rework.
- Event-driven (push): when something happens in system A, it notifies system B straight away, usually through a webhook. Best for leads, payments and bookings where speed matters.
- Scheduled sync (pull): every few minutes or every night, the integration checks for changes and copies them across. Fine for reporting data and stock levels where a short delay is acceptable.
- Hub: several systems connect to one central service that holds the rules, instead of each tool connecting to every other. Once you have more than three or four tools exchanging data, a hub stops the connections multiplying into a tangle.
For example, a service business might push new website and Meta leads into the CRM instantly, sync won deals to the accounting package nightly, and route WhatsApp conversations through the WhatsApp Business API into the same contact records. Three tools, three patterns, one customer record.
What usually goes wrong?
Integrations fail at the edges: bad data, changed APIs, expired credentials and conflicting edits. Good ones are built expecting all four.
| Risk | What it looks like | How it's handled |
|---|---|---|
| Messy source data | Missing phone numbers, duplicate contacts | Validation and clean-up rules before data moves |
| Rate limits | The other system refuses requests when you send too many | Queues and paced retries |
| API changes | A vendor updates its API and fields disappear | Monitoring, versioned connections, maintenance budget |
| Expired access | A password change or departed admin breaks the link | Business-owned credentials, expiry alerts |
| Two-way conflicts | Both systems edited the same record | A clear "source of truth" per field |
| Silent failure | Data stops flowing and nobody notices | Daily count checks and failure alerts |
Decide which system owns each piece of data before anything is built. The CRM might own contact details while the accounting package owns invoice status. Without that rule, two-way syncs overwrite good data with stale data.
How much does a custom integration cost?
A single, well-defined integration usually falls within the simple internal tool or automation range; a hub connecting many systems costs more. Typical market estimates, depending on scope:
| Scope | India (₹) | Australia (AUD) | Global (USD) |
|---|---|---|---|
| One or two systems, one direction, clear rules | ₹1.5–5 lakh | $10k–30k | $6k–20k |
| Several systems, two-way sync, business rules | Toward MVP range, ₹4–12 lakh | $25k–80k | $15k–50k |
Ongoing maintenance typically runs 15–25% of the build cost per year, and integrations need it more than most software because the systems at either end keep changing. If the real problem is that your CRM can't be shaped around your process, compare the options in custom CRM vs HubSpot vs Zoho vs Salesforce.
How should you brief an integration project?
Describe the flow in business terms: what triggers it, what moves, where it goes, and what happens when it fails. A developer can work out the technology from that.
A good brief answers:
- Which systems are involved, and do you have admin access to each?
- What event starts the transfer (new lead, paid invoice, cancelled booking)?
- Which fields move, and which system owns each one?
- How quickly must data arrive: seconds, minutes or overnight?
- Roughly how many records per day?
- Who should be told when something fails?
If one side of the integration involves AI, such as summarising enquiries before they reach the CRM, our guide to integrating ChatGPT, Claude or Gemini into business software covers the extra considerations. For how integrations fit alongside CRM and ERP, see our overview of business systems that scale.
Frequently asked questions
What if one of my tools has no API?
There are usually other routes: scheduled file exports, reading a shared database, parsing notification emails, or in the last resort automating the screen. These are more fragile than an API, so build in stronger monitoring and consider whether that tool should be replaced.
Who owns the integration code?
That should be written into your contract before work starts. Make sure the IP clause gives you ownership of, or at least full access to, the code and credentials, so you can move to another developer without starting again.
How long does a custom integration take to build?
A single, clearly scoped integration typically takes a few weeks including testing. Multi-system syncs with business rules take longer, and the timeline depends heavily on how quickly you can get access and answer the "which system wins" questions.
Will an integration break when a vendor updates its software?
It can. Vendors usually announce API changes in advance, and well-built integrations use stable API versions and monitoring. Budget for maintenance rather than treating the build as a one-off cost.
Is it safe to connect systems that hold customer data?
It can be, with care: least-privilege access keys, encrypted connections, logs that don't store more personal data than needed, and awareness of laws such as India's DPDP Act 2023 or Australia's Privacy Act 1988. Each extra tool in the chain is another place data lives, which is one argument for custom over chained third-party services.
Tired of copying data between tools?
Tell us which systems you're juggling and where the retyping happens. We'll map the flows and give you a fixed price. See our services or start a conversation.