The number on the invoice is not the cost
When a multi-site operator adds up the cost of its software, the easy figure is the one on the invoices: a licence here, a per-seat charge there, a payments fee on top. That number is real, but it is not the cost. The larger cost of a stack of disconnected tools is the work of holding it together, and that work rarely appears on any invoice. It is spread across the finance team, the operations team and the front desk, in hours that are simply absorbed into the week.
This resource is about counting the real total. The point is not that software is expensive, it is that the cost of disconnected software is mostly hidden, and that hidden cost is what an integrated platform is designed to remove.
The four hidden costs
A stack of separate tools carries four costs beyond its licence fees.
The first is integration. Tools that do not share data have to be connected, and connectors have to be built, monitored and fixed when they break or when one tool changes. That is ongoing engineering or vendor cost, and it grows with every tool you add.
The second is reconciliation. When the same event lives in two systems, someone has to make them agree. The classic case is the front desk and the ledger: a casual entry is an operational record in one system and needs to become an accounting entry in another. Multiply that across venues and pay cycles and it becomes a standing job.
The third is duplicated administration. A new staff member is set up in the rostering tool, again in payroll, again in the access system. A member exists in the booking tool and again wherever finance sees them. Every duplicate is a place to maintain and a place to get out of step.
The fourth is the cost of missing visibility. When the data is scattered, the questions that matter at head office, such as how a program performed across all sites or what the network actually earned this week, take a reporting project to answer. The cost here is the decisions delayed or made on stale numbers.
How to count your own total
You can estimate your own total without a formal study. List the systems you run: facility or club management, accounting, payroll and rostering, maintenance, signing, governance. For each pair that needs to share data, note how that sharing happens today, whether by a connector, a scheduled export, or someone re-keying it. Then estimate the hours per week spent keeping those tools in sync and the hours spent assembling cross-system reports.
That weekly figure, annualised, is usually larger than people expect, and it grows as sites are added. It is also the figure that an integrated platform reduces, because it attacks the joins rather than the licences.
How an integrated platform changes the maths
Cohiva is built as one platform with purpose-built products on top of it, sharing one identity and one data layer. That structure removes the joins that drive the hidden costs.
- Complex runs the venue: classes, memberships, point of sale, bookings and access control.
- Crunch is the finance product. Transaction data flows natively from Complex, so the reconciliation between operations and the ledger largely disappears.
- Culture is the HRIS. Staff records flow into Complex for rostering, so a person is set up once, not three times.
- Control is the maintenance system, and it posts depreciation to the ledger, so an asset's maintenance and accounting views are one record.
Because these products share a foundation, adding one does not add another integration to maintain. The capability does not shrink, since each product is deep in its own category. What shrinks is the cost of the joins, which is where most of the hidden total lives.
The trade to weigh honestly
An integrated platform is not free, and a single specialist tool can be cheaper in isolation for a single job. The honest comparison is not licence against licence. It is the full cost of running and connecting a stack against the full cost of running a platform. For a single-site operator with a short list of tools, a stack may well win. For a multi-site operator whose list is long and growing, the hidden costs usually dominate, and removing the joins is where the saving is.
Where to go next
To see the operating model behind the saving, read one platform, one data layer. For the direct comparison of the two approaches, read integrated suite vs point solutions. And to picture the model in a real operation, read running a multi-site leisure operator on one platform.
If you want to see the products that make up the platform, start with the Complex overview and Crunch overview, or explore the full set from the products hub.