Most medical software doesn't fail because of the code. It fails in the gap between the people who build it and the clinicians who use it. Our founder is a medical doctor and a software engineer, so that gap is where we start: before we ask what stack, we ask who the user is and what happens to the patient.
What we build
Software as a Medical Device (SaMD). Software whose output informs treatment decisions, built with the traceability and release discipline that medical products require.
Clinical decision support. Tools that turn patient data into recommendations a clinician can act on and verify.
Hospital workflow tools. Patient flow between departments, capacity and overcrowding decision support, assistant bots for clinical teams.
Patient-facing apps and portals. PWAs that patients actually keep using, because they were designed around a patient's day, not a database schema.
Case: Progalit
A Software-as-a-Medical-Device platform for urology, built with a French health-tech company backed by European funds. Doctors follow each patient's urine pH, fluid intake and diet in real time, while AI adapts the citrate therapy that dissolves kidney stones without surgery.
The project had been through previous development teams without reaching launch. We took over the architecture and brought it to a live product, still in patients' hands today.
Where our healthcare work runs
- France — AI clinical decision support platform
- Germany — assistant bot for doctors in a trauma unit
- Norway — hospital overcrowding decision-support tool
- Ukraine — patient flow system across hospital departments
- Ireland — health & wellness website
Why a doctor-led team matters
We read the clinical logic, not just the ticket. When a requirement says “adjust the dose”, we know which questions a clinician will ask about edge cases, contraindications and what the patient sees.
We design for real clinical environments. Busy wards, shared devices, interrupted workflows, patients with low digital literacy.
We say no to features that put patients at risk, even when they are easy to build.
Regulatory
We are a software engineering team, not a notified body or a regulatory consultancy. What we do is build software so that your regulatory team or consultant has what they need: documented architecture, traceable requirements, versioned and reproducible releases, and a clear record of what changed and why. If you already work with a regulatory consultant, we work alongside them.
How we work with you
End-to-end product build. From discovery and architecture to launch and support.
Dedicated team. A team that works solely on your product, as an extension of your company.
Rescue of stalled projects. If your medical project has stalled with a previous team, we start with an architecture review and a realistic plan before writing new code.
Our senior core team scales with a vetted network of engineers, so the team is sized to your problem, not the other way round.
Taking an idea to a first release instead? See how we build MVPs or the rest of our work.
Let's talk about your product
Tell us what you are building and who it is for. You'll get an honest opinion from a team that has shipped medical software, even if we're not the right fit.
Contact us
