
The bottleneck was never typing
Every nearshoring provider is talking about AI. Here is what we actually point it at — requirements, test coverage and code review — and why that is a deliberate choice rather than a modest one.


Healthcare facilities typically run separate systems for scheduling, member management, billing, and documentation — with the media breaks, data loss, and double entry that implies. With Proleos⁺, a modular platform was built that unifies these processes: practice management, rehab management, member management, billing and POS, scheduling, and digital anamnesis (eVA), each activatable as an independent module.
The existing physiotherapy system had grown over many years on an aging technical foundation: workarounds instead of clear processes, features reachable only through extra steps, and increasingly difficult evolution. It had to be fundamentally rebuilt — while daily practice operations continued uninterrupted. Rehab sport, by contrast, was greenfield: built cloud-native from scratch, usable standalone or integrated. A deep partnership integration connected the studio/fitness domain. Requirements shifted continuously — the largest customer’s expectations, then rehab modules, then fitness integrations.

A technically obsolete system was progressively replaced by a modern web platform; rehab sport was launched cloud-native and integrated; the studio domain was deeply connected. The modular structure lets facilities activate exactly the functions they need — self-pay services in physiotherapy, for instance, are now switched on as an app instead of requiring system changes. The platform is a stable, scalable base for new business models.

Frontend: a modern Angular 14 single-page application with NgRx state management and PrimeNG components — component-based, modular, layered, with a strong focus on self-explanatory UX for fast onboarding.
Backend: a deliberate middle path between monolith and microservices — a modular monolith in PHP 8.2 / Laravel Lumen with a service-layer architecture, domain-organized code (Physio, Rehasport), dedicated service classes for business logic, and cron-driven background jobs automating processes like invoicing.
dotWhite’s team held the coordinating role between business and development: structuring user stories, managing the Kanban board, coordinating testing and feedback loops, combining remote collaboration with on-site alignment in Germany.

Pure Kanban is ideal for volatile early phases, but as complexity grows, a hybrid of Kanban and sprint structure reduces context switching and restores predictability. And modernize legacy systems step by step — never big-bang.


Every nearshoring provider is talking about AI. Here is what we actually point it at — requirements, test coverage and code review — and why that is a deliberate choice rather than a modest one.

We've moved into a house in the middle of Cluj-Napoca — 35+ desks, rooms to think in and rooms to argue in, and a garden that has already seen its first barbecue.
So what's next?
interested in exploring potential business opportunities with dotWhite? Use the button below to send us a message.
Or better yet, book a meeting with us in Calendly.