Funeral Home Management Software: Layer on Passare, or Replace It?
The deciding question is not whether to build, it is whether your case system moves. Keeping SRS Computing, Passare or FDMS Plus as the record and layering automation on top holds a first release at $50,000 to $120,000 in 10 to 16 weeks.
On this page
The deciding question is not whether to build, it is whether your case system moves. Keeping SRS Computing, Passare or FDMS Plus as the record and layering automation on top holds a first release at $50,000 to $120,000 in 10 to 16 weeks. Replacing it moves you into the $150,000 to $350,000 platform band and adds months of migration before anyone sees a benefit, and that only makes sense when a group is consolidating two or three incompatible legacy installs anyway. If you are a single location home at modest volume whose directors are not losing mornings to re keying, buy the module your vendor already sells and revisit in two years.
When is off the shelf genuinely the right call here?
If you are a single location home at modest volume, and your arrangement, obituary and accounting flow through Passare, SRS Computing or Frazer without your directors complaining, do not build. Buy the module your vendor already sells, spend the difference on staff, and revisit in two years. A custom build at that scale is an overhead you will resent by the second winter.
The same holds when your pain is one specific thing. If the real problem is that after hours calls reach voicemail, price a better answering arrangement first. If the real problem is your website and obituary presentation, that is a far smaller purchase than a platform. Naming the single failure honestly is the cheapest step in this whole decision.
These products are good at what they sell. Passare, SRS Computing and FDMS Plus hold the case, the arrangement record and the accounting properly, and they encode years of trade detail in how a preneed contract, a price list revision or an at need file is represented. Rebuilding that is not where a funeral home's capital belongs, and we would say so on the first call.
What they were built to do is store a case. What they were never built to do is move it: answer a phone at two in the morning, chase a physician who has not signed, or watch an arrangement that stalled. That gap is the whole build conversation and it is a layer, not a replacement.
When does a custom build actually pay off?
Build when two or more of these are true. You run multiple locations, or you are a group holding two or three legacy systems that do not reconcile. Your volume has directors typing the same case into four places. Your history is trapped in an install nobody can export cleanly. Or you want something the case tool will never offer.
That last category is specific rather than aspirational. A genuine after hours first call agent that opens the case and pages the on call director with the address and access notes. A single arrangement conference intake that populates the death certificate worksheet, the burial or cremation permit and the state Electronic Death Registration System (EDRS) submission from one entry. A preneed and aftercare engine working against years of archived cases. An arrangement portal built to your own Federal Trade Commission (FTC) Funeral Rule review.
The re keying signal is the one to measure rather than argue about. Across the homes we have built for, a director loses two to three hours a day to typing the same name and dates into a certificate, an EDRS submission, a permit, an obituary and an insurance assignment. One transposed number and the state bounces it back a day later. That is the daily bleed, and it is a labour cost your renewal invoice never shows.
The first call is the second signal, and it is revenue rather than time. A family whose person just died calls once. If the phone rings out at nine at night, or an answering service reads a flat script and takes a name, that family often calls the next home in the search results before anyone wakes up. Count your after hours voicemails for a month before you decide anything, because that count is the whole argument in either direction.
How do they compare on the things that matter in this industry?
Paperwork chain. Legacy funeral tools have form fill, and it stops at the edge of the product. No vendor wires your specific state EDRS, your carrier formats and your local obituary outlets together, because that stack is different in every home. That connective work is what a build is for, and it is where the morning hours actually go.
After hours intake. An answering service is a call centre disconnected from your records, and a case tool waits for a human to type at nine in the morning. Neither can start the case and dispatch the removal van, which is the only outcome that matters at two in the morning.
Scheduling as constraints. Most case tools treat scheduling as a calendar you fill in. With two chapels, shared vehicles, staff certifications and cemetery and crematory windows, it needs to be a set of constraints that refuses to double book and refuses to schedule a committal before the permit has cleared.
Watching versus storing. A stalled preneed inquiry, an unsigned contract, an aftercare date. These are open records in every case system, faithfully stored and never worked. Watching them, ranking them and drafting the next message is the automation layer.
Where the products win. Case records, arrangement history, accounting, price list handling and a support desk that understands the trade. Keep all of it.
What does total cost of ownership look like at your scale?
An automation layer on top of your existing case system runs $50,000 to $120,000 and ships in 10 to 16 weeks. A worked three location home in one state, running SRS Computing with two insurance assignment processors and roughly four hundred calls a year, lands at $98,000. Take the scheduling engine out and it is $84,000. Add a second state and it is near $118,000, at the ceiling of the band. A full operations platform is $150,000 to $350,000 phased over 6 to 12 months.
Below $50,000 you are buying one workflow rather than a system. Obituary drafting and distribution alone is a legitimate purchase at that level and it will not noticeably change the morning load, because the load is the certificate, the permit and the state filing.
Running costs are a support retainer of 12 to 18 per cent of build annually, roughly $12,000 to $18,000 on a $98,000 build, plus consumption that scales with call volume rather than seats: telephony minutes and speech processing for the first call agent, and model inference for obituary drafting. Then allow a few days a year per integration for regulatory drift, because state vital records offices and insurance assignment processors change requirements without asking you.
Compare that against your own twelve months of software spend across every location, including case management seats, obituary and website services, the answering service and any per case fees. On licence alone the packaged route usually wins. It flips when you price the director hours, and the hours are the number the build is attacking.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the default here, not the compromise. Case management, arrangement records and accounting stay in Passare, SRS Computing or FDMS Plus. The build handles the first call, the paperwork populating, dispatch, follow up and aftercare around them. That single decision is the difference between the two bands.
Sequence by pain rather than by module. Certificate and state filing automation first, because that is the daily bleed. The first call agent alongside it or immediately after, because it is revenue rather than time saved. Scheduling second, because a double booked chapel is visible to families. Preneed and aftercare mining third, because it earns money and needs the earlier data to be clean.
Leave the family facing arrangement portal out of phase one entirely. It is the most visible feature and one of the least urgent, and it carries the heaviest Funeral Rule review. Directors do not lose their mornings to the portal.
Two sequencing rules keep the number down. Start with one state even if you operate in two, and add the second EDRS integration once the first is live and proven, because the second and third are not materially cheaper than the first. And wire the two insurance assignment processors carrying most of your volume, leaving the rest manual, rather than integrating C&J Financial, Homesteaders and Global Atlantic Forethought all at once.
One preparation task belongs to you rather than the developer. Have your General Price List in a structured file before kickoff rather than as a printed sheet, because otherwise the first fortnight of the project is somebody typing it in at a developer's day rate. Accept a director in the loop on anything a family will read, since drafting with human approval costs a fraction of straight through publishing and is the right answer for an obituary regardless of price.
Which should you choose, by operator size and stage?
Single location, modest volume, directors not complaining: buy. Configure what you have, turn on the modules you already pay for, and put the money into staff.
Single location with a genuine after hours problem: price an answering arrangement and your vendor's booking tools first. If those fail on the evidence rather than on impression, a first call agent is a defensible standalone purchase at the bottom of the band.
Two or three locations in one state: layer automation on top of the case system you have. Certificate and state filing automation plus the first call agent is the release that changes the mornings, and it sits comfortably inside $50,000 to $120,000.
Multi state groups: layer, and phase the states. Ship the state carrying most of your volume, run it for a full quarter, then fund the next as its own phase rather than paying for three before any of them is proven.
Groups consolidating two or three incompatible legacy installs: this is the one case where full replacement earns its cost, because you were going to do the migration anyway. Budget the platform band, insist on a migration test against a copy of your real data before signing, and expect the older on premise installs to take several extra weeks of mapping.
If you would rather scope this before committing budget, Digital Heroes contracts through India LLP, US LLC and UK LTD entities, so the agreement and the intellectual property assignment sit under law your own advisers already read. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- The federal government spends about 80% of its IT budget on operations and maintenance of existing systems rather than on development or modernization, with many critical systems being decades old. Source: U.S. Government Accountability Office (GAO) (2025) →
- Companies in the top quartile of McKinsey's Developer Velocity Index had 2014-18 revenue growth four to five times faster than bottom-quartile peers, showing that software-building capability is a driver of business performance, not just a support function. Source: McKinsey & Company (2020) →
- In the Flexera 2025 State of ITAM report, respondents reported roughly 33% of SaaS spend is wasted, underscoring how paying for off-the-shelf seats and tiers that go unused erodes the supposed cost advantage of generic SaaS. Source: Flexera (2025) →
- In an RCT, the no-show rate was 23.5% for patients receiving a text-message reminder versus 38.1% for the control group - a 14.6 percentage-point reduction (p = 0.04). Source: Clinical Pediatrics / PubMed Central (Lin et al.) (2016) →
Frequently asked questions
What does it cost to leave Passare or SRS Computing later if we layer on top?
Less than a cold migration, because the layer has been reading and writing your case data throughout and holds its own record of first calls, filings, follow ups and aftercare. Those are the parts that would otherwise have to be reconstructed.
You would still be replacing case management, arrangement records and accounting, which is the part the incumbent does well. Budget $5,000 to $15,000 for the extraction depending on the source system, and insist on a migration test against a copy of your real data before committing to any date.
What happens if our case management vendor raises its pricing?
Pull twelve months of your own invoices across every location first, including case seats, obituary and website services, the answering service and any per case fees, then project the increase over five years rather than one.
A layer does not remove the subscription, since you keep the case system. What it does is cap what that subscription has to cover, because the first call, the paperwork populating and the follow up now live in software you own. That turns a repricing into a commercial decision rather than a renewal you cannot refuse.
How long before something is actually live?
Ten to sixteen weeks for a first release, and a full platform phases over 6 to 12 months. More usefully, individual pieces go live well before the end. The after hours first call agent and the certificate and permit populating are each independently deployable.
A director should be waking up to a fully briefed page while obituary drafting is still in development. If a proposal has one launch date and nothing usable before it, push back on the phasing rather than on the price.
Is this cheaper than what we already pay Passare or SRS Computing?
Not on the licence line alone, and anyone telling you otherwise has not run your numbers. Take your own twelve month invoices, project them over five years, and compare against build cost plus a retainer at 12 to 18 per cent.
For most single location homes the packaged route wins that arithmetic and you should stay put. It flips when you price the director hours lost to re keying the same case into four places, which is the cost your renewal invoice never shows and the only cost the build is designed to remove.
Why does operating in more than one state cost so much more?
Because each state runs its own Electronic Death Registration System with its own submission rules, field requirements and validation behaviour. A group across three states carries three integrations, and the second and third are not materially cheaper than the first, so budget roughly $20,000 each.
Control it by sequencing. Ship the state carrying most of your volume, run it for a full quarter, then add the next as a funded phase rather than paying for all three before any of them has proven itself against real filings.
Can we keep our case system and just add automation on top?
Yes, and for most homes that is the right structure. Case management, arrangement records and accounting stay where they are, while the build handles the first call, paperwork populating, dispatch, follow up and aftercare around them.
Full replacement earns its cost only when a multi location group has to consolidate several incompatible legacy systems anyway. That single decision is the difference between the $50,000 to $120,000 band and the $150,000 to $350,000 one, so make it deliberately rather than letting scope drift into it.
Does Funeral Rule compliance add much to the build?
It adds cost anywhere the software quotes a price to a family, which means arrangement screens, any portal, and anything the after hours agent says about cremation pricing. Expect design and review time rather than heavy engineering, and expect your own counsel to want a look.
The cheap way to handle it in a first release is to keep the agent to intake and routing, answering price questions only from your General Price List rather than generating them. Save the family facing arrangement portal for a later phase when the review is worth paying for.
What is the cheapest useful version we could build?
Single intake populating the certificate worksheet, the permit and one state's Electronic Death Registration System submission, with validation before filing. That is the daily bleed and it sits at the lower end of the band.
Add the first call agent as the second piece if you can name the number of after hours calls you lose, because that one is revenue rather than time. Leave scheduling, the portal and preneed mining out entirely until the paperwork automation has run for a season and your data is clean enough for mining to say anything true.
What is a discovery phase, and is it worth paying for separately?
Pay for it, and treat the output as yours. A discovery phase runs two to three weeks, typically 5 to 10% of the eventual build budget, and produces a written scope, wireframes, and a fixed quote you can take to any vendor, including a competitor of the agency that wrote it. Skipping it is how projects end up quoted from a two-paragraph email and delivered at twice the price.
Can custom software connect to the tools we already use, like QuickBooks, Stripe, and Google Workspace?
Yes, and connecting your existing tools is one of the main reasons to build custom: mainstream platforms like QuickBooks, Stripe, Shopify, and Google Workspace all publish documented APIs. Budget 1 to 3 weeks of work per integration depending on API quality and how much data flows in both directions. Ask any vendor whether they have integrated with your specific tools before, because quirks like QuickBooks' OAuth token handling and API rate limits get learned on someone's project, and it should not be yours.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
What should I have ready before I contact a development agency?
Three things, none of them technical: a one-page description of the problem in your own words, a list of the tools and spreadsheets the new system must replace or connect to, and a must-have versus nice-to-have split of features. Add a budget range, even a wide one, because it changes the conversation from fantasy to engineering. You do not need a formal specification; producing that is what a discovery phase is for.
Will custom software work with the tools we already use, like QuickBooks and Stripe?
Yes, and this is one of custom software's genuine advantages: QuickBooks, Stripe, Shopify, and most mainstream business tools publish documented APIs built for exactly this. Expect each standard integration to add one to two weeks of build time, and be suspicious of any quote that lists five integrations without asking what data flows in which direction. The hard cases are legacy systems with no API, which is a question to raise in discovery, not in week nine.
Should we build an MVP first or go straight to the full system?
MVP first, for almost everyone: ship the single workflow that carries the business value in 10 to 16 weeks, learn from real users, then fund phase two from evidence instead of guesses. The caveat is that an MVP is a small version of a well-built system, not a badly built version of a big one; the data model must already support what comes next. An agency that cannot tell you what they deliberately left out of your MVP has not designed one.
We run everything on spreadsheets and Airtable. How do we know it's time for custom software?
The reliable signals are re-typing the same data into multiple tools, one employee acting as human middleware between systems, and errors appearing in handoffs between teams. Hard limits force the issue too: Airtable's Team plan caps at 50,000 records per base, and Business costs $45 per seat per month, so a 20-person team pays about $10,800 a year for a tool it has already outgrown. When workarounds consume more hours than the tools save, the spreadsheet era is over.
Does the tech stack matter, and which one should I ask for?
It matters less than agencies imply, provided it is boring. A mainstream stack, something like React or Next.js on the front end, Node.js or Python behind it, and PostgreSQL for data, means thousands of developers can maintain your system if you ever change vendors. Apply one test: ask how hard it would be to hire a replacement developer for the proposed stack, and walk away from anything built on an agency's in-house framework.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Who can build a custom software system?
Digital Heroes builds custom software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Varalika.
Web Developer · Lucknow · 1 post on the site
Published · Last updated .
