Loading...
Program status · Paused
We are not taking new Founding Operator applications right now. Customer proof will come through operator co-development, at gates rather than dates, during the pre-production period. Founding Operator terms will be available once the record is built. The program description below is kept for reference.
Request an Executive BriefingFounding Cohort I · Program detail
The diligence detail behind the Founding Operator Program: how the agreement is structured, who qualifies, how deployment is sequenced, what the security posture is today, and what is built versus still being validated.
Plain language first
Program Economics
Operators use this page for diligence, so the program has a single commercial definition. Any figure, month count, price range or service level attributed to the Founding Operator Program anywhere else — including earlier materials, cached search results or third-party summaries — is superseded by the rows below. Rates are quoted under NDA against your own portfolio.
10–40 communities
5 direct operators. Multi-state portfolios preferred.
41+ communities
Engagement outside the Founding Cohort. Custom integration design and commercial terms.
Subscription structure
This is additive spend in the default parallel configuration: the operating record is populated from your EHR, eMAR, CRM, payroll, and GL, and you keep running them. SeniorCRE includes its own EHR and eMAR and can carry the clinical record where an operator elects that configuration — the default is to keep what works, and that is a choice rather than a limit.
What it does offset is the spend you built because those systems do not join: the BI consultant retainer, the internal warehouse project, and the analyst headcount that hand-assembles board and lender reporting. We build that teardown against your actual invoices during diligence — line by line, with the residual additive number stated in the same document. No SeniorCRE engagement is priced on a claimed replacement of software you will still be paying for.
Typically offset
BI/analytics consulting retainer, warehouse build & maintenance, reporting analyst time
Never offset
EHR, eMAR, CRM, payroll, GL, pharmacy — you keep and keep paying for these
Benchmark frame
Judge the quoted subscription against your own per-bed NOI and agency-labor line, not against a per-community sticker
A single-state assisted living portfolio of 90-unit communities with three source systems sits near the bottom of the range. A four-state portfolio with skilled nursing, seven source systems, and monthly lender reporting sits near the top.
| Founding Term | Set in the agreement Founding economics run for the contracted term stated in the agreement, with the snap-back date and post-term rate set at signing. |
|---|---|
| Implementation | Defined in the order form Implementation scope and fees are defined in the applicable order form. Implementation covers deployment of the operating record across your existing systems — EHR, eMAR, CRM, payroll, GL, AR, and incident reporting. |
| Subscription | Quoted per portfolio Contact SeniorCRE for current commercial terms. Founding economics are the consideration for documented proof rights, and terms are quoted under NDA against your own portfolio. |
Growth is handled by addendum, not by renegotiation.
No expansion rate, discount, or repricing protection is published on this page. Commercial terms are governed by the commercial record above and set in the signed agreement.
Operating Record Diagnostic
Delivery capacity is one engagement per delivery pair at a time. Scheduling is first-come, and a Diagnostic is not scheduled until the engagement letter, the BAA, the named owners, and the frozen community list are all in place.
Evidence Program
The evidence program measures the infrastructure directly. Business results are contributory: the record informs the decision; the operator makes it. SeniorCRE does not convert a target date into a production claim. Production entry occurs only when the agreed security, data, integration, governance and operational acceptance gates are satisfied.
SeniorCRE publishes no occupancy, labor, NOI, survey or clinical improvement commitment. Where these move, the operator moved them.
Deployment
1
Gate: authority map accepted. Operating model mapped and integration architecture approved by named executive sponsors on both sides.
2
Gate: first source reconciled. The operating record is populated from the operator’s incumbent source systems — EHR, GL, payroll or CRM — with lineage documented.
3
Gate: metric accepted by the operator. A named metric is produced from the record, traced to source rows, and accepted as the figure the business will use.
4
Gate: reporting package produced from the record. Board, lender and regional reporting is assembled from the operating record rather than rebuilt by hand.
5
Gate: addendum executed per addition. New communities are onboarded by executed addendum. Economics for communities added during the term are set in the agreement, including the expansion basis and the addendum mechanism.
Eligibility
Maximum of five participants. Applicants must meet every criterion below to be considered.
Operator must have at least 10 communities actively under management at time of application.
Founding economics are gated to portfolios of 10–40 communities. Portfolios at 41 or more are routed to a separate Strategic Enterprise engagement.
Operators running across multiple state regulatory environments are prioritized for selection.
Applicant must operate the communities directly. Pure asset owners, REITs without operating arms, and third-party managers without operational authority do not qualify.
Executive sponsor at CEO/COO/CFO/CCO level must commit to quarterly advisory participation throughout the engagement. Founding Advisory status, subject to the council charter.
Founding economics are granted in exchange for documented proof rights, specified in the agreement: named-reference use, logo usage, written case documentation of the deployment and its measured results, and peer-operator introductions. You approve the published wording; the participation itself is the consideration for the discount.
Founding economics run for the contracted term stated in the agreement, with the snap-back date and post-term rate set at signing. The value gate and its exit right are set in the same agreement.
Operators above the Founding Cohort I scope are engaged separately through a Strategic Enterprise deployment — custom integration design, dedicated delivery, and executive-level commercial terms. Lenders, GPs, family offices and REIT capital teams are served by the Capital Partner Council: members review and may endorse the canonical operating-record reporting format, sit in the same quarterly sessions as Founding Operators, and may reference the format in term sheets or reporting covenants. No fee, no license, no revenue relationship to disclose.
01
Submit pre-qualification and request the Program Overview. SeniorCRE leadership reviews fit against cohort criteria.
02
Working session with SeniorCRE founders and your executive sponsor. Confirm strategic alignment, scope, and portfolio fit.
03
NDA executed. Architecture review, integration footprint assessment, and reference exchange. Both parties decide to proceed.
04
Final selection by SeniorCRE leadership. Agreement, implementation addendum, and advisory participation formalized.
Security & Data Governance
No SeniorCRE SOC 2 report has been issued. SeniorCRE does not claim SOC 2 certification, an issued report, an engaged auditor, or an open observation window. Founding agreements carry any security-milestone covenant against report issuance, not a published target date.
You cannot check our references — we have no public customers yet. So the risk sits with us instead of you: named milestones in the agreement, a joint written review of them, and your right to exit without penalty if they are missed.
Named source systems joined, agreed reporting packages produced from the record, and executive adoption criteria — all written into the agreement, not the deck.
Joint written assessment against those milestones. Not a satisfaction survey — a checklist with dates.
You may terminate at the review point without penalty for the remaining term. Your canonical data exports with you, in full.
We also disclose the asymmetry rather than hide it: our diligence includes your references, and yours cannot include ours. The exit right, the Diagnostic, and the Capital Partner Council exist because that asymmetry is real.
Status as of September 29, 2026 (last modified 2026-09-29)
| Capability | Evidence step | What is true today | Proof note |
|---|---|---|---|
| Operator-Controlled Operating Record (source authority, field-level lineage) | Not yet built | The Operator-Controlled Operating Record is designed and not yet implemented in any community. Source authority, reconciliation, and field-level lineage require implementation and operator-owned acceptance evidence. | The next proof gate is one de-identified census or payroll export mapped into the record and traced back to its source rows; operator acceptance is a separate gate. |
| Operator-exported census and payroll files | Not yet built | Specified as ingestion Mode A (operator-exported files) and Mode B (scheduled report drop). Not yet built: both depend on the operating record, which is not built yet. | The gate is one de-identified census or payroll export mapped into the record and walked back to its source rows. |
| Clinical record surfaces (EHR configuration) | Built · demonstrable | Clinical record surfaces are built. Medication administration remains a separate roadmap row. After function-specific gates clear, an operator may choose SeniorCRE for defined clinical system-of-record functions; no community does so today. | Inspect the clinical configuration and one-authoritative-MAR controls in a controlled SeniorCRE environment; no PHI production evidence is claimed. |
| Medication administration surface (eMAR build-out) | Not yet built | The medication administration surface has build-out remaining and has not passed readiness review as of September 2026. No independent review and no clinical sign-off has been performed. The gate that would change this: a defined scope, completed build-out, and clinician review. | No step-1 demonstration is published for the full medication-administration control set. |
| Billing, revenue, and reimbursement governance | Built · demonstrable | Revenue and reimbursement reconciliation controls can be shown in controlled SeniorCRE conditions with synthetic data. No operator billing runs in production on SeniorCRE. | Inspect the reconciliation-control trace; step 4 requires an accepted operator billing workflow. |
| Scheduling and labor governance | Built · demonstrable | Labor, agency, and coverage governance controls can be shown in controlled SeniorCRE conditions. Payroll or scheduling write-back into operator systems is not in production. | Inspect the labor-governance control trace; step 4 requires an accepted operator workforce workflow. |
| Clinical risk intelligence (including sepsis-risk surfacing) | Built · demonstrable | Decision support only, with human review and escalation. Controls can be shown in controlled SeniorCRE conditions; no efficacy claims and no production deployment. Never issues diagnoses, orders, medication changes, or transfer decisions. | Inspect the human-review and escalation controls; no clinical efficacy or operator workflow validation is claimed. |
| AI agents with write authority into operator systems | Not yet built | Read and recommend paths are built; human-in-the-loop write authority into third-party systems remains in the build queue and is not enabled. | The write-authority capability is not started for third-party systems; absence of an operator grant remains a denial. |
| Third-party integrations (EHR, CRM, payroll, GL, property management) | Built · demonstrable | Connector and extract paths can be demonstrated against vendor sandboxes or synthetic extracts. No third-party integration is live in operator production. | Inspect sandbox or extract persistence where available; step 3 requires the full authority, reconciliation, access, and lineage control trace for the connector row. |
| PHI in production | Not yet built | Blocked by a governance gate. PHI is not processed in operator production until that gate is cleared with the operator. | No production PHI processing is claimed; the gate is a signed operator scope, BAA, and acceptance evidence. |
No workflow has been validated in an operator production environment, and no operator outcome has been measured.
This register inherits the Evidence Record. Each row states its highest proven evidence step; no step is inferred from the one before. Pre-production. No operator runs SeniorCRE in an operator production environment; no operator workflow has been validated; no measured operator outcome or independently validated result is published; no third-party integration is live in operator production; and no PHI is processed in operator production. Last verified September 29, 2026. Maintained by SeniorCRE Platform Governance; reviewed by SeniorCRE Executive Review Group.
BUILT
The operating record and its governance rules are implemented and exercised by SeniorCRE.
BUILT
The record shows up on the floor, hour by hour, across a full shift.
BUILT
These workflows are read-only, record-native, and human-approved. They have not yet been validated. Initial Production Scope and Production-Entry Gates are set per agreement. Stated as of September 29, 2026.
BUILT
The operator keeps existing systems and can export the full record without vendor permission.
BUILT
Clinical record surfaces are built; medication administration and eMAR remain roadmap—not built. Each selected function requires agreed scope and complete workflow, clinical-safety, data, and operator-acceptance validation before reliance.
BUILT
Diligence documents are available for vendor risk and audit committee review.
Status language follows the evidence ladder on /evidence-architecture. Pre-production. No operator runs SeniorCRE in an operator production environment; no operator workflow has been validated; no measured operator outcome or independently validated result is published; no third-party integration is live in operator production; and no PHI is processed in operator production. Last verified September 29, 2026. Third-party marks are referenced nominatively and remain the property of their owners.
Frequently Asked
Applications are reviewed directly by SeniorCRE leadership.