The SaaS Bill Is the Smallest Part of What Those 25 Apps Are Costing You

The average Australian SME runs between 25 and 40 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 aggregate, and almost none have accounted for the costs that never appear on a credit card statement.

This post does that calculation.

The Subscription Layer: What You Can Actually See

Let's start with the visible number. A typical SME running a modest stack might carry:

• Project management: $15 to $25 per user per month (Asana, Monday.com, Trello)
• CRM: $50 to $150 per user per month (HubSpot, Salesforce)
• Time tracking: $10 to $20 per user per month (Harvest, Toggl)
• Team chat: $8 to $15 per user per month (Slack)
• Accounting: $60 to $120 per month (Xero, MYOB)
• Document storage: $10 to $25 per user per month (SharePoint, Google Workspace)
• Integration middleware: $50 to $200 per month (Zapier, Make)
• Reporting and BI: $30 to $100 per user per month (Power BI, Looker)

For a ten-person team, that stack lands somewhere between $4,000 and $8,000 per month before you add the niche tools: e-signature platforms, scheduling software, equipment trackers, proposal builders, and the three apps that one team member swore were essential eighteen months ago and nobody cancelled.

According to Productiv's 2024 SaaS Management Index, the average per-employee SaaS spend for SMEs sits at approximately $4,800 AUD annually. For a team of ten, that is $48,000 per year in subscriptions alone. That number is uncomfortable but at least it is knowable.

The costs below are harder to see. They are also larger.

The Context-Switching Tax

In 2001, Gloria Mark at the University of California, Irvine began studying how knowledge workers recover from interruptions. Her research, replicated and extended across multiple studies, produced a figure that should concern every business owner: after switching tasks or applications, the average worker takes 23 minutes to return to full cognitive engagement with the original task.

Twenty-three minutes. Not two. Not five. Twenty-three.

In a fragmented SaaS environment, your team is not switching applications occasionally. They are switching constantly. A project update in Asana triggers a question in Slack, which requires pulling up a client record in HubSpot, which surfaces an invoice query that needs Xero, which prompts a timesheet check in Harvest. That sequence, which might take four minutes to execute, carries a recovery cost measured in tens of minutes per transition.

Mark's later research found that workers in high-interruption environments self-interrupt at increasing rates over time, partly because the cognitive cost of sustained focus in a fragmented environment becomes too high. The brain learns to expect interruption and stops investing in deep work.

If each of your team members switches between major applications eight times per day (a conservative estimate in a multi-tool environment), and each switch carries even a fraction of the 23-minute refocus penalty, the productivity loss per person per week runs into hours. At an average loaded labour cost of $45 to $65 per hour for knowledge workers in Australia, that is a cost you are paying every week without a single invoice to show for it.

For a ten-person team, conservative modelling puts this loss between $60,000 and $120,000 per year in productive capacity. That is capacity that could go toward delivering work, winning clients, or building the business.

Duplicate Data Entry: The Work That Creates No Value

Disconnected systems do not share data. That is not a design flaw; it is a structural reality of buying separate products from separate vendors. The consequence is that your team enters the same information multiple times across multiple systems.

A new client gets created in the CRM. Then in the project management tool. Then in the accounting platform. Their contact details, project scope, billing terms, and agreed rates live in three or four places simultaneously, and none of those places talk to each other automatically unless someone has built and is maintaining an integration.

When details change, which they do, someone has to update each system manually. When they forget, which they do, the systems diverge. You get a project in Asana with one scope, a contract in your document system with a different scope, and an invoice in Xero that reflects neither.

A 2023 study by Salesforce found that data entry and administrative duplication consumes an average of 11.5 hours per employee per week in organisations without integrated systems. Even if your team is more efficient than that average, at five hours per person per week across ten people, you are losing 50 hours weekly to work that generates no output. That is more than one full-time equivalent position dedicated entirely to re-entering data that already exists somewhere.

Integration Maintenance: The Hidden Engineering Cost

Many businesses attempt to solve the disconnected-systems problem with integration middleware. Zapier and Make (formerly Integromat) are the most common choices. They allow you to build automated workflows that pass data between applications when certain conditions are met.

This works, up to a point. The problems emerge over time.

Every integration you build is a dependency on two external APIs simultaneously. When either vendor updates their API, changes their data model, or modifies their authentication requirements, your integration breaks. You either pay someone to fix it, spend hours troubleshooting it yourself, or discover it was broken three weeks ago when you notice that 47 client records failed to sync.

For businesses running 10 to 20 active Zapier workflows, the maintenance burden is not trivial. Zapier's own research suggests that complex automation workflows require meaningful ongoing maintenance as connected apps evolve. Add the cost of the middleware subscription itself ($50 to $500 per month depending on task volume), the staff time to build and maintain workflows, and the periodic cost of fixing broken integrations, and the integration layer adds several thousand dollars annually to your true SaaS cost.

More importantly, integrations are approximations. They pass selected fields between systems on a schedule or trigger. They are not the same as having one system that holds all the data natively. The gap between those two things is where reporting errors, billing mistakes, and project cost blowouts live.

The Reporting Gap

When your data lives across eight systems, producing a meaningful business report requires someone to extract data from each system, reconcile the formats, and assemble it manually. This is typically done in a spreadsheet, which introduces its own error surface.

The consequence is that most SMEs are operating on financial and operational information that is weeks old by the time it reaches the person who needs to make decisions. Project profitability is calculated after the project closes, not while it is running. Client acquisition costs are estimated, not measured. Staff utilisation is approximated from timesheet exports that someone remembered to pull last Thursday.

Decisions made on stale, incomplete data are not decisions. They are guesses with extra steps.

Adding It Up

Here is a conservative total cost model for a ten-person SME running a standard fragmented SaaS stack:

• Subscriptions: : $48,000 per year
• Context-switching productivity loss: : $60,000 to $120,000 per year
• Duplicate data entry (5 hours per person per week at $55/hr): : $143,000 per year
• Integration maintenance (build, fix, middleware costs): : $8,000 to $20,000 per year

Total: somewhere between $259,000 and $331,000 per year.

The subscriptions, the part everyone focuses on, represent less than 20% of the true cost.

Why Consolidation Is an Operational Decision, Not Just a Financial One

The argument for consolidating your SaaS stack is not primarily about saving money on subscriptions. It is about recovering the productive capacity that fragmentation destroys.

When projects, finances, clients, timesheets, and communications share a single data model, several things change structurally. Data entered once is available everywhere. A timesheet entry feeds directly into project cost calculations without any manual reconciliation. A client record connects to every project, invoice, and conversation without duplication. Reporting is real-time because the data is already unified.

The context-switching problem does not disappear entirely, but it shrinks substantially when the answer to most questions lives in one place rather than requiring four application switches to find.

This is the design principle behind Opus. Not a bundle of separate tools sharing a login screen, but a single PostgreSQL database that treats projects, finances, clients, equipment, and team communications as facets of one connected data model. The AI business intelligence layer works because it can see all of that data simultaneously, not because it has been trained to guess at what might be in a system it cannot access.

The Business Triangle concept is useful here. Admin balloons not because business owners are disorganised, but because fragmented systems create administrative overhead structurally. Every disconnected tool adds friction. Consolidation is how you compress that friction back to something manageable, freeing time for the work that actually builds the business.

Before You Audit Your Stack

If you are going to calculate your true SaaS cost, be honest about the hidden layers. List every subscription, including the ones on personal credit cards and the trials that became paid accounts. Estimate the hours your team spends moving data between systems each week. Ask how many of your Zapier workflows have broken in the last six months.

The number you arrive at will almost certainly be larger than you expected. It usually is.

For businesses that have done this exercise and decided the fragmentation cost is no longer acceptable, Opus is worth a closer look. The details are at [opus.net.au](https://opus.net.au).