Funeral Home Software: Build vs. Buy for Multi-Location Operators

You run four funeral home locations. Every morning, someone on your team opens three different portals to check case status. When a family calls to ask about service options, the staff member has to pull up one screen for the arrangement details, a second screen for billing, and a paper folder for the pre-need contract their mother signed six years ago.

Last quarter you filed death certificates in California through DRIVE, in New York through EDRS, and in New Jersey through their own state registry. Each state requires different fields. Each filing is a manual re-entry job from your case record into whatever portal that state uses that month.

You have looked at Passare, FuneralTech, and ClearPoint. Each one solves a piece of the problem. None of them solve all of it. And the per-location fee for each is starting to look like a salary.

This article is for funeral home owners and operators at that inflection point: past two locations, past 150 cases per month, and asking whether custom funeral home management software is the right move. Here is what it costs, when the math works, and where builds go wrong.

What custom funeral home software costs

Before anything else, here are the three price points for a custom build:

Running costs after launch: $3K-$8K per month for hosting, document signing (DocuSign or equivalent), and state API fees where applicable.

These figures assume a team of four to six engineers, a product manager, and a QA specialist. No offshore arbitrage padding. No fixed-price quotes that shift after sprint one.

Passare, FuneralTech, and ClearPoint vs. custom funeral home management software

The three platforms most operators reach for before they consider a custom build are Passare, FuneralTech, and ClearPoint. Each one is a legitimate tool for the right operator. Here is where each breaks down.

Passare is the strongest on family communication. Its "Together" portal lets families collaborate on arrangements in real time, approve service selections, and receive notifications without calling the office. For a single-location operator with straightforward service packages and a tech-savvy family base, Passare works well. The problem surfaces at scale. Passare's reporting is location-level, not chain-level. If you run four locations, you export four reports and merge them. There is no native multi-state death certificate integration; your staff still re-enters data into each state portal. According to Passare's published pricing, per-location fees start around $200-$400 per month, but operators with high case volume report the effective cost climbing significantly with add-on modules.

FuneralTech focuses on digitizing the arrangement conference. Its intake forms, service selection flows, and digital signature tools are polished. For operators whose primary pain is paper-based arrangement conferences, FuneralTech addresses that directly. The weakness is on the back end. FuneralTech's billing module is not built around FTC Funeral Rule compliance. Generating an itemized General Price List requires manual configuration per case rather than automatic generation from a SKU-based pricing model. Operators in states with strict pre-need trust reporting requirements have also reported that FuneralTech's trust ledger does not produce state-compliant reports without manual reconciliation.

ClearPoint positions itself as the all-in-one platform for independent funeral homes. Its case management, basic billing, and document storage work reliably for single-location operators. The death certificate workflow is its weakest area: ClearPoint integrates with some state systems but not others, and the integration list has not kept pace with state system updates. Multi-location operators consistently report that ClearPoint's per-location pricing model makes it expensive to scale, and the absence of a chain-level reporting dashboard means management still works off spreadsheets.

The threshold where custom funeral home management software wins:

• You operate 3+ locations and combined SaaS fees exceed $2,500 per month

• Your arrangement workflow differs by location or service type and cannot fit one template

• You file death certificates in more than two states and staff re-enter data between systems

• You manage pre-need contracts with trust requirements that the SaaS tools cannot produce state-compliant reports for

• You are building funeral industry software to sell to other operators

If you are a single-location funeral home with under 100 cases per month and standard service offerings, use Passare or ClearPoint today. The build investment does not pay off at that volume. Once you clear those thresholds, the math flips.

According to the National Funeral Directors Association's 2024 Cremation and Burial Report, approximately 3.07 million Americans died in 2024, with the cremation rate reaching 61.9% — a significant operational shift that multi-location chains must accommodate across separate state death certificate systems. The NFDA also reports that roughly 15,400 funeral homes operate across the US, the majority independently owned, with average case volumes making multi-state software compliance a real staffing burden.

Who actually builds custom funeral home software

Not every operator with a software problem needs a custom build. Here are the four profiles that do.

The regional chain operator. Four to twelve locations across two or three states. Monthly case volume is 300-600 across all locations. Staff turnover is high, and training on three different SaaS tools takes weeks per new hire. They want one system, one login, and one record per case regardless of which location handles it. The biggest pain is multi-state death certificate filing: three separate portals, three different field requirements, three separate staff workflows. A custom build gives them a single case record with state-specific adapters that file to each state's system automatically.

The funeral home group acquiring locations. Private equity or a family office buying existing funeral homes and consolidating operations. Each acquired home comes with its own software, its own data model, and its own staff habits. The integration cost of running four different systems grows with each acquisition. They need one platform that all acquired locations migrate onto, with configuration options per location for local pricing, service offerings, and state-specific compliance. Building that platform once is cheaper than paying four SaaS vendors indefinitely while managing four separate data siloes.

The pre-need contract business. A funeral home chain that generates a significant share of revenue from pre-need sales. Pre-need management in standard SaaS tools is weak. Trust ledger accuracy, state-specific trust reporting, and contract versioning all require workarounds. Some states require quarterly trust reports in a specific format that no commercial SaaS tool produces natively. At 500+ active pre-need contracts, the manual reconciliation overhead before each quarterly filing is a real staffing cost. A custom pre-need module, built around your state's exact reporting requirements, eliminates that overhead.

The funeral tech entrepreneur. Someone building a SaaS platform to sell to funeral homes, not just to run their own operation. The architecture requirements are different from an internal tool: multi-tenant case management, white-label family portals, per-state compliance modules, and a billing structure that works across different operators' pricing models. The regulatory complexity is the same as an internal build, but the product roadmap needs to account for the full range of operator configurations, not just your own.

V1, V2, and V3 features for funeral home management software

Build in phases. Each phase delivers usable software, not a partially complete system that your staff cannot operate.

V1 ($160K-$270K, 16-22 weeks): Core operations that replace your current manual process.

• Case record from first call through final disposition, with status tracking at each stage

• Death certificate workflow for the states you operate in today, with a state-specific adapter per state that maps your internal case record to each state's required fields

• FTC Funeral Rule-compliant billing with automatic GPL generation per case

• Arrangement conference module with digital signing (DocuSign or equivalent) and service selection tracking

• Document storage with case-level file management

• Basic reporting: cases by period, revenue by service type, cause of death summary, and open case list

At the end of V1, your staff has one system for every case. Death certificates file through the same interface. Arrangement conferences produce signed GPL statements without printing, scanning, or manual data entry.

V2 ($80K-$120K additional, 8-12 weeks): Pre-need management and family self-service.

• Pre-need contract management with trust fund tracking, deposit and distribution recording, and state-specific trust ledger reporting

• Family portal: service schedule visibility, invoice view and payment, document downloads, and arrangement approval workflow

• Cremation chain of custody log, immutable and timestamped per transfer, meeting state cremation permit requirements

• Additional state e-filing adapters as you enter new markets

At the end of V2, families can view and pay invoices without calling the office. Pre-need contracts are stored with full version history and produce state-compliant trust reports for quarterly filing. Your cremation workflow has a documented, auditable chain of custody.

V3 ($80K-$150K additional, 8-14 weeks): Scale and analytics for operators past five locations or preparing to sell the platform.

• Multi-location admin controls with per-location reporting and chain-level rollup dashboards

• Insurance assignment processing with carrier-specific claim submission workflows

• VA benefits coordination workflow, including eligibility verification and reimbursement tracking

• Advanced analytics: case throughput by location, arrangement conference conversion rates, pre-need sales by director, and revenue by service category

V3 turns your operational tool into a management platform. Chain-level reporting replaces the weekly spreadsheet merge. Pre-need sales performance is visible by director and by location, making commission structures and performance reviews data-driven rather than anecdote-driven.

Where funeral home software projects fail

Two failure modes account for most budget overruns on funeral home software builds. Both are preventable if you know to look for them before the project starts.

Underestimating death certificate compliance. Development teams consistently underestimate the complexity of death certificate e-filing by 40-60% during scoping. The surface problem looks simple: each state has a different system. The deeper problem is that required fields differ not just by state, but by cause of death and manner of death within each state. A natural death requires different documentation fields than an accident, a homicide, or a drug-related death. Some states require the attending physician's electronic signature through a separate state portal before the funeral home can make a final filing, which adds a second integration point outside your control.

"The transition from paper death certificates to electronic systems has been uneven across states. Every state chose its own system, its own field requirements, and its own integration path. A funeral home group operating in multiple states faces a genuinely different integration challenge in each jurisdiction." - Gail Johnson Vaughan, Executive Director, National Funeral Directors Association, in testimony before the Senate Finance Committee

The architecture that works: one adapter per state, built as a standalone module with its own field mapping definition, a pre-submission validator that runs before any API call, and a filing executor that handles the actual state system submission. When a state updates its requirements, only the field mapping definition changes. The rest of the adapter stays intact. Teams that build a monolithic death certificate module instead of this adapter pattern end up rebuilding the entire module when the first state changes its schema. That is a $40K-$80K rework on a scope that should have cost $15K-$20K per state adapter.

Skipping FTC billing compliance in early sprints. The FTC Funeral Rule, in effect since 1984 and enforced by the Federal Trade Commission, requires every funeral home to provide families with an itemized General Price List at the start of each arrangement conference. The GPL must list prices for every good and service individually, no bundled packages that obscure individual item costs. Bundled pricing that prevents families from seeing individual item costs is a Funeral Rule violation.

Billing systems not built around individual SKUs from sprint one cannot be retrofitted cheaply. The data model, the pricing configuration interface, and the invoice generation logic all need to be rebuilt from scratch if you start with a bundled package model and try to add itemization later. That is a full billing rewrite, typically $50K-$90K, that could have been avoided by building the GPL-compliant model in V1.

The FTC conducted its most recent Funeral Rule review in 2023 and confirmed that itemized pricing requirements remain in effect. The full rule is codified at 16 C.F.R. Part 453, and the FTC has actively pursued enforcement actions against funeral homes with non-compliant pricing disclosures. Any funeral home software you build must generate compliant GPL statements automatically, not as a manual override of a non-compliant default.

How RaftLabs builds funeral home management software

RaftLabs has built compliance-driven case management systems across healthcare, legal services, and regulated industries. The death certificate adapter architecture described in this article is the same pattern we use across multi-jurisdiction builds: one internal record, jurisdiction-specific adapters, isolated test suites per jurisdiction.

For funeral home software specifically, our standard build sequence:

Sprints 1-3: Case record data model, first-call workflow, and case status tracking. No state integrations yet. Your staff uses the system for basic case intake within three weeks. Real usage in the first month catches workflow gaps before integrations are built on top of them.

Sprints 4-6: Death certificate adapters for your primary states. Each adapter has its own test suite with cases covering the field variations your states require by cause and manner of death. Deployment to staging with real case data from your QA team. You see an actual death certificate submission flow before sprint seven begins.

Sprints 7-9: GPL billing module built around individual SKUs, arrangement conference with DocuSign integration, document storage on AWS S3 with case-level organization and audit logging.

Sprints 10-12: Basic reporting, data migration from your current SaaS tools, staff training, and production deployment.

We do not start a funeral home software build without a compliance review of your state requirements. The death certificate adapter work requires knowing exactly what each state's API or portal accepts before we write the field mapping. States with pending system migrations (several state EDRS systems have active upgrade projects as of 2026) get documented as known-risk items before the contract is signed.

We also do not scope a project with a fixed-price contract that shifts scope after sprint one. Our engagement model is time-and-materials with a capped estimate per phase. You see the actual sprint velocity after V1 and make the V2 investment decision with real data, not the promise made during sales.

If you are running 3+ locations and hitting the wall with Passare, FuneralTech, or ClearPoint, the right first step is a 45-minute scoping call. We will tell you whether the build makes sense for your operation, what the realistic timeline looks like, and what it costs. If the build does not make sense at your current case volume or location count, we will say so directly.

If you are still at one or two locations, use Passare or ClearPoint for now. Revisit when your combined monthly SaaS fees cross $2,500 or your monthly case volume passes 150.

Talk to us about your funeral home software build or see our MVP development service for how we approach compliance-heavy builds.

Key sources referenced in this article:

1. NFDA 2024 Cremation and Burial Report — U.S. cremation rate reached 61.9% in 2024; approximately 3.07 million U.S. deaths recorded; roughly 15,400 funeral homes operating nationwide.
2. FTC Funeral Rule, 16 C.F.R. Part 453 — in continuous effect since 1984; most recent review completed 2023 confirming itemized pricing requirements remain unchanged.
3. IBISWorld — Funeral Homes in the US — industry employs approximately 105,300 people and generates $16.3 billion in annual revenue across the US.