Back to projects
Case study/2026

Sygraft.

Multi-tenant SaaS for hair transplant clinics: the full surgical record, usable inside the operating room and independent of the network.

Year
2026
Industry
Healthcare (hair restoration)
Scope
Multi-tenant SaaS product (web app + API + database)
Timeline
~5 months of continuous development, actively evolving
Status
In production
In production
Sygraft
(Capabilities)

Offline-first

Operates with no connection inside the OR

Multi-tenant

Data isolation per clinic

Installable PWA

Built for tablet use

(01)

The client.

A hair transplant clinic that kept its surgical record on paper and spreadsheets. Every surgery ended up scattered across printed forms and loose files: no single source of truth, and no clean way to reconstruct afterwards what had happened in the operating room. They needed a system of their own, modeled on their actual procedure rather than on the generic flow of an off-the-shelf medical management tool.

(02)

The challenge.

The system had to work where no management app works well: inside the operating room. Connectivity drops there, the team works on a tablet while operating, and nobody is going to stop a surgery because a screen says "network error".

On top of that, two requirements that allow no shortcuts: this is patient medical data, with several clinics living in the same system, and the procedure itself —follicle-by-follicle counting, FUE and FUT techniques, anatomical donor area planning— is not covered by any generic tool. It had to be modeled from scratch, alongside the medical team.

(03)

The solution.

We built a platform that covers the surgical record end to end —patient file, diagnosis, planning and graft counting— with an interface meant to be used during surgery, not filled in from memory the next day. Each clinic works with its own data isolated from the rest, across five user roles and three languages.

It works without internet. If the connection drops, the team keeps working exactly the same and the app stores everything on the tablet; when the network returns, the information syncs on its own and in the right order, without duplicating or overwriting records. Installed as a PWA, it opens even with no signal, with the day's data already available.

Since this is medical data, each clinic sees only its own, passwords are stored encrypted, and the session closes by itself on inactivity or when the user changes, wiping whatever was left on the device: critical on tablets shared across the clinic.

The hardest part, though, wasn't the system itself: it was translating the procedure into software. Graft-by-graft counting, donor area planning over interactive anatomical drawings, and the controls that keep data already recorded from being corrupted later on. Even the numeric keypad is custom, because the system one covers the screen exactly when the operator needs to see what they are counting.

(04)

Tech stack.

ReactTypeScriptTailwind CSSNode.jsExpressPostgreSQLPWA
(Next step)

Want results like these for your business?