How it works
Everything she needs, booked the day she finds out.
Nine months of appointments, made in one go, in your calendar, on your protocol.
First trimester
Weeks 1 to 13
- Booking visit
- Dating scan
- First blood panel
- Urine culture
- First trimester screening
Second trimester
Weeks 14 to 27
- Morphology scan
- Second blood panel
- Glucose tolerance test
- Two check-ups
- Antenatal classes
Third trimester
Weeks 28 to 40
- Growth scans
- Monthly, then fortnightly check-ups
- Group B strep swab
- Anaesthetic consultation
- Birth preparation
An example maternity protocol. Yours decides what goes on the list and when.
What actually happens
- 01 / 05
She starts her treatment with you
Her first visit with you sets the plan going, and the plan is built from your own protocol.
- 02 / 05
The whole nine months get booked
Every scan, test, screening, class and check-up goes straight into your booking system in one go. These are real appointments in real slots, not reminders asking her to ring you later.
- 03 / 05
She opens the app every day
A short piece each day about what is happening with the baby that week. It is the reason she opens the app at all, and an app nobody opens is a plan nobody follows.
- 04 / 05
She moves what she cannot make
In the app, in seconds, into another slot you have free. A woman who cannot make Tuesday either moves it with you or goes to whoever can see her this week.
- 05 / 05
The plan changes as the pregnancy does
If something needs watching more closely, appointments get added. If one date moves, everything after it shifts to match.
Why booking beats reminding
A reminder asks her to do something. A booking means it is already done. Everything she is going to need over nine months is in your calendar before she has any reason to look anywhere else, and the only thing left for her to decide is whether Tuesday still works.
And when something needs a closer look
Between appointments she is still telling the app how she feels. If something she reports crosses a line your clinicians have set, her doctor gets a short summary and decides whether to bring her in sooner. The app never makes that call itself, it puts the decision in front of a person.
How a project runs
- Adapt
- We turn your protocol into the plan, with your appointments, your intervals, your content and your language. The system already exists and already runs, so this is shaping something that works, not building from scratch.
- Integrate
- We connect to your booking system so the plan books real slots and does not just ask somebody else to. What she reports goes into her file with you, and anything needing a doctor lands where your doctors already look.
- Adopt
- The part most projects skip, and why most clinic apps quietly die. We design how your staff hands the app to a patient in the room and train them on it, wake up the patient database you already own, run the ads, and keep people opening it.
- Operate
- Safety testing, content updates, clinical reviews, and reporting you can take to your board.
What we answer for
Sign-ups. How many are still opening it after 90 days. How much of the protocol actually gets booked. How many appointments get moved instead of dropped. What each sign-up costs you.
Why it is safe to put your name on
- Emergency first
- A fixed set of rules checks every message for danger signs before the AI is allowed to answer.
- It refuses on purpose
- No diagnosis, no drug doses, no reading lab results, no telling anyone to start or stop treatment. That is built into it, not an instruction it might ignore.
- It shows its sources
- Every health answer links to the medical source it came from, and she can open it.
- Her data
- Never sold, never used to train anything. Consent is explicit and she can withdraw it whenever she wants.