Work09 / Executive mandate

Healthcare founders and operators who need a decision product, workflow application, portal, dashboard, or internal operating system built close to the business problem

Healthcare Product and Application Development

Healthcare product strategy, UX, full-stack application development, data products, APIs, dashboards, integrations, QA, and operating handoff built around real payer, provider, and revenue workflows.

Read the operating brief

The buyer problem

The issue underneath the visible activity.

This is the problem leadership must make legible before adding more pipeline, tooling, headcount, or implementation burden.

The business logic is scattered across spreadsheets, decks, CRM exports, policy documents, and operator intuition. The team needs a product architecture that preserves evidence, makes decisions visible, and can actually be adopted.

What gets built

A working management system, not a recommendation left in a deck.

The scope is organized around the artifacts, operating rules, and decision cadence the team needs to keep using after the engagement.

  1. 01

    Product thesis, user and buyer journeys, information architecture, workflow states, decision rights, and success measures.

  2. 02

    Executive dashboards, market-intelligence tools, provider or partner portals, account-priority systems, and operating control planes.

  3. 03

    Full-stack web applications with typed data models, APIs, ingestion workflows, permissions, QA, and deploy-ready architecture.

  4. 04

    CRM, EHR, claims, public-data, workbook, and operating-system integration patterns with explicit privacy boundaries.

  5. 05

    Launch instrumentation, training, governance, documentation, and handoff so the product becomes an operating habit.

Proof patterns

What leadership should be able to observe.

  1. 01

    A Medicaid activation operating system spanning public data, decision marts, APIs, executive dashboards, and no-PHI controls.

  2. 02

    A specialty-infusion growth-intelligence product spanning thousands of accounts, geographic opportunity, field sequencing, CRM motion, and clean QA.

  3. 03

    Healthcare RevOps and integration architectures connecting marketing, CRM, capacity, clinical-system boundaries, attribution, and executive visibility.

Decision questions

What the executive room must answer.

  1. 01

    What operating decision should become easier, faster, or more defensible?

  2. 02

    Which data sources are authoritative, restricted, incomplete, or modeled?

  3. 03

    Which user must act differently on Monday morning?

  4. 04

    What is the smallest working product that can prove the operating thesis?

Trust boundary

What this mandate will not pretend away.

Related proof

These records are contextual proof paths, not blanket client-outcome claims. Evidence class and claim boundary are shown from the public case record where available.

01

Operating architecture

Medicaid Nutrition Activation OS

Food-as-medicine strategy translated into an executable operating system
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.

02

Operating architecture

Specialty Infusion Market Intelligence

A market-entry thesis converted into a field-ready growth intelligence product
Claim boundary

This is a market-intelligence and application build. Account counts and QA results describe the built system, not client adoption, booked pipeline, or realized infusion revenue.

03

Employer outcome

Databricks Claims Forensics / Referral Leakage

Claims signal -> account strategy
Claim boundary

Aggregate results are reported in the September 12, 2026 executive resume. The $125.9M leakage figure is a modeled opportunity and $22M downstream LTV is an estimate, not realized or booked revenue. Account-level and patient-level records remain private.

Connected context

Related mandateHealthcare AI Implementation and Revenue IntegrityRelated mandateHealthcare AI Consulting and Implementation

Start a serious conversation

Make the buyer problem clear enough to build, prove, and fund.

Discuss an operating mandate