It's budget season. Finance teams are forecasting revenue, headcount, compensation, capital spending, technology investments and every other assumption that will roll up into the organization's 2027 plan.
If your organization uses IBM Planning Analytics, IBM Cognos Analytics or IBM SPSS, one more assumption belongs on that list: your IBM software costs.
What Is IBM's 2027 Software Price Harmonization?
IBM announced its 2027 Software General Price Harmonization on August 31, 2026, with pricing changes beginning as early as November 1, 2026, under IBM's Passport Advantage program. For Planning Analytics customers specifically, two dates matter:
- Planning Analytics as a Service pricing is scheduled to increase 20% effective November 1, 2026.
- Eligible on-premises IBM software, including Planning Analytics, Cognos Analytics and SPSS, will see a 9% increase effective January 1, 2027.
And existing customers need to pay attention for a third reason: software renewals are affected too, not just new purchases.
Why Isn't This Just About Buying New Licenses?
Because IBM's announcement is broader than most people assume. When people hear “software price increase,” they think about the cost of adding licenses. That is part of it, but IBM states that eligible offerings subject to harmonization include Software License and 12-month Subscription & Support, Software S&S Renewal, S&S Reinstatement, Trade-up Licenses, Monthly Licenses, Subscription Licenses and several support options.
For Software Subscription & Support renewals specifically, IBM says the price change applies to coverage periods beginning on or after January 1, 2027, regardless of when payment is received. That distinction matters: if your organization is budgeting its 2027 IBM renewal based mainly on what you paid in 2026, that assumption needs a second look.
Here's the detail that catches most finance teams off guard: your existing Subscription & Support contract renews every year whether or not you buy anything new. Unless your contract already caps the uplift, a renewal that falls on or after January 1, 2027 renews at the new price automatically. No new purchase is required to feel it.
Why Does Budget Season Make the Timing So Important?
Because most organizations are building or finalizing 2027 budgets right now. Technology teams are estimating costs, FP&A is collecting assumptions, department leaders are requesting investments, and software renewals are being rolled forward. This announcement lands at exactly the right time to fold the changes into those plans.
The simplest approach is to take your existing IBM costs and add the expected percentage increase. We'd recommend going further: use the pricing change as a reason to review the entire IBM investment, not just the line item.
How Should You Start With Your Existing Renewal?
Start by understanding exactly what you're renewing. What products do you own? How many licenses? What are your entitlements? What are you paying Subscription & Support on? Are you actually using everything you're paying for? Are there licensing changes worth considering? And when does your next coverage period begin?
These aren't questions to answer after a renewal quote arrives; they're questions to answer while the budget is still being built. Confirming what you own is also the first step in preparing for an IBM licensing audit, and if it's been a while since you checked, it's worth running through your ILMT compliance checklist at the same time.
What Should You Budget for 2027 Growth?
Your existing renewal is only part of the picture. Will you add Planning Analytics users? Will more departments participate in planning and forecasting? Will you build additional PA models? Will Cognos Analytics expand to more teams? Do you anticipate additional SPSS requirements? Will you need more environments or capacity?
If those investments are likely to happen anyway, understand their expected cost before finalizing the 2027 budget, then ask whether the timing should change.
Should You Buy Software Just Because Prices Are Increasing?
No, not on its own. A price increase creates urgency; it shouldn't create panic. We aren't recommending organizations buy software they don't need simply because it may cost more later.
Instead, distinguish between an unplanned purchase and an investment you already expect to make. If you're confident you'll need additional licenses or capacity in 2027, accelerating a planned investment may be worth evaluating. That's smart financial planning. Buying something you may never use just to avoid an increase isn't.
What Does the Planning Analytics SaaS Increase Mean for You?
For organizations considering Planning Analytics SaaS, the conversation gets more important, because a 20% adjustment effective November 1 can materially change the economics of an investment. Consider a simplified example: a $100,000 investment subject to a 20% increase becomes roughly $120,000; at $250,000, the difference is $50,000.
If SaaS has been something your organization has vaguely considered for “sometime next year,” this announcement is a reason to move the analysis forward. Our Planning Analytics on-prem to SaaS migration guide walks through the typical timeline and framework. But again, the objective isn't simply to beat an increase. Ask whether SaaS is the right long-term strategy first. If the answer is yes and the investment was already coming, then timing matters.
That 20% headline number also isn't the full comparison. On-premises software carries its own quiet costs: upgrade cycles, audit risk, and infrastructure and administration time. SaaS customers stay on IBM's current version automatically, including new AI functionality as it rolls out, and they don't need to install or maintain ILMT, the tool IBM uses to track on-premises license compliance, which also means far less audit exposure. Price in what on-premises actually costs to maintain, and the SaaS math often looks a lot closer than the headline number suggests.
Should You Put More Money Into On-Premises Licensing Right Now?
There's another side to this. Perhaps your organization is about to purchase additional on-premises licenses. Before doing so, ask: is on-premises where we want this environment to be three to five years from now?
If yes, understand your anticipated requirements and evaluate whether purchasing before January 1 makes sense. But if SaaS has been on the table for the last several years, don't make another substantial on-premises investment without modeling the alternative. The same question applies on the Cognos side: if a move has been on your radar there too, see our flat-rate approach to Cognos Analytics SaaS migration before committing more budget to an on-premises footprint. The wrong architectural decision can cost considerably more than 9%.
What Seven Questions Should Your 2027 Budget Answer?
Rather than simply adding 9% or 20% to a spreadsheet, IBM customers should use budget season to answer:
- What IBM software do we own today?
- What are we paying to maintain it?
- What are we actually using?
- What will we need during 2027?
- What should we budget for renewals?
- What additional purchases are already anticipated?
- Does on-premises or SaaS make the most sense for our next investment?
Those answers build a much stronger technology budget than simply rolling last year's expenses forward.
How Do You Turn IBM's Deadline Into a Planning Deadline?
Technology decisions have a habit of getting postponed: “we'll look at SaaS next year,” “we'll review licensing at renewal,” “we'll deal with additional capacity when we need it.” IBM's announcement is an opportunity to replace those statements with actual dates: November 1, 2026 for Planning Analytics SaaS, and January 1, 2027 for eligible on-premises software. Those dates shouldn't force your technology decision; they should force the conversation.
Budget season doesn't last much longer. Teams that check their entitlements, renewal dates and contract terms against these increases now will present a planned number to their board in Q1. Teams that roll last year's spend forward will be explaining a surprise instead.
Is the Goal Simply to Avoid 9% or 20%?
Avoiding a price increase is good, but there may be much larger opportunities hiding inside your IBM environment. Perhaps you're paying maintenance on licenses you don't need. Maybe your licensing model no longer reflects how your organization actually uses the technology.
Maybe additional on-premises investment is absolutely the right choice, or maybe SaaS eliminates infrastructure, administration and upgrade responsibilities that make the broader economics more attractive. It's also worth checking the license type itself: organizations still paying for on-premises SPSS Stat licenses when a subscription would fit better should review IBM SPSS Stat licensing options as part of this exercise. You won't know until you model it.
What Should You Do Now?
If you're using IBM Planning Analytics, Cognos Analytics or SPSS and currently building your 2027 budget, now is the time to review your IBM roadmap: update renewal assumptions, forecast 2027 licensing requirements, identify expected growth, review licenses and entitlements, evaluate planned purchases, and model on-premises versus SaaS.
At Lodestar Solutions, we've spent more than 20 years helping organizations understand and maximize their IBM Analytics investments through our IBM Planning Analytics and Cognos Analytics services. We can review your existing licensing and entitlements, estimate upcoming renewal requirements, identify future needs, and evaluate the economics of on-premises versus SaaS.
Don't wait until your 2027 budget is approved to discover your IBM software assumptions have changed. Budget for the increase now, then determine what you can do about it.
