Executive Summary
Old systems don’t lose you families. Silence does. A family asks one simple question, and nobody in the room can answer it.
Multi-location groups collect systems through acquisitions, growth, and department choices. Each site keeps working, so nothing looks broken. The cost still lands in 4 places: family experience, staff time, revenue, and group-wide visibility.
Modernization should not start with replacement. Start by defining your core records, fixing the one that most often delays a family, and connecting the systems you already run in phases that each stand on their own.
Key Takeaways
- Families feel fragmentation first. The question you cannot answer in the room costs more trust than any back-office inefficiency.
- Fragmentation leaks revenue. Services sold twice, spaces hidden from other sites, and charges that never reach finance are margin problems, not reporting defects.
- Watch for the system nobody works in. When staff do the real work elsewhere and log it later, your data describes your paperwork, not your business.
- Replacing everything is rarely the right first move. A group-wide cutover risks the one week you cannot afford to get wrong.
- Every phase should stand on its own. If a phase pays off only when the whole program lands, the program will not land.
A daughter sits down with one of your directors. Her mother has passed away. Her father was buried 11 years ago at one of your cemeteries, about 40 minutes away. She has one question: can Mom go in with Dad, and what will it cost?
It is the most ordinary question in this business. In many multi-location groups, the director cannot answer it today. The grave record sits at the other site, on a different system. The deed may be in a filing cabinet. Pricing is set regionally, and the version in front of him may be out of date. So he promises to call her tomorrow, and it takes 3 days.
One question from one family
“Can Mom be buried with Dad, and what will it cost?”
Part 1
Is there space in the grave?
Depth, existing interments, whether the plot allows another.
Cemetery system, other site
Part 2
Who holds the right?
Deed from 2015, holder possibly deceased, authority unclear.
Paper file, cemetery office
Part 3
What does she already have?
A pre-need contract sold in 2011 at another location.
Legacy system, third site
Part 4
What is the price today?
Regional list, opening fee, memorial permit, product changes.
Spreadsheet, head office
4 systems, 3 locations, 2 phone calls that go to voicemail, and one grieving daughter waiting. Every part of the answer exists. None of it is in the room.
No individual system failed. Nothing crashed. Every location runs fine, which is exactly why this problem is so easy to live with.
For a multi-location funeral group, fragmented systems rarely look like a technology failure. They look like delayed answers, duplicated work, inconsistent pricing, missed revenue, and executives who cannot get one reliable view of the business.
At Net Solutions, we’ve worked on this problem at scale, including a program for a group operating over 150 facilities across 8 provinces. Our position is clear: modernization does not have to start with replacement. It starts with deciding what to define, what to fix first, and what to connect.
The rest of this article follows that path. It starts with what fragmentation costs you.
Fragmented Records Cost Your Group in 4 Places
The cost rarely appears as a single line item. It spreads across families, staff, revenue, and leadership.
1. Family Experience: Answers That Wait Until Tomorrow
This is where fragmentation matters most and where you measure it least.
- The question you cannot answer. Availability, entitlement, pre-need coverage, or a space beside a relative. Every deferral draws down the trust a family placed in you.
- The name spelled 2 ways. Staff enter it at the funeral home and again at the cemetery, and the register no longer matches the memorial. Families notice, and they remember.
- The pre-need contract nobody can find. Another location sold it 15 years ago, against a price list that no longer exists. The family holds the paperwork. You look uncertain.
- The double-booked chapel. One room, 2 calendars.
2. Staff Productivity: The Same Details, Entered Again and Again
Ask an arranger how many places they enter a family’s details. The answer is rarely one.
Each site also has one person who knows the old system. That person is usually excellent, long-tenured, and the reason the system still works. That is a single point of failure with a pension plan, and everyone knows it.
3. Revenue Leakage: Margin Lost Between Systems
This is the version of the problem that reaches your finance director.
- A service sold twice. Staff sells a service that a pre-need contract already covers.
- A space nobody can see. A plot sits available at one location and invisible to an arranger at another.
- A charge that never arrives. It never reaches finance, because nobody reconciled the operational record with the billing record.
None of these are reporting defects. They affect margin, cash collection, and how quickly an acquired location starts behaving like part of the group.
4. Enterprise Visibility: Numbers That Need a Caveat
You cannot compare locations, because they count differently. You cannot see real capacity across cemeteries. Month-end takes longer every year. When the board asks about performance by site, the answer takes a week and arrives with a caveat.
This is not a sign of bad management. It comes from decisions that each made sense at the time.
Every System Choice Made Sense. Together, They Created the Problem
Most groups arrive at fragmentation by one of 4 routes:
- Acquisition. A well-run funeral home arrives with software that works, staff who know it, and 20 years of records inside it. Migration is costly and risky, and the site earns from day one, so you leave it alone.
- Organic growth. A new crematorium needed something the funeral home system could not do. A cemetery needed different software again. Each branch bought the best option available that year.
- Department choices. Finance chose the accounting package, operations chose scheduling, and marketing chose the website and obituary platform. Each department picked well for itself.
- Mergers. Societies merged, dioceses combined administration, and family firms joined together. Each brought its own records and its own way of keeping them.
The route matters less than the destination. You end up with several ways to record a case, several contract numbering schemes, a few price list formats, and a finance team reconciling by hand every month.
Every individual decision was correct. The sum of those decisions is a group that cannot reliably answer a simple question from a family.
The most damaging version of this problem is also the easiest to miss, because the data looks fine.
The Most Dangerous System Is the One Everyone Uses, and Nobody Works In
On the program for the group with over 150 facilities, we expected to find software that lacked capability. We found the opposite. The arrangement system generated contracts and documents perfectly well. It simply did not match how staff actually worked.
So people did the real work the way they always had, on paper and in conversation. Then they came back to the system to log what had already happened. The system had stopped being a place where anyone worked. It had become a record-keeping tool.
One case, one working day
When the work happened, and when the system found out
09:15
First call taken, details written on a padCoordinator is on the phone, not at a desk
16:40
10:30
Arrangement conference, selections made on paperNobody types in front of a family
16:45
13:05
Cemetery confirms the space by phoneVerbal only, no record on either side
Next day
14:20
Family changes the service timeTold to the director in the parking lot
Not logged
16:40
Director enters the day from memory6 to 8 hours after the fact
16:40
Every field in this record will be populated, and every report will run. The database describes the paperwork, not the business.
Why No Data Audit Will Catch It
Every field gets populated, and every report runs. Nothing is missing, so no audit flags a problem.
But anything you build on that data inherits its unreliability without inheriting the warning. That includes reporting, forecasting, and any automation you are being sold.
Complete data is not the same as true data. A system can hold every field and still describe your paperwork, not your business.
This finding also explains why the usual fixes disappoint.
Three Obvious Fixes Make Fragmentation Worse
Once leadership sees the problem, 3 instincts usually follow. Each sounds reasonable. Each carries a risk that outweighs its promise.
| The instinct | The risk | The better move |
|---|---|---|
| Replace everything with one platform | A group-wide cutover in a business with no quiet week | Define and connect first, then migrate site by site |
| Wait for the vendor to solve it | Your mix of systems will never appear on any vendor’s roadmap | Own the connections between your systems yourself |
| Fix it with better reporting | Confident dashboards built on inconsistent data | Fix the records before the reports |
Instinct 1: “Replace Everything” Fails on Migration and Timing
Funeral homes and cemeteries need genuinely different things, and few platforms do both well. Migration means moving decades of records nobody cleaned, from systems with undocumented conventions. A cutover also needs a date, in a business that cannot pause. Deathcare has no quiet week.
One platform is sometimes the right end state. It is rarely the right first step, and rarely right everywhere at once.
Instinct 2: “Wait for the Vendor” Fails Because Your Mix Is Unique
Your vendors sell one product to many customers. Reconciling your particular combination of inherited systems is your problem, not theirs. That is not a criticism. It is their business model.
Instinct 3: “Better Reporting” Hides the Problem Behind a Chart
This is the most common and the most expensive mistake. A dashboard across 8 locations that count differently produces confident, wrong numbers, and people act on them. You’d be better off knowing you didn’t know.
Fix the record before the reports. Reporting built on inconsistent data does not reveal the inconsistency. It hides it behind a chart.
The approach that works is less dramatic than any of these, and far less risky.
Modernization Starts With Definitions, Not Replacement
Leave your systems where they are, at least at first, and build one shared record underneath them. Net Solutions runs this in 5 steps. Each step solves a business problem before it solves a technical one.
- Define: agree what a case, a customer, a contract, and a space mean across every site.
- Prioritize: fix the record that most often delays a family.
- Connect: link the systems you already run, so staff see one answer.
- Modernize: digitize only the records that block work today.
- Migrate: retire legacy systems site by site, when a business reason appears.
The shape of it
One shared record first, with no forced group-wide cutover
What people need answered
Shared record, one definition each
Systems you already run, unchanged
Nothing in the green layer is retired on day one, though some will need retiring sooner than others on security or support grounds. Sites migrate individually, when there is a reason.
Steps to Connect and Unify Your Multi-Location Funeral Business
Each step below opens with what the business gets, then explains how it works.
Step 1. Define: Agree What a Case Is
What the business gets: one meaning for every core record, across every site.
This sounds like a technical decision. It is a management decision about whose conventions win. Groups avoid it because it means telling a well-run location that its way is no longer the way.
This step also punishes assumptions. Documented workflows often lag years behind the real work. Before you define anything, watch how teams actually handle cases across roles, locations, and exceptions. Otherwise, you standardize a process that exists only on paper.
Step 2. Prioritize: Fix the Record That Most Often Delays a Family
What the business gets: an answer in the room, instead of “I will call you tomorrow.”
For groups with cemeteries, burial space is usually the strongest first move: every space, at every location, in one availability view the group trusts. For groups without cemeteries, the first target may be pre-need contracts, chapel scheduling, current pricing, document status, or transfer logistics.
The rule holds either way. Start with whatever most often stops someone answering a family, not with whatever is easiest to integrate.
In practice: for the 150-facility group, Net Solutions built burial space management directly on the enterprise finance platform. Plots, crypts, niches, and lawn crypts became live inventory, searchable by cemetery, section, type, and adjacency. The availability an arranger reads to a family and the position finance closes against became the same record.
Step 3. Connect: Link the Systems You Already Run
What the business gets: one consistent answer, through the tools staff already use.
A connecting layer reads from your existing systems and writes back where it should. Directors see one answer, and you can migrate sites later, one at a time, when it makes sense.
In practice: the same program connected 7 external services, including:
- Identity-verified electronic signature
- Insurance-backed installment payments
- Card processing
- Address verification
- Scheduling across facilities
- Media delivery
Each service sits behind its own isolated connector. Replacing a provider changes one connector, not the arrangement application. That is the difference between a supplier change and a redevelopment project.
The same discipline handles rules that vary by place. Signature requirements differed by province, so the system checked location when it assembled a contract. When electronic signature wasn’t permitted, it prompted for a physical signature instead. Before that, long-serving staff held the rules in their heads.
The team also built the interfaces to work offline, because cemetery grounds and rural family homes often have no signal.
Step 4. Modernize: Digitize the Records That Block Work Today
What the business gets: visible progress, without a records program that never finishes.
Paper cemetery maps, deed files, and pre-need contracts in cabinets are real constraints and real risks. But digitizing everything before anything improves is how these programs die. Start with the records that block a sale or an answer today.
In practice: our memorial platform shows this principle at small scale. Instead of an organization-wide records program, we replaced one application. Behind it sit templates, component inventory, supplier and product data, and a structured workflow from draft to approval to production. Revisions now happen in the conversation, not across days of printouts and callbacks. The platform is live today because we scoped it small enough to finish.
Step 5. Migrate: Retire Legacy Systems When a Business Reason Appears
What the business gets: fewer single points of failure, removed one at a time.
Migrate a site only when a trigger appears, such as a failing system, ending vendor support, or a retiring expert. Leave the sites that work alone.
How the Shared Record Works Underneath
For technology leaders, here is the architecture behind the 5 steps:
- A canonical data model. One agreed definition each for cases, people, contracts, spaces, and events.
- One authoritative system per record. For each part of the model, you decide which existing system holds the trusted version.
- An integration layer. It matches identifiers across systems, synchronizes approved changes, and presents one current view.
- Visible conflicts. When 2 systems disagree, the layer flags the conflict for a person to resolve. It does not let the last write silently win.
The method only helps if the program survives long enough to deliver it. That is why the phasing matters as much as the steps.
Every Phase Should Stand on Its Own
Apply one test to every phase: if the program stopped here, what would you still have? If a phase pays off only when the whole program lands, the sequence is wrong. Programs that demand 3 years of faith rarely survive a change of priorities.
The stop-here test
What you still have if the program halts after any phase
Phase 1Define
You still haveA written standard for what a case, a space, and a contract mean, and a measured view of how far apart your sites are.
Phase 2Prioritize and connect the first record
You still haveArrangers answer the availability question in the room, across every location, without a phone call.
Phase 3Connect finance
You still haveA shorter month-end, and numbers you can compare between sites without a caveat.
Phase 4Modernize and migrate by need
You still haveEach retired legacy system removes one single point of failure, and each removal stands alone.
Reporting comes last, deliberately. Once the definitions and records hold, it becomes much simpler. Before that, it is misinformation with a budget.
What the 150-Facility Program Taught Us About Phasing
For that group, Net Solutions designed and built a single cloud ecosystem covering the 3 separate applications it ran for arrangement, cemetery inventory, and fulfillment. The group had no central presentation system. Each pre-need representative built and maintained their own, and we sent any changes to each representative one at a time.
We delivered the architecture, integration design, and module builds. The client then paused the wider program before production rollout.
That outcome reinforced why phased modernization matters: transformation timelines change, regardless of work quality. Every stage has to deliver value on its own, because nobody can promise the next stage will start on schedule.
How to Keep a Phased Program on Track
- Map what you actually have, not what the org chart says. Include who at each site is the only person who understands a given system.
- Write the definitions down, and have someone senior enough to overrule a location sign them off.
- Let the pain choose the order, not the architecture diagram.
- Build reporting last, once the definitions hold.
Before you commission any of this, a few questions will tell you whether a program is built to finish.
Five Questions to Ask Any Modernization Partner
- Which site’s conventions win when 2 disagree, and who has the authority to decide?
- What happens at each location if the integration is unavailable for a day?
- Which records genuinely block a sale today, and which are merely untidy?
- Can an arranger answer the availability question in the room after phase 1, or only after phase 4?
- If we stopped after the first phase, what would we still have?
That last question matters most. A partner who cannot answer it has designed a program that works only if nothing changes for 3 years. In this industry, and in your boardroom, something always changes.
FAQs
No, not as a first step. A shared record sits underneath the systems you already run and connects them. You can retire individual systems later, site by site, for business reasons such as a failing platform, ending vendor support, or a retiring expert.
Avoid a group-wide cutover. Connect existing systems first so staff can keep working in familiar tools while the shared record builds beneath them. Plan for each location to keep operating if the integration is unavailable, and move sites one at a time.
Do not clean everything first. Define what each core record means, then fix the records that block a sale or an answer today. When the connecting layer finds 2 versions of the same record, it flags the conflict for a person to resolve, rather than letting one silently overwrite the other.
Connect the new site’s system to the shared record, and map its records to your agreed definitions. The location keeps running on day one, and you decide later whether migrating it is worth the cost and risk.
A phased model can run as long as each phase keeps delivering value on its own. Families notice when the record that most often delays them, often burial space availability, is connected across locations. How soon that happens depends on how scattered that record is today.
No. It is a records and integration project. Any AI tool you add later depends on reliable data. If your system describes paperwork rather than the business, any AI tool you add later inherits that problem. Fixing the record first makes any later automation far more trustworthy.
Find the Systems and Records Creating the Most Friction Across Your Locations
In a working session, Net Solutions maps how your sites record cases, spaces, and contracts today, identifies the record that most often delays a family, and outlines a first phase that stands on its own.
