Lomax: the sales and operations platform we built for senior living

What problem does Lomax solve?

A senior living community sells on one system and operates on another. The family's first inquiry, the tour, the deposit and the move-in sit in a CRM. The apartment, the care level, the monthly bill and the maintenance ticket sit somewhere else. Every handoff between the two is a person re-typing what another person already typed.

That split costs twice. It costs accuracy, because a rate that depends on both the apartment type and the care level is now maintained in two places. And it costs move-ins, because the thing that most decides whether a community fills is how quickly somebody calls a family back, and a lead sitting in an inbox is not a lead anybody is calling.

How Lomax works

One record, inquiry to resident. A prospect's history stays attached to them when they become a resident, and to the unit, the rate and the bill. Nothing is re-keyed at the handoff because there is no handoff.

A five-minute clock on every inquiry. Each new inquiry creates a first-contact task with a five-minute target, and misses escalate to the manager while the lead is still warm rather than showing up in a report at the end of the month.

A move-in score that shows its working. Every prospect carries a 0 to 100 score built from six weighted factors: stage, temperature, urgency, recency, tour and decision maker. It is rules-based on purpose, not machine learning, and it displays the factor breakdown, so a counselor can see why a family scores what they score and argue with it.

Billing that follows the care level. A rate card by apartment type and care level, with effective dates, feeds recurring charges, monthly invoicing with proration, a full ledger and standard aging buckets. Residency and service agreements generate pre-filled from the resident record and are signed in the browser, capturing signer, timestamp, IP and a content hash of the exact document text.

Access enforced at the database. Six roles, scoped per organisation and per community, with row-level security on every table rather than checks in the application layer. Financials are restricted, and managers see only their own community.

Where it stands

Lomax is live in production, replacing Eldermark at its launch community.

The migration moved real operating history, not a fresh start: 5,517 archived inquiries into the lead pool, 759 prospects with their full activity history, 337 referral partner records and 138 residents.

It is deliberately not clinical. Lomax records a resident's care level, because pricing depends on it, and never care delivery. No medication administration, no care plans, no clinical notes. That boundary is a design decision, not a gap.

Quality is tracked formally: 164 test cases across 19 passes, run against production.

It was built multi-tenant from the first migration rather than retrofitted, with organisations, communities and per-organisation isolation, so it is a product rather than a one-off build.

Stack: Next.js and React with TypeScript, Supabase Postgres with row-level security, Clerk for authentication, Resend for transactional mail and sequences.