From request to first case.

A funeral home requests access

A funeral home owner discovers Memoria — through a referral, a search, or a Memoria sales conversation — and requests an account. The platform team verifies the business (state license, address, contact) and provisions the tenant: a unique slug, a default locale, currency, timezone, and the first owner user.

Look for: In the demo this step is done by the seed script. In production it’s a sales/ops handoff.

Coming soon · narrative only

First sign-in by the owner

The owner receives sign-in credentials and lands on the admin shell. The interface is intentionally calm: no cluttered dashboard, no marketing inside the tool. The home immediately sees what matters — recent cases, pending condolences, today’s orders.

Set the funeral home profile

The owner enters the funeral home’s legal name, primary location, default locale (English / Spanish), currency, and timezone. These drive how the public site presents content and how operational reports are scoped. Multiple locations can be added later.

Look for: Locales are first-class — every text field that faces the family is bilingual from day one.

Choose a website template and brand it

Pick a design template — colors, hero layout, and headings — from the gallery, then upload the logo and set the bilingual tagline. Everything is locale-aware and the public site updates immediately — no deploy, no engineer. The template can be changed anytime.

Invite staff and assign roles

The owner invites the rest of the team: directors, family service staff, billing. Each invitation includes a role from a built-in matrix — Owner, Director, Family Services, Billing-only, Read-only. Roles are tied to a set of 30+ fine-grained permissions enforced server-side.

Look for: Role changes are audit-logged. The platform admin can see who promoted whom and when.

Configure pricing rules

The funeral home decides how to mark up the platform’s sympathy catalog. A simple percentage on a category (e.g. +15% on flowers) or a flat addition on a specific product. The pricing engine applies these rules at checkout and at order management consistently — the price shown is the price charged.

Look for: Pricing is engine-driven, not a per-product field. One rule covers the whole catalog and stays current as new products arrive.

Coming soon · narrative only

Publish public CMS pages

About, contact, grief resources, FAQs — the marketing pages that surround the obituary list. Edited in a structured editor with locale toggle. Slug-based routing means the funeral home keeps URLs they care about (e.g. /pages/about, /pages/our-staff).

Connect with a florist partner

The platform pairs the funeral home with one or more florist partners in their service area. Either side can request the link; the platform admin approves it. Once linked, the florist’s products become available for sale on this funeral home’s site, with the funeral home’s pricing rule applied.

Coming soon · narrative only

Register the first case

The funeral home is now live. A family arrives, a case is opened, an obituary is drafted, condolences and tributes begin. The day-to-day flow is covered in the operational tour.

Weekly settlements begin

At the end of the first week with paid orders, the funeral home appears in the platform’s settlement statements: revenue, platform fee, vendor cost, net payout. Settlements are run on a regular cadence and the funeral home sees their statement before any money moves.