5 min read
Competing for the Hospice Technology Budget: How CFOs Decide What Wins Funding
BetterRX
:
Oct 14, 2026, 9:00:01 AM
Competing for the hospice technology budget means making the case for a specific investment against every other initiative asking for the same limited dollars. Proposals that win tie the investment to a measured outcome rather than a general efficiency claim. The strongest business cases connect directly to predictable per-patient-day pharmacy spend, nurse hours recovered, or reduced medication service failures, the same outcomes BetterRX delivers as The Better Way to Manage Hospice Medications.
Why Technology Requests Compete Harder Than They Used To
Hospice CFOs are fielding more technology requests than they used to, and the budget hasn't grown at the same pace. Clinical teams want tools that reduce administrative burden. Operations wants systems that make multi-location reporting less painful. IT wants to retire aging point solutions. Every request sounds reasonable in isolation, which is exactly the problem: reasonable isn't the same as ready to fund.
What actually separates a funded initiative from a deferred one is whether the person making the request can answer a simple question with a number instead of an adjective: what specifically changes, and how would we know it worked?
This dynamic isn't unique to hospice, but it's sharper here because the budget itself is more constrained. Under a fixed per-diem Medicare benefit, there's no revenue line that grows simply because the organization spent more on technology. Every dollar allocated to one initiative is explicitly a dollar not allocated to another, which is exactly why the business case has to do more work than it might in an industry with more budget flexibility.
What a Fundable Business Case Actually Looks Like
A technology request that competes well for budget usually has four characteristics.
1. It ties to one of a small number of outcomes finance already tracks:
predictable per-patient-day pharmacy spend, nurse hours recovered, or reduced medication service failures, rather than a vague claim about efficiency.
2. It includes a baseline.
If the initiative can't state what the current number is, it can't credibly claim to improve it.
3. It scales.
An investment that only helps the location proposing it is a harder sell than one that improves the same metric everywhere the organization operates.
4. It accounts for the transition.
A CFO will weigh training time and disruption against the gain, so the strongest proposals name the onboarding plan up front instead of leaving it as an unspoken objection.
It's also worth naming what doesn't help a proposal's chances, even though it often gets included anyway: comparisons to what competitors are doing, general industry benchmarks without a source, or urgency framed around a deadline rather than a measured outcome. None of these give a CFO anything to hold the investment accountable to six months after approval, which is ultimately what determines whether a similar request gets easier or harder to fund next cycle.
The Metrics CFOs Should Ask Every Proposal to Address
Rather than evaluating every technology request on its own terms, CFOs get more consistent decisions by asking each proposal the same set of questions:
How BetterRX's Model Makes This Case for Itself
The reason BetterRX's business case is straightforward to build is that its outcomes are already measured and tied to specific numbers rather than general claims. Per BetterRX's Voice of the Customer survey across six consecutive years, 86% of clients report reduced medication service failures, with 41% reporting failures “significantly decreased.” That's a concrete before-and-after claim a CFO can put directly into a budget request. On nurse time, BetterRX's 2026 Voice of Customer Survey Results show 5–6 hours saved per nurse per week.
BetterRX Guardrails™ and real-time reporting move cost visibility from a monthly report into the ordering workflow itself, which lets finance teams make proactive decisions using today's data, not last month's reports. A PPD Performance Dashboard and 30+ reports put the pharmacy spend analysis finance teams would otherwise build in spreadsheets inside the platform. And because BetterRX is one standardized platform that scales from 1 to 100+ locations without multiplying complexity, the same business case can carry from one site to the next. Transparent, pass-through pricing matters here too: BetterRX does not profit from medication or delivery markups, so its incentives stay aligned with the hospice's. For the transition, BetterRX provides dedicated onboarding from kickoff through go-live, with implementation coordinated across teams and locations.
The analytics have been very useful and have helped us reduce unnecessary costs."
- VOC respondent
Building the Case Leadership Will Actually Approve
The technology requests that win funding aren't necessarily the most sophisticated ones. They're the ones that make it easy for a CFO to say yes, because the outcome, the baseline, and the scalability are already spelled out. That matters because a champion's enthusiasm doesn't transfer to the people who didn't sit through the demo; the case has to stand on the finance outcomes alone. Before bringing a technology request to the budget conversation, it's worth writing the one-sentence version first: “This investment moves [specific metric] from [current number] to [projected number], and it works the same way at every location we operate.” If that sentence can't be written honestly, the proposal isn't ready for budget season yet.
A Short Example: Two Proposals, Same Meeting
Consider two proposals competing for the same budget cycle. The first asks for funding to "improve pharmacy efficiency," citing general industry trends and a vendor's marketing claims. The second states that current medication service failures run at a specific baseline rate, that the proposed platform publishes sourced customer data showing reduced medication service failures, and that the same investment will apply without modification at every location the organization operates today or adds in the next two years.
The second proposal wins more often, not because it's more expensive or more sophisticated, but because it gives the CFO something concrete to hold the initiative accountable to after the money is spent.
What Happens After a Proposal Gets Funded
Winning approval is only the first half of a strong technology business case. What happens in the months afterward often determines whether a similar request gets easier or harder to fund next cycle.
Frequently Asked Questions
-
Proposals tied to a specific, measurable outcome like reduced medication service failures or nurse hours recovered compete better than proposals built around a general efficiency claim.
-
How it affects per-patient-day pharmacy spend, how many nurse hours it recovers, whether it reduces medication service failures with real data behind the claim, whether it still works after the organization adds a location, and how much time it saves your own finance team.
-
Under a fixed per-diem Medicare benefit, there's no revenue line that grows because an organization spends more on technology, so every dollar funded for one initiative is a dollar not available for another. Proposals need a clear, measurable business case to stand out.
-
BetterRX ties its outcomes to specific, measured proof points, including reduced medication service failures and hours saved per nurse per week, giving finance teams concrete numbers to build a business case around.
-
BetterRX Guardrails™ are configurable clinical and financial standards built into the medication ordering workflow, so cost-effective choices are guided at the moment of ordering. Together with real-time reporting, they give finance teams live PPD tracking and cost alerts at the point of ordering, not 15 to 30 days after the fact.
-
No. The strongest investments hold their value at every new location without multiplying complexity, which is a key test CFOs should apply to any technology proposal.
-
Plan an initial check-in 90 to 180 days after implementation, comparing the actual result against the baseline and projection in the original proposal.


