Integration guides

Do you need an integration specialist, or can you connect your tools yourself?

Flow Mesh · 6 October 2026 · 4 min read

Zapier, Make and the native connectors inside most business software have made it genuinely possible for a non-technical owner to connect their tools. Plenty of firms should do exactly that. Others discover six months later that the automation they built on a Sunday afternoon has been quietly dropping records.

This article gives you a straightforward way to tell which side of that line you are on.

When doing it yourself is the right call

DIY works well when all of these are true:

• Two tools, one direction. A new form submission creates a contact in your CRM. A signed document is saved to a folder.
• A native integration exists. Most mainstream tools (Clio, HubSpot, Xero, QuickBooks, Google Workspace, Microsoft 365) ship built-in connections for the common cases. Setting one up is usually a matter of hours and needs little technical expertise.
• A mistake is cheap. If the automation fails, someone notices within a day and nothing reaches a client.
• Someone owns it. One named person knows it exists, gets the error emails, and can switch it off.

If that describes your situation, start with the native integration, then a simple two-step automation. You will learn more about your own process in a week of doing it than in a month of meetings.

Red flags that DIY will cost more than it saves

Bring in help, or at least a second pair of eyes, if any of these apply:

1. Client, financial or health data passes through the automation. Automation platforms keep logs of the data that flows through each step. You need to know where that data sits, who can see it, and whether your client agreements allow it. Some platforms state plainly that they are not designed for certain regulated data, so this is a design decision, not a checkbox.
2. More than three systems are involved. Every extra system multiplies the ways the chain can break, and the failure usually shows up in the last system, far from its cause.
3. Two-way sync. If a change in either system should update the other, you need rules for conflicts, duplicates and deletions. This is where most home-built integrations go wrong.
4. Money moves. Invoices, payments, trust or client accounts, payroll. An error here is not an inconvenience.
5. Nobody can describe the current process the same way twice. Automating an unclear process makes it faster, not better.
6. The person who built it is the only one who understands it. If they leave, so does your integration.

What a specialist actually does differently

A good integration specialist spends less time building than you might expect. Most of the value is in the decisions made before the build:

• Choosing the right layer. Native connector, no-code platform, or custom API. Each has a different cost and failure profile, and the right answer is often a mix.
• Naming a source of truth. For every type of record (client, matter, invoice, appointment), one system is the master. The others follow.
• Designing for failure. Error alerts that reach a person, retries, a log you can read, and a manual fallback.
• Documenting it. A one-page map of what connects to what, so the next person is not reverse-engineering it.

They should also tell you when not to integrate. Connecting a tool you should be cancelling is money spent twice.

A simple decision test

Score one point for each statement that is true:

• The workflow touches client, financial or health data.
• It involves more than three tools.
• Data needs to flow in both directions.
• A failure would be noticed by a client before it is noticed by you.
• Nobody on the team has built and maintained an automation before.

0 to 1 point: do it yourself, starting with native integrations. 2 to 3 points: do it yourself with a review, or have a specialist scope it and your team build it. 4 to 5 points: have it designed and built by a specialist, with a handover your team can maintain.

What it costs to get help

Rates for automation consultants vary widely; our guide to how much software integration costs breaks down subscriptions, build costs and upkeep. The more important question is how the work is priced. Hourly work with no written scope tends to grow with every exception found in production. A fixed-fee scope first, then a fixed quote for the build, keeps the number honest.

How Flow Mesh approaches it

We work with firms of roughly 10 to 50 people: law firms, accounting firms, healthcare clinics and consulting firms. Every engagement starts with a fixed-fee stack audit (€1,500): a verdict on every tool you pay for, the integrations worth doing, and a written scope. Some clients take that scope to their own team. Others ask us to build it, which we quote in writing before starting. We work inside your own accounts and sign an NDA at the start of every engagement.

Key takeaways

• Native integrations and simple two-step automations are well within reach for most owners. Use them.
• Sensitive data, more than three systems, two-way sync and money movements are the signals to get help.
• The value of a specialist is mostly in scoping, failure design and documentation, not in clicking buttons faster.
• Whoever builds it, name an owner and write down how it works.