Challenge
Medicaid covers more than 80 million Americans and approaches roughly $1 trillion in annual program spend — the largest government-funded healthcare program in the United States — yet there is no single source of truth for how providers are paid. Every state publishes fee schedules differently: Excel workbooks, PDF bulletins, provider manuals, and ad-hoc portals, each with its own coding conventions and effective-date rules.
Strategy teams need answers in days, not weeks: reimbursement accuracy, cross-state benchmarks, expansion economics, and the trajectory of rates over time. Without a dedicated platform, analysts manually chase documents across all jurisdictions — and often learn about material changes too late.
“Before MediRate, our team manually scoured state websites for fee schedules, regulatory changes, and legislation — inconsistent formats, hard-to-find data, and late notice of rate changes. MediRate consolidates state-by-state schedules, historical and real-time data for trends, and regulatory context for market entry.”
— Senior VP of Payor Development, multi-state ABA provider
Solution
Metasys partnered with MediRate to design and ship a full-stack platform: public marketing and SEO, subscriber SaaS, Stripe billing, and an internal operations suite for curators and campaigns.
Today MediRate is positioned as the dedicated Medicaid fee-schedule intelligence layer — searchable by state, service line, billing code, program, and date, with comparison analytics, historical views, exports, and policy monitoring nationwide.
Executive summary
MediRate helps providers, consultants, and policy analysts answer Medicaid payment questions without hand-maintaining spreadsheets for fifty-plus fee schedules.
The product combines master rate data, provider alerts, state plan amendments, and legislative tracking in one searchable, exportable surface — with billing, team seats, and an internal admin layer for ongoing operations.
Data foundation
Before the polished SaaS experience, the platform’s data foundation was built with custom automation: Selenium-based scripts systematically traversed state Medicaid portals and related sources, extracting rate schedules from heterogeneous files — Excel workbooks, PDF bulletins, and agency downloads — and normalizing them into a single growing dataset.
That pipeline was the fastest honest path to national coverage: repeatable runs across jurisdictions, with human review where sources were ambiguous. As MediRate’s operations team matured and stayed ahead of changes day to day, day-to-day curation shifted toward a streamlined manual workflow — editorial control over what ships, without abandoning the unified model the automation era proved out.
One model, fifty-one jurisdictions
Designing one schema for fifty-one jurisdictions is the hard part behind the demos. States disagree on how CPT/HCPCS codes are grouped, how modifiers stack, how effective dates are expressed, and what “program” means locally. The platform has to represent that nuance without flattening it into misleading averages — while still letting analysts filter, compare, and export at speed.
Questions MediRate answers
The platform was designed around the strategic questions teams ask every day:
01Are we being reimbursed accurately for the services we offer and populations we serve?
02How do payment rates in our market compare to other geographies and programs — and is there room to advocate for higher amounts?
03How do managed care payment rates compare to fee-for-service reimbursement?
04Can we design value-based contracting models with managed care payers to drive improved outcomes?
05Are there other service lines we can offer to broaden treatment options?
06Which expansion markets may be attractive organically or through acquisitions?
07How frequently are rates adjusted, and what is the historical trend?
08When considering acquisitions, how do we assess reimbursement stability and growth opportunity?
Challenge → platform response
| Challenge | Platform response |
|---|
| Rates vary by state, program, code, modifier, and effective date | One master model with advanced filtering, cross-state comparison, and governed exports |
| Administrative and legislative changes are easy to miss | Rate Developments (alerts, bills, SPAs) plus subscriber email preferences matched by geography and line of business |
| Analysts need defensible snapshots, not only “current” screens | Rate history visualizations and multi-date “as of” Excel workbooks for audit-ready comparisons |
| Enterprises need seats, roles, and export discipline | Primary vs sub-user vs subscription manager, with per-plan Excel row quotas and template save/load |
| Operators must refresh authoritative sources on a schedule | Admin sync from structured source files, change logs, and tooling that reflects what actually shipped to subscribers |
Subscriber product
Dashboard & rate lookup
Cascading filters (service line, state, code, program, region, modifiers, dates), saved templates, code-definition reference, and pagination tuned for very large states.
State rate comparison
All-state or single-state comparison views with sortable analytics and export under plan limits.
Rate history
Time-series views of reimbursement movement with controls tuned for how analysts read Medicaid tables.
Rates in Effect As Of & multi-date export
Reconstruct point-in-time reimbursement: pick snapshot date(s), deduplicate to the active row per key, and land a wide workbook for year-over-year or acquisition-era review — the kind of feature that signals serious product thinking, not just a CSV dump.
Recent rate changes
Operational view of material movements in master data — old vs new, percent change, effective dating — for teams tracking volatility.
Data Export Center
Rate data and policy-export paths with column picker, templates, and tier-aware monthly row budgets.
Subscription & teams
Embedded checkout, portal management, optional alternate payment path, and seat administration aligned to how buyers actually procure.
Admin & operations
Ingestion & source-of-truth syncAlert operationsGrowth & digest toolingGovernance & quality
Who MediRate serves & what we track
Behavioral health providersABA & early interventionHCBS & personal careIDD servicesSubstance use disorderManaged care organizationsHealthcare consulting firmsInvestment & financial servicesTrade associationsHealthcare law firms
Applied Behavior Analysis (ABA)Early interventionHome & community-based servicesBehavioral healthSubstance use disorderIntellectual & developmental disabilitiesHome health & private duty nursingPersonal care
Technology & architecture
Visitors and subscribers hit a single Next.js application: marketing routes for acquisition and SEO, authenticated routes for the product, and API routes on the same serverless deployment for auth checks, billing webhooks, exports, and internal tools.
PostgreSQL (via Supabase) holds master reimbursement rows, subscription linkage, and operational metadata; object storage holds large source files and document-library assets. The browser loads heavily precomputed filter bundles so national dashboards stay responsive without round-tripping impossible payloads.
Next.jsReactTypeScriptSupabasePostgreSQLPrismaStripeTailwind CSSApache EChartsExcelJSAzure BlobPlaywrightServerless hosting
Key product decisions
- Stay on one codebase for marketing and product — fewer integration seams for SEO, auth handoffs, and brand consistency.
- Push pre-aggregation and compression to the edge of the browser where national filter cardinality would otherwise choke latency.
- Model subscriptions, seats, and export quotas in the data layer so monetization rules stay enforceable — not a spreadsheet the team hopes people follow.
- Prefer managed Postgres and storage over bespoke clusters until throughput demands it — operational focus stays on the Medicaid domain, not racking servers.
Performance & engineering
Compressed filter delivery
Filter metadata ships in a gzip bundle orders of magnitude smaller than raw JSON — meaning faster first meaningful paint on data-heavy dashboards.
Vector-quality charting
Comparison and history charts render crisply at any zoom — important when executives screenshot slides from the product.
Pagination that respects reality
Largest states don’t collapse the UI: APIs page through result sets instead of pretending every jurisdiction fits in memory.
Snapshot exports without shipping all history
“As of” reconstruction runs over the minimum data needed so analysts get defensible workbooks without downloading the entire longitudinal warehouse.
Platform capabilities
National master data
A single schema holds fee-for-service payment data across 51 jurisdictions — codes, modifiers, programs, regions, and effective dates — with filters and exports tuned for analyst workflows.
Point-in-time & multi-snapshot exports
“Rates in Effect As Of” and multi-date Excel exports reconstruct which rate applied on each snapshot date without forcing users to download full history — a non-trivial product and data problem at this scale.
Reliable alert pipeline
Subscriber preferences match state and service-line dimensions; operational tooling sends preview-identical HTML, deduplicates newly ingested items, and tracks delivery — treating alerts as a data pipeline, not a one-off mail merge.
Enterprise access model
Primary users, sub-users, and subscription managers with export quotas tied to plan tier — so teams scale seats and Excel volume without losing control.
Documents & state resources
A hierarchical library (billing manuals, service-line folders) on cloud storage, with full admin tooling for moves, archives, and state-level links.
Operations & growth tooling
Excel-driven ingestion sync, legislative change logging, marketing digest workflow, and usage analytics so the operator team can run the product day to day.
Tech at a glance
Next.jsReactTypeScriptSupabasePostgreSQLPrismaStripeTailwind CSSApache EChartsAzure BlobPlaywrightServerless deployment
Impact
- A national reimbursement dataset bootstrapped through systematic browser automation across state portals, then transitioned to a curator-owned workflow as operations matured — without throwing away the unified schema.
- Subscribers move from weeks of fragmented manual research to minutes of filtered search, comparison, and governed export.
- Policy and rate-change signals (bulletins, SPAs, legislation) reach the right inbox through a preference-matched, production alert pipeline.
MediRate is an enterprise-grade example of how we pair data engineering, product judgment, and full-stack delivery for regulated, high-stakes domains — the kind of build consulting buyers hire for when “digital product” means data truth, not just a landing page.