Build or buy
When should you connect tools instead of building?
Direct answer
Connect tools when each one is already the right home for its record and the pain is the retyping between them. Build a new record when neither tool can hold the thing the team actually needs to see. Automation is the right size only after the steps are clear; connecting a confused process makes the confusion arrive faster.
The gap is usually between products, not inside one
A firm can have a good accounting tool, a good mailbox and a good spreadsheet, and still lose the thread, because the work happens in the spaces between them. An enquiry arrives, a person copies it, a reminder is sent from memory, and the status is updated if someone remembers. No single product is “broken”. The hand-off is.
If both sides of that hand-off have a usable interface, an integration or a small automation is the proportionate answer. Building a third product to sit in the middle is how firms end up maintaining a system whose only job was to move a field.
When the interface is the deciding fact
Ask, early, whether the product can be read and updated by something other than a person at a keyboard. A documented API, a reliable export, or an official automation are very different from “we can probably scrape it” or “someone can download a CSV on Fridays”. The first is an integration. The second is a future incident.
Paid interface tiers are part of the cost. A cheap subscription that charges heavily for the API can make a custom build, or a different product, the more honest option. Discover the price of the interface before you discover it in a change order.
When to build the record instead
Build when the thing you need does not exist in any of the current tools. A drawing register with a transmittal history, a checklist of documents against an engagement, a day list that includes the walk-in: if every product would still leave that list in a sheet, the sheet is telling you the record is missing. The products can stay. The new system holds the missing record and connects where it should.
This is the usual shape of the industry work Sunbeam describes. We are not looking for an excuse to replace the till, the tax portal or the practice system. We are looking for the list those systems do not contain.
Make the automation visible
A flow that copies data should have an owner, a way to see the last success, and a way to notice the failure. Silent automation is how a firm discovers, weeks later, that leads stopped arriving or reminders stopped sending. The person who gets the alert should be the person who can do something about it.
Leave a human step where judgment belongs. Routing a new enquiry to the right owner can be automatic. Deciding the firm will take the matter should not be. The guide on AI agents makes the same point for drafts: generate, then let an accountable person send.