CEO question
What system did this work make more launchable, fundable, or scalable?
Case study / Operating architecture
Medicaid Nutrition Activation OS
A Medicaid growth thesis became a governed operating model spanning provider activation, MCO value, unit economics, contracting, data controls, and executive decision support.
Return to verified workFood-as-medicine strategy translated into an executable operating system
Evidence register
What this case can support.
- Evidence class
- Operating architecture
- Claim boundary
- This is an advisory and product-architecture build. It does not claim a live payer contract, deployed client product, booked revenue, or realized clinical outcome.
- Source basis
- Public-data ingestion and local application build
- Provider and MCO orchestration workbooks
- Contracting, governance, and 90/180-day operating design
Case architecture
Ecosystem thesis
Food-as-medicine growth is not a partnership list. It is a payment and delivery system where eligibility, provider trust, MCO economics, community networks, clinical scope, privacy, contracting, fulfillment, and proof have to align before a pilot is credible.
System path
- 01Policy signal
- 02Activation network
- 03Contractable model
- 04Governed pilot
- 05Proof loop
Executive decision brief
Operating answer
A healthcare market becomes investable when policy, buyer economics, distribution, implementation, governance, and proof are designed as one operating system.
Proof to inspect
The evidence is architectural and technical: a working local system, a governed provider universe, contract and risk artifacts, and an execution cadence. It should not be read as a deployed client outcome.
Ecosystem context
The outcome only makes sense inside the system around it.
Medicaid nutrition programs sit across fragmented authority: state policy, managed-care plans, social-care networks, provider referral pathways, community organizations, clinical qualification, and vendor operations. A promising market map can still fail if eligibility, contracting, fulfillment, data exchange, or evidence ownership remains ambiguous.
The build converted that fragmentation into an operating system: public-data loaders, workbook ingestion, decision marts, executive dashboards, provider and MCO segmentation, unit economics, contracting gates, risk controls, and a staged activation plan.
The proof is the completeness and operability of the architecture. Every market claim has a source lane; every target has a role; every pilot has legal, privacy, clinical, finance, and operating gates before it can move.
Outcome record
The proof signals attached to the case.
Provider master
A governed provider and partner decision universe.
Operating layer
Data ingestion, marts, endpoints, and executive dashboards.
Data boundary
Restricted-file and evidence-lineage controls built into the system.
Execution horizon
Staged contracting, activation, KPI, and risk cadence.
Interoperability map
How the layers connect.
The case is designed as an operating ecosystem: signal, economics, workflow, proof, and expansion are connected rather than treated as separate workstreams.
Market Authority
Where is the reimbursable opening real?Policy, waiver, managed-care, and social-care signals were separated from assumptions and mapped to buyer pathways.
Activation Network
Who can identify, refer, and support eligible members?Provider, MCO, community, and strategic partner roles were organized into a governed activation map.
Commercial System
Can the model be contracted and operated?Unit economics, SOW and BAA gates, operating ownership, workflow, and KPI cadence were designed together.
Proof and Control
What can leadership safely claim and scale?No-PHI controls, source lineage, risk registers, and executive readouts separated verified facts from modeled opportunity.
Operating record
The work, the sequence, and the strategic read.
The record separates the conditions, operating moves, interpretation, and repeatable lessons so the result can be evaluated without flattening the work into a headline.
Challenge
Turn a broad Medicaid and food-as-medicine opportunity into a focused, contractable activation model without confusing market potential with implemented outcomes.
Approach
Built a local decision system connecting public data, provider and MCO segmentation, operating marts, dashboards, unit economics, contracting artifacts, risk gates, and 90/180-day execution.
Founder takeaway
A healthcare market becomes investable when policy, buyer economics, distribution, implementation, governance, and proof are designed as one operating system.
Strategic read
The case demonstrates how Azis moves beyond a deck: market research becomes structured data, structured data becomes decision infrastructure, and decision infrastructure becomes a governed pilot path.
Proof interpretation
The evidence is architectural and technical: a working local system, a governed provider universe, contract and risk artifacts, and an execution cadence. It should not be read as a deployed client outcome.
Operator moves
- Structured a 2,306-row provider and partner master into decision lanes rather than a flat target list.
- Connected public-data ingestion and workbook logic to DuckDB marts, FastAPI endpoints, and executive Next.js dashboards.
- Separated confirmed evidence, modeled economics, and validation-required assumptions.
- Designed SOW, BAA, privacy, clinical, finance, and operating gates before market activation.
- Created KPI, risk, and 90/180-day governance so a pilot could move from thesis to accountable execution.
Expansion path
- 01
Validate one state, payer lane, and provider-led proof market.
- 02
Lock the legal, privacy, clinical, and financial claim boundaries.
- 03
Activate a narrow provider and community referral corridor.
- 04
Measure eligibility, referral completion, fulfillment, retention, and buyer value.
- 05
Expand only after operating evidence supports the next contract lane.
What I would do again
- Start with contractability and claim boundaries before partner outreach.
- Keep modeled value visibly separate from booked or realized value.
- Treat provider activation, data governance, and fulfillment as one workflow.
What this proves
Azis can translate Medicaid policy and food-as-medicine complexity into a productized, governed growth system leadership can inspect and operate.
Start a serious conversation
Build the wedge. Prove the motion. Scale what repeats.
For Series A/B teams that need sales, partnerships, implementation, payer logic, and revenue intelligence to become one operating system.