Falls are proven. Wellness and staffing are the bets.
Fund the climb, not the feature list. Each line gets the investment to clear its next rung, and no more until it does.
| Product line | Signal | Workflow | Outcome | Scale |
|---|---|---|---|---|
| Safety AI | EarnedOver 99% accuracy reported. A person checks every alert. | EarnedAlerts land in nurse call, now inside PalCare. | Earned80% fewer fall related ER visits in the 2019 study they cite. | Earned600,000+ fall events across 1,000+ communities. |
| Staffing intelligence | EarnedCare measured without wearables, per the Yardi interface announcement. | EarnedFlows into Yardi EHR: staff time in rooms, direct vs indirect care. | In progressLabor hours and billing accuracy. No public proof yet. | Not yetFollows the outcome. |
| Wellness AI | EarnedA wellness score per resident. Hourly checks 7 pm to 7 am. | EarnedStaff use the dashboards. | Not yetNo published outcomes yet. | Not yetFollows the outcome. |
What clears each rung
- Signal. Accuracy and false alarm thresholds, set per product line before anything reaches the field.
- Workflow. Staff act on it inside the systems they already use. PalCare and Yardi are the model.
- Outcome. A number the operator pays for moves: hospital transfers, length of stay, labor hours, billing accuracy.
- Scale. It holds in every care setting, not just the communities that adopted first.
Trusted AI travels with every line
You already solved the hard part on falls. Video is kept only when someone is on the floor, and a person checks every alert.
I'd carry that standard into wellness scores and presence data. Human review until the evidence earns more autonomy. Privacy by design from the first sprint.
Halo and PalCare can both be right.
Halo makes you an eCall company with your own pendants and buttons. PalCare makes you the intelligence inside someone else's nurse call, and that launched October 13. Both are good moves. Together they need a rule.
Run deal by deal
It's a conflict. Sales sells whichever one closes this quarter, and the roadmap chases both.
Run as a portfolio
It's coverage. Partner where an operator loves its nurse call system. Lead with Halo where they're replacing it anyway. Either way your AI reaches the caregiver.
The rule I'd write in the first 90 days
- Which segments Halo leads.
- Which partners lead, and where.
- What evidence would change the call. Then it goes on the one roadmap, so Sales sells what's committed.
The clock
Inspiren raised $70M in September and plans to deepen its integrations with the major EHR platforms, per Senior Housing News. Operators are picking partners for the next decade. A muddled ecosystem story is how you lose that pick.
Prove NOI one care setting at a time.
The claim
Your ROI analysis shows up to $3K in net NOI per resident. That's the number a CFO and an investor both care about.
Today it comes from internal analysis. The posting asks for it proven with outcome data in each care setting. I'd treat that proof as a product, not a slide.
How I'd build the proof
- Pick the drivers per setting. My starting hypothesis: memory care leans on falls, ER transfers and length of stay. Assisted living adds labor hours and billing accuracy.
- Baseline, then compare. Measure before install, then against matched communities that don't have it yet.
- One readout for everyone. Sales and Customer Success share the same numbers with each operator, every quarter.
- Publish the method. So the number survives a skeptical CFO, and the next one, and the board.
I’ve shipped 50% faster before.
I've made this move before
| Where | Launch by NTT Data. I built the firm's first product org. |
|---|---|
| Starting point | Client teams ran on BAs and project managers. |
| The move | 45+ client accounts to product, outcomes and design. |
| Time | 12 months. |
| Result | Launches about 50% faster. Fewer escalations on top accounts. We kept our people. |
| Since | The model has scaled to hundreds of PMs. |
Devices in the field
For HCA Healthcare I owned an iPad intake app across 36 hospitals in the US and UK. That meant the rollout, the MDM and the field reliability.
It ran on Epic and Meditech data over FHIR and HL7 and reached 745K monthly users.
The 90 days on the board, in detail
Listen and map
Days 1 to 30
Meet every PM, engineering lead, clinical consultant and seller. Map what Sales has promised against what the roadmap commits. Draft the keep, rebuild and stop list.
One roadmap
Days 31 to 60
Publish decision rights with the CPTO and VP of Engineering. Align teams to outcomes on shared platforms for AI, data and integrations, and devices. Baseline throughput by release and adoption.
Gates live
Days 61 to 90
Run the first stage gate reviews on wellness and staffing. Ship the partner rule. Deliver the first NOI readout with Customer Success.
What I'd expect to stop
- Roadmap promises made inside deals
- Measuring teams by tickets closed
I'd confirm both once I'm inside.