The booking peak needs more ready capacity without paying for idle containers all day.
Fast evening booking protects patient access, while a higher capacity floor increases AWS spend.
Who you’d be doing this for
“I found someone with an opening, then the booking page just kept spinning while I was on my break.”
Grete Holmberg · Therapy-Seeking Patient
An insured patient trying to secure an evening appointment after work.
What is at stake
Evening booking requests are stalling when Mamba tasks take too long to become ready. You have to weigh faster ready capacity against runtime safety and AWS cost.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- booking speed vs. idle AWS spend
- capacity protection vs. hidden runtime regression
- rapid release vs. observable rollback
Why Headway
Mamba carries the booking flow that connects insured patients to in-network outpatient care.
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.