Ep 3: Objection Handling for Pathway.AI

Emily Spencer

Welcome back to another episode of KARL STORZ AI Education! I'm Emily Spencer, and I'm here again with David Collins. Today, we're diving right into the art of handling objections when pitching Pathway.AI in the operating room. Now, if you've been following along, you’ll remember that in our last couple of episodes we explored how AI is really transforming hospital workflows—especially in the OR—and the importance of a consultative, value-led approach to these conversations.

David Collins

Yes, that's right, Emily. We’ve talked a lot about the practical benefits of AI in healthcare, not just the theoretical ideas. Platforms like Pathway.AI and Artisight are actually streamlining operations and solving real workforce issues. But—let’s face it, you don’t get far unless you address the concerns people have. Handling objections, whether it’s about data, value, or change management, is absolutely key. It’s not about ‘winning the argument’, it’s about building trust and clearing up misconceptions so you can move the dialogue forward.

Emily Spencer

Exactly! And, as we discussed before, objections aren’t roadblocks—they’re more like signposts that help you steer the conversation where it needs to go. If you don’t address them, all those value points just get lost. If you do, you create space for real engagement and build credibility, which is what actually makes those follow-up demos and meetings happen.

David Collins

And it's worth highlighting—many objections are just misunderstandings or surface-level worries. When we handle them well, we unlock opportunities to show the real strength of our AI and what it can mean for clinicians and hospitals. Shall we dig into the most common ones?

David Collins

The number one topic that comes up again and again is privacy. There’s always that uneasiness about cameras in the OR—people worry about surveillance, or think someone's watching or recording them constantly. You’ll also hear questions about HIPAA compliance and how data is handled. These are all perfectly valid concerns, and the best response is to get specific.

Emily Spencer

Absolutely, David. Pathway.AI addresses these right out of the gate by using privacy-blurring filters so no identifying features are ever stored or even leave the operating room. Data processing is local, which means information isn’t being shipped off to unknown servers—everything stays securely within the hospital’s existing infrastructure. We also use third-party certifications to confirm compliance with HIPAA and best security practices. You can confidently tell teams: “No images ever leave the OR. Everything is fully compliant.”

David Collins

And when it comes to control, that’s another common point. Some worry the system's going to automate everything and take away their ability to intervene. But actually, Pathway.AI lets clinicians manually review and correct entries to the EMR, or just keep manual processes in place if they wish. It’s about giving staff options—not forcing change but supporting their workflow and preferences.

Emily Spencer

Yes, being able to overwrite or validate AI-suggested documentation puts end-users at ease. It shows them that this is about augmentation, not replacement. Allowing their judgement to take priority gains real buy-in from even the most cautious stakeholders.

Emily Spencer

Once those privacy and control concerns are settled, the conversation almost always shifts to value and accuracy—sort of the “Does this really make things better?” angle. Sometimes people don’t quite see the impact immediately, or maybe they’re just used to their current systems. But with Pathway.AI, you can walk clients through our gradual rollout—what we call the ‘crawl, walk, run’ approach. We don’t rip and replace, we let teams ramp up in phases with lots of support, making adoption much more comfortable.

David Collins

And about accuracy—once the AI is localised to a hospital’s workflows, it’s consistently achieving over 99% accuracy in automated documentation and task recognition. That beats manual charting in both speed and reliability. When sellers get objections like, “How is this better than our current solution?” or, “What about the other vendors like Stryker or Care.AI?” it helps to highlight that Pathway.AI actually automates the charting, not just records video or provides a digital whiteboard. That’s a tangible operational benefit.

Emily Spencer

Definitely, and raising references from real hospitals in the Midwest or East US who’ve measured those time savings and accuracy improvements adds a lot of credibility to these claims. For integration concerns, your best approach is to explain that Pathway.AI is designed for compatibility, with low-impact infrastructure and straightforward EMR interfaces. You can use a question like, “What would it mean for your team if charting took half the time it does today?” to help them envision the shift in everyday workflow.

David Collins

And don’t forget to cover the exceptions policy. If asked, make it clear—data flagged by the AI can always be reviewed and validated or corrected by staff. That way, they maintain oversight, and trust is preserved. It’s not a black box. It’s a transparent, auditable process designed for cooperation between people and technology.

Emily Spencer

So, to sum up, addressing objections is about delivering specifics, offering reassurance, and showing pathways to value. That’s how objections become opportunities. We’ll be diving even deeper into best practice demos and next-level questions in our upcoming episodes—so, thanks for joining us today. David, always a pleasure!

David Collins

Thank you, Emily, and thank you to everyone listening. Don't forget to bring your toughest questions for next time. Have a great week, everyone.