In multi location service businesses, disconnected legacy systems are not just an IT problem. They slow down the moment that matters most: the conversation with a family sitting across the table.
A leading North American bereavement services provider ran more than 150 funeral homes, cemeteries, and crematoria on a set of isolated legacy desktop applications. Client records lived in one place, product availability in another, and scheduling somewhere else entirely. Staff rekeyed the same information three times, printed compliance forms by hand, and had no reliable view of which burial spaces were actually available.
Net Solutions engineered a cloud based enterprise platform that became the single point of control for the entire customer lifecycle. It centralizes point of sale, contract management, compliance driven e-signatures, insurance backed payment plans, and multi location scheduling. We connected that hub directly to the existing Microsoft Dynamics 365 ERP and rebuilt the legacy field tools as an offline capable Progressive Web App.
The result: data silos removed, contract processing time down 35%, and manual administrative overhead down 30% across the network, delivered without a high risk rewrite and without taking a single live branch offline.
Faster contract processing time
Lower manual administrative overhead
Client snapshot locations on a single source of truth
Most enterprises treat scheduling, inventory, and contract execution as three separate administrative chores. Run that model across multiple regions with no single source of truth, and the friction compounds fast.
Separate legacy desktop applications held separate copies of the truth. Customer details, product availability, and calendar data all had to be entered more than once, which made record errors routine rather than exceptional.
Contract generation, compliance form printing, and updates to plot or crypt availability were all manual. Every handoff added days to delivery timelines and another chance for a mistake to reach a grieving family.
Branch staff and field coordinators had no real time view of daily service tracking, facility utilization, or inventory status. Scheduling conflicts were discovered late, usually by the person least equipped to fix them.
Cemetery crews worked in exactly the places mobile coverage is worst. Signal drops during interments and memorialization work created gaps in the record and pushed mandatory paperwork into a backlog that someone had to reconstruct from memory at the end of the day.
Digital signatures are not universally permitted. Certain jurisdictions restrict exactly which agreements can be signed electronically, and the applicable rule depends on the location, the document type, and sometimes both. Expecting staff at 150+ sites to track that correctly was not a viable control, so the platform needed automated, rules driven overrides rather than training and hope.
Core operational modules were locked into Angular v5 and weighed down by rigid, resource intensive third party visual plugins (Wijmo/GrapeCity) that dominated page load. The result was severe latency on the screens staff used most, a codebase that resisted extension, and no meaningful mobile responsiveness for crews working outdoors.
The most constraining problem was not the age of the code but what sat on top of it. The central single sign on package was compatible only with Angular 11, which ruled out any direct move to version 13 or 14. Forcing the upgrade risked login failure across every live branch simultaneously, in a business that cannot ask a family to come back tomorrow.
The obvious move was a full rewrite. We advised against it.
Given the authentication constraint, a jump to the newest Angular release would have traded a slow platform for an unavailable one. We isolated the problem instead of detonating it, and scoped a staged, risk mitigated roadmap: refactor the frontend in place, strip out the heavy legacy dependencies, upgrade only as far as the single sign on package safely allowed, and introduce modern data synchronization pipelines to connect distributed field tools back to the corporate database core.
We delivered the platform in five layers, each able to go live independently of the others. The first four solved the problems the business felt every day: scattered records, manual contracts, unreliable inventory, and crews working blind in the field. The fifth dealt with the constraint underneath all of them, and it is the reason the other four could ship at all.
We built a centralized, cloud based platform that acts as the single point of control for the entire customer lifecycle. A single profile view gives staff instant access to client details, preferences, and historic arrangements from any location in the network.
We paired that with a centralized, rules driven document repository that automatically serves the correct location compliant forms, so the right paperwork is the default rather than something staff have to remember.
We engineered an automated property management layer that tracks burial spaces, crypts, and niches across the entire network.
The operational execution module coordinates cremations, interments, and memorialization workflows, and it is used by the people least likely to have a reliable signal. We rebuilt it as a high performance Progressive Web App.
Service workers cache data locally so field teams can view and enter real time operational data fully offline. Real time GraphQL pipelines handle the reconciliation, synchronizing automatically with the central Microsoft Dynamics 365 ERP as soon as connectivity returns. No record is lost, no crew has to write anything twice, and the end of day backlog disappeared.
Rather than accept either a slow platform or a risky rewrite, we modernized the frontend in place and stopped exactly where the dependency told us to.
Digital e-signature workflows and automated document routing accelerated contract closure and cut the back and forth that used to sit between agreement and execution.
Digital validation rules and a unified customer record eliminated duplicate data entry, which returned hours to staff and let them spend that time on family care rather than forms.
Real time ERP synchronization gave every branch one authoritative view of physical space availability, ending double bookings.
The platform’s validation architecture tracks mandatory legal paperwork such as burial permits and cremation certificates, and blocks service status changes until every compliance check is satisfied.
Enterprise modernization fails more often on sequencing than on code. Our value here was knowing which upgrade not to attempt.
We combine deep integration engineering with disciplined product strategy, which means we look at the authentication dependency and the compliance rulebook before we look at the component library. A modernized frontend is only as good as the synchronization logic underneath it, and a compliance workflow is only as good as its worst connected branch.
By setting clean component boundaries and treating content, inventory, and compliance as independent product layers, we build systems that keep evolving after the engagement ends.
If you operate a distributed service network on aging software and cannot afford downtime to fix it, that is the problem we solve.
The provider ran 150+ funeral homes, cemeteries, and crematoria on isolated legacy desktop applications. Client records, product availability, and scheduling data lived in separate systems, which forced duplicate data entry, kept contract generation on paper, and left branch staff without a real time view of inventory or facility utilization.
Contract processing time dropped 35% and manual administrative overhead dropped 30% across the network. Real time ERP synchronization eliminated inventory double bookings, automated validation now blocks service status changes until mandatory permits are verified, and the entire rollout happened with zero live system downtime.
The client’s single sign on package was compatible only with Angular 11. Forcing a jump to version 13 or 14 would have broken authentication across every live branch. Upgrading from v5 to v11 removed the worst technical debt, restored performance, and preserved login stability, which mattered more than being on the newest release.
Most of the latency came from rigid, resource intensive third party visual plugins (Wijmo/GrapeCity) that dominated page load on the screens staff used most. We removed those dependencies entirely and rebuilt the affected interfaces with lightweight native Angular components, which sharply reduced the application’s processing footprint and removed the third party licence constraint on future changes.
The application evaluates regional compliance rules at runtime and automatically hides digital signature options in jurisdictions where they are prohibited for a given agreement. Staff cannot select a non compliant signing method, so regulatory adherence is enforced by the system rather than by training or manual checklists.
The field execution module is a Progressive Web App. Service workers cache data locally so crews can view and enter operational records fully offline, and the app synchronizes automatically with the Microsoft Dynamics 365 ERP once connectivity returns. No records are lost and nothing has to be re-entered later.
Burial spaces, crypts, and niches are tracked in a real time property management layer that synchronizes instantly with the central ERP. Every branch reads from the same authoritative availability record, so two locations can no longer sell or reserve the same plot, crypt, or niche.
OneSpan handles remote and in person e-signatures. Trustage supports insurance backed payment plans and itemized cost calculation. Canada Post validates addresses. The Microsoft Outlook API powers multi location scheduling with availability checks and conflict alerts, and Microsoft Dynamics 365 serves as the ERP system of record.
Yes. The same pattern fits any distributed operation where inventory, scheduling, contracts, and regional compliance are currently handled in separate systems. Healthcare networks, property and facilities operators, equipment rental, and field service organizations all face the same combination of legacy constraints and zero tolerance for downtime.
Tell us where the friction is. We will review your current stack, dependencies, and compliance constraints, then come back with a staged modernization path and a realistic view of risk.
Results matter. Discover how our customized solutions have delivered measurable business outcomes for clients across various industries. Each case study highlights the strategic impact of our work, turning challenges into opportunities for growth.
Ask Sol anything about digital products, AI, engineering, or growth, and get answers drawn from years of Net Solutions thinking and experience.