Twenty-Five Subscriptions, One Business: What Your SaaS Stack Is Actually Costing You

The average Australian SME is running 25 or more separate SaaS subscriptions at any given time. Most business owners know roughly what they pay per month. Very few have calculated what those tools cost in total, once you account for everything that isn't on the invoice.

This post does that calculation.

The Subscription Line Item Is the Easy Part

Start with the obvious: the monthly charges. A typical SME stack might look something like this:

• Project management (Asana, Monday.com or similar): $120/month for a team of ten
• CRM (HubSpot Starter or Salesforce Essentials): $90 to $450/month
• Time tracking (Harvest or Toggl): $60/month
• Team messaging (Slack): $100/month
• Accounting (Xero or MYOB): $80/month
• Document storage (SharePoint or Google Workspace): $60/month
• E-signature (DocuSign or similar): $45/month
• Reporting/BI (Power BI or Looker Studio with connectors): $120/month
• Integration middleware (Zapier or Make): $80 to $200/month
• HR and onboarding tool: $90/month
• Password manager: $30/month
• Video conferencing: $50/month

That's twelve tools and roughly $900 to $1,400 per month before you've touched anything industry-specific. Add a quoting tool, an equipment tracker, a scheduling app, a client portal, and a form builder, and you're looking at $1,800 to $2,500 per month for a modest team.

Annualised, that's $21,600 to $30,000. For a ten-person business, that's $2,160 to $3,000 per employee per year, just to keep the lights on operationally.

That number is uncomfortable. The number underneath it is worse.

The 23-Minute Tax on Every Interruption

In 2005, Gloria Mark at the University of California, Irvine published research showing that it takes an average of 23 minutes and 15 seconds to fully regain concentration after an interruption. That figure has been replicated and refined in subsequent studies, and the core finding holds: switching context is expensive, and the cost is paid in cognitive recovery time, not just the seconds spent switching.

Now consider what a fragmented SaaS stack does to a working day.

A project manager checks Asana for task status, opens Slack for a client update, switches to Gmail to find an attachment, jumps to Harvest to log time, opens Xero to check whether an invoice has been paid, and then returns to Asana. That's five context switches in under ten minutes. Each one carries a recovery cost. Each one pulls attention away from the work itself.

Research from Asana's own Anatomy of Work report (2023) found that knowledge workers switch between apps an average of 25 times per day. If even a fraction of those switches carry a meaningful refocus penalty, the productivity loss across a ten-person team is not marginal. It's structural.

A conservative estimate: if each employee experiences five meaningful context switches per day, each costing ten minutes of effective recovery time (well below the 23-minute ceiling), that's 50 minutes of lost productive capacity per person per day. Across ten people, that's 500 minutes, or roughly 8.3 hours, every single working day.

At an average fully-loaded cost of $60 per hour for a knowledge worker, that's $498 per day, or approximately $124,500 per year. From context-switching alone.

That figure will vary by business. But even at a quarter of that estimate, you're looking at $30,000 per year in lost output that never appears on any invoice.

Duplicate Data Entry: Paying Twice for the Same Information

When your tools don't share a database, your people become the database.

A new client is won. Someone enters their details into the CRM. Someone else creates a project in the project management tool. A third person sets up a billing contact in the accounting software. The client's name, ABN, address, and contact details now exist in three separate systems, entered by hand, three times.

When the client's address changes, someone has to update it in three places. When it only gets updated in two, the invoice goes to the wrong address. When it only gets updated in one, the CRM shows stale data and a sales rep follows up a contact who moved on six months ago.

This isn't a hypothetical failure mode. It's the default state of any business running disconnected tools.

A 2022 study by Salesforce found that data entry and administrative duplication accounts for approximately 17% of a typical knowledge worker's week. For a ten-person team working 40-hour weeks, that's 68 hours per week spent re-entering information that already exists somewhere in the business.

At $60 per hour, that's $4,080 per week, or $212,160 per year.

Again, your numbers will differ. But the direction of the calculation doesn't change.

Integration Maintenance: The Hidden Engineering Tax

At some point, most businesses try to fix the fragmentation problem by connecting their tools. Zapier, Make, and similar middleware platforms exist precisely because SaaS vendors don't talk to each other natively.

The problem with integration middleware is that it trades one kind of fragility for another. Every integration is a dependency. When a vendor updates their API, the integration breaks. When you upgrade your CRM tier, the field mappings change. When you add a new tool, you need a new set of Zaps or scenarios to wire it in.

Small businesses that build these integrations themselves spend time they don't have maintaining them. Businesses that outsource it pay a developer $150 to $250 per hour to keep the plumbing working. Either way, the cost is real and recurring.

A conservative estimate for a business running fifteen to twenty tools with ten to fifteen active integrations: four to eight hours of integration maintenance per month, plus the middleware subscription itself. At $200 per hour for external development support, that's $800 to $1,600 per month, or $9,600 to $19,200 per year, on top of the middleware subscription.

The Full Accounting

Pull these numbers together for a ten-person SME:

• SaaS subscriptions: : $21,600 to $30,000 per year
• Context-switching productivity loss: : $30,000 to $124,500 per year (conservative to full estimate)
• Duplicate data entry: : $50,000 to $212,000 per year (conservative to full estimate)
• Integration maintenance: : $9,600 to $19,200 per year

Total: $111,200 to $385,700 per year

Even at the conservative end, you're looking at over $100,000 per year in costs that don't appear on any single line item. They're distributed across payroll, contractor invoices, and the invisible drag of a team that spends more time managing tools than doing work.

This is the admin balloon that the Business Triangle describes. When systems aren't working, administration expands to fill the available time. A healthy business runs at roughly 20% admin. A business held together with disconnected SaaS tools often runs at 50% or more, with the shortfall coming directly out of craft and business development.

Why More Tools Doesn't Solve It

The instinct when something isn't working is to add a tool. The project management tool isn't showing financial data, so you add a BI tool. The BI tool doesn't connect cleanly, so you add a middleware layer. The middleware breaks, so you add a monitoring tool.

Each addition increases the surface area of the problem. The integration graph grows. The maintenance burden grows. The number of places where data can be wrong grows.

The consolidation argument isn't about finding a single tool that does everything perfectly. It's about recognising that the cost of fragmentation compounds. Every new tool you add increases the cost of every other tool you already have.

What Consolidation Actually Looks Like

Opus was built around a single PostgreSQL database. Projects, finances, clients, timesheets, equipment, and team communication all share one data model. When a timesheet entry is submitted, it flows directly into the project's cost calculation. When a client's details change, they change once. When you want to know whether a project is profitable, the answer is available immediately, not after someone exports data from three systems into a spreadsheet.

This isn't a philosophical position about software architecture. It's a practical response to the cost structure described above. A single database eliminates the duplicate entry problem by design. It removes the integration maintenance cost entirely for the functions it covers. It reduces context-switching because the information a team member needs is in one place, not distributed across a dozen browser tabs.

For Australian SMEs already paying for Xero, Opus connects via two-way sync rather than replacing it, because Xero handles tax compliance well and there's no reason to rebuild what works. The goal is to replace the tools that are creating fragmentation, not to replace everything indiscriminately.

The Decision Framework

If you're evaluating your current stack, the questions worth asking are:

• How many tools require manual data entry that duplicates information already in another system?
• How many active integrations are you maintaining, and when did one last break?
• How long does it take to answer a question like "is this project profitable" or "what did this client spend with us last year"?
• What percentage of your team's week is spent on administrative tasks that exist because systems don't talk to each other?

The answers to those questions define the cost of your current architecture. The subscription invoices are the smallest part of it.

If you want to work through what consolidation might look like for your business, the team at Opus can walk through your current stack and identify where the real costs are sitting. Start at [opus.net.au](https://opus.net.au).