What we're building next

One JSON request returns the calculated amount, whether the code is payable, and citations down to the CMS file row behind every input. When a payer disputes a number, you can show exactly where it came from and which release it used.

• Historical lookups by year and quarter—ask for Q2 2024, get Q2 2024
• Locality by MAC code or plain ZIP, through the versioned crosswalk
• Gross or sequestration-net with one flag, never baked in
• payable=false always carries a machine-readable reason

Bookmarking codes, tracking localities, and pricing every pair against each other is already free in your Workspace. What's still missing is a view of what each new release did to your revenue across the codes you bill, and a bulk export sized for your whole book instead of a starter cap.

• Revenue impact across quarters for your saved codes
• Bulk export at practice scale, not just a starter cap
• Cross-locality comparison built for negotiation and budgeting

Most practices know their payer contracts as "some percent of Medicare" and can't say which percent, for which codes. Store your multipliers once, and every rate on the site becomes your rate, with underpayments flagged against what you were actually paid.

• Per-payer multipliers applied across every code page
• Upload a remittance, get expected-vs-paid per line
• Payer benchmark data from published MRF files

CMS reshuffles the fee schedule four times a year, and most people find out when payments change. Rate-change alerts already work. The goal is to also flag changes that are harder to notice, like a status change, a new NCCI edit, or an OPPS cap that starts applying.

• Quarterly digests, or watch a single code
• Status changes that affect payment, not just dollar changes
• Specialty-scoped so you only hear about your codes