About
I move toward ambiguous problems and build what deserves to scale.
Product leadership, hands-on technical work, and domain depth have appeared in different proportions over 14 years: originating Doximity Dialer, leading R&D at CancerCompass, founding Andwise, and since 2024 building the systems myself when that's the fastest way to learn.
- Learning how complex technical systems work
- Turning capabilities into products
- Owning company-level consequences
- Building the underlying machinery directly
Experience
Scope over time
| Stage | Scope | Challenge | Impact |
|---|---|---|---|
| Georgia Tech / NASA 2009–2012 | Technical Research | Modeling RNA folding dynamics and sRNA-mRNA interactions that determine whether gene regulation proceeds or stalls. | First author on a chapter in the ACS Symposium Series on the thermodynamics of sRNA–mRNA interactions and the role of Hfq, presented at FASEB, BMES, and the ACC Meeting of the Minds. |
| Epic 2012–2013 | Clinical Software | Owning what happened to eight client organizations after installation — an at-risk account, a health system going online for the first time, and the federal quality reporting both depended on. | Turned an at-risk account into a reference account, took a health system online with MyChart and EpicCare Link for the first time, co-led CMS PQRS and built its escalation path, and was recruited to internal area leadership four months in. |
| Doximity 2013–2017 | Networked Workflows | Solving the 'unknown caller' bottleneck that kept telehealth calls from being answered. | Authored HIPAA compliance documentation, ran a national ID-verified physician compensation survey, built an ML salary model on the verified data, and led the Doximity Dialer identity layer and its Epic Haiku integration. |
| CancerCompass / CTCA Marketplace 2019–2021 | Patient Navigation Systems | Translating oncology clinical protocols into plain-language steps for the families navigating cancer care. | Directed digital products for an oncology platform, cutting bounce rate and raising chat conversions. |
| Transcarent 2021–2022 | AI-Assisted Decisions | Standing up four specialty-care programs — Surgery, urgent care, Behavioral Health, Oncology — on one shared triage and routing architecture rather than four. | Architected automated triage and role-based routing rules — the system assigned ownership of each case, and nurses and navigators shared the same facts across Surgery, urgent care, Behavioral Health, and Oncology. |
| Andwise 2022–2024 | Automated Review with Sign-Off | Building automated contract analysis and accountable review routing for physician financial guidance. | Raised initial funding and grew a physician user base by shipping automated clause-level contract analysis with escalation-clock review routing. |
| Independent product builds 2024–present | Technical Product Building | Investigating emerging technical possibilities directly in software to discover what product should exist before an organization allocates a team. | Built NextConsensus for biopharma claim shifts, Ambit for agent tool permissions, and Stims as a browser graphics product. Refract and Fast Harm extend change detection and agent error benchmarking. |
The record, in order
RNA Research
My work in complex systems began at Georgia Tech, modeling RNA folding dynamics in Roger Wartell's lab. As an undergraduate, I was first author on an ACS Symposium Series chapter on the thermodynamics of sRNA–mRNA interactions and the role of Hfq. I presented our findings at FASEB, BMES, and the ACC Meeting of the Minds as one of eight students selected institute-wide.
Epic
I had an MD admission in hand and deferred it a year to find out what healthcare technology was like from the inside. I joined Epic in Technical Services, owning what happened to client organizations after their software was installed, and wrote Caché plug-ins where the base product couldn't reach a department's actual workflow. I co-led CMS PQRS and built its escalation path.
- 8 client organizations owned post-install Two on outpatient, six on the patient web portal
- 4 months to internal area leadership Recruited from Technical Services
- 6,000 person company On its smallest team, building the patient-facing portal
| Client | Product | Scale | Outcome |
|---|---|---|---|
| 477-bed health organization | Outpatient (EpicCare) | 477 beds | An outpatient issue list long enough to be a cancellation risk, worked to root cause — 95% resolved — until the account became a reference. |
| 514-bed research hospital | MyChart and EpicCare Link | 514 beds; a 134-year-old health system | Online for the first time in the system's history. |
By the end of that year I was building the patient-facing portal — and I turned the medical school acceptance down.
Doximity Dialer
Before Dialer, I authored Doximity's HIPAA compliance documentation and ran a national physician compensation survey. I directed the data-science team that turned it into a predictive salary model by county and specialty. Verifying that many physicians is what built the identity infrastructure behind Doximity Dialer.
- 35,000+ ID-verified survey respondents National physician compensation survey; the data behind the salary model
- 6 of top 10 U.S. research hospitals On the enterprise marketing platform I built
- 350K NPs and PAs brought onto the platform People who had not been able to join
- 300K+ Dialer calls per average workday Across 250+ hospitals and health systems
As founding product lead, I proved over a weekend that outbound calls could carry an unverified caller ID, and launched on that route deliberately. Our physician identity verification was strong enough to stand behind the number — the physician's own office line, on their own device. I built the compliance framework for hospital IT approval and drove the Epic Haiku integration.
Across four years I built an enterprise marketing platform for research hospitals, founded the search team, and brought nurse practitioners and physician assistants onto the platform. I left as Head of Mobile Products & Growth, running every mobile app and user growth.
Dialer is #1 Telehealth Video Conferencing Platform in the 2026 Best in KLAS Report, its fifth consecutive year.
Trust is a product decision: what a system can prove about itself determines whether anyone acts on it.
NYU Stern
Doximity taught me that a technically sound product still has to clear institutional defenses — the compliance policy, the security review, the procurement process — before it can matter. I took an MBA at NYU Stern to study finance, capital allocation, and organizational power as variables I had been building around without reasoning with directly.
I tested the question on other people's companies before testing it on my own. I evaluated seed-stage healthcare and deep-tech teams for General Catalyst's Rough Draft Ventures, then diligenced seed and Series A deals at a three-person healthcare fund.
The pattern held everywhere I looked: the constraint had moved beyond the product. At Andwise, three years later, I learned the answer with the authority to act on it myself.
CancerCompass
At CancerCompass / CTCA Marketplace, I was the first product and technical hire for a pre-CEO, pre-revenue venture, and stayed through its growth from 2 to 25 people. I led a cross-functional team of 14 across three products — the oncology navigation platform, a hospital digital-marketing platform, and a patient-engagement web app (CTCA was later acquired by City of Hope).
I cut the bounce rate and raised chat conversions, translating clinical protocol into steps a frightened family could act on.
Transcarent
I joined Transcarent as an early product hire and stayed from the first activated member through 200+ employees; the company reached a $1.6B implied valuation over that period. I directed product across four specialty-care and navigation programs (Surgery, everyday urgent care, Behavioral Health, and Oncology Care).
I led the Cancer & Decision Support pod — shipping CancerCare v1, a symptom-checking triage tool that inferred the right care pathway from reported symptoms, and an in-app second-opinion experience with automated handoff to Nurse Ally through Consumer Medical. I replaced manual case-by-case coordination with automated routing rules tied to clinical roles. The system assigned responsibility for each case, and nurses and navigators worked from a shared record during live care.
Andwise
As co-founder and CEO of Andwise, I raised the initial funding, grew the physician user base, and convened a physician medical advisory board. I built the Contract Analyzer — automated clause-level analysis of physician contracts that flagged key terms for review — and review routing with escalation clocks so each analysis reached an accountable reviewer on a deadline.
- $240K initial funding raised
- 1,200+ physician users
- 700 member community
Andwise settled the user question in year one. I did not settle who would pay until year two, and by then every path that could fund growth put someone other than the physician in the customer seat. Who pays is an architectural question, and I had been treating it as a later one.
| Funding path | Customer | Whose interests the product would optimize for | Verdict |
|---|---|---|---|
| Direct physician subscription | The physician | The physician — but CAC exceeded LTV | Aligned incentives, unsustainable unit economics. |
| Hospital or employer benefit | The hospital or employer | The employer's HR reporting, at the cost of physician confidentiality | Revenue possible, core premise destroyed. |
| Advisory or wealth-manager referral | The financial advisor, per referral | Lead generation for advisors; the physician becomes the product | Highest revenue, antithetical to the fiduciary premise. |
| Decision, 2024 | Shut the company down rather than build that company. | ||
The assumption I got wrong wasn't the product — it was believing enough user value would eventually produce a business model that preserved whose interests the company served.
Current Work
I build independently now because it is the fastest way to learn what an idea is worth. The record of shipping through teams is the decade above it: a 14-person cross-functional R&D org at CancerCompass, and Dialer taken from prototype to a Doximity-wide release through its engineering, design, and clinical organizations.
| Project | What it is | Link |
|---|---|---|
| NextConsensus | Tracks when medical evidence moves ahead of institutional guidelines, joining healthcare domain knowledge to full-stack engineering. | /nextconsensus/ |
| Ambit | The control layer: an explicit permissions model that separates what an AI agent can reach from what it is authorized to do. | github.com/zz-plant/ambit |
| Stims | A browser-native MilkDrop visualizer with 1,787 presets, .milk compilation, and WebGL2/WebGPU rendering. | toil.fyi |
| Whether | Turns macro signals into weekly operating decisions backed by an immutable snapshot model. | whether.work |
| Refract | The trace layer beneath the others, maintaining provenance across 16,146 manifest-backed events. | github.com/refract-org/refract |
| Fast Harm, Slow Repair | A draft recovery-evaluation scaffold for what remains wrong after an error leaves the model: how far it travels, and whether the correction reaches everything it touched. | /current-work/#fast-harm-slow-repair |
| The Crumple Zone | Essays on the wider pattern: how institutions distribute their own failures. | thecrumple.zone |
| Ethotechnics | An open framework for AI decision accountability. | ethotechnics.org/about |
- Data Data pipelinesTemporal modelsForecasting infrastructure
- Agents Agent capability and authorization graphs
- Evaluation Evaluation frameworks
- Compilers + rendering CompilersRendering engines
Four of the projects sit on one thread; the current work inventory carries every project's stage and artifacts.
I can now take an unproven technical idea far enough to find out whether it holds, before an organization has to commit a roadmap to it.
How I build
- Agent-driven development
- opencode is the primary development surface, combining skills, MCP servers, and local model routing. This site is built and maintained through it; skills encode the reusable workflows for changes and checks.
- Capability accounting
- Ambit reads this stack and records which capabilities are reached, one dependency away, or decaying, and keeps capability separate from authority. What Ambit is →
- Local model routing
- Classification, extraction, summarization, and log scanning go to local models, because their output can be checked cheaply; reasoning goes to a frontier model. The rule is written down and re-tested: when a local model silently lost tool-calling, the fix was a script that re-verifies each model.
- Behavioral agent evaluation
- Agents are tested on real tasks, not plausible responses. Fast Harm, Slow Repair is a draft recovery-evaluation scaffold.