The short version: most small businesses already pay for good software. The waste is in the gaps between it, where someone copies details from one screen to another. Start by drawing how a customer moves through your business, mark every place data gets retyped, decide which system is the "master" for each kind of information, then connect the most painful gap first using the simplest reliable method: a built-in integration, an automation tool like Zapier or Make, or custom code.
Why connecting your systems matters
A typical small business might take enquiries through a website form, keep customers in a CRM or a spreadsheet, run appointments in a booking app, take card payments through one provider and do the books in Xero, QuickBooks, Sage or FreeAgent. Each tool is good at its job. The trouble is that none of them talks to the others, so somebody becomes the link: reading an email, typing the details into the CRM, creating the booking, raising the invoice, chasing the payment, then matching it up in the accounts.
That human link causes the same problems in almost every business:
- Time lost to retyping that nobody ever counts, because it's spread across the week in small pieces.
- Mistakes: a wrong digit in a phone number, a booking missed, an invoice never sent.
- Slow responses. The enquiry sits in an inbox until someone has time, while the customer calls the next business on Google.
- No clear picture. You can't easily answer "how many enquiries did we get from Google last month, and how many became paying jobs?"
- Key-person risk. Only one person really knows how it all fits together.
An integration replaces that human link with a reliable automatic one, so information entered once flows to everywhere it's needed.
The jargon, explained
You'll hear these words from software companies and developers. None of them is complicated.
| Term | What it means |
|---|---|
| Integration | Any connection that lets two systems share information without someone retyping it. |
| Native (built-in) integration | A connection the software company has already built, usually switched on in its settings or "apps" page. |
| API | A doorway a piece of software provides so other software can read or send information in a controlled way. If a tool "has an API", it can usually be connected to. |
| Webhook | An automatic message one system sends the moment something happens, such as "new booking made". It lets other systems react instantly instead of checking every few minutes. |
| Automation platform | Tools like Zapier and Make that connect thousands of apps through a visual editor, without writing code. |
| Trigger and action | "When this happens (trigger), do that (action)." For example: when a booking is paid, create an invoice. |
| Field mapping | Matching up the boxes: the "Mobile" field in your form goes into the "Phone" field in your CRM. |
| One-way or two-way sync | Whether information flows in one direction, or changes in either system update the other. Two-way is harder to get right. |
| Source of truth | The one system that holds the master copy of a piece of information. Everything else follows it. |
What a connected business looks like
Here's one common customer journey with every handover automated. Your tools will differ, but the shape is usually similar.
Nobody retypes anything. You can see, for each customer, where they came from, what they booked, what they paid and whether they left a review. And your accounts are up to date without a Friday afternoon of matching payments.
The four ways to connect systems
There is a ladder of options, from quick and cheap to flexible and bespoke. Always start at the bottom rung and only climb when you need to.
1. Built-in integrations
Many tools already connect to each other. Booking platforms often link to popular accounting packages and calendars; card payment providers often feed straight into accounting software; CRMs often connect to email and website forms. Check each tool's "integrations", "apps" or "marketplace" page before anything else.
Good for: common pairings. Watch for: they do exactly what they were designed to do, and no more. If the built-in link only copies half the information you need, you may still need another layer.
2. Automation platforms (Zapier, Make and similar)
These sit between your apps and pass information along: "when a new form is submitted, create a contact in the CRM and send a text to the owner". You build them in a visual editor and they connect to thousands of apps.
Good for: joining tools that don't have a built-in link, quick wins, testing an idea. Watch for: pricing based on usage (each step that runs counts towards a monthly allowance), failures that nobody notices, and a sprawl of small automations that nobody documented. Set them up properly, name them clearly and switch on error alerts.
3. Custom API integrations
When the automation tools can't handle the logic, the volume or the reliability you need, a developer can write code that talks to each system's API directly. This can handle complex rules ("if the job is over a certain value and the customer is new, take a deposit and notify the manager"), large volumes and proper error handling.
Good for: core processes the business depends on, and anything the off-the-shelf connectors can't do. Watch for: it needs hosting, monitoring and occasional updates when a supplier changes its API. Make sure it's documented and you own it.
4. A custom app
Sometimes the honest answer is that you're stitching together five tools to do one job none of them quite fits. A single custom system, connected to the few tools you keep (usually payments and accounts), can be simpler in the long run. Our guide Do I need a custom app? covers the signs.
Free integration map chat. Tell us which tools you use, logins and all. In 30 minutes we'll sketch how they could connect, which gap to close first and the simplest way to do it.
How to map your own integrations
You don't need a developer to do the most valuable part. Grab a large sheet of paper and work through this.
- List every tool you use, including email, spreadsheets, WhatsApp and paper. Note who uses each and what it costs.
- Draw the customer journey from first contact to paid invoice and review, as boxes and arrows.
- Mark every handover where a person reads something in one place and types it into another. Put a rough weekly time against each.
- Choose a source of truth for each kind of information: customers (usually the CRM), appointments (the booking system), money (the accounting software). Other systems copy from the master, never the other way round.
- Check what's possible. For each handover, look for a built-in integration, then Zapier or Make support, then whether both tools have an API.
- Rank the gaps by time wasted and by the cost of mistakes. A missed enquiry usually costs more than a slow reconciliation.
- Start with one flow, test it with real examples for a week or two, then move to the next.
Tip: the most common first win is getting every enquiry, from every channel, into one place automatically, with an instant acknowledgement to the customer and an alert to you.
Common problems, and how to avoid them
- Duplicates. The same customer appears three times because the systems match people differently. Decide on one matching rule (usually email address or mobile number) and apply it everywhere.
- Two-way sync loops. System A updates B, which updates A, which updates B. Use one-way flows from a single source of truth wherever you can.
- Silent failures. An automation stops working when someone changes a password, and nobody notices for a month. Every integration needs an alert when it fails, sent to someone who will act on it.
- Creeping costs. Usage-based tools get more expensive as you grow. Check what you'll pay at double your current volume.
- Accounts owned by the wrong person. If the integration runs on a staff member's personal login and they leave, it stops. Use business-owned accounts and keep a list of logins somewhere safe.
- Supplier changes. Software companies update or retire their APIs. Someone needs to watch for notices and adjust.
- No documentation. Six months later, nobody remembers why the invoice is created twice on Tuesdays. Write down what each integration does, what triggers it and who to call.
Data protection and UK GDPR
Connecting systems means moving personal data around, so a little care is needed. In plain terms:
- Only move what's needed. The accounting software needs a name and an invoice; it doesn't need a client's treatment notes.
- Check each supplier's terms. Under UK GDPR, software that stores customer data on your behalf is usually a "processor", and you need a contract with the terms the law requires. Most reputable providers publish a data processing agreement; read it and keep a copy.
- Know where the data goes. Many tools store data outside the UK. That's often fine, but you should know, and your privacy notice should be accurate.
- Limit access. Give integrations the minimum permissions they need, and remove access for tools you stop using.
- Keep a simple record of which systems hold which data and how they connect. It helps with data requests and with the ICO's expectations around accountability.
Making Tax Digital: another reason to connect
HMRC's Making Tax Digital rules already apply to VAT-registered businesses, which must keep digital records and send returns from compatible software. Where more than one piece of software is involved, HMRC expects the data to flow through "digital links"; copying and pasting or retyping figures between systems doesn't count.
Making Tax Digital for Income Tax now applies to sole traders and landlords too: from 6 April 2026 for those with qualifying income over £50,000, from April 2027 over £30,000 and from April 2028 over £20,000, according to GOV.UK. If your bookings and payments feed your accounting software automatically, keeping digital records becomes a by-product of running the business rather than a quarterly chore. Speak to your accountant about what applies to you.
What integrations cost
Costs fall into three buckets:
- Software subscriptions. Built-in integrations are often included, or need a higher plan. Automation platforms have free tiers for light use (at the time of writing, Zapier's free plan includes 100 tasks a month and Make's includes 1,000 credits a month) and paid plans priced by volume. Check current pricing, as it changes often.
- Set-up. Your own time, or a specialist's. A simple automation is a small job; a set of connected flows across your whole business is a project.
- Upkeep. Monitoring, fixes when something changes and occasional improvements.
For transparency, our list prices for larger system work are £2,200 for system design (mapping and specifying how your systems should work together) and £3,300 for system set-up and development. Smaller automations and connectors are quoted per job, in writing, before any work starts. Not VAT registered - no VAT added.
To judge whether it's worth it, add up the weekly hours spent retyping and fixing mistakes, multiply by what that time costs you, and add a fair figure for enquiries lost to slow replies. Then compare.
Questions to ask before anyone builds it
- Which method will you use for each connection, and why not something simpler?
- Which system is the source of truth for customers, bookings and money?
- What happens when a connection fails, and who gets told?
- Whose accounts will it run on? (The answer should be yours.)
- What will the ongoing software costs be at our current volume, and at double?
- Will we get written documentation of what was built?
- What customer data is moved, and where is it stored?
- What support do you offer after it's live, and what does it cost?
If you're commissioning something larger, our guide to choosing an app developer has a fuller list, including who owns the code.
Integration questions
Can my booking system connect to my CRM?
Usually, yes. Check the booking system's integrations page first. If there's no built-in link, an automation platform such as Zapier or Make often supports both tools. If neither works, and both systems have an API, a developer can connect them directly.
What's the difference between Zapier and a custom integration?
Zapier and similar platforms connect apps through ready-made building blocks without code, and charge by usage. A custom integration is code written for your process. It handles more complex rules and higher volumes, but needs hosting and maintenance.
Do I need to replace my software to connect it?
Rarely. Most businesses can connect the tools they already have. Replacement only makes sense if a tool has no way in (no integrations and no API) or no longer fits how you work.
Is it safe to connect systems that hold customer data?
It can be, if it's done properly: use official connection methods, move only the data needed, limit access, check each supplier's data processing terms and keep a record of what connects to what.
What should I connect first?
The handover that costs you most when it goes wrong. For many businesses that's getting every enquiry into one place with an instant reply, so none slip through.
Sources
- GOV.UK: Find out if and when you need to use Making Tax Digital for Income Tax
- GOV.UK: VAT Notice 700/22: Making Tax Digital for VAT (digital links)
- ICO: Contracts and liabilities between controllers and processors
- Zapier: Pricing and Make: Pricing
Software pricing and features change often. Figures reflect publicly available information in October 2026.