Your tools start talking to each other.

A form is filled in on your website. The details land in the CRM as a new contact, a job is created in the sheet or system your staff use, a confirmation goes to the customer, a task appears for the right person, and when the job is marked done an invoice is prepared. Five systems, one event, no retyping. Most offices have a dozen of these chains, each one currently done by a person copying from one screen into another.

Current published prices for Zapier, Make, n8n and Power Automate, checked October 2026.

Everything. The Zapier, Make or n8n account is yours, created in your name with your billing. Every API key and login is stored in your own password manager, not ours. The code, if there is any, is in a repository you own. If we stopped tomorrow, the workflows would keep running and any competent developer could pick them up from the handover documents.

A one-page diagram of each workflow, a plain-words description of what it does and when it runs, a list of every account and key it uses and where they are stored, what to check when something looks wrong, and who to call. It is written so your office manager can read it, not only a developer.

Connected systems change. A supplier starts sending a different PDF layout, a CRM renames a field, a tool retires an old connection. The monthly care plan covers monitoring, so we usually see the failure before you do, the fix, small changes as your business changes, and a monthly note on what ran and what failed. It is priced with the build and either side can end it on 30 days' notice.

In the steps that need reading or writing. A rule can move a form into a CRM; it cannot read a customer's email and work out which job they mean, pull the fields off a scanned document, or draft a reply in your voice. Those steps use Claude, with the output checked against rules before it goes anywhere, and with a person on the send button until you say otherwise. Everything that can be a plain rule stays a plain rule, because rules do not have off days.

Count the copying. If sixty web enquiries a week each take six minutes to enter into the CRM, the job sheet and the confirmation email, that is six hours a week of retyping, or about 300 hours a year, before counting the ones typed wrong. The first workflow usually pays for itself on the copying alone; the second one is where the errors disappear.

It will not replace your accounting system, your CRM or your industry software; it connects them. It will not automate a process nobody in your office can describe in a sentence; discovery writes the sentence first. And it will not be built in our accounts to keep you dependent on us; the accounts are yours from day one.