You're Probably Paying for 25 Apps. Have You Ever Added Up What They Actually Cost?

Marcus runs a mid-sized marketing agency in Brisbane. Twelve staff, decent revenue, good clients. On paper, the business is healthy. But every Sunday night, he sits down to do something he dreads: reconcile the week.

He opens Asana to check project status. Then HubSpot to see where a proposal is sitting. Then Harvest to pull timesheet data. Then Xero to cross-reference invoices. Then Slack to find a message someone sent about a client three weeks ago. Then a spreadsheet, because the data from all of the above doesn't actually talk to each other cleanly, and he needs to build a picture manually.

By the time he's done, it's nearly midnight. He hasn't touched the campaign strategy he promised a client on Friday. He hasn't followed up the two leads that came in Thursday. He's just... administered.

Marcus isn't unusual. He's typical.

The Average SME Is Running a Small Software Company on the Side

A 2024 report from Productiv found that the average mid-market company uses 291 SaaS applications across the organisation. Even at the SME level, research from BetterCloud puts the average at 130 apps across a business, with individual teams typically relying on 25 to 40 tools to do their daily work.

For a twelve-person agency like Marcus's, the stack usually looks something like this:

• Project management: Asana or Monday.com
• CRM: HubSpot or Salesforce
• Communication: Slack, plus email, plus sometimes Teams
• Time tracking: Harvest or Toggl
• Invoicing and accounting: Xero
• File storage: Google Drive or SharePoint
• Proposals: PandaDoc or a Word template emailed as a PDF
• Reporting: A spreadsheet someone built in 2021 that only one person understands
• Integration glue: Zapier, to make half of the above talk to the other half
• Password management: LastPass or 1Password
• Video calls: Zoom
• Scheduling: Calendly

That's twelve tools before you count the industry-specific ones. And each one has a subscription attached.

The Subscription Bill You're Not Looking At Clearly

Let's do the maths that most business owners avoid.

For a team of ten, a typical mid-range SaaS stack costs roughly:

That's roughly $11,500 per year. For ten tools. And this is a conservative estimate, using mid-tier plans. Many businesses are on higher tiers, or paying for tools they've forgotten about entirely.

A 2023 survey by Zylo found that 56% of SaaS licenses in SMEs go unused or underused in any given month. You're likely paying for seats that haven't logged in since the last quarter.

But the subscription cost, as painful as it is, is actually the smallest part of the problem.

The Cost Nobody Puts on a Spreadsheet

Here's the number that should worry you more than your credit card statement.

Researchers at the University of California, Irvine, found that when a knowledge worker is interrupted or switches context, it takes an average of 23 minutes and 15 seconds to return to full focus on the original task. Twenty-three minutes. For a single context switch.

Now think about how many times per day your team switches between tools. Opening Slack to answer a question about a project that lives in Asana. Jumping to Xero to check an invoice status that should connect to the client record in HubSpot. Copying a timesheet figure from Harvest into a spreadsheet to build a report that Asana can't generate.

If each team member switches context just five times per day, and each switch costs even half that refocus time, you're losing roughly an hour of productive capacity per person per day. For a ten-person team, that's ten hours daily. Across a working year, that's over 2,400 hours of lost focus.

At an average fully-loaded cost of $50 per hour for a knowledge worker, that's $120,000 per year. Evaporated. Not because anyone was lazy or inefficient. Because the tools don't connect, and human brains pay the price.

The Data Entry Tax

Beyond context-switching, there's the quieter drain of duplicate data entry.

When a new client signs on, someone enters their details into the CRM. Then into the project management tool. Then into Xero. Then into the timesheet system. If you're using a proposal tool, that's another entry. If you track equipment or resources, another one.

Same client. Same information. Entered four or five times by a human being who could be doing something else.

And every time a human enters data, there's a chance of error. A transposed digit in an invoice number. A misspelled company name that causes two records to exist in your CRM. A project code that doesn't match between your PM tool and your accounting software, so your profitability reports are always slightly off and nobody can figure out why.

A 2022 study by IBM estimated that poor data quality costs businesses an average of $12.9 million per year at the enterprise level. For SMEs the absolute number is smaller, but the proportional impact is often worse, because there's no dedicated data team cleaning it up. It just sits there, quietly corrupting your ability to make good decisions.

The Integration Maintenance Trap

At some point, Marcus's team tried to solve this. They hired someone to set up Zapier automations connecting HubSpot to Asana to Xero. It worked, mostly, for about four months.

Then HubSpot updated its API. One of the Zaps broke silently. For three weeks, new contacts created in HubSpot weren't flowing through to Asana. Nobody noticed until a client complained that their project hadn't been set up.

This is the integration maintenance trap. Every connection between two separate tools is a liability. It requires someone to build it, someone to monitor it, and someone to fix it when it breaks. And it will break. APIs change, pricing tiers restrict access, authentication tokens expire.

Zapier's own documentation recommends checking your Zaps weekly. How many business owners actually do that?

The time cost of maintaining integrations across a 15-tool stack is rarely measured, but it's real. It falls on whoever is most technically capable in the team, which is usually the person who should be doing something more valuable.

The Hidden Cost of Slow Decisions

There's one more cost that's harder to quantify but arguably the most damaging.

When your data lives in fifteen different places, you can't see your business clearly. You can see fragments. You can see this week's Xero balance, and separately this month's Harvest hours, and separately the pipeline in HubSpot. But you can't easily answer the question: which of my clients is actually most profitable, after accounting for all the time we spend on them?

That question requires pulling data from at least three systems, normalising it, and building a view that none of those systems will give you natively. Most business owners don't do it. Not because they don't care, but because it takes half a day they don't have.

So decisions get made on gut feel. Or on whichever number was easiest to find. Or they don't get made at all, because the picture is too murky to act on confidently.

This is where the Business Triangle concept becomes relevant. In a well-run business, administration should consume roughly 20% of the owner's time, with the majority going to craft and business development. But when your tools are fragmented, admin expands to fill whatever space it can find. It creeps to 35%, then 50%, then higher. The owner is spending more time managing data than managing the business.

The revenue consequence of that shift is hard to calculate precisely, but it's not zero. Every hour spent reconciling spreadsheets is an hour not spent on a client proposal, a product improvement, or a conversation that might have led somewhere.

What Consolidation Actually Looks Like

The argument for consolidating onto fewer tools isn't about minimalism for its own sake. It's about what happens to your business when the data all lives in one place.

When a project, its client, its finances, its team hours, and its communications all exist in a single system with a single database, a few things change.

You enter information once. When a client's billing address changes, it changes everywhere, not because a Zapier automation synced it across four tools, but because there was only ever one record.

You can ask real questions. Not "what does Xero say" and separately "what does Harvest say" but "which projects made money last quarter, and why." The answer is available without a spreadsheet.

Your team switches context less. Instead of jumping between Slack, Asana, and a shared drive to understand the status of a project, everything is in one place. The conversation about the project is next to the project.

And your Sunday nights look different.

The Consolidation Calculation

If you're running a ten-person business on a typical fragmented stack, here's a rough tally of what you might be spending:

• Direct subscriptions: $11,500 per year
• Context-switching productivity loss (10 people, 5 switches/day): $120,000 per year
• Duplicate data entry (estimated 30 minutes per person per day): $32,500 per year
• Integration maintenance (estimated 3 hours per week at senior rate): $9,750 per year

Total: roughly $174,000 per year in direct and indirect costs.

That number will vary depending on your team size, your hourly rates, and how disciplined your current stack is. But the point isn't precision. The point is that the subscription line item on your credit card is probably the smallest part of the problem.

A Different Way to Think About It

Consolidation doesn't mean finding one tool that does everything badly. It means finding a platform where the core functions of your business, projects, clients, finances, time, and communication, are designed to work together from the ground up, not bolted together through integrations.

Opus is built on exactly that principle. One database. One place where a project knows its client, its budget, its hours, its conversations, and its invoices. Not because integrations are syncing data between systems, but because those things were never separate to begin with.

It's built in Australia, hosted in Australia, and designed for the kind of business that doesn't have a dedicated IT team to maintain a 25-tool stack. Whether you're running a marketing agency, a trades business, a consulting practice, or a health clinic, the underlying problem is the same: too many tools, too much friction, too little visibility.

If you want to see what your stack could look like with the pieces actually connected, the features page at [opus.net.au](https://opus.net.au) is worth an hour of your Sunday. You might find it's a better use of the time than reconciling spreadsheets.