Skip to content
View packages

GoSeedly Funeral Home Kit / INSTALLATION

A clear path
to your workspace.

Bring the kit into your compatible Seedly installation, preserve existing work, and choose the starter content that fits your team.

01

Start with your Seedly project.

Use your separately obtained Seedly CRM 5.8.4 installation with extension API 1, a configured backend, and working authentication. Keep a private source checkpoint, including existing customizations. Use Node.js 20 or newer.

02

Run guided setup.

Extract the kit outside the Seedly source folder. From the kit directory, run node setup.mjs. The check identifies supported integration files, changed files, and destination conflicts before installation.

03

Build and connect.

Deploy the included required helper from your authoritative backend source before connected edits. Follow QUICKSTART.md with your project’s existing package manager. Build the web app, sign in, and open your existing /location/YOUR_LOCATION_ID address. Verify access, navigation, and your important CRM flows.

Install the interface.
Choose the starting content.

Frontend installation and optional account content are separate. 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. Follow QUICKSTART.md and STARTER_CONTENT.md for the exact integration. The frontend installer does not deploy your backend.

Pick your starting structure.

Starter setup offers Families served, Aftercare calls, Vendors and clergy, Community relationships. Select individual pipelines and drafts, or use a suitable existing pipeline with the exact stage needed by the chosen draft.

Adapt each workflow.

All nine workflows remain inactive drafts. Review their native triggers, internal tasks, notes, timing, and assignments before publishing in Seedly. Timed waits do not check whether a task is complete or the stage has changed. These examples do not send customer messages.

Explore sample mode.

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. Add ?example=1 to the home or custom-view URL. Leave sample mode to return to your real account.

MORE OF THE WORKING DAY

From the first inquiry
to the final handoff.

Editable native forms and document templates give your team a practical starting point.

01 / INTAKE & FOLLOW-UP

Three ready-to-edit forms.

  • Pre-need planning inquiry
  • Obituary preferences
  • Aftercare check-in

Choose forms individually in Setup & resources, then customize and publish them in the native form builder.

02 / WORKING DOCUMENTS

Three reusable templates.

  • Arrangement conference summary
  • Service day run sheet
  • Aftercare call record

Open each template in Documents and complete it for the actual job or visit.

03 / THE NEXT STEP

Checklists alongside the work.

Record progress and notes in the kit’s operating views. Keep earlier rows by archiving them, and retain the context for the next person.

Forms collect information for staff review. They do not automatically change the kit’s custom records. Repeating setup preserves existing resource edits.

INSTALLING WITH AN AI AGENT?

Give it the context.
Keep your custom work.

Existing records and unrelated custom source do not require starting over. Modified integration files need a deliberate merge.

Start with the copy-and-paste prompt in INSTALL_WITH_AI.md.
Read AGENT_INSTALL.md for routes, permissions, provider wiring, backend contracts, and compatibility requirements.
Run node setup.mjs check "/path/to/seedly" before modifying files.
Preserve existing extensions, providers, account controls, custom pages, and unrelated data.
Use a reviewed merge for changed integration files; never replace them with clean copies or bypass the installer’s fingerprints.
Deploy the required write helper from the authoritative backend source before connected edits; preserve existing functions and authorization.
Build and verify account access, original CRM modules, new screens, saving, and reload behavior before publishing.

Make the workspace
feel like your team.

Edit apps/web/components/devlaunch-funeral-home/config.ts to set business name, descriptor and default pipeline name, then rebuild. The design applies to the entire web installation. Use separate web installations to evaluate different full-interface kits, rather than stacking their installers.

Starter removal, updates, and rollback

Review unused starter additions for removal in Starter setup before removing the frontend. Server checks preserve edited or published workflows and pipelines with jobs or references. The process targets recorded kit additions rather than sweeping account records.

Preserve your local configuration and source edits. Preview frontend removal with node setup.mjs remove "/path/to/seedly" --dry-run. The automatic uninstaller uses a private restoration receipt and refuses to overwrite later edits. Keep that receipt private and out of public hosting or source exports. Removing frontend files does not remove account data or undeploy backend functions.

For an update, follow the documented removal/install process and reapply your preserved changes. A manually merged installation needs its own private change ledger and reviewed source rollback.

What the workspace records

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.

The kit’s original operational screens share the frame with full CRM modules from your own Seedly source. Existing account permissions, feature gates, and configured providers still determine access to those modules.