Healthcare product leader · software builder · Chicago & Remote
After years leading healthcare products, I started building the systems myself.
Over the last two years, I expanded from leading healthcare products to building the systems myself. Today I build healthcare intelligence and agent infrastructure, alongside independent technical software.
Current work
Primary builds: healthcare intelligence, agent permissions, and browser graphics.
- NextConsensus Healthcare intelligence — tracks when medical evidence moves ahead of clinical guidelines, coverage determinations, and regulatory policy. Built on Refract, an open-source change-tracking engine.
- Ambit Agent permissions — lets an autonomous agent discover what it can do without assuming it is allowed to do it, stopping unauthorized actions before execution.
- Stims Browser graphics — 1,787 presets, direct .milk compilation, live WebGL2/WebGPU rendering, and projectM reference testing.
More work Whether Refract Fast Harm, Slow Repair
What I'm brought in for
I was already an experienced product leader before this technical period. Across more than a decade in healthcare technology, I originated Doximity Dialer, led product organizations, deployed hospital systems, and founded Andwise. I knew how to identify opportunities, work with engineers, make prioritization tradeoffs, and take responsibility for company-level outcomes.
What changed after Andwise was becoming technically independent. I have independently designed and implemented data pipelines, temporal models, forecasting infrastructure, agent capability graphs, compilers, and rendering engines. That changes what I can work on: I can now enter before the roadmap exists, build an unproven technical idea far enough to discover whether it is sound, and bring senior judgment to what happens next.
I work best where the product category is still emerging — formulating the technical object that doesn't yet exist, building it far enough to test whether it works, and bringing senior product judgment to what to build next.
The recurring job is working out which layer a problem actually sits in — workflow, permissions, product architecture, implementation, or business model — and turning that into a direction a team can build against. It is rarely the layer the request names.
Selected work
The patient sees the office, not the cell phone
Built the identity layer that let a physician call a patient from their own phone while the patient saw the office number — so the call got answered and the physician's cell number stayed private. Trust had to be a product surface, not a compliance footnote.
Read case study →
Four specialty programs on one routing architecture
Put four specialty-care programs — Surgery, everyday urgent care, Behavioral Health, and Oncology — on one shared system instead of four custom ones, so a nurse and a navigator worked from the same facts and every case had someone whose job it was to own it.
Read case study →
Reading the contract before the physician signed it
Co-founded Andwise and built software that read a physician's employment contract, flagged the clauses worth arguing about, and put a named reviewer on a deadline behind every analysis before the physician acted on it.
Read case study →Outcomes at scale
| 35K+ | physicians surveyed | Doximity — I directed the data-science team that turned the survey into a predictive salary model |
|---|---|---|
| 4 | specialty-care programs launched | Transcarent — Surgery, everyday urgent care, Behavioral Health, Oncology Care |
| 1,200+ | physician users | Andwise — I co-founded it |
| $5M | revenue | Doximity Talent Finder — I grew it 60% YoY |
| 14 | cross-functional team led | CancerCompass — onshore and offshore, across three products |
Organizations I've worked with
Explore
- Decisions Four calls, with the reasoning as I recorded it before the outcome was known.
- Framework Ethotechnics — a proposed framework for making consequential AI claims verifiable and correctable.
- Writing Essays on AI governance, institutional power, and cognitive scarcity.
- Build Practice The agent-driven toolchain this site is built and checked with.
- Research The open questions behind the method, and what would settle them.
Get in touch. I'm looking for senior product, research-product, agent-platform, or founding-product roles where technical independence, operating judgment, and domain depth meet. Also open to NextConsensus pilots and advisory work.