FuneralHQ competes in this market. This guide separates review observations, the vendor's current descriptions and our recommended evaluation steps. We have not performed an independent Osiris deployment test or verified every reviewer's account.
What do the review sites show?
At our November 2, 2026 research check, Capterra's Osiris review page displayed 4.7 out of 5 from 65 reviews, with a page update dated October 19, 2026. Positive accounts included support and document workflows. Eric G.'s November 23, 2024 review raised concerns about particular reports and mobile usability; his customer-service rating was nevertheless 5 out of 5. These observations do not support describing the overall review record as broadly poor.
The G2 page offered a much smaller review set. Sara P.'s January 5, 2023 account described dissatisfaction with service and the effort of arranging separate hosting, phone and email services. That older account is a reason to clarify service scope, not proof of the current experience for every Osiris customer.
Do not average scores from different sites as if they were one controlled study. Review populations, dates and collection methods differ. Read source and incentive disclosures. Capterra, GetApp and Software Advice can display shared reviews, so three listings need not represent three independent samples.
What does Osiris currently say it offers?
The Osiris website describes cloud-based software for funeral homes, cemeteries and crematories, including document storage, electronic signatures, payments and QuickBooks integration. It also describes monthly plans without long-term obligations. These are vendor descriptions to verify against the quote and agreement for your firm.
A fair comparison should not call Osiris desktop-only or claim it lacks those features. Presence on a feature list does not establish how a particular workflow behaves, but it does establish that categorical absence claims would be misleading.
Ask the vendor to identify the product, package, integrations and services included in your demonstration. A review of an older configuration may not describe the setup you are considering. Record the date of your own evaluation so staff can distinguish an observed result from an assumption carried over from an old article.
Turn a reporting concern into a specific test
Bring a report your office actually uses, with anonymized data and a clear definition. For example, define which location, date basis, case status and payment activity belong in the result. “Show me reporting” is too broad to reveal a mismatch.
Have the vendor produce the result and explain the inputs. Then change one relevant item, such as a payment date or case status, and inspect what changes. Ask how adjustments, voids and different locations appear. A total without a definition can look correct while answering the wrong question.
Write the acceptance criteria before the demo. Your accountant may need a different view from the arrangement team. Distinguish a standard report, a configurable report, an export for further analysis and a promised future feature. Those options can all be useful, but they have different costs and maintenance requirements.
Test mobile work on the device staff use
Choose a task employees perform away from the office: finding the next action, reviewing a document or checking a balance. Use the actual screen size and supported browser. A desktop window resized briefly by a salesperson is a weaker test than the device your director carries.
Observe how much context survives the change of device. Can the employee identify the case safely, read the relevant information and complete the supported action? If a task is not supported on mobile, record the limitation and decide whether it matters to your operating model.
Do not convert a 2024 usability complaint into a claim that the 2026 product is unusable. Use it as a prompt for a current demonstration. Apply the same standard to FuneralHQ and every other vendor on the shortlist.
Clarify support and service boundaries
Separate software support from services such as website hosting, business email, telephone service and accounting assistance. A buyer can be satisfied with the case system but surprised by an unrelated service boundary. Write down who supplies and supports each part.
Ask how a blocked case is escalated, which channels are monitored, what hours apply and what response commitments are contractual. A published contact number is useful but does not, by itself, establish an after-hours restoration promise. Ask what the covering director should do when an issue occurs outside ordinary hours.
Give the vendor a fictional example: a signing request fails before a scheduled arrangement, and the original employee is unavailable. Ask who opens the issue, what reference the team receives, how an update is communicated and what workaround is supported. Do not manufacture an emergency support ticket to test response time.
Review cemetery and crematory fit separately
A combination business should evaluate the cemetery record as carefully as the funeral case. Use a fictional plot, rights record and interment task. Check how references remain connected and how a correction is handled. Do not assume the funeral arrangement demonstration proves cemetery fit.
For crematory work, use a case with a missing prerequisite and a handoff between employees. Ask what the system records and what staff must verify outside it. Avoid treating a software status as independent proof that an operational requirement was satisfied.
FuneralHQ also offers cemetery workflows and online arrangements. Bring the same examples to both vendors. A consistent task list makes the comparison more useful than two unrelated tours of each product's strongest screens.
Use a written decision sheet
| Area | Evidence to request | Record the result |
|---|---|---|
| Reports | Your defined sample report and a changed input | Observed / workaround / unavailable |
| Mobile | A real staff task on the intended device | Steps, restrictions and support |
| Support | Written scope and escalation route | Hours, channels and commitments |
| Migration | Your source types and acceptance checks | Included work and unresolved items |
| Payments | Account access, refunds and historic records | Provider and responsible party |
| Exit | A complete sample export | Files, identifiers, fees and timing |
Use notes as well as a score. A missing mandatory requirement should not disappear inside an average of many minor conveniences. Conversely, an unfamiliar layout may be manageable with training if the underlying work is sound.
A fictional owner evaluating a switch
An owner likes the current system's document workflow but cannot get one monthly report into the format the office expects. Instead of deciding from a negative review, the owner first defines the report and asks the current vendor to demonstrate the available options.
The owner then gives the same anonymized example to another vendor. One approach may require an export; another may provide a direct view. The decision includes staff effort, ongoing reconciliation, migration work and the importance of the report, rather than a claim that one product is universally best.
If the existing vendor resolves the issue acceptably, switching may not be justified. If an important requirement remains unmet, the owner has a concrete reason to evaluate alternatives and a way to check whether a replacement actually solves it.
What should you do next?
Use FuneralHQ's existing Osiris alternatives guide for a separate shortlist discussion. This article's purpose is narrower: interpreting reviews and turning them into testable questions.
Download the blank review-to-demo worksheet. Write down the concern, its source and date, the task to demonstrate and the observed result. Bring that worksheet to a FuneralHQ demonstration as well. Credible comparisons make the evidence visible and let the buyer decide which result fits the firm.
The FuneralHQ advantage
Run the whole case in one place
Keep intake, arrangements, documents, payments and the books together. Bring one of your cases to a demo and see how your team would work through it.
We will work through a real example with you, from the first details to the finished record.
See it on one of your casesAbout the FuneralHQ Editorial Team
This guide was written by the FuneralHQ Editorial Team, the in-house team behind funeral home software used by independent firms to run cases, documents, payments, and QuickBooks sync in one record. Our editorial standards explain how we review product claims, outside sources, automation, updates, and corrections.