Software is bought to remove work. Each tool also creates work of its own, and that second amount rarely appears on the invoice.
Call it the integration tax. It is the standing cost of making a tool part of how a business actually runs.
What the tax is paid in
The tax is not one line item. It is collected in five places:
- Connecting: a new system has to exchange records with the systems already in use.
- Securing: it needs accounts, roles, credentials, and a reliable way to remove them.
- Reconciling: the same customer, order, or document now exists in more than one place.
- Explaining: people have to be told which tool to use for which decision.
- Deciding: someone has to declare which system is the source of truth, and keep defending that choice.
None of that work is visible to a customer. It is the price of the tool having a place in the business at all.
Why it stays invisible
A subscription has a number, a renewal date, and an owner. The tax has none of those.
It is spread across the person who writes the sync script, the administrator who provisions the accounts, the operator who checks two dashboards before answering one question, and the finance lead who reconciles two exports at month end. Each share is small enough to absorb quietly. Together they are rarely counted at all.
The tax also compounds unevenly. A tenth tool does not add a tenth of the burden. It adds a relationship with each of the nine already there.
Agents raise the rate
Automation does not settle the bill on its own. An agent asked to work across a fragmented stack needs a credential in each system, a mapping between each pair of records, and a rule for which copy wins. Every ambiguity a person used to resolve with judgment must now be resolved explicitly—or resolved wrongly, quickly.
That makes a useful test. Work that only functions because people silently absorb the inconsistencies between tools is not yet work that software can be trusted to do.
Lower the rate, not just the bill
Consolidation that merges invoices leaves the tax in place. What reduces it is shared structure underneath the applications: one identity, one set of permission boundaries, one catalog of what exists, and one governed way to act on it.
A shared foundation makes distinct Topolo products coherent, governable, and extensible for people and agents. Connecting stops being a project, because applications already share a workspace and a permission model. The source of truth stops being an argument, because context is shared rather than copied.
The subscription is the visible price of a tool. The tax is what it costs to live with it. Both belong in the decision.