The operations platform its acquirer couldn't replace
We spent eight years building a custom enterprise operations platform for a U.S. medical equipment service organization. When the company was acquired, the plan was to migrate everything onto a standard enterprise system. The plan changed — because the platform modeled the business better than anything off the shelf could.
A business that had outgrown its systems
The client services medical equipment for hospitals, surgical centers, and healthcare systems across the U.S. — depot repair, field repair from mobile vans, loaner devices, vendor coordination, quality control. Their ERP handled the money. Nothing handled the work.
A standard CRM could hold the accounts. The ERP could hold the ledger. Neither could model a medical device moving through intake, inspection, quote, approval, repair, final QC, and shipment — with a loaner keeping the hospital running in the meantime. So we built the system that could.
One platform, every workflow, four audiences
The platform grew from CRM and dashboards into a custom vertical ERP — the operational system of engagement, integrated with the client's existing ERP as the financial system of record.
One business object at the center
Every repair — intake, inspection, quote, approval, repair, final QC, shipment — lives on a single Work Order. Every department works on the same record from its own perspective. No duplicate processes, no swivel-chair data entry.
Portals, not separate systems
Customers create and track repairs; vendors update outsourced work. Both portals expose controlled views of the same internal workflow — one engine, one audit trail, zero synchronization headaches.
The ERP stayed where it belonged
We never tried to replace the client's ERP. It remained the financial system of record while the platform owned operations — connected through APIs and scheduled synchronization. Lower risk, faster delivery, preserved investment.
Built module by module, never a big-bang rewrite
- 2017
Foundation
CRM, dashboards, reporting, and ERP integration groundwork. The goal was operational support — not yet an ERP replacement.
- 2018
The work order becomes the center
Work order management, structured quality control, the customer portal, and the offline field service application. The platform became the daily workspace for operations.
- 2019
Enterprise growth
Vendor portal, loaner asset management, contract management, preventive maintenance, fleet analytics. Business processes became fully interconnected.
- 2020–22
Scaling
Working-vs-history data architecture, background archival, query optimization, deeper ERP synchronization. The database passed 500 tables while screens stayed fast.
- 2022–25
Mature platform
700,000+ work orders, 2,000+ users, millions of history records — plus a full migration of the platform to a modern, long-term-supported .NET stack.
- Today
Still in production
The platform continues to run the business years after active development ended — the quietest, strongest endorsement enterprise software can get.
Three decisions that made it last
Longevity wasn't luck. It came from architecture decisions that respected how the business actually operates.
Designed for hospital parking garages, not perfect Wi-Fi
Field technicians repair surgical instruments from mobile vans — often in underground garages with no signal. A web app was never going to work. We built an offline-first desktop application on a local database: technicians sync in the morning, work all day disconnected, sync when they're back online.
The key innovation: synchronization transfers the entire local database as one atomic snapshot instead of dozens of fragile API calls. Either the whole sync succeeds, or nothing changes. Interrupted connection? Just retry. No partial states, no lost work — ever.
Fast at 700,000 work orders — by design
Most systems slow down as data accumulates. We recognized early that operational and historical data have completely different jobs: users work on today's 7,000–10,000 open orders, while hundreds of thousands of closed orders exist for history, audits, and reporting.
So the database separates working tables (small, hot, heavily indexed) from history tables (read-mostly, unlimited growth). Background jobs continuously archive closed work. The result: screens stayed sub-second for eight years while the dataset grew into the millions of records.
Business users answering their own questions
Instead of developers hand-building every report, we built a metadata-driven reporting engine. Developers expose curated datasets; business users build, filter, pivot, save, and export their own reports — no release cycle required.
The showpiece: automatic PowerPoint generation. Account managers select a customer and a period, and the platform assembles a presentation-ready business review from live operational data. Hours of manual preparation became minutes — and every meeting ran on current numbers.
The proof no marketing metric can match
When the client was acquired, the plan was to retire the platform and migrate onto the acquirer's standard enterprise system. After evaluation, the custom platform stayed — and half of the combined organization kept running on it.It wasn't preserved because it was fashionable. It was preserved because it modeled the business correctly.
Figures are production-scale numbers from the engagement. Client identity withheld under confidentiality; diagrams recreated for publication.
Every solution has its own story
Software for places where the internet doesn't reach
150+ van technicians, atomic snapshot sync, zero partial states.
Read the story → ERP IntegrationDon't replace the ERP — surround it
System of record vs. system of engagement: the boundary that held for a decade.
Read the story → Data ArchitectureFast at 700,000 work orders — by design
Working vs. history tables and the archival pipeline behind eight years of speed.
Read the story → PortalsOne workflow, three audiences
Customer and vendor portals as controlled views of a single workflow engine.
Read the story → Quality & ComplianceQuality control that holds up in a dispute
Device-specific templates, photo evidence, and two enforced QC gates.
Read the story → Business IntelligenceThe reporting backlog that deleted itself
Self-service BI and customer-ready PowerPoint decks from live data.
Read the story → LogisticsEvery device, accounted for
300k+ tracked equipment movements — with loaners keeping hospitals running.
Read the story →The same work, productized
Your operations deserve software that outlives the slide deck.
Start with an Operational Intelligence Assessment — the same understand-the-business-first approach that made this platform irreplaceable.
Book an Operational Intelligence Call