Designed with pharmacists, tested at the counter.
A pharmacist runs operations and regulatory matters, and a committee of customer pharmacy owners tries every feature before its release.
His point of viewCarlos Benejam Molero
CEO, co-founder of Nexum Technologies
Her point of viewLaetitia Elkaim
Pharmacist, head of pharmacy operations
His point of viewImri Balourd
CTO, co-founder — engineering and artificial intelligence
The committee is being formed: its pharmacy owner members will be presented here with their agreement.
How pharmacists oversee what we build.
The method hasn't changed: start from a real problem at the counter, then plug in the assistant that removes it — never the other way round.

- 01The problem comes from the counterEvery feature starts from a friction observed in a pharmacy — a call that interrupts a dispensing, a stock-out, a prescription to re-enter.
- 02The pharmacist reviews every journeyDispensing remains in the hands of the pharmacy owner. What is automated is data entry — never the decision. The doubt is raised with the pharmacist, not silently absorbed.
- 03The committee tests before releaseCustomer pharmacy owners try every feature at their counter before it is delivered to everyone. The committee brings together eight pharmacy owners.
- 04What ships is dated, with its statusNew features are published every month: available, rolling out, coming soon. Nothing is presented as delivered before it is.
“This innovation has a direct organisational impact: it reduces task interruptions, lowers the mental load on teams and improves the quality of service to customers.”
Test before everyone else.
Are you a pharmacy owner? Join the committee: try features before release and shape what we build.
A committee of eight pharmacy owners