Status
What is live, what is in beta, and what is planned
Three labels, used the same way everywhere on the site. live works today on ingested CMS data. beta works today with a stated limit. planned is not built, and says what it waits on. No dates are published, because none are committed.
Live today
| Capability | What it does | Status |
|---|---|---|
| Market explorer, all 3,199 counties | Filter, rank and export every county on the April 2026 CMS county file. | live |
| MA & other health plan share and momentum | National, state and county records, each from its own CMS geography row. | live |
| SNP and D-SNP intelligence | Plan-level SNP enrollment, integration mix and the D-SNP capture proxy. | live |
| Stars movement | Derived enrollment-weighted carrier averages from official CMS contract ratings. | live |
| Carrier & plan intelligence | Carrier enrollment movement, plan exits and quality comparisons. | live |
| Policy and bid intelligence | Tracked CMS actions with dates and status, and the 25-milestone bid cycle. | live |
| Sales intelligence | AEP targeting, market headroom and carrier battlecards. | live |
| Marketing intelligence | Market opportunity, D-SNP opportunity, competitive structure, policy lens and calendar. | live |
| Weekly national brief | One seven-day window per issue, every item dated and sourced. | live |
| Citations, provenance and vintage on every figure | Copy a citation, open the provenance panel, export with the source embedded. | live |
In beta
Working, with a limit that is stated where you use it.
| Capability | What it does, and the limit | Status |
|---|---|---|
| Local workspace | Saved markets, saved analyses and marketing projects, stored in your browser. | beta |
| Marketing Opportunity Score | MA mode computable on 5 of 9 components, D-SNP mode on 6 of 6. Every component shown. | beta |
| Campaign business case | Modelled entirely from assumptions you enter. | beta |
| Marketing strategy brief | Thirteen sections assembled from the data on this site. | beta |
Planned: waiting on a CMS ingest
These are data problems, not design problems. Each names the file it needs.
| Capability | What it would add | Waits on |
|---|---|---|
| Which competitors are bleeding members, contract by contract? | CMS publishes contract-level disenrollment rates annually. Once ingested, voluntary-disenrollment signals feed straight into the carrier battlecards. | planned Planned CMS source: Part C and D contract-level disenrollment file |
| How large is the year-round sellable population here? | LIS and dual SEP-eligible counts by geography, so territory plans work outside AEP. Duals and LIS beneficiaries hold recurring enrollment rights all year. | planned Planned CMS source: LIS enrollee and dual-eligibility counts by geography |
| Who is winning while the AEP window is open? | Month-over-month CPSC enrollment deltas during AEP, showing carrier-level capture as it happens rather than after January reconciliation. | planned Planned CMS source: monthly CPSC enrollment files (in-season deltas) |
| Which carriers are entering and exiting our markets for next year? | Plan entries, exits and service-area changes overlaid on the opportunity ranking, so displacement shows up as a marketing opportunity with a county list attached. | planned Planned CMS source: service-area files and the plan-year contract crosswalk |
| What is the Stars environment where we are about to spend? | Contract-level Star Ratings joined to county, so the quality context component of the opportunity score activates and star claims can be checked locally. | planned Planned CMS source: Part C and D Star Ratings files |
| Who lives in this market, beyond Medicare counts? | Age 65+ population, income and poverty, language and limited-English proxies, broadband access, rural and urban classification, and aggregate disability indicators. County-level aggregates only, for channel and communication planning. | planned Planned public source: Census ACS 5-year county tables |
Planned: platform phase
These need a backend. Nothing on the site pretends otherwise today.
| Capability | What it would add | Waits on |
|---|---|---|
| Cross-device accounts | Workspace data syncing beyond one browser. | planned Platform phase |
| Delivered alerts | Alerts that arrive by email rather than recording intent locally. | planned Platform phase |
| Team workspaces | Shared saved analyses and marketing projects. | planned Platform phase |
| API and data feeds | The same numbers, with provenance, in your own stack. | planned Platform phase |
| Stars optimization workflows | Measure-level improvement value, ranked. | planned Needs contract-level Star Ratings ingest |
| Scenario modeling | What-if on benefit and market assumptions. | planned Platform phase |
| Decision Brief export | A sourced brief as a file, not a page. | planned Platform phase |
Detail on the data dependencies:
methodology. Detail on the platform dependencies is in the
repository at docs/backend-phase-dependencies.md.