There are very few pieces of software I use every day without thinking about them. Waze is one. When I pull out of my driveway, I'm confident Waze knows something I don't. Somewhere ahead, another driver has already hit the accident or construction zone I'm about to run into and my route has already adjusted. The value isn't the map. It's that every trip makes the experience better for the next driver. That's a fundamentally different way to think about software. Enterprise applications used to be judged on efficiency: Can they automate a workflow? Reduce manual effort? Those still matter, but they're no longer the only questions worth asking. The better question: Does this software help me make better decisions based on what it has learned across its entire customer base? Every revenue cycle team develops hard-earned expertise, recognizing subtle shifts in payer behavior, refining documentation, adjusting workflows. Yet that expertise is remarkably isolated. Two organizations can hit nearly identical reimbursement challenges months apart and solve them independently, because their systems were never designed to benefit from what was already learned elsewhere. We lived a version of this at Aptarro before we had language for it. Solving one customer's challenge didn't just improve one implementation or one customers rule set, it improved the reimbursement logic and the global rules that are at the core of our product and behind every implementation we deliver. We weren't sharing customer information. We were building a better understanding of reimbursement and extending that leverage to everyone of our customers. And here's why it matters: payers already operate with the advantage of scale. Their policies are informed by patterns and trends across enormous claim volumes. Providers see only their own four walls. That's not a gap in expertise...it's a gap in visibility. We stopped judging Waze by the quality of its maps long ago. We judge it by the quality of its recommendations. I suspect enterprise healthcare software is heading the same direction and Aptarro is leading the way.
The shift from isolated problem-solving to collective, scaled intelligence is a game-changer for revenue cycle management. When every organization’s learnings benefit the entire network, we stop fighting battles in silos and start out-scaling payer policies."
This really highlights the shift from systems of record to systems of intelligence. Software that continuously learns and improves recommendations delivers far more value than software that simply executes workflows.
The Waze reframe is the right one: the value is not the workflow automation, it is that every customer's hard earned lesson improves the next customer's outcome. The blocker in revenue cycle specifically is that payer behavior shifts get learned in isolation, and most systems were never designed to propagate that signal across the base. When you turn one client's solved payer problem into something the whole network benefits from, how do you draw the data separation line so no one's specifics leak into the shared model?
🎯
I think the unique part for Waze is that most drivers contribute passively. Reporting an accident or other items are prompted so the user contribution has little friction. That's the design challenge for many enterprise healthcare software I see. The learning has to happen as a byproduct of doing the work, not as another ask on top of it when the healthcare workforce is already very stretched. I wonder how does Aptarro generalize those individual user learnings and apply across unique agreements with various payers and products.