Inside a Bohaus Sprint: An Independent Pharmacy

The situation

The client is an owner-led independent pharmacy. One location, the owner as pharmacist in charge, a second pharmacist on busy days, four or five technicians, and a front counter that also runs a small retail section. Dispensing runs through PioneerRx, PrimeRx or a similar system. A med-sync program keeps a group of regular patients on a single monthly pickup date.

The phones never stop. Patients call to ask whether a refill is ready. Techs call patients to say it is. Med-sync patients get a check-in call before each fill date, by hand, from a list on a clipboard or a spreadsheet. Prescriptions sit in the will-call bin past the return-to-stock window because nobody reached the patient.

The work matters. It is also mostly the same conversation, over and over, done by the people who should be filling and checking.

What the sprint finds

In Discover, we sit at the counter through the morning rush and the late-afternoon pickup wave and watch where the techs' time goes. A large share of it is on the phone, and most of those calls are about status: is it ready, when will it be ready, did the doctor respond.

Then we look at what the pharmacy system already supports. Most modern dispensing platforms include, or integrate with, automated refill reminders, ready-for-pickup texts and voice messages, and med-sync scheduling. In many independents these features are licensed and half configured, or were switched off after a rough first try.

In Diagnose, automated refill and pickup messaging ranks first. It happens every day, it takes hours of tech time, and missed pickups cost the pharmacy in restocked fills and patients who drift to a chain. It is also rules-based: a fill is ready or it is not.

Clinical work does not go on the list. Counseling, interaction questions, prescriber calls and anything that needs a pharmacist's judgment stay with the pharmacists.

What it builds

In Build, we configure messaging inside the existing pharmacy system rather than adding a separate app that would need its own copy of patient data.

Patients who opt in get a refill reminder when a maintenance medication is due, and they can reply to request the refill. When a prescription is filled and bagged, they get a ready-for-pickup message. If it is still in will-call after a set number of days, they get one follow-up, and then a tech gets a task to call.

Med-sync patients get an automated check-in ahead of their sync date asking about medication changes or recent hospital visits. Any reply that is not a simple confirmation goes to a pharmacist queue, never to an automatic response.

Messages say as little as possible. No drug names in texts unless the patient has agreed to it. Patient data stays inside the pharmacy's existing compliant system.

Hand over

In Hand over, the lead tech and one pharmacist learn the configuration in depth: message wording, timing, opt-in rules and the pharmacist queue. The rest of the techs get a short session on what the system now handles and what still comes to them. A playbook covers the edge cases, such as a patient who replies with a question about side effects, and names who owns the system.

The owner gets a dashboard of refill requests by reply, fills waiting in will-call and returns to stock, plus a 30/60/90-day roadmap of what to tackle next.

What changes

The phone quiets down. Techs spend more of the day on the bench and at the counter. Patients stop calling to ask whether something is ready, because they already know. Fewer bags age out of will-call. Med-sync check-ins happen on time without a clipboard.

The pharmacists spend their phone time on the calls that actually need a pharmacist.

What this means for your business

When skilled people spend the day answering the same status question, the first automation is usually the status update itself.

For an independent pharmacy, that is refill and pickup messaging. For a veterinary clinic, vaccine reminders. For an auto repair shop, the message that says the car is ready.

That is a Bohaus Sprint: six weeks, fixed scope, four phases (Discover, Diagnose, Build, Hand over), and one live system inside the tools you already use, with a trained team, a playbook, a dashboard and a 30/60/90-day roadmap.