Case study
A US telemedicine service: the patient reaches a doctor over video, and everything else lives around that consultation — scheduling, clinical notes, documents, prescriptions and payment. Hundreds of consultations a day.
The problem
The platform was inherited in an outdated state and rewritten from the ground up without ever going offline: consultations ran every single day while the foundations were being replaced.
A medical consultation is not a video call. Around it sit finding a slot with a doctor of the right specialism, syncing with external calendars, the doctor's notes during the appointment, documents and discharge summaries, prescriptions, follow-up visits, payment and several interface languages. A scheduling error here means the patient and the doctor never met.
What we did
Result
Why this one is us
Both halves of the studio work here: Inga runs product and project, Gennady runs development, architecture and integrations. The full cycle — from framing the problem and the user journeys through to the code that carries a real patient consultation.
The only difference from our own products is that all of it happens inside the client’s large product team. The way of working is the same: the decisions are made by the people who then build and then run them.