A faster availability experiment pulls against the reliability of the booking path patients already depend on.
The new release path protects product learning while ECS capacity and Mamba isolation protect completed appointments.
Who you’d be doing this for
“I found three therapists who take my insurance, then none had a time I could actually use.”
Radu Dumitru · Therapy-seeking patient
An insured patient using the marketplace to find an in-network therapist with an appointment that fits their schedule.
What is at stake
Patients are leaving booking after finding clinicians whose schedules looked promising in search. You must weigh faster availability experiments against the reliability of live booking traffic.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- product iteration speed vs booking reliability
- self-service access vs platform guardrails
- capacity headroom vs attributable AWS cost
- isolated releases vs shared Mamba dependencies
Why Headway
The marketplace depends on patients turning verified in-network availability into completed outpatient mental health appointments.
Written with these in mind
Not your kind of problem? 75 more at Headway, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.