PratiConnect is the first all-in-one practice OS built for the 27 wellness specialties Doctolib dropped in 2022. Where others force practitioners to juggle 5 disconnected tools, we unify booking, teleconsultation, patient records, and invoicing in one HDS-compliant platform. Our edge: native Factur-X e-invoicing (mandatory in 2026) turns a regulatory burden into your reason to switch, and a single sovereign AI layer powers notes, OCR, and scheduling. Compliance by design, not bolted on.
No reviews yetBe the first to leave a review for PratiConnect
Maker
📌
What inspired me to build this?
In 2022, Doctolib quietly pushed 27 wellness specialties off its platform — osteopaths, sophrologists, naturopaths, self-employed psychologists, and others. Overnight, roughly 120,000 practitioners in France lost access to serious tooling. They didn't stop working; they just went back to juggling spreadsheets, SMS, and PDFs. What struck me is that these people run real practices and handle real health data, yet every vendor treated them as second-class: too "medical" for generic SaaS, not "medical enough" for health-tech. The trigger was personal: my sister, an osteopath, kept searching for a single complete tool to manage her patient base — and there simply wasn't one. Watching her stitch together half-solutions that none of them fit made the gap impossible to ignore. That's what I decided to close.
What problem was I trying to solve?
A wellness practitioner today stitches together four or five disconnected tools — booking, video consultation, patient notes, invoicing, payments — and not one of them is HDS-compliant or built for their reality. On top of that, France's 2026 e-invoicing reform (Factur-X) is about to make their current invoicing non-compliant by default. So the problem is twofold: give this ignored segment a single, regulated practice OS instead of a patchwork, and turn an incoming regulatory burden into the reason they switch. Compliance isn't a feature we added — it's the wedge.
How did my approach or process evolve while working on this launch?
Three shifts mattered. First, I stopped chasing feature-parity with Doctolib and committed to one opinionated offer — no choice paradox, faster time-to-value. Second, compliance moved from "something we'd bolt on later" to the foundation: HDS and RGPD by design from day zero, because retrofitting regulation is how products die. Third, I unified the entire AI layer on a single provider (Mistral) instead of stitching vendors together — simpler, sovereign, cheaper to run. The launch deck itself evolved the same way: from a feature list into a tight narrative — market gap, regulatory timing, unit economics.