OPERATOR CASE NOTE · Operator Case Note, Overhead and Growth
Reducing IT Overhead While Supporting Multi-Site Growth
Multi-site ambulatory organization during a period of expansion
Roughly One-Third
Reduction in recurring technology expense
Significant Growth
Supported during multi-site expansion
One
Standard site-build playbook
Situation
The organization had grown by acquisition and opportunistic site openings. Every new location had solved its own technology problems locally, so the estate had accumulated overlapping contracts: multiple connectivity vendors, several phone systems, duplicated licensing, redundant support agreements, and hardware refresh cycles that nobody owned.
Nobody could produce a single list of every technology contract, its renewal date, and its annual cost. That absence, not any individual bad deal, was the actual problem. Auto-renewals passed unexamined because no calendar existed to examine them against.
The growth plan called for several more sites. Each prior opening had consumed months of senior leadership attention on problems that were identical to the last opening, because there was no standard build.
What the Operator Found
Every turnaround starts with measurement. These were the findings that changed the priority order.
No contract register
Spend could not be managed because it could not be seen. Renewal dates, terms, and overlapping scopes lived in individual inboxes.
Duplication from growth by accretion
Each acquired or opened site brought its own vendors. Nothing was ever retired, so the organization paid several times for the same capability.
Auto-renewal as the default negotiating posture
Contracts renewed without a competitive look because nobody was accountable for the calendar. Every renewal was a missed negotiation.
Every site opening was a custom project
Without a documented build standard, expansion cost was dominated by rediscovery rather than by the actual work.
Action
Built the contract register first
Every technology and infrastructure agreement was catalogued with cost, term, renewal date, and owner. The register itself surfaced immediate duplication before a single negotiation started.
Consolidated overlapping vendors
Where multiple vendors delivered the same capability across sites, the estate was standardized onto one and the rest were wound down at term. Consolidated volume also improved the pricing on what remained.
Renegotiated against real usage data
Renewals were approached with utilization evidence, seats actually used, bandwidth actually consumed, tickets actually raised, rather than with the prior year's invoice.
Wrote a standard site build playbook
Connectivity, hardware, licensing, phones, and go-live sequencing were documented once with a defined cost per site. Subsequent openings followed the playbook instead of improvising.
Put a renewal calendar on the operating cadence
Upcoming renewals appeared in the monthly operating review 120 days out, so negotiation became scheduled work rather than a scramble.
Result
Recurring technology expense fell by roughly one-third without reducing core capability. The largest gains came from eliminating duplication, consolidating overlapping vendors, and creating visibility into contracts and renewal dates.
At the same time, standardized infrastructure and a repeatable site-build process reduced the amount of senior leadership attention required for each expansion. The organization was able to support significant growth without continuing to recreate the same technology decisions at every location.
The renewal calendar and contract register remained in the monthly operating review, which is what kept the savings from quietly reaccumulating.
Why It Worked
Overhead rarely arrives in a single bad decision. It accumulates as a series of reasonable, urgent, local choices that nobody ever revisits. The register is the intervention; the negotiation is just the follow-through.
Important Context
This work took place in a particular organization under particular circumstances. Results in your practice will depend on its operations, payer mix, market, leadership, staffing, and execution.
About these case notes: they are drawn from prior healthcare operating experience. Organization details, scale, timelines, and selected results have been generalized where appropriate to protect confidentiality. They are shared as evidence of method, not as Edison Breakwater client results or predictions of what another organization will achieve.