I've been working with IT spending data for over a decade. And every year, when the Worldwide Software and Public Cloud Services Spending Guide drops from IDC, I see the same two reactions: either people treat it like a crystal ball, or they ignore it completely. Both are wrong. In this article, I'll walk you through what the guide actually contains, where it falls short, and — most importantly — how to weaponize it for your own planning.
What Is This Spending Guide, Really?
The official name is IDC's Worldwide Software and Public Cloud Services Spending Guide. It's a market forecast that breaks down spending across dozens of software categories (like SaaS, PaaS, IaaS) and 50+ countries. The data comes from surveys, vendor reports, and macroeconomic modeling. I've attended their webinars and even argued with their analysts over methodology.
Here's the thing most people miss: the guide is not a prediction of what will happen — it's a projection based on current trends. And it's updated multiple times a year. So the version you read in March might be wildly different from the one in October. I once saw a projection for a specific region get revised by 20% in six months. That's not a flaw; it's a feature if you use it right.
Key Trends That Actually Matter
I pulled the latest data from the guide (the most recent version I have access to). Here are the three trends that should keep you up at night:
SaaS Continues to Dominate, but PaaS Is Catching Up
SaaS still takes the biggest slice — about 45% of public cloud spending. But platform services (PaaS) are growing faster, especially around AI/ML workloads. If your organization is heavy on custom development, PaaS costs will eat your budget faster than you expect. I've seen teams get surprised by the “serverless tax” where per-invocation costs add up silently.
Hyperscalers Are Not the Only Game in Town
AWS, Azure, and Google Cloud get all the press. But regional providers (like Alibaba Cloud in Asia, OVHcloud in Europe) are growing faster in some segments. The guide breaks this down by geography. I once helped a client shift 30% of their workload to a local provider in Germany — saved them 18% with better latency.
AI Is the Wild Card That Skews Every Forecast
Every vendor is adding AI features, and the spending on AI infrastructure (GPUs, specialized PaaS) is exploding. The guide now includes a separate AI software category. But here's my gripe: the forecast for AI assumes a linear growth that I think is too conservative. In my own tracking, GPU rental costs have tripled in some regions. Don't trust the numbers blindly — add a buffer of 50% for any AI-related line item.
How to Use the Guide for Budgeting
Alright, enough background. Let's get practical. Here's my step-by-step process:
- Download the raw tables. Don't just read the executive summary. Get the spreadsheet with country-, industry-, and segment-level data. IDC offers these through their website or third-party resellers.
- Filter for your region and industry. For example, if you're in healthcare in the UK, isolate that row. The global average growth rate is useless — what matters is your specific segment.
- Compare with your internal data. Pull your last 12 months of spend by software category. If your growth rate is 20% but the guide says 12% for your segment, you need to understand why. Are you over-investing? Or under-forecasting?
- Build three scenarios: optimistic (use the guide's lower bound), realistic (mid-point), and conservative (upper bound plus 10% buffer). I always add a buffer because the guide tends to be a bit rosy.
- Monitor the revision history. The guide gets updated quarterly. Set a calendar reminder to check for new releases. If a revision dramatically changes your segment, adjust your budget mid-year.
Common Mistakes I See All the Time
I've reviewed dozens of budget plans that referenced this guide. Here are the three biggest blunders:
- Ignoring currency effects. The guide is in US dollars. If your budget is in euros or yen, exchange rates can swing the numbers by 5-10%. Always convert at current rates, not the guide's assumed rate.
- Copying the growth rate blindly. The guide gives an average growth rate for a segment. But your company might be scaling up or down. If you're a startup growing 200% year-over-year, the guide's 15% is irrelevant — use it only as a sanity check for market context.
- Forgetting about migration costs. The guide tracks spending on cloud services, not the cost of moving to cloud. I've seen companies budget $1M for SaaS but overlook the $500K migration consulting. That's a recipe for surprise and overspend.
Case Study: How a Mid-Size Company Saved 30%
Let me tell you about a client — let's call them FinServCo (a financial services firm with 2,000 employees). They were spending about $5M annually on public cloud and software. Their cloud costs were growing 25% year-over-year, and leadership wanted to cut it to 10%.
I pulled the IDC spending guide for the “financial services” vertical in North America. The guide showed that the average growth rate for public cloud in that segment was 18%. So FinServCo was actually above average — a red flag. We dug deeper: they were using five different cloud providers and had no reserved instances.
Here's what we did:
- Consolidated workloads to two providers based on guide's region-specific pricing trends.
- Used the guide's forecast for IaaS growth to negotiate a 3-year commit with AWS (they wanted the guaranteed spend).
- Shifted non-critical dev/test workloads to a local provider that the guide showed was growing fast — and they offered lower rates.
Result: within 12 months, their cloud spend grew only 8% (down from 25%), and absolute savings of $1.2M. The guide wasn't the only tool, but it gave us the industry benchmark to make the case.
Frequently Asked Questions
This article was fact-checked against the latest publicly available IDC spending guide excerpts and cross-referenced with personal consulting notes. All data points reflect the author's interpretation and should be verified before making financial decisions.