SeniorCRE is the operator-controlled operating infrastructure for senior housing & care. It is designed to govern definitions, source authority, reconciliation, and lineage across the systems an operator already runs, and can carry selected system-of-record functions where the operator chooses. Govern first. Replace only by choice.

How is SeniorCRE different from PointClickCare?

PointClickCare is a clinical EHR. Operators can keep PointClickCare; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How is SeniorCRE different from Yardi Senior Living Suite?

Yardi Senior Living Suite is a property-management and accounting system. Operators can keep Yardi Senior Living Suite; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How is SeniorCRE different from MatrixCare or ALIS?

MatrixCare or ALIS is a clinical and community-management system. Operators can keep MatrixCare or ALIS; SeniorCRE is designed to govern definitions and source authority above it. Where an operator chooses, SeniorCRE can assume selected system-of-record functions. Govern first. Replace only by choice.

How does SeniorCRE approach HIPAA and security?

SeniorCRE signs Business Associate Agreements and is designed with the administrative, physical, and technical safeguards applicable to its role under HIPAA. SOC 2 in progress.

Who is SeniorCRE for?

Senior housing & care operators, REITs, and capital partners. Our operator beachhead is organizations running 10 to 40 communities; larger portfolios are served through a separate Strategic Enterprise engagement.

How much does SeniorCRE cost?

Pricing and implementation fees are set in the applicable order form.

How long does SeniorCRE take to implement?

Deployment is gate-based and operator-specific; SeniorCRE publishes no standard implementation duration.

DESIGN · SYSTEM · TYPOGRAPHY

The institutional type voice.

Geist is the body. Instrument Serif italic is the accent — one phrase per section, never more. Geist Mono carries the operational signal: eyebrows, KPIs, terminal moments.

H1 · DISPLAY

font-tight tracking-display + text-5xl/6xl

Page-defining headline. One per page. Optional one-phrase Instrument Serif italic accent.

One operational data model.

H2 · SECTION

font-tight tracking-display + text-3xl

Section heading. Pair with an eyebrow above it.

ARCHITECTURE · AS · MOAT

Why the architecture is the moat.

EYEBROW

.eyebrow (Geist Mono, uppercase, tracked)

Operational tag above a headline. Dot-separated for telemetry feel.

LIVE · ONE · ROW · OF · TRUTH

CANONICAL · DATA · LAYER · v2

EDITORIAL ACCENT

font-editorial (Instrument Serif italic)

One phrase per section. Reserved for moat words: moat, truth, entire, sovereignty.

The operator owns the schema, the export, and the audit trail.

BODY

default (Geist via html font-family)

All prose, UI, and form copy. Do not declare font-sans manually.

Resident, care plan, ledger, shift, property, and entity — one record each, flowing into clinical, financial, workforce, compliance, and investor surfaces. No integrations to reconcile.

KPI · NUMERIC

font-mono nums-tabular

Counters, tables, terminal moments. Tabular nums prevent jitter on animation.

Communities

142

Hours returned

18.4

Occupancy lift

+3.2%

LEGACY · DISPLAY

font-display / font-heading (Playfair)

Preserved on existing investor & marketing surfaces (haven-sage system). Do not strip without intent.

Capital-grade infrastructure for senior housing & care.

ARTICLE · BODY · VOICE

.article-prose (compose with prose prose-neutral)

Long-form articles & blogs. Drop-cap on first paragraph, Instrument Serif on <em>, pull-quote on <blockquote>, Geist Mono inline <code>, primary-tinted underlines on <a>.

The capital layer reads the same operator-controlled operating record the operator writes to. That is the moat — not the UI, not the dashboards, not the AI. It is one governed record, surfaced to every role through property-level tenant isolation and a role hierarchy.

The investor reads the same governed record the operator writes.

Operators query through useEffectiveOperatorId(). REITs read covenant rollups and IRC §856 income tests from the same canonical entities — Resident, Care Plan, Ledger, Shift, Property, Entity. No copy. No lag. No portal.