From care to longevity

Bend the curve
of aging.

Aging services can extend excellent care by knowing each person over time, not only in the moment. The KM360 Life Record and the operator-led Aging Data Collective, built together with the industry, make that possible.

Video overview coming soon

The movement

Three ideas, one direction.

Why now

People are living longer. Communities hold a lifetime of knowledge about each person, but it sits in separate places.

Why together

No single organization can build this alone. Banking built ATM networks and ACH together; aging services can build shared rails too.

What changes

When you know the whole person over time, you notice change sooner. That is the Life Record.

Featured column

From Care to Longevity: Why Aging Services CEOs Must Build the Next Infrastructure Together

By Mike Rambarose, President & CEO, Whitney Center, and Steve Lindsey, CEO, Garden Spot Communities

AI cannot fix fragmented systems. We need a shared foundation that connects data, preserves each person's unique story, and helps us anticipate their needs. No single organization can build this future alone. Together, we can use technology to create a more human-centered approach to aging.

Read the column
McKnight's Senior Living

Guest column, written by two operators building this together.

Two commitments

Go deeper on the person. Build it with the industry.

Depth

A growing set of capabilities for knowing each person: a Life Record foundation, then location and context, needs reporting, a common application for action, and research toward earlier awareness of change. You see what is live, what is in pilot, and what is still research.

Partnership

KM360 is built with operators, not sold at them. Participating organizations help shape priorities and co-develop data and functionality, and take part through equity under distinct cohort agreements. We work with every system you already have. We replace none of them.

Products

We work with every system you already have.
We replace none of them.

With implementation, you get the Life Record foundation: one trusted picture of each resident, questions answered in plain language through Ask KM360, and Power BI reporting. Location and needs reporting are products we are building next.

Read-only by design

Current integrations read from your systems. They do not write back unless separately approved and configured.

HIPAA-compliant

Built for protected data, with access controls set around roles.

What KM360 does not do

It does not replace a source system. Future authorized actions are not ruled out, but nothing is written back today without your approval.

Three product areas

What you get, and what we are building.

The first is what you receive with implementation. The second and third are in development.

Available with implementation
Know the Person

The Life Record foundation

What you get with implementation: One trusted picture of each resident and of the enterprise, with standard C-suite indicators built from the person up.

  • A unified data lake across your existing systems
  • Data-cleaning tools that surface discrepancies (the discrepancy report)
  • Ask KM360, an LLM for questions in plain language
  • Power BI reporting
In development
Know the PersonUnderstand Change

Location

What we are building: understanding how people live. We are developing a way to connect location and movement information with each resident's Life Record to better understand daily routines, activity, and social engagement. By recognizing changes in individual patterns, communities could identify emerging needs earlier and provide more personalized support.

It is not just knowing where someone is, but understanding what their daily patterns reveal about their well-being.

In development
Understand ChangeAnticipate and Act

Needs reporting and early awareness

What we are building: Earlier, better-informed conversations about who may need what next.

  • Reports on emerging resident needs
  • Early-warning tools that flag change from a person's own baseline

KM360 is being built to detect, flag and inform. We make no claim of prediction accuracy.

The roadmap

Five steps, one progression.

Each step builds on the last. The first is available with implementation. The next two are in development. The last two are still ahead.

Life Record foundation

Know the Person
Available with implementation

Location and context

Know the Person
In development

Needs reporting

Understand Change
In development

Common application

Anticipate and Act
Planned

Predictability

Anticipate and Act
Research stage

A research agenda. No accuracy claims.

Working on something? Bring it to the community.

Is there something you have been working on, or looking for, that would be great for the community to take on together with others? Tell us what you have in mind.

Value

The same executive view,
built from the person up.

What a CEO and a CFO gain, and a calculator to test it against your own numbers.

Bottom-up beats top-down

Today's dashboards are an aggregate of aggregates. KM360 builds the same executive view from knowing each individual, which makes cost and margin per resident possible.

Forward, not backward

Top-down indicators help you close the month faster. Flagged indicators let you adjust within the month.

Both, not either

You keep the standard C-suite indicators and gain the whole person. KM360 adds a data foundation built around the individual. It does not argue against the one you have.

Where the value shows up

Three kinds of benefit.

Operational Efficiency

Less time spent reconciling and more time deciding. Meetings, weekly reporting and board preparation start from one shared picture.

Organizational Performance

Cross-system discrepancies surface continuously, so billing errors and rework are found and fixed instead of discovered late.

Resident Well-being and Long-Term Potential

Noticing change earlier supports better conversations and, over time, fewer avoidable transitions. This is the least certain category, and we show it separately below.

Calculator

Put in your own numbers.

An illustrative scenario based on CEO-vetted operator assumptions. Everything runs in your browser; nothing you type is sent anywhere unless you choose to submit the form. Results are based on your inputs and the stated assumptions. They are not realized, independently validated or guaranteed savings.

Your organization
Staff in your weekly coordination meeting
Hourly costs, fully loaded
Investment (optional)
Leave blank to see gross value only. Enter your own figure to see net value and return.
Show workings and assumptions

Each use case shows a conservative and a mid-range estimate. Floors and ceilings keep results inside a plausible band for your size. Where a benefit depends on another (for example meeting time and board reporting both draw on leadership hours), categories can overlap, so do not treat the sum as independent.

Use caseConservativeMid-rangeBounds
1. Reconciliation meeting(attendees × 1.5 h × 50%) × frontline $/hr × 52 × 50% + departments × 3 h × dept-head $/hr × 52 × 50%(attendees × 1.5 h × 50%) × frontline $/hr × 52 + departments × 5 h × dept-head $/hr × 52 × 50%Cons. $30K to the lesser of 1.2% of revenue or $200K. Mid $50K to the lesser of 1.8% of revenue or $280K.
2. Early signal detection(residents × 35% hospitalizations × $1,500 × 10%) + (residents × 30% injurious falls × $3,000 × 10%)(hospitalizations × $4,000 × 15%) + (falls × $7,000 × 15%)Cons. $30K to the lesser of $600/resident or $250K. Mid $55K to the lesser of $900/resident or $400K.
3. Board and weekly reporting[300 h × (1 + directors × 12%) × exec $/hr × 60% + directors × 3 h × 52 × exec $/hr × 50%] × 70%Same, without the 70% factorCons. $15K to the lesser of $15K per director or $120K. Mid $25K to the lesser of $22K per director or $180K.
4. Billing and data qualityrevenue × 0.5% + departments × 2 h × frontline $/hr × 52 × 25%revenue × 1.0% + departments × 2 h × frontline $/hr × 52 × 50%Cons. $40K to the lesser of 1.2% of revenue or $280K. Mid $65K to the lesser of 1.8% of revenue or $420K.
5. Avoidable transitions (Year 2+, research stage)max(2, 0.8% of residents) transitions × 3 months × $4,200 + residents × $35 × 5%max(3, 1.5% of residents) transitions × 5 months × $4,200 + residents × $35 × 10%Cons. $40K to the lesser of $800/resident or $350K. Mid $70K to the lesser of $1,200/resident or $500K.

Use cases 1 to 4 make up the Year 1 totals. Use case 5 is shown separately because it depends on that foundation and on enough shared data. Benchmarks are industry-based estimates reviewed by an operator CEO and remain editable through your inputs.

What your result means

Use it to start a conversation, not to set a budget. The estimates show where time and money may be going today and how large the opportunity could be under stated assumptions. Your own data would sharpen every line.

Be careful with the future-facing part

Reducing avoidable care transitions (use case 5) is an anticipated benefit that depends on building the earlier steps and on shared data. It is kept out of the Year 1 totals. A return calculation is not scientific validation, and we do not present it as one.

Aging Data Collective

Five communities stepped forward to lead.
Join them as a Design Partner.

The Aging Data Collective is an operator-led coalition. Participating organizations help set priorities, contribute operating expertise, share learning and take part through defined equity and governance arrangements.

KM360 owns its platform and the IP it develops. Each partner keeps its original data and pre-existing IP, subject to authorized data-use and privacy agreements.

Where the cohorts stand

The founding cohort is full. Design Partner seats are open.

First cohort Full

Founding Builders

Five communities stepped forward to lead this effort.

Whitney CenterGarden Spot CommunitiesCedar CommunityThe Pines at DavidsonWillow Valley Communities

Founding Builders hold equity on the first SAFE terms and help shape priorities, co-development and peer convening. Specific governance rights are set out in each executed agreement.

Next cohortNow open

ADC Design Partners

The opportunity now is to join them.

  • Equity participation under a different SAFE and economic structure
  • Co-development participation and early access
  • Benchmarks and peer learning

Specific governance rights are set out in each executed agreement.

For both cohorts: KM360 owns the platform, software, algorithms, AI and predictive models, and enhancements developed in collaboration. Partners retain their original data and pre-existing IP.

What members get

Benefits in four groups.

01

Influence and Governance

  • Help shape KM360 priorities, the roadmap and shared data standards
  • Take part in defining rules for privacy, access, model use, auditability and benchmarking
  • Influence what gets built when existing market tools fall short
02

Intelligence and Benchmarks

  • Anonymized peer benchmarks on transitions, utilization, staffing pressure, incidents, engagement and cost drivers
  • Shared playbooks and emerging research on signals that may help flag change
  • Governed shared learning as benchmarks and collective insights come online
03

Access and Co-Build Rights

  • Early access to new KM360 capabilities, with a peer cohort to test and shape what works
  • Structured co-build working sessions
  • Preferred access to early capabilities through the program
04

Shared Learning and Peer Network

  • Quarterly ADC CEO working sessions to review benchmarks and shape the roadmap
  • A trusted peer environment where members share risk and avoid building alone
  • A place to share what is working
Founding builders

Meet the founding builders.

Operators building this because they want aging services to look different.

How to join

What engagement actually looks like.

Express interest

Tell us who you are and the data problem you want to solve.

Leadership discussion

A conversation about fit, the cohort that suits you, and what you want to build.

Agree, then map

  • Participation, commercial and security agreements
  • Phase 0 implementation-readiness review: organization, systems, data access, privacy and operating priorities
  • Phased implementation, with a focused proof sprint where it helps

A proof sprint is an option, not a required step.