Work
How we build, shown on a real project.
We only show work we have built. This is the story behind NTEKX Clinic: what we set out to do, who we built it for, how it fits together and the problems we had to solve along the way. Client projects are added once they are cleared for sharing.
Case study · NTEKX Clinic
- Project
- NTEKX Clinic
- Client
- NTEKX, our own product
- Sector
- Healthcare: clinics first, then hospitals
- Apps
- Flutter, for web and mobile
- Backend
- Java
- Used by
- Front desk, doctors, therapists, owners and patients
01 · The brief
Software a busy clinic would actually use.
In many clinics, the front desk, the doctor and the patient each work from a different record. Registration sits in one register, appointments in another, and the doctor's notes on paper. When a clinic opens a second branch, the records split again.
The brief we set ourselves: one system a receptionist can pick up quickly, a doctor can use between patients, and an owner can run across every branch.
02 · Who we designed for
Five people, one record.
A clinic visit passes through several hands. We started by writing down what each of them needs from the software on a normal, busy day.
- Front desk
- Register a walk-in, check who is free and book the right doctor without switching between screens.
- Doctor
- See the patient's history before they sit down, and write notes and the prescription in the same place.
- Therapist
- Record long assessments without losing their place, and compare progress from one session to the next.
- Clinic owner
- See every branch's day, doctors and schedules from one login, without asking each branch for updates.
- Patient
- Know when the next visit is and follow home exercises on their own phone.
03 · How we built it
Four steps, in this order.
- 01
Follow one patient's day
We mapped a visit from walk-in to report, and designed the screens in that order: registration, appointment, consultation, assessment, progress, report.
- 02
Give each patient one ID
Every patient gets one NTEKX ID that works in every branch, so nobody types the same details twice.
- 03
Build the apps and the backend side by side
The screens were built in Flutter and the rules behind them in Java, so each screen was tested against real behaviour, not a mock-up.
- 04
Show it before selling it
We put an interactive demo online with sample data, so a clinic can try the product before it talks to us.
04 · How it fits together
Flutter in front, Java behind, one record underneath.
Flutter
Apps
The clinic's web app and the doctor and patient mobile apps are built with Flutter, so the same screens look and behave the same on a desktop, a tablet or a phone.
Java
Backend
A Java backend holds the clinic's rules: scheduling across branches, patient IDs, who can see what, and the APIs every app talks to.
One source of truth
Patient record
Registration, visits, assessments and reports all add to the same record, so nothing is copied from one place to another.
APIs
Connections
Labs, payments, messaging and India's digital health systems can be connected through the same APIs as the product grows.
05 · Problems we had to solve
The hard parts, and how we handled them.
- One patient, many branches
- Each ID carries a branch code, such as NTEKX-NOI-24023, and stays unique across the whole chain. A patient who visits another branch keeps the same ID and history.
- A consultation on one screen
- Everything a doctor needs during a visit sits together, so they never click through tabs while the patient waits.
- Long assessments
- Detailed clinical assessments are split into short, ordered steps, so a therapist always knows what is done and what is left.
- Reports nobody retypes
- Discharge and progress reports draw on what is already in the record, so the last step of a visit isn't typing it all out again.
06 · Decisions we stand by
The choices that shaped the product.
- AI supports, the doctor decides
- AI summaries help a doctor prepare for a visit. They don't diagnose or prescribe; the doctor makes every clinical decision.
- Sample data in public
- The demo and the video use made-up patients only. No real health data is ever used to show the product.
- India first, built to travel
- Indian clinics come first, so walk-in queues, multi-branch chains and Hindi shaped the design. The same product works for clinics anywhere.
- Concepts are labelled
- Features we are still designing appear in the video as marked concept screens. We never present unfinished work as ready.
Have a project like this?
We work the same way for every business: start from the real day's work, keep one record, build once for every screen and show working software early.