At a private healthcare institution, surgical scheduling, patient data, and resource management were scattered across various tools: shared spreadsheets for bookings, a common calendar for surgery dates, and manual email communication with patients. Administrators and doctors worked in parallel, often using inconsistent data. Statistics could only be compiled manually, a task for which there was rarely any capacity.
With no internal development resources available, the requirement was for a custom-built system. The solution was live and operational within 2 man-months. Below, we detail how and under what conditions this was achieved, and what it means for organizations in a similar position.
The Delivered System: What It Solves and What It Doesn’t
Surgery Reservation is a dedicated internal administration application that manages the clinic’s entire surgical scheduling process on a unified platform. It was designed exclusively for internal use: there is no public interface and no patient-side access.
The system operates with three authorization levels (staff, admin, super admin) and covers the following areas: a weekly scheduling calendar with operating room and staff management, a patient database with Social Security Number (TAJ) based search and document management, automated email communication to patients, and filterable statistics by period, doctor, and surgery type.
This was not a customized off-the-shelf product, nor a migration of an existing system, and it did not involve external system integrations. These circumstances had a direct impact on the delivery time.
The 2 Man-Months: Conditions and Constraints
The 2-man-month delivery time is a real figure, but it is important to understand exactly what made it possible and what would have differed under other circumstances.
Factors contributing to speed: There was a clear decision-maker on the client side, the scope was finalized within the first two weeks, and there was no migration obligation (previous Excel-based data did not need to be imported into the system). The development team worked with AI coding assistents (Cursor), which measurably accelerate well-defined, repetitive development tasks.
What might differ in other projects: If the scope changes significantly during the collaboration, if integration with existing systems is required, or if decision-making on the client side is slower, the timeline increases proportionally. This same project with external system integration or data migration would likely have taken 3–4 person-months, even with AI tools.
The baseline: Using a traditional development approach with the same scope, we would have estimated at least 4 person-months.
Data Management and GDPR in a Healthcare Context
The system handles Social Security Numbers (TAJ), birth data, mother’s names, and other special categories of personal data. For a CIO, this is a non-negotiable issue, so we are outlining exactly how we handled it.
The application runs on a VPS rented in Hungary, ensuring data remains within the country. The system operates on a closed internal network with no external access points. From the Nitrowise side, only the developers working on the project had access, and only for the duration of the project.
Should specific compliance questions arise for a similar project (GDPR, internal IT security audits, data processing agreement templates), these are addressed during the consultation phase.
AI-Assisted Development: What This Actually Means for a C-Level Decision-Maker
In this model, AI tools result in increased delivery speed without compromising the risk profile.
This is significantly different from what is colloquially known as “vibe coding.” In the Nitrowise AI-Powered Delivery Team model, AI tools operate under developer control within an auditable process, featuring high test coverage and automated verification workflows. The client sees progress through bi-weekly demos and has constant visibility into what has been completed. This does not suffer from the “drift” common in many traditional fixed-price projects.
What Was Included and What Was Not
This question is almost always asked at the procurement level, so we are making it explicit.
- Included: Needs assessment and scope refinement, UX/UI design, backend and frontend development, database architecture, automated email integration, testing, documentation, deployment, bi-weekly demos, and daily standups during the collaboration.
- Not included: Infrastructure operations, data migration from previous systems, integrations with third-party systems, post-launch support (subject to a separate agreement).
Changes Since Going Live
While precise metrics are not available, client feedback indicates noticeable changes in two areas:
- Reduced Errors: Prior to automated email dispatch, it was a recurring issue that certain patients did not receive necessary notifications or consent forms. These errors have practically been eliminated by the automated process.
- Efficiency: For administration, drafting, copying from templates, and retrieving emails took approximately 30 minutes of work per patient. This time has now been reclaimed.
When Is It Worth Discussing This?
If your organization has a process currently coordinated via spreadsheets, email, or several independent tools, and digitalizing or replacing it is on the agenda, it is worth estimating the actual development capacity required.
If you need software that was previously only achievable through the complex customization of “boxed” software. If the launch date of your own software and/or product is critical and requires accelerated development.
Through a 30-minute consultation, we can provide a more accurate picture—not with a presentation, but with specific questions regarding scope, deadlines, and expected results.
Contact us: genai@nitrowise.com | nitrowise.com
