Rockin' HIT Sales Podcast
Inside GPOs: How Health IT Actually Gets Evaluated and Purchased
James Ludwig, former VP of Strategy and Corporate Development at Premier, Inc., and now Managing Principal, Axiom Global Ventures
Watch or Listen
Choose your preferred platform:
Also available on all major podcast platforms.
Episode Summary
In this episode of Rockin’ HIT Sales, David Hacker sits down with James Ludwig for a practical look at how Group Purchasing Organizations actually work in Health IT. James explains the GPO as a contracting “bridge” between suppliers and health systems, then walks through the realities vendors often misunderstand: competitive-bid processes, proof of problem-solution fit, value analysis, scale readiness, and why getting “on contract” is not the same as having the GPO sell the product for you. He also covers how licensing and investment models can work, and why GPO strategy matters once a company is truly ready to sell and support at scale.
Why This Matters for Health IT Companies
A GPO can make it easier for a Health IT company to transact with hospitals and health systems, but getting onto a contract is not the same as creating market demand. Before a GPO takes a solution seriously, the vendor still needs to demonstrate that it solves a meaningful healthcare problem, has evidence that the solution works in provider environments, and can support deployment beyond a single customer.
For Health IT companies, GPO strategy should therefore come after—and reinforce—a working go-to-market motion rather than substitute for one. A contract can reduce administrative friction and expand access to potential health-system customers, but the vendor still has to create relationships, differentiate the solution, win individual opportunities, and deliver successfully at scale. James describes the contract as effectively giving the vendor a “license to hunt,” not a sales force.What You’ll Hear in This Episode
- How James explains the real function of a GPO in healthcare
- The most common misconceptions vendors have about GPO contracts
- What has to be true before a Health IT solution is taken seriously for evaluation
- How GPO teams and member health systems work together through value analysis
- When licensing, investment, or co-development models can make sense
- Why scale readiness matters as much as the solution itself
- What vendors should do — and avoid — when building a GPO strategy
Questions This Episode Answers
What does a healthcare GPO actually do for Health IT vendors?
A GPO serves as a contracting bridge between suppliers and healthcare organizations. It manages contracting and competitive-bid processes that can make it easier for participating health systems to transact with approved suppliers.
Can a Health IT company simply approach a GPO and get on contract?
No. Most products and services move through some form of evaluation or competitive process. In some circumstances, a health system already using and supporting a solution may help create another path, but vendors should not assume that simply approaching the GPO is enough.
What has to be true before a GPO will take a new Health IT solution seriously?
The company first needs to identify a meaningful problem that exists across healthcare and demonstrate that its solution addresses that problem. A narrow technology capability is less compelling than evidence that the solution solves an issue healthcare organizations actually care about.
How do GPOs and member health systems evaluate new technology?
Evaluation often involves both GPO teams and provider representatives through a value-analysis process. They assess whether the solution fits the healthcare environment, provides meaningful value, and can be supported beyond an isolated implementation.
Why does scale readiness matter before pursuing a GPO strategy?
Because a GPO relationship can potentially expose a vendor to hundreds or even thousands of healthcare organizations. A company that cannot sell, implement, support, and deliver consistently at greater volume may be pursuing the channel before its commercial and operational infrastructure is ready.
Does getting on a GPO contract mean the GPO will sell the product?
No. The contract primarily makes it easier for member organizations to transact with the vendor. The Health IT company still needs to generate interest, develop opportunities, build relationships, and win business inside the GPO’s member base.
Does being on a GPO contract turn a differentiated Health IT solution into a commodity?
Not necessarily. James explains that the contract addresses the administrative side of doing business; it does not require a company to stop innovating or differentiating. Vendors still need to strengthen their value proposition and continue improving the solution if they want the relationship to renew and expand.
What should Health IT companies avoid when approaching a GPO?
Avoid cold outreach without context, overstating limited customer evidence, and assuming success at one hospital proves enterprise scalability. Vendors should first establish credible healthcare results, demonstrate broader applicability, and build relationships before asking for a GPO contract.
David’s GTM Takeaways for Health IT Vendors
About the Guest
James Ludwig is a former Premier GPO leader who spent time as Vice President of Strategy and Corporate Development at Premier working across GPO strategy, joint ventures, licensing, and investment models. He is now serving as Managing Principal at Axiom Global Ventures.
Transcript
Prefer to read or download the conversation?