Walk into most practices and the loudest conversation about artificial intelligence is happening in the wrong room. It is pointed at the exam lane. Scribes and imaging reads, aimed at the one part of the visit where a licensed doctor is already the expert. Meanwhile the front desk is underwater, and almost nobody is building for that.
Dr. Rhue has been rebuilding the operations side of her own South Florida practice, and her read on where the help is actually needed is blunt. Not the exam room, where a trained doctor already moves fast and sure and the patient is in good hands. The admin, the unglamorous grind between patients that nobody went to school to do and nobody has time to fix.
Take that seriously and the next dollar a practice spends on automation lands in a very different place.
The front desk is where the day backs up
The exam itself is the part that already works. A doctor lands a refraction and makes a judgment call that took a decade of training to make look easy, and the patient walks out feeling looked after. That is almost never where a practice loses its afternoon.
The afternoon goes somewhere else. It goes to looking up a patient’s insurance across a stack of separate portals and still missing a secondary plan. It goes to fielding call after call at the front desk and printing a routing slip for each one. Then there are the twenty small handoffs that have to line up in the right order before and after the doctor ever walks in. None of that requires a diagnosis. All of it eats the day, one interruption at a time, while the exam that everyone trained for sits finished and fine.
Point a smart tool at the exam lane and you have automated the part that was already working. Point it at the admin and you give the whole office its hours back.
The dashboard problem
Ask a practice owner to list the software running their office and the number climbs fast. Something for reminders. Something for online scheduling. A portal for each vision plan. A separate system for optical orders. Another for contact lenses. One more for payments. Every one of them solved a real problem the day it was purchased.
Together they created a new one. Dr. Rhue calls it a dashboard problem: a wall of tools that do not talk to each other, so a person has to become the integration. Someone on the team is the reason a patient’s insurance and order both end up in the same place, because the systems will not do it themselves. That person is expensive, hard to replace, and one bad week away from a backlog.
When those tools are connected, the math changes. A brand new front desk hire can start working like a veteran, because the system carries the parts that used to live inside one experienced person’s head. A thirty patient day starts to feel like a ten patient day. When they are not connected, every new tool is just one more login, one more place for a task to quietly fall through.
We have written before about the five systems that actually run a practice and the discipline of getting each one working before stacking anything on top. This is the question that comes right after. Once those systems are running, where should the automation actually point?
The patient feels it too
A disconnected stack is not only a staff problem. The patient sits inside it.
They are the ones waiting while someone toggles between windows to find their benefits, or hearing “let me pull that up in another system” twice in one visit. Sometimes their reorder reminder never fires at all, because the reminder tool and the ordering tool were never introduced to each other. Every seam between two systems is a place where the visit gets a little slower and a little less certain, and that is exactly what nudges a patient toward the online option that feels effortless. The stack you cannot see is shaping the visit they can.
Point it where the day leaks
The reason this matters past staff sanity is money. The admin is where revenue leaks without anyone deciding to let it go.
Think about the handoff between the chair and the optical, or the moment a contact lens patient decides whether to reorder with you or take a photo of their prescription and walk. Those are not clinical moments. They are front desk moments, and they are won or lost by whether the next right step is obvious or buried under a pile of open tabs. We broke one of those all the way down in the thirty second script that keeps patients ordering with you. The script only works when the person saying it is not also drowning in six other windows.
This is also why two practices on the identical platform can post completely different numbers. The difference is almost never the tool. It is whether the process around the tool actually runs, which is the whole story behind the $37K office versus the $200 office. The winning office did not have better software. It had software that was connected to a process, so the software got used.
A connected stack, not another dashboard
The goal here is not a smarter dashboard. It is fewer of them.
Dr. Contact Lens is built to be one connected piece of the stack for the contact lens side of a practice, and the integrations keep getting tighter on purpose. Insurance verification is one of the next pieces, open as a beta, aimed straight at getting a team out of the job of hand verifying plans across a row of separate windows. The point of each new connection is the same. Take a task that used to require an expert and a good memory, and make it something a new hire can do correctly in their first week.
That is the quiet test for any tool a practice is weighing. Not whether it is impressive in a demo. Whether, six months in, it removed a login or added one.
Follow the rebuild
Dr. Rhue is doing this rebuild in the open, and she is not the only one watching it closely. Perry Brill visited her practice and came away pointed at the same target: not an exam room gimmick, but the unglamorous admin that actually runs a front desk, the billing and the vision plan math that eat the day. It is worth following along, because the practices that pull ahead over the next few years will not be the ones holding the most software.
They will be the ones whose tools finally talk to each other, so the team can spend its attention on patients instead of portals.
Here is a small audit that costs nothing. Follow one contact lens reorder from the moment the patient calls to the moment it ships, and count how many separate systems and logins it touches. Then count how many of those steps only happen because one specific person remembered to do them. That second number is your real front desk workload, and it is the one worth pointing your next tool at, long before you point anything at the exam room.
