There is a moment every growing company reaches and nobody warns them about. You bought the CRM, the billing tool, the support tool, the analytics tool and the scheduler. Each decision was right on its own.
And now none of them talk to each other, so you are building the connections anyway.
You did not buy a solution. You bought five products and the job of connecting them.
The four signals
1. More than four systems have to share data. Below that, point to point connections are manageable. Above it, the number of possible connections grows faster than anyone's ability to remember them.
2. The same data is entered twice. Anywhere. It means the connection does not exist and a person is the connection.
3. At least one connection is a human copying values. This is the clearest signal because it has a salary attached to it.
4. Your automation bill tracks volume rather than value. Per task pricing is comfortable at hundreds of runs and uncomfortable at hundreds of thousands. When the invoice grows with activity rather than with results, the model no longer fits you.
What owning the layer actually means
It does not mean writing everything from scratch. It means three things:
The logic is yours. The rules about what happens when a lead arrives, how records are matched, what to do when a field is missing. Written down, in your words, outside any tool.
It is portable. If you changed platforms tomorrow, the rebuild would be mechanical rather than archaeological. This is the practical test, and most teams fail it.
It has an owner. A named person, not a team and not a vendor.
The layer itself can live on an automation platform you self host. Self hosting stops the cost tracking executions and keeps records in your infrastructure, in exchange for owning updates, backups and uptime. If nobody will own a server, do not self host, whatever the saving looks like.
What to bring in house first
The connection a person currently performs by hand. It has an obvious cost, an obvious owner and an obvious definition of done.
Not the most complex integration. Not the most interesting one. The one with a salary attached.
What to keep buying
Everything undifferentiated and mature: email infrastructure, calendars, payments, enrichment sources, calling infrastructure, the CRM itself. Building these spends your scarcest resource on a solved problem.
What you own is the logic between them, which is the part that encodes how your business actually works and the part no product will ever model correctly.
How not to build a monolith
One flow per job, each with its own trigger and its own failure. The alternative, a single integration that does everything, fails entirely when it fails and becomes the thing nobody will touch.
Every flow needs an error route, because what has no error route fails in silence. And the layer needs monitoring that alerts on absence, not only on errors, since a flow that stops running produces no errors at all.
The question that settles it
If you changed automation platforms tomorrow, how much of your business logic would you have to rediscover by reading old workflows?
If the answer is most of it, you do not own your integration layer. You are renting it, and the rent goes up with your volume.