That's the short version. The longer one starts with what the tools are for.
The shelf
On our home page, the subscription shelf lists the kinds of tool a small business ends up subscribing to. The shelf is headed: "Nine logins. Nine invoices. Nothing talks to anything." There are nine kinds, and each is described in a line.
A CRM is where the customer lives, until they're also in the next six. Sequencing is follow-ups on a schedule, in a tool that doesn't know the deal closed. Marketing automation is lists, forms and drips, with its own contacts and its own truth.
Accounting is the books, fed by hand from everything above. Project management is the work, tracked somewhere the customer can't see. E-signature is paid per envelope, per seat, per year.
Scheduling is a booking link that doesn't know the route or the job. Payment processing is another dashboard, another fee, another copy of the customer. Integrations are the glue between all of the above. Our shelf says it breaks whenever one of them updates.
There is also a tenth tile on the shelf, dashed, labeled the one you forgot. Its line is "Still renewing."
Our home page puts it this way: each one is reasonable on its own, and together they are a stack of renewals, nine systems to learn, and you as the integration, retyping the same customer into each of them.
Built for the process, not the outcome
Most software is built around a process. A CRM has its process for contacts. Accounting has one for the books. E-signature has one for envelopes. Each does its own process well.
What you need is the outcome: the report, the billing, more leads, more sales. No one tool on the shelf owns that. It comes from the tools working together, and on the shelf they don't. So you carry the information between them, and you are the connection.
Three questions to ask of your stack
There's no count to hit. Ask three questions instead.
Do your tools work together, or do you carry information between them? If you are the one carrying it, you are the integration.
Do they produce the outcome you need? The report. The billing. More leads. More sales. Measure each tool by what it produces, not by what it does.
And do you enter the same information in more than one place? Try one test. Pick a customer from last month and look for them in every tool you pay for. If you entered their details in more than one place, that is the entering twice this article is about. If you entered them once and everything else followed, the pile isn't costing you that.
The hours are yours to count.
What fixing it looks like
Start from the outcome and work back. Say what has to come out the other end: a report, conversion numbers, billing, more leads. Then connect the tools that feed it, so the information is entered once and travels on its own. The outcome comes out the other end.
That is how we start a build. Our own shelf is the example here. Its answer is a business that runs on one tool shaped to it, built on parts that already work together. One login. One place the customer lives. The books fed automatically. The pieces you'd otherwise rent are already built and kept running underneath.
Our how it works page says how a build goes, and we start from parts that are already working.
Add up your own
We built a small page for this. The add-it-up page has a row for each of the nine kinds and one for anything else. You enter what you pay each month for each, and it gives you a yearly total.
Your number, not ours. We don't put one of our own on it, and we don't say what the average is.
Once you have the total, you have the cost in dollars. The cost in time is what is left, the hours spent being the connection between the tools, and that part is also yours to count.
When you don't need us
If your tools already work together and produce what you need, keep them, whatever the count.
If a no-code tool or an off-the-shelf product already fixes your problem, use that, and we'll tell you so.
If that is what you find, how it works shows how a build goes with us.