Every KPI, Role, and Action - In One App.

A standing agent inside skyCommand™. Overnight it reads each person’s own numbers, in their own role, and puts a short list in front of them the next morning: what moved, what it means, what it costs to leave alone, and the play that addresses it — with a button that runs it.

It covers four horizons. Today is what moved against you. Tomorrow is where it lands if nothing changes, with its confidence stated. This Week is what you can realistically move. This Month is whether you are on pace and what closes the gap.

Three items per horizon, deliberately. A short list is the only list people actually finish.

Yes. skyCommand™ ships a vertical pack per service line — senior living, skilled nursing, home health, provider groups, health plans. The pack carries the vocabulary, thresholds, dollar rates and plays for that industry, so the same engine reads naturally to a director of nursing and to a revenue leader.

What changes between packs is judgment, not the product. Your metric catalogue stays yours, and the way work reaches a person is identical.

Some capabilities are genuinely specific: rate recommendations apply where you set your own rates, so they are on for senior living and off for skilled nursing, where payers set them. A CCRC running several service lines turns on a pack per line.

Only where you tell it to. Producing recommendations and executing them are separate switches, and executing is off until you turn it on. Sending anything outside the app — email, SMS, Teams — is a third switch, and reaches only recipients you have allowlisted.

Every action records who it was generated for and which governed metric it came from, and every change the agent makes is written to the same audit log as a change made by a person.

skyCommand™ monitors 350+ KPIs organized across five operational domains: Census & Occupancy, Staffing & Workforce, Quality & Safety, Revenue Cycle & Financial Performance, and Referral & Admissions. All KPIs update in real time and are viewable at the enterprise, regional, facility, or individual level.

When skyCommand™ surfaces a priority issue — a billing exception in revenue cycle, a compliance gap, a staffing shortfall, or any KPI trending off-target — you can click directly into the relevant workflow in the appropriate Skypoint module without navigating away. The action is logged, tracked, and tied back to the originating KPI.

skyInsights™ is your deep analytics and reporting layer via Power BI; skyCommand™ is your real-time operational command center for monitoring, prioritization, and immediate action.

skyCommand™ is the operational hub — bidirectionally integrated with 250+ systems and Skypoint’s 20+ agentic apps, creating a closed loop from KPI signal to resolved outcome.

No. Every read runs under that user’s own login and row-level security — never a shared system account. A regional director’s list is built from the communities that director can already open; an executive director’s is built from theirs.

The overnight run generates only for users whose own credential skyCommand™ holds, and skips the rest rather than falling back to broader access.

It crosses what you actually realise per occupied unit against where your occupancy sits, community by community, and adjusts for acuity so a heavier-care community is not mistaken for an expensive one.

That produces a verdict rather than a number to argue with: raise, hold, or — the one a pricing tool cannot reach — this is not a pricing problem. When occupancy is soft and rate is already at market, the answer is demand, and skyCommand™ says so instead of recommending an increase that would make it worse.

Recommendations are advisory. Nothing changes a rate without a person approving it.

No. skyCommand™ reads Power BI, Databricks and Lakebase, and resolves the source per query — so one deployment can serve all three side by side. You are not migrating to a warehouse before you get value, and your existing semantic model stays the source of truth for what a metric means.

Your KPI catalogue is configuration, not code: adding a metric is a setting, not a release.