Meta description: Your Zendesk bill keeps rising because SaaS is indirect procurement. Learn how to spot waste, control spend, and cut unused licenses.
Your Zendesk invoice lands. It is higher than last month.
You remember adding a few agents. Fair enough. But the total still feels off. A few seats were for contractors. One manager asked for temporary access during a rollout. A couple of people changed roles and probably never needed a full license after that.
That is the point where what is indirect procurement stops being a textbook term and starts being your problem.
If you are the Zendesk admin, IT manager, or ops lead who got handed SaaS spend on top of everything else, indirect procurement is the bucket you are already managing, whether anyone calls it that or not. It covers the goods and services your company buys to run the business, not the things it sells. For your team, that usually means software licenses, IT services, support tools, contractors, office services, and all the small recurring purchases that pile up.
That Zendesk Bill is Higher Than You Expected
Indirect procurement includes the goods and services a company buys to keep day-to-day operations running, without those items becoming part of the final product sold to customers. That includes software licenses, IT services, office supplies, facilities management, and consulting. In many organizations, that spend represents 15-30% of total revenue, according to Ramp’s explanation of indirect procurement.
Zendesk sits squarely in that category.
Your company does not sell Zendesk seats to customers. Your team uses them to deliver service, manage tickets, and keep support running. That makes Zendesk an operating cost, not a production input.
Why this spend gets messy fast
Indirect spend gets messy because no single team sees all of it.
Finance sees invoices. IT sees applications. Department heads request seats. HR drives onboarding and offboarding. Zendesk admins often control user setup, but not always budget ownership. So licenses get added one by one, often for valid reasons, with very little review after the initial purchase.
A few patterns show up over and over:
- New hires stay licensed after ramp issues
- Departed employees keep seats longer than expected
- Temporary project access becomes permanent
- Managers request full agent licenses when lighter access would do
- Renewals happen before anyone checks actual usage
That is how spend leaks. Not through one huge mistake, but through dozens of ordinary ones.
Zendesk makes the problem easy to miss
Per-agent pricing is clean on paper. In practice, it hides waste well.
If you are on annual billing, the current Zendesk Suite prices are Team $55, Growth $89, Professional $115, and Enterprise $169+ per agent per month. Those numbers make unused seats expensive very quickly, especially when no one has a habit of reviewing activity before renewal.
Ramp also notes that in SaaS-heavy environments, underused licenses are a clear form of indirect spend leakage, and read-only audit tools can surface significant wasted costs from idle seats in some cases through usage analysis.
Tip: If your Zendesk bill feels wrong, start by treating licenses as a procurement issue, not just an admin issue. The money leak usually comes from weak buying and review habits, not from the platform itself.
Indirect vs Direct Procurement What Is the Difference
Many teams understand direct spend better because it is easier to tie to revenue.
If you manufacture something, direct procurement covers the materials and components that go into the product. If you run a software business, you can think of direct spend as the infrastructure or inputs tied tightly to delivering what customers buy. Those costs usually get close attention because they affect delivery, margin, and customer commitments right away.
Indirect procurement is everything the business buys to operate. It matters just as much to your budget, but it is harder to control because it is spread across teams.
Since 2011, the share of indirect procurement in company expenditure has increased by 7% every year, and in many organizations it now accounts for up to 50% of total purchasing volume. In major markets it represents 35–45% of average company spend, according to Procurement Partners’ summary of the trend.
Direct vs. Indirect Procurement at a Glance
| Attribute | Direct Procurement | Indirect Procurement |
|---|---|---|
| Purpose | Supports the product or service you sell | Supports the business running behind the scenes |
| What gets bought | Raw materials, production inputs, delivery-critical items | Software licenses, IT services, office supplies, consulting, facilities |
| Who usually owns it | Supply chain, production, operations | IT, finance, HR, facilities, department managers |
| Demand pattern | Planned, forecast-driven | Request-driven, irregular, often reactive |
| Supplier setup | Fewer strategic suppliers | Many vendors across many categories |
| Control level | Usually centralized | Often decentralized |
| Risk if unmanaged | Product delays, quality issues, revenue impact | Budget creep, duplicate tools, weak visibility, off-contract buying |
| Zendesk licenses fit where | Not here | Here |
Why direct procurement methods do not map cleanly to Zendesk
Direct procurement usually has a clear planning model. You know roughly what you need, when you need it, and what volume looks like.
Zendesk licenses do not behave that way.
Seat counts move with hiring, attrition, reorganizations, seasonal support demand, vendor access, and internal projects. One department asks for speed. Another asks for budget control. Finance wants fewer surprises. Support leadership wants no risk to service levels.
That mix creates a common failure mode. Teams borrow direct-procurement habits like annual budgeting and preferred vendor approval, but skip the ongoing review needed for indirect categories. The result is approved spend with poor follow-through.
The practical takeaway
For Zendesk admins, the key difference is not academic. It changes how you manage cost.
You do not fix indirect procurement with better forecasting alone. You fix it with better visibility, tighter access rules, and regular checks on whether the thing you bought is still being used.
Common Categories of Indirect Procurement
Indirect procurement covers a wide range of spend. Some categories are obvious. Others hide in plain sight because each invoice looks small, or because the owner sits outside finance.
The usual categories include:
- IT and software
- Marketing services and ad spend
- Professional services like legal, consulting, and accounting
- Facilities and utilities
- Travel and entertainment
- HR services such as recruiting and benefits administration
- Maintenance, repair, and operations supplies
Why IT spend deserves special attention
For your role, the category that usually matters most is IT, especially SaaS.
That includes Zendesk, chat tools, knowledge management, analytics add-ons, project tools, identity products, monitoring tools, and all the niche subscriptions teams buy to solve local problems. The hard part is that these tools are easy to buy and easy to keep paying for.
A support leader might approve seats to get a queue under control. An IT admin might keep former agents active during a migration just in case. Procurement may not see any issue because the vendor is approved and the invoice matches the contract. Yet the business can still be paying for access nobody uses.
SaaS is where indirect procurement gets expensive
SaaS subscriptions are a hidden, high-growth category within indirect spend. They make up 15-30% of total indirect spend globally, and in the last 12 months to April 2026, Gartner reported SaaS spending rose 22% year over year to $195B in major markets, while 35% of enterprises cited poor license governance as a top indirect cost driver, as summarized by Tipalti’s indirect procurement guide.
That should feel familiar if you manage Zendesk.
SaaS buying often starts centrally, then drifts outward. One admin owns setup. Team leads ask for additions. No one wants to remove access too early. Over time, you get a mix of active users, occasional users, former users, and “keep them there for now” users, all billed the same way.
Zendesk is a clean example of the problem
Zendesk licenses are a useful example because the waste is easy to understand.
You pay per agent. If an agent is inactive, reassigned, or barely logging in, the business still pays the full seat cost until someone catches it. Admin Center gives you user data, but many teams still end up exporting CSVs, checking last login manually, and debating whether someone is inactive or just quiet.
That process breaks for three reasons:
| Problem | What happens in practice | Result |
|---|---|---|
| Decentralized requests | Managers ask for seats as needed | Seat counts rise faster than reviews happen |
| Weak offboarding follow-up | Access remains after role changes or exits | You keep paying for avoidable licenses |
| Manual audits | Spreadsheets get outdated quickly | Finance gets a late, incomplete picture |
Key takeaway: Not all indirect categories deserve the same attention first. For most mid-market Zendesk teams, SaaS gives you the fastest path to visible savings because usage data exists and waste is measurable.
Cost of Unmanaged Indirect Spend
The biggest cost in unmanaged indirect procurement is not one bad contract. It is the pile of low-drama decisions nobody revisits.
A team buys outside the usual process because it is faster. A manager adds users without checking whether old seats are still active. Another department signs a small subscription that overlaps with something you already pay for. None of it looks serious in isolation.
Then the budget review happens.
A 2025 McKinsey survey found that 28% of indirect spend in mid-sized enterprises with 20+ agents is maverick spend, causing $50K+ annual losses per 100 employees in major markets, driven by 2-3x more suppliers than direct procurement, according to NetSuite’s write-up on indirect procurement.
Maverick spend is not always reckless
Most maverick spend comes from reasonable behavior.
People buy what they need to keep work moving. The problem is that they buy outside approved channels, outside negotiated terms, or outside any shared review process. In SaaS, that often means duplicate subscriptions, unmanaged renewals, and access that keeps running long after the original need is gone.
For Zendesk teams, common examples look like this:
Seat additions without review A manager requests more agents during a busy period, but no one checks whether older inactive accounts could cover the need.
Add-ons left in place A trial or special project ends, yet the extra access remains attached to users.
Fragmented ownership Support, IT, and finance each own part of the picture, but no one owns the full cost.
The Zendesk math gets real fast
Take a Zendesk Suite Professional seat at $115 per agent per month. If you have five unused seats, that is $6,900 per year in wasted spend.
That is not a made-up procurement model. That is ordinary license drift.
The harder part is that wasted seats rarely stay isolated to one tool. If your team is loose with Zendesk access, the same pattern usually shows up in adjacent SaaS products too. That is why finance teams increasingly care about tail spend and low-visibility buying. If you want a useful breakdown of how these small transactions build up, this guide to tail spend management is worth a read.
Visibility is the primary bottleneck
Most companies do not fail because they refuse to cut waste. They fail because they cannot see it clearly enough to act with confidence.
Manual audits take time. Screenshots and exports go stale. Managers disagree on whether someone still needs a seat. By the time everyone aligns, renewal has already happened.
Tip: Start with categories where you can tie spend directly to named users. Zendesk is one of the best places to do that because every paid seat has an owner and a usage trail.
How to Build a Basic Indirect Procurement Process
You do not need a full procurement department to get control of indirect spend. You need a repeatable process that people will follow.
Structured indirect procurement programs deliver 10–20% savings across major categories, according to this industry benchmark summary. The gains usually come from the basics, not from fancy theory. Better visibility, fewer suppliers, and less off-process buying do most of the work.
Step 1: Get visibility first
Pull the data before you write policy.
Start with invoices, vendor lists, expense reports, and your finance system. Group spend by category. Then identify which tools have recurring subscription costs and per-user pricing. For Zendesk, compare billed seats against actual active users and recent agent activity.
You are not trying to build a perfect spend cube. You are trying to answer three practical questions:
- What are we paying for
- Who approved it
- Is it still being used
Step 2: Set basic rules people can follow
Most companies overdo policy and underdo enforcement.
Keep the first version light. Define who can request software, who approves it, and what review should happen before a new seat is added. For Zendesk, that could be as narrow as requiring a quick check for inactive seats before approving any additional agent.
A good rule is specific. A bad rule is broad and easy to ignore.
| Process area | Bad rule | Better rule |
|---|---|---|
| New software requests | “Get approval first” | “IT and budget owner must approve before purchase” |
| Zendesk seat additions | “Add seats as needed” | “Check inactive agents before adding paid seats” |
| Offboarding | “Remove access promptly” | “Disable or review Zendesk access during offboarding workflow” |
| Renewals | “Review annually” | “Review named users and actual usage before renewal sign-off” |
Step 3: Reduce supplier sprawl where it makes sense
Indirect spend often suffers from too many vendors serving the same need.
In software, that can mean overlapping support tools, duplicate reporting products, or teams buying niche apps when the approved platform already covers the use case. Vendor rationalization helps because fewer suppliers usually means less admin work, fewer contracts to track, and better buying power.
That does not mean forcing every edge case into one tool. It means challenging overlap.
If your support team is paying for Zendesk plus a separate tool that exists only because no one cleaned up processes inside Zendesk, fix the process first.
A more detailed look at this sits in this guide on software procurement management.
Step 4: Automate the checks that humans skip
Manual review works for a while. Then hiring changes, people go on leave, teams reorganize, and the spreadsheet dies.
Automate the repetitive checks in high-cost categories. For Zendesk, that usually means recurring license audits, inactivity thresholds, and alerts before renewal or expansion. Keep final decisions with admins and budget owners, but stop relying on memory.
Key takeaway: Good indirect procurement process is not about adding paperwork. It is about adding enough control to stop waste without slowing down legitimate work.
Key Metrics to Track Your Progress
If you cannot show progress in plain numbers, indirect procurement turns into a vague cleanup project. That is when leadership loses interest.
You do not need a giant dashboard. A few metrics are enough if they tie directly to control, waste, and decision quality.
Spend under management
This is the share of indirect spend going through your approved process.
For a mid-market team, that usually means purchases with an approved vendor, a clear owner, and a recorded approval path. The exact formula depends on your systems, but the working version is:
Spend under management = approved indirect spend / total indirect spend
A rising number is good. It means fewer purchases are happening in the dark.
Track it by category if possible. SaaS is often the easiest place to start because subscriptions are recurring and easier to list than one-off purchases.
Avoided waste
This is the money you stop spending after fixing known issues.
For Zendesk, calculate it using removed or downgraded unused seats multiplied by the seat cost over the remaining billing period or annual cycle. Keep the math visible and conservative. Finance trusts savings more when they can tie them to actual licenses removed, not estimated efficiency.
A practical example is:
| Metric | Example using Zendesk |
|---|---|
| Issue found | Inactive paid agents |
| Action taken | Remove or downgrade seats |
| Savings basis | Per-agent monthly price x seats removed x time period |
| What to record | Date, owner, seat count, value avoided |
Supplier count by category
This metric is blunt, which makes it useful.
Count how many vendors you pay in categories like software, marketing, or professional services. If the number keeps growing while usage stays flat, you likely have fragmented buying and duplicate tools.
Lower is not always better. You do not want forced consolidation that creates operational pain. But if three different teams are buying overlapping help desk or workflow tools, supplier count helps surface the issue fast.
Contract and renewal coverage
You want a current record of renewal dates, pricing terms, owner, and usage review status for major vendors.
That is less about legal housekeeping and more about avoiding lazy renewals. If nobody can tell you when a Zendesk renewal hits, who owns it, and whether seat usage was reviewed, you are still operating reactively.
For teams trying to clean up that side of the house, this guide on contract management for procurement is a practical next read.
Tip: Pick one metric per problem. Use spend under management for control, avoided waste for savings, supplier count for consolidation, and renewal coverage for planning.
Your Starter Checklist for Controlling Indirect Spend
The fastest win for most Zendesk teams is not a full procurement overhaul. It is a focused cleanup of software licenses, then building a better habit around them.
Start there.
Do these first
Pull your top indirect vendors Export the last few months of spend from your accounting or ERP system and sort by recurring vendors.
Choose one category for a pilot Pick SaaS first if you own Zendesk. The waste is usually easier to verify than in services or facilities.
Audit your top three software tools manually Check named users, recent activity, role changes, and obvious duplicates.
Review Zendesk before the next seat increase Do not approve more paid agents until you confirm whether inactive accounts already cover the need.
Add one approval checkpoint Require a usage review before new seats or renewals in your biggest software category.
What to avoid
A lot of teams burn time in the wrong places.
Do not start with every category at once Broad transformation projects stall fast.
Do not write a long policy before checking real spend You need evidence first.
Do not trust seat count as a proxy for need Assigned does not mean used.
Do not rely on quarterly spreadsheet audits forever They get skipped when work gets busy.
A short explainer can help your team align on why this matters before you change process:
Where automation earns its keep
Manual review is a good starting point. It is not a good long-term system.
Zendesk license waste is one of the few indirect procurement problems where the path from data to action is very clear. You can connect usage to named users, compare that with paid seats, and decide whether to remove, downgrade, or keep each license.
That is why SaaS license auditing is usually the highest-ROI first move for IT and ops teams. You can quantify the waste, fix it quickly, and use the result to justify broader indirect spend controls later.
What to do before your next Zendesk renewal
Use this order:
- Export current agents and roles
- Review recent activity
- Flag inactive or low-use paid seats
- Confirm business need with team leads
- Remove or downgrade what is not justified
- Document the savings
- Set a recurring review cadence
If you do only one thing after reading this, do that.
If Zendesk license waste is the easiest place to start, LicenseTrim helps you audit it without manual spreadsheets. It connects to Zendesk via OAuth with read-only access, finds inactive agents, and shows the cost of unused seats so you can clean up renewals with real numbers instead of guesswork.