The Fragmentation Tax.What 8–12 vendors actually cost.

Operators don’t buy a fragmented stack. They inherit one — one renewal, one acquisition, one well-meant point solution at a time. By the time it’s 8–12 vendors deep, the cost has stopped being visible on any single invoice. This report puts the cost back on the page.

Use the operator’s own contracts, invoices, payroll, integration logs, and workflow records. SeniorCRE publishes no universal savings range and does not present this worksheet as measured operator-production evidence.

The teardown — 10 costs of fragmentation

1. 01 · License stacking
   Enter the recurring cost of each retained application, including minimums, modules, users, interfaces, and support.
2. 02 · Integration build cost
   Enter internal and external costs to build, test, monitor, repair, and revalidate each interface.
3. 03 · Integration change
   Record actual rebuild work caused by API changes, schema drift, acquisitions, re-platforming, and security reviews.
4. 04 · Reconciliation labor
   Measure the staff time your properties actually spend reconciling census, billing, eMAR, and payroll across systems. Use payroll-backed hours rather than an industry estimate.
5. 05 · The BI overlay
   Enter the actual cost of data pipelines, warehouse or BI licenses, report maintenance, and manual validation.
6. 06 · Security review load
   Count the security review, BAA, reassessment, incident-response, and evidence work required for each applicable vendor.
7. 07 · Cross-module workflow gaps
   Document workflows that require middleware, duplicate entry, manual handoffs, or delayed decisions.
8. 08 · Authority conflicts
   Record where legitimate systems disagree, which decisions are affected, and whether definitions, source authority, exceptions, and lineage are explicit.
9. 09 · Survey and audit evidence
   Measure the effort required to assemble control evidence across source systems without assuming that consolidation establishes authority.
10. 10 · Vendor management overhead
    Enter payroll-backed time for renewals, escalations, outage triage, contract review, and vendor governance.

Annualized fragmentation tax — 30-community portfolio

All values are operator-entered. Commercial terms are not published and remain outside this calculation.

Why the tax persists

Inheritance, not choice. No operator sat down and designed an 8–12 vendor stack. They acquired one with each community, each EHR loyalty, each well-meant pilot.

Per-line invisibility. Each contract individually is defensible. The sum is not. No single line item triggers a board conversation.

Integration sunk cost. Every integration already built feels too expensive to abandon — until the next API break forces the rebuild anyway.

Vendor mythology. The industry has accepted “senior care is too specialized for a single platform” as a given. The data does not support it; the architecture does not require it. See the companion essay: Why senior housing & care got stuck on best-of-breed.

Recommended action

Operators do not need to rip and replace. Start by documenting definitions, source authority, reconciliation rules, exceptions, and lineage across retained systems. Replace a system only when the operator chooses and after explicit readiness and acceptance gates are met.