CHALLENGE 03
Leading With ROI Instead of Payback Period
A Health IT company can present an impressive ROI and still fail to give a provider what it needs to make an investment decision.
ROI tells leadership how much value an investment may ultimately generate relative to its cost.
But it does not answer one of the most immediate questions facing a hospital or health system:
“How long will it take us to get our investment back?”
That is where payback period becomes especially important.
Providers are not only evaluating whether a technology can eventually create value. They are evaluating how much capital and organizational effort must be committed, when benefits will begin, how quickly the investment can be recovered, and what happens if those benefits take longer than expected.
ROI describes the potential return. Payback period tells the provider how long its money is at risk.
Seller’s Lens vs. Buyer’s Lens
Health IT companies often view the financial case through the economics of the product. Providers evaluate the economics of making the solution work inside their organization.
SELLER'S LENS
“The ROI is compelling.”
The seller sees:
• a strong projected return;
• significant long-term savings;
• new revenue opportunity;
• measurable efficiency gains;
• attractive percentage improvement;
• favorable customer case studies;
• a large potential economic benefit;
• and a financial story that demonstrates value.
From the seller’s perspective, the size of the return supports the investment.
BUYER'S LENS
“How long before we get our money back?”
The provider is asking:
- What is the total initial investment?
- When will implementation be completed?
- When do measurable benefits actually begin?
- How quickly do those benefits ramp?
- What internal resources must we commit?
- What additional implementation or integration costs exist?
- When does cumulative benefit exceed cumulative cost?
- What happens if adoption is slower than expected?
A large future ROI does not eliminate the financial risk of waiting years to recover the investment.
Why This Becomes a GTM Problem
When the financial story begins and ends with ROI, the vendor may answer how valuable the solution could become without answering how quickly the provider can justify the investment.
The ROI Is Impressive, but the Deal Still Stalls
Leadership likes the long-term economics but remains uncomfortable with the time required to recover the investment.
The Model Ignores the Ramp
Savings or revenue are shown as if they begin immediately rather than building gradually after implementation.
The Investment Is Understated
Implementation, integration, internal resources, training, and change costs are excluded from the payback calculation.
The Benefits Arrive Too Late
The model may produce an attractive multi-year return while requiring significant upfront spending before meaningful value appears.
The Business Case Is Generic
The same calculator is used for every provider regardless of local workflows, costs, volumes, or constraints.
The Downside Was Never Modeled
The financial story only works if adoption, utilization, and outcomes meet the vendor’s best-case assumptions.
The question is not only whether the investment eventually pays off. It is how long the provider must wait for that to happen.
Provider Perspective:
Robin Damschroder
Chief Financial Officer, Henry Ford Health
Finance Is Evaluating the Timing of Value
Healthcare finance leaders must evaluate far more than the theoretical upside of a technology investment.
They need to understand what the organization must spend, when those costs occur, when benefits begin, what assumptions drive the model, and how the economics change if implementation or adoption takes longer than expected.
A credible financial discussion therefore needs to address both value and timing.
The GTM implication
Do not make the provider reverse-engineer the payback period from your ROI model. Put the timing of the investment and benefit directly into the business case.
How to Build a Credible Payback Case
Lead With Payback Period
ROI can still be useful.
But payback answers a different—and often more immediate—question:
How many months will it take before the cumulative financial benefit equals the cumulative investment?
That forces the model to account for timing.
A solution could generate substantial long-term value while still creating an unattractive near-term financial burden.
Payback period converts the financial discussion from “How much could we make?” to “How long until we recover what we spend?”
Model the Ramp to Value
One of the easiest ways to overstate Health IT economics is to assume benefits begin at full strength immediately after purchase.
They rarely do.
Implementation takes time.
Users need to adopt the solution.
Workflows change gradually.
Volumes may increase over several months.
Financial benefits therefore usually ramp, rather than appear on Day One.
A credible model should show:
- implementation period;
- go-live timing;
- adoption ramp;
- monthly costs;
- monthly benefits;
- cumulative cash flow;
- and the month in which cumulative benefit exceeds cumulative cost.
If the benefit ramps over time, the business case should show the ramp—not hide it inside an annual ROI percentage.
Include the Full Investment
The subscription price is not necessarily the provider’s investment.
The organization may also commit:
- implementation resources;
- integration expense;
- internal IT time;
- project management;
- workflow redesign;
- training;
- clinical or operational labor;
- cybersecurity and governance resources;
- ongoing support;
- and change-management effort.
Those costs affect payback.
Ignoring them may make the financial story look better initially, but it also makes it easier for finance to challenge the credibility of the model later.
The payback period is only credible if the investment side of the equation is credible.
Pressure-Test the Payback
Do not calculate only one payback period.
Model what happens under different assumptions.
Conservative
Adoption is slower, implementation takes longer, or benefits ramp more gradually.
Expected
The most realistic combination of cost, timing, adoption, and benefit.
Upside
Implementation and adoption outperform expectations.
Then show how the payback period changes.
For example:
Expected Payback: 14 months
Conservative Payback: 20 months
Upside Payback: 10 months
The specific numbers will vary by provider, but the discipline matters.
A payback period that remains attractive under conservative assumptions is far more credible than an extraordinary ROI built only on the best case.
Diagnostic Content — Bottom Line
A provider-grade financial case shows not only the value the technology can create, but when that value begins, how quickly it ramps, and how long the organization’s investment remains unrecovered.
Better Discovery Questions — Don’t Ask / Ask Instead
Good financial discovery should reveal how the provider evaluates the timing and risk of an investment—not simply whether the projected return sounds attractive.
DON’T ASK
“Would a 3X ROI be compelling?”
ASK INSTEAD
“What payback period would leadership consider reasonable for an investment like this?”
DON'T ASK
“How much budget do you have?”
ASK INSTEAD
“What costs and internal resources need to be included for us to understand the complete investment?”
DON'T ASK
“If we can prove the savings, will finance approve it?”
ASK INSTEAD
“How quickly would those benefits need to materialize for the investment to meet your organization’s financial expectations?”
The objective is not to produce the highest possible ROI. It is to build a financial case the provider believes it can actually achieve.
From Payback Period to Commercial Readiness
Before treating an attractive payback period as evidence of financial readiness, the sales team should understand the provider’s complete investment, the ramp to value, and how the payback changes under more conservative assumptions.
1. Questions Health IT Companies Should Be Able to Answer
☐ What is the provider’s total initial investment?
☐ What additional internal costs must be included?
☐ When will implementation be completed?
☐ When do measurable benefits begin?
☐ How quickly will those benefits ramp?
☐ What is the expected monthly cash flow?
☐ In what month does cumulative benefit exceed cumulative cost?
☐ What is the expected payback period?
☐ What payback period does leadership consider acceptable?
☐ How does slower adoption affect payback?
☐ What does the conservative scenario look like?
☐ Are the assumptions based on the provider’s actual environment?
If the sales team can explain the ROI but cannot explain when the provider gets its money back, the financial case is incomplete.
The Buyer’s-Lens Test
A financially credible opportunity should allow the provider to answer “yes” to each of the following:
✓ Yes, we understand the full investment.
The model includes the technology and the organizational cost of making it work.
✓ Yes, we know when benefits begin.
The model reflects implementation and a realistic ramp to value.
✓ Yes, the payback period is clear.
Leadership knows when cumulative benefit is expected to recover cumulative cost.
✓ Yes, the assumptions reflect our organization.
Volumes, costs, workflows, and resource requirements are grounded in provider-specific inputs.
✓ Yes, the economics remain acceptable if things take longer.
The business case has been tested against a more conservative scenario.
When those five answers are present, the provider is no longer looking at a vendor ROI claim. It is evaluating a defensible investment case.
David's GTM Takeaway
Health IT companies love ROI because it can produce a very impressive number.
But a large ROI percentage can hide an important question:
How long does the provider have to wait to get its investment back?
That is why I prefer to lead with payback period.
Build the model month by month.
Account for the ramp.
Include the real cost of making the solution work.
Identify when cumulative benefit crosses cumulative investment.
Then pressure-test that date against a conservative scenario.