CRM KitsFuneral homes
From the first call to the one-year call.
A calm workspace for a funeral home office: each family's case from the first call through the arrangement conference, the services on the calendar and the service day to the aftercare calls at 30, 90 and 365 days, with the chapel and rooms for the week beside it. Lindenrow records what your office recorded, keeps no cause of death or medical details, and makes no regulatory or pricing claim.
See every family's case by stage.
Five columns in the order a case runs: first call, arrangement conference, service scheduled, service held and aftercare. Each card leads with the next date that matters, such as the visitation time and room or the next aftercare call, then the family, the person as a first name and last initial with the service type, the arranging contact, and services and confirmed vendors in their own tags. Beside the board, the chapel and rooms for the next seven days. Conferences and services whose date passed without a record, obituaries past the paper's deadline, overdue aftercare calls and pre-need meetings that passed lead in the needs attention strip.
Actual interface captures with fictional sample data. Open a screenshot to see it full size.
What’s in the kit
Screens
- Family case board operating view
- Chapel and rooms operating view
- Pre-need inquiries operating view
- Aftercare calls operating view
- Obituaries operating view
- Vendor contacts operating view
- Insights operating view
- Three closed-choice native form drafts and three editable document templates
- Editable case checklists and preserved row history
four pipelines
- Families served · 8 stages
- Aftercare calls · 7 stages
- Vendors and clergy · 7 stages
- Community relationships · 7 stages
Optional. Install the ones that match your work, or connect drafts to a pipeline you already use.
nine workflow drafts
- First call follow-up
- Arrangement conference preparation
- Service details confirmation
- Obituary family review
- After the service
- 30-day aftercare call
- 90-day aftercare call
- One-year aftercare call
- Pre-need follow-up
Inactive until you review and publish them. None send customer messages.
Forms and documents
- Pre-need planning inquiry
- Obituary preferences
- Aftercare check-in
- Arrangement conference summary
- Service day run sheet
- Aftercare call record
Editable native forms and document templates. Forms collect information for staff review.
Sample workspace
Explore 16 fictional records: ten family cases, two at first call, two at the arrangement conference, three with services scheduled, one with the service held and two in aftercare, and six pre-need inquiries, with 11 services, 6 aftercare calls, 16 vendor rows naming 8 vendors and 23 family contacts. Sample edits stay in memory and reset on navigation or reload.
No sample customers are added to your CRM.
Setup and source
- Guided setup and compatibility report
- Private rollback receipt
- AI-agent guide for customized installations
- Original editable source, configuration, and tests
How setup works
Full installation guideCheck your Seedly
Extract the kit and run the guided setup. It checks your installation and flags customized files before it changes anything.
Connect the helper
Deploy the included helper from your backend source, then build your web app and choose any starter pipelines and drafts.
Make it yours
Set business name, descriptor and default pipeline name. Then sign in and check the workflows and permissions your team uses.
Technical details and compatibility
Seedly CRM 5.8.4 · extension API 1. Node.js 20 or newer. The installer checks supported integration-file versions and does not deploy your web app or backend. The included original backend helpers are required for connected case creation, edits and resource setup. They preserve native account permissions, unrelated custom fields and row history, keep a record's kind and currency fixed, keep cases, calls and money apart, refuse a cause of death or medical details, Social Security, veterans' service, card, bank and policy numbers, dates of birth, ages from 10 up, access codes and logins in the usual phrasings, and check revisions before saving. Deploy them from the authoritative backend source. Pipelines and workflow drafts are optional.
One contact-linked record is a family case or a pre-need inquiry. A family case holds the person as a first name and last initial, the service type, where the first call came from, the funeral director, the first call and arrangement conference dates and times, the obituary's status, paper, deadline, publish date and word count, the statement total as recorded, an office note, services with their room or place and status, aftercare calls with due and done dates, vendors with their phone and status, family contacts with their role and an editable nine-step checklist. A pre-need inquiry holds the inquiry, the information sent, the planning meeting and the date the family's wishes were recorded.
Lindenrow records what your office recorded. It is not a price list, a statement of goods and services, a contract, a death registration system or a pre-need trust record, and it makes no regulatory, pricing-disclosure, legal, licensing or pre-need trust claim. It takes no payments, sends no messages, books no vendor and sends nothing to a paper. Cases, services, calls, vendors and money keep their own units and are never added together. A cause of death or medical details, Social Security numbers in the usual phrasings, veterans' service and VA file numbers, card, bank and policy numbers, dates of birth, exact ages from 10 up, access codes, passes and logins are refused in recorded text, while funeral home text such as Hymn 23, Plot 14, Section B, Pacemaker removed, Autopsy pending, release Thursday and Memorials to the American Cancer Society is kept. The guard is a protection against accidental entry, not a guarantee, so keep sensitive details out of the workspace. The three public form drafts hold only names, email, phone and fixed choices, with no message box; name answers are capped at 80 characters and phone answers take a phone number only.
Four optional pipeline templates and nine inactive workflow drafts. 16 fictional in-memory family cases and pre-need inquiries.
Calling, messaging, signing, payments, and external integrations depend on your Seedly installation, account permissions, plan, and configured providers. Screenshots use sample data and reference imagery. Hosting, installation, and ongoing maintenance are your responsibility.
Get the Funeral Home Kit
Checking access…
DevLaunch All Access
Every kit and every template.
- All 220 CRM kits for Seedly CRM
- All 190 website templates for Seedly Sites
- Every class, course, and product we release, added as it ships
- Private calls with Aaron
Already a member? Open your downloads.
Questions
How do I receive the kit?
Purchase securely through Whop. Your original source ZIP and installation documentation are delivered manually to the email used at checkout. This is a one-time purchase of this kit; Seedly software, hosting, and installation services are separate.
Does this include Seedly CRM?
You obtain and configure Seedly separately. The kit adds original frontend screens, a shared theme, starter definitions, and integration instructions. It does not include Seedly’s codebase, license, hosting, or a separate CRM database.
Is this one connected workspace?
Lindenrow keeps its light side rail and calm periwinkle accent across the kit views and native CRM tools in the same signed-in account. Contacts, Calendar, Estimates, Documents, and other full modules retain the functionality supplied by your own Seedly installation. Existing authored content and provider screens retain their own layouts.
Can I use it with existing customizations?
Yes, with a compatibility review. The installer checks the supported integration files. Changed integration files need a reviewed merge; the included AI-agent guide explains how to preserve custom extensions, permissions, providers, and routes.
Do I have to import all the starter content?
No. Choose individual pipelines and workflow drafts, use a compatible existing pipeline, or install none. Workflows remain inactive until reviewed and published. They use native triggers, internal tasks, optional notes, and timed waits. A wait does not verify task completion or recheck the current stage. The included drafts do not send customer messages.
Can I remove the examples and starter content?
Sample records stay in memory and never create customers in your CRM. Leave sample mode to return to your account. Starter setup lets you review removal of unused kit additions; server checks retain edited or published workflows and pipelines with live work or references. Removing the frontend does not delete account records.
Can different subaccounts use different kits?
The current design and branding apply to the whole web installation. Subaccounts still separate data and access. Use a separate web installation for another full-interface kit; running different kit designs by subaccount in one installation requires additional customization.
More professional services kits
Browse all 220 kits
