About Pinnacle
There was a gap in home and community-based services. Pinnacle lives there.
An orchestration layer that sits between the people receiving care, the teams delivering it, and the state programs making it possible.
Why we exist
The middle ground HCBS was missing.
Remote support existed in two forms: heavy monitoring designed for facility-level care, or nothing at all. Neither fit members living in their own homes under CFC and HCBS waivers. Pinnacle exists because there was space between — a middle ground where support is present without being intrusive.
We're not a monitoring product. Pinnacle is an orchestration layer: it ingests data from the devices already in a member's home, normalizes it into a single event ledger, and drives staff workflow from the evidence. No proprietary hardware. No surveillance dashboard. Just the infrastructure the rest of HCBS operates on.
We're launching in Colorado under CFC in August 2026 — four HCBS specialties on Day 1 (Remote Supports, PERS, Electronic Monitoring, and Assistive Technology), ten billed members, and a functioning evidence-to-claim pipeline. State-by-state, not a national launch that promises everything and delivers nothing.
Who stands behind Pinnacle
Built in Colorado, grounded in the waivers.
Pinnacle is a Colorado-based provider built specifically around the Community First Choice and HCBS waiver programs. We operate within the specialty rules — Remote Supports, PERS, Electronic Monitoring, Assistive Technology — not adjacent to them.
Our accountability is to case management: transparent documentation, authorized access, and a provider relationship that CMAs can evaluate on Day 1. No black-box platform. No distant corporate parent. A local team that answers to the same system you do.
HIPAA-aligned from day one
Every workflow, data path, and export follows HIPAA-aligned protocols — built in from the start, never bolted on later.
Consent-first, always
Each interaction is authorized and tied to a specific service plan. Support happens on purpose and with permission, never quietly in the background.
Documentation, not surveillance
We record what happens during an authorized check-in: structured notes, timestamps, and outcomes. No cameras, no microphones, nothing captured between sessions.
Authorized access only
Care teams see role-appropriate summaries and nothing more. The system enforces permission boundaries, so no one sees beyond what they're cleared for.
Start a pilot conversation
No commitment required. We'll walk through your current model, identify where Remote Supports fits, and show you exactly what a pilot looks like.
Start a conversationTypical pilot timeline: 4–8 weeks. We handle onboarding, device configuration, and documentation setup.