Case study
Dr Nathalie Le Jeune
Booking, reminders, and session reports, automated
- Healthcare practice
- Practice automation
The brief
Dr Nathalie Le Jeune's practice depended on administrative work that repeats every week: booking appointments, sending reminders, following up with patients, and writing up each session. Every hour spent on that work is an hour not spent with patients.
The brief was administrative, not clinical: take the repeatable parts of the week (appointment booking, reminders, follow-up checks, and the report a patient receives at the end of a session) and make them happen without anyone having to remember them. In the client's words, it gave her back hours every week.
What we delivered
What the client can do now that they couldn't do before.
Automated booking
Appointment booking runs automatically, so the calendar no longer has to be managed by hand.
Reminders that send themselves
Appointment reminders go out on schedule rather than depending on somebody remembering to send them.
Follow-up checks, triggered automatically
The follow-up contacts that are easiest to lose track of between sessions are triggered by the system rather than by memory.
A clear report after every session
Every patient receives a clear written report at the end of each session, generated automatically.
How we build systems like this
In a practice, the goal of automation is to remove the tasks that only exist because someone has to remember them. This is how we approach this type of project in general.
This section describes how we approach this type of project in general. It is not a technical record of what we built for this client.
Map the week before automating
We write down every repeatable task, what triggers it, and what it depends on. We usually start with the three or four tasks that take the most time, and leave the rare ones for later.
Automate the trigger, keep the judgment
A booking, a reminder, a follow-up date, and the end of a session are events a system can detect. Professional judgment is not. We draw that line explicitly and keep a person in control of every decision that needs one.
Reports patients can read
A generated report has to be clear to the person receiving it. We write the template with the practitioner, keep the language plain, and add a review step before sending wherever one is needed.
Tools you can keep and inspect
We build automations with Make or n8n to run the steps, Claude or GPT where a step needs to understand language, and custom code where a workflow is too specific for a standard building block. We tell you which part does what, so nothing is a black box.
Sensitive data and handover
Personal data comes with obligations: access limited to what each person needs, retention rules agreed in writing, and hosting in a region you choose. At handover, you receive documented workflows you can read, change, or hand to someone else.
Tools we use for systems like this
- Make / n8n
- Claude & GPT
- Next.js
- Vercel & Supabase
In the client's words
“Codinou automated my appointment booking, reminders and follow-up checks, and now every patient receives a clear report at the end of each session — automatically. It gave me back hours every week.”
The service behind this work
AI & automation
Automations that take repetitive admin out of your week, scoped in writing before we build. Packages from €1,890.
Free guide
Get the architecture guide
Custom build or platform, what a web app costs to run, and where AI automation pays for itself. We send it to your inbox as a link you can forward.
Start with a written scope
Tell us what is slowing your operation down. You get a fixed price, a written scope, and a reply within one business day.