# Funeral software requirements and proposal request

Prepared by the buying funeral home. Replace the bracketed fields; use fictional examples and blank forms only. Do not send family or decedent records in a proposal request.

## Our operation
- Service mix: [funeral / cremation / cemetery / trade / preneed; describe the work that matters]
- Locations, annual calls, staff and roles: [counts and required access]
- Current tools, accounting edition and required integrations: [systems]
- Target decision date and responsible buyer: [date and business contact]

## Demonstrate one fictional case
For each requirement mark Live / Configurable / Separate product / Development / Unsupported. Name the plan, limit, fee, implementation owner and evidence. A roadmap item is not a shipped capability.

1. Intake: review a first call, create the case, verify carried-forward details.
2. Persistence: edit, save, leave, reopen, and verify the saved values; demonstrate recovery from failure.
3. Arrangements: use our sample price list, itemize services, and inspect changes.
4. Documents: populate our blank sample form, verify fields, and retain a completed version.
5. Signatures: send to test recipients, complete signing, retrieve the final copy, and explain delivery failures and resends.
6. Payments: demonstrate a controlled test payment, remaining balance, adjustment and refund lifecycle; distinguish recorded payment from settled payout.
7. Accounting: show the exact edition, transaction types, direction, mapping, failed-sync recovery and reconciled result.
8. Operations: update tasks/board stages and verify another permitted staff member sees the right status.
9. Access: show roles, location boundaries, audit history, offboarding and support access.
10. Migration and exit: open a sample export including documents and relationships; identify source cleanup, validation and responsibilities.
11. Specialized work: [add our necessary cemetery, crematory, pet, preneed or reporting scenario].

## Written commercial response
Quote subscription units, included users/cases/signatures, required modules, volume overages, setup, migration, training, processing, optional services, renewal, cancellation, export charges and support response commitments. Mark unknown items explicitly. Attach current scope and terms; do not omit a required add-on from the comparable price.

## Acceptance and references
For each must-have list a pass condition, reviewer, unresolved issue, owner and retest date. Provide a relevant customer reference only with that customer's permission. Separate observed use, a customer opinion and a measured outcome. Ask permission before recording a demonstration.

## Decision
[Must-haves passed / exceptions accepted in writing / cost confirmed / migration validated / go-live owner / decision date]. The lowest total is not an automatic winner; an unfulfilled must-have can disqualify a product.

Published by FuneralHQ as a blank evaluation tool. Apply the same requirements to FuneralHQ and every other finalist. No email is required to use this template.