Omada Health
Each of these is a real decision Omada Health is working through, written so you can make the call yourself — incomplete information, someone who pushes back, no answer key.
Omada Health is a virtual-care provider for chronic and cardiometabolic conditions that delivers care between in-person visits through care teams, health coaching, connected devices, and clinical monitoring. It provides virtual-first care for weight health, diabetes, hypertension, and musculoskeletal issues. It sells condition-specific programs to employers, health plans, health systems, and pharmacy benefit channels for their members, and also offers selected cash-pay medication-related care. Its engineering teams use Ruby on Rails, Python (Flask, FastAPI), React, native iOS (Swift, SwiftUI), native Android (Kotlin), PostgreSQL, GraphQL, AWS (RDS, SQS), Docker, Kubernetes, GitLab, Datadog and PagerDuty.
Your first one is free. No card.
8 live right now.
The rest
Win broker introductions while employers cut their vendor lists
Employers want GLP-1 support but are consolidating chronic-condition vendors. You must weigh a focused broker package against the proof and flexibility buyers need.
Close the GLP-1 contract within 18 days without uncapped downside
A 180,000-life employer deal is splitting over access, fee risk, and proof of outcomes. You must weigh contract certainty against the member reach that makes the program commercially meaningful.
Close an outcomes deal while the employer questions the evidence
A 45,000-life employer deal is stalled over an outcomes measure the committee can independently verify. You must weigh a stronger guarantee against terms Finance can support and Legal can defend.
Build a packet of incident evidence in 10 minutes without naming cause
On-call engineers must reconstruct member-facing incidents across PagerDuty, Datadog, and GitLab before deciding what to do. You must weigh faster context against evidence that is safe and reliable enough to guide production judgment.
Ship context for member readings without changing escalation rules
Care teams see readings without the member context that explains them. You must weigh member clarity against preserving clinical judgment and a safe first release.
Recover blood-pressure alerts before routine outreach masks them
Some concerning blood-pressure readings reached a general queue instead of clinical escalation. You must weigh rapid recovery against duplicate outreach and corrupted member histories.
Make enrollment stick before members open an empty app
Eligible members are completing enrollment but sometimes open the app without their assigned program. You have to weigh a quick message-handling change against protection for existing care assignments.