About LabCaseBook
It started in a dentist's chair
I was getting a routine filling. My dentist looked at it, said the tooth needed more protection, and suggested a crown. Fine — I agreed.
He picked up the scanner, took an impression, and then did something that stopped me mid-sentence: he opened WhatsApp and sent the scan file straight to the lab.
I sat there thinking — it's 2026. A clinic is sending a patient's case file, the thing a lab technician needs to get a restoration exactly right, through a consumer chat app. No case history. No structured file. No way to track what was sent, when, or whether the lab even confirmed receipt. Just a WhatsApp thread, the same place people send memes and voice notes.
It got worse. On my next visit, the crown came back the wrong color. The visit after that, the fit was off — the dimensions weren't right, most likely because WhatsApp compresses whatever you send through it, silently degrading a file that needs to be precise to the millimeter.
Two appointments. Two avoidable mistakes. Not because the lab technician wasn't skilled — but because the system they were forced to work in was never built for this job.
The real problem
That chair is where LabCaseBook started, but the pattern was bigger than my one crown. Clinics and labs across Egypt run their entire working relationship — case files, shade instructions, revisions, approvals, invoices — through WhatsApp threads. It's not a workflow, it's chaos that everyone's just learned to tolerate. Files get compressed. Instructions get buried in chat history. Nobody has a clean record of what was actually asked for. And when something goes wrong, there's no case file to point to — just a scroll back through messages, hoping you remember which one had the shade guide.
I kept asking myself: how is there no dedicated system connecting clinics and labs? Not a chat app repurposed for medical files — an actual tool built for this specific relationship.
There wasn't one. So I built it.
Why I was the one to build it
I run Axidv, a studio that looks for exactly this kind of gap — a real, painful, everyday problem that businesses have quietly worked around instead of fixed. We diagnose bottlenecks and build the minimum system needed to solve them properly. No unnecessary features, no hype, just something that actually works better than what people are duct-taping together today.
LabCaseBook is that same philosophy applied to my own case file. A platform where clinics send cases to their labs with full fidelity — no compression, no lost instructions, no shade guide buried in a chat thread three weeks old. Every case has a home. Every revision has a record. Every clinic and every lab can finally see the same information, in the same place, at the same time.
What we're building toward
LabCaseBook starts in Egypt, with the clinics and labs living this exact problem every day, and it's built to grow across the wider region. The goal isn't to add another app to someone's phone — it's to replace the one workaround that every clinic-lab relationship has settled for, with something that was actually designed for the job.
It started with a crown that came back the wrong color. It's becoming the system that makes sure that never has to happen again.