New project, new team, urgent need: 20 Adobe Creative Cloud licenses. Procurement places the order - $15,000. Meanwhile, in the same company: 35 users with Adobe CC who haven’t opened the application in 6 months. Marketing switched agencies, design team shrunk, but licenses still assigned. If someone had checked before purchasing - 20 licenses to reclaim without spending a cent.
This is everyday reality in most organizations. Research shows that 30-40% of software licenses are unused or underutilized. Companies pay for software nobody uses while buying new licenses instead of reclaiming existing ones.
License harvesting is a systematic process of identifying and reclaiming unused software licenses for reassignment. Sounds simple, but requires processes, tools, and organizational discipline. A well-implemented harvesting program can reduce software spending by 15-25% without any restriction of access to needed tools.
What is license harvesting and why is it critical for cost optimization?
“Organizations waste an average of 33% of their software spend on unused or underutilized licenses.”
— Flexera, State of IT Asset Management Report 2024 | Source
License harvesting is a process consisting of three elements:
- Identification - finding licenses that aren’t actively used
- Reclamation - taking licenses from users who don’t need them
- Reallocation - assigning reclaimed licenses to new needs
Why it’s critical:
Scale of the problem: Gartner estimates that organizations overpay for software by 25-30% due to unused licenses. For a company with a $10M software budget, that’s $2.5-3M annually.
Subscription model increases urgency: In perpetual model - you paid once, license sits. In subscription model - you pay monthly/annually for every unused license. SaaS proliferation means waste is ongoing.
Audit risk: When you buy new licenses instead of reclaiming existing ones, you increase exposure. During an audit, the vendor will see purchases and may question whether you have appropriate entitlements for all installations.
Sustainability and ESG: More companies are reporting digital sustainability. Unused software = unnecessary data center resources, energy consumption. Harvesting supports ESG goals.
Alternative to cuts: When you need to reduce IT budget, harvesting enables savings without taking tools from people who need them.
What are the main sources of unused licenses?
Personnel changes:
- Employee departures (licenses remain assigned)
- Position changes (old tools no longer needed)
- Long-term leaves (maternity, medical)
- Contractors who finished projects
Organizational changes:
- Restructuring (teams change, licenses don’t)
- M&A (license duplication after merger)
- Function outsourcing (licenses stay in company)
- Project completion
Technology changes:
- Migration to new tools (old licenses still active)
- Vendor consolidation (multiple tools to one, but old ones not reclaimed)
- Shadow IT becomes official (users had both versions)
Over-provisioning:
- “Just in case” licensing during onboarding
- Granting higher editions than needed (Enterprise instead of Professional)
- Bulk purchase without specific assignments
Seasonality and projects:
- Licenses for completed projects
- Seasonal workers
- Training and certifications (temporary needs)
Changed work patterns:
- Remote work changed needs (office-based tools unnecessary)
- Automation replaced manual tasks
- AI tools replacing some functions
How to identify unused licenses - metrics and thresholds?
Usage data sources:
Where to get usage data:
- Software metering tools (Flexera, Snow, ServiceNow SAM)
- Vendor admin consoles (Microsoft 365 Admin, Google Workspace Admin)
- Application logs (last login, activity logs)
- EDR/endpoint data (application execution)
- SSO/Identity logs (authentication events)
- Network monitoring (application traffic)
Key metrics:
Last active date: When user last launched/used application. Basic metric for most software.
Thresholds (examples):
- < 30 days = Active
- 30-60 days = Review
- 60-90 days = Warning
-
90 days = Harvest candidate
Frequency of use: How many times in a period. User who opened application once a month vs. daily.
Thresholds:
-
10x/month = Active user
- 3-10x/month = Light user
- 1-2x/month = Minimal user
- 0x/month = Inactive
Feature utilization: Are they using features that justify the edition? Enterprise user using only Basic features.
Concurrent usage: For named user licenses - how many people actually need concurrent access vs. occasional.
Threshold considerations:
Different software = different thresholds:
- Daily use tools (email, IDE) - 30 day threshold
- Monthly tools (reporting, analytics) - 60-90 days
- Quarterly tools (tax software, annual reporting) - 180 days
- Project-based (CAD, video editing) - activity-based
Industry/role matters:
- Sales on 30-day vacation - normal
- Developer not using IDE for 30 days - red flag
How to implement license harvesting step by step?
Step 1: Inventory and baseline
Before harvesting - you need to know what you have:
- List of all licenses (purchased, assigned)
- Current assignments (who has what)
- Usage data (who uses what)
- License terms (is harvesting allowed - some licenses have restrictions)
Tools: SAM tool, CMDB, vendor portals, spreadsheets for small companies.
Step 2: Define policies
Formal harvesting rules:
- Thresholds for different software categories
- Notice period (how much time to respond before reclamation)
- Exceptions process (how to get exemption)
- Re-assignment process (how to get license from harvesting pool)
- Escalation path
Step 3: Identify candidates
Based on usage data - list of harvesting candidates:
- Filter by threshold (e.g., > 90 days inactive)
- Exclude exceptions (parental leave, sabbatical)
- Prioritize by cost (most expensive licenses first)
- Group by manager (easier communication)
Step 4: Communication campaign
Don’t reclaim without warning:
- Email to user: “Your [software] license shows no usage for X days. Please confirm if you still need it.”
- Email to manager: “Team member has unused licenses…”
- Grace period (e.g., 14 days to respond)
- Clear next steps
Step 5: Reclaim
After grace period without response or with confirmation not needed:
- Unassign license in vendor portal
- Update inventory
- Move to available pool
- Notify user that license was reclaimed
- Document action
Step 6: Reallocate
Use harvested licenses:
- Pending requests - assign from pool instead of buying
- New hires - onboarding with harvested licenses
- Project needs - temporary assignments
Step 7: Measure and improve
Track effectiveness:
- Licenses harvested per period
- Cost avoided (harvested × license cost)
- Re-assignment rate (harvested that were used)
- User satisfaction (complaints, appeals)
What tools support license harvesting?
Dedicated SAM platforms:
Flexera One:
- Comprehensive software recognition
- Usage metering
- Automated harvesting workflows
- License optimization recommendations
- Enterprise-grade, complex setup
Snow License Manager:
- Strong discovery and metering
- License optimization module
- Harvesting automation
- Good Microsoft/SAP coverage
ServiceNow SAM:
- Integrated with ITSM
- Workflow automation
- Software asset management
- Usage analytics
Vendor-specific tools:
Microsoft 365 Admin Center:
- Usage reports (last activity)
- License utilization
- Inactive user reports
- Manual reassignment (no automation)
Google Workspace Admin:
- User activity reports
- License usage
- Archiving inactive users
Salesforce:
- Login history
- Feature adoption
- License optimization tips
Tool selection depends on:
- Size of estate (small companies: spreadsheets OK, enterprise: dedicated SAM)
- Vendor mix (Microsoft-centric: M365 + basic tool, diverse: comprehensive SAM)
- Automation needs (manual OK for < 500 licenses, automation for > 1000)
- Integration requirements (ITSM, procurement)
How to communicate harvesting to users and managers?
Framing matters:
Don’t: “We’re taking your license because you’re not using it” Do: “We’re optimizing our software resources - we can allocate saved funds to tools you actually need”
Don’t: “Monitoring your software usage” Do: “Making sure you have access to tools you need and we’re not paying for ones you don’t use”
Communication sequence:
Initial awareness (organization-wide):
- Announce program: “Starting license optimization program”
- Explain why: cost savings, better resource allocation
- Explain process: regular reviews, notice before action
- Assure: “If you need it, you keep it”
Individual notification (pre-harvest):
- Personal email (not mass)
- Specific: which software, usage data
- Action requested: confirm need or acknowledge removal
- Timeline: deadline for response
- Easy process: one-click confirm/release
Manager notification:
- List of team members with inactive licenses
- Cost of inactive licenses
- Request: verify business need
- Offer: discuss during 1:1 or respond async
Post-harvest:
- Confirm action taken
- Explain how to request again if needed
- Thank for cooperation
Handling objections:
“But I might need it soon!” → “You can request reactivation anytime. Current wait time is X days. We’re not deleting data, just freeing license.”
“My usage is legitimate but infrequent” → “Let’s review together. If your pattern is normal for your role, we’ll adjust threshold for this software/role.”
“This is unfair monitoring” → “We only track whether application was used, not what you do with it. This is standard practice for cost management.”
“My manager approved this license” → “We’re checking with manager too. If there’s business need, license stays.”
How to balance harvesting with user experience and productivity?
Avoiding productivity impact:
Generous grace periods: Don’t harvest too aggressively. 90 days inactive = reasonable. 30 days = too aggressive for most software.
Easy re-request process: If someone needs harvested license back, make it < 24h to restore. Self-service portal if possible.
Role-based exceptions: Some roles have legitimate infrequent use. Configure thresholds by role, not one-size-fits-all.
Project-based tracking: If license is for specific project, track project status not just last login.
Seasonal awareness: Don’t harvest tax software in March. Don’t harvest vacation coverage tools in August.
Balance metrics:
Track not just licenses harvested, but also:
- Re-request rate (if high → thresholds too aggressive)
- Complaint rate
- Time to fulfill re-request
- Productivity incidents reported
Target: maximize harvesting while keeping re-request rate < 10% and complaints minimal.
How to measure ROI of license harvesting program?
Direct savings:
Cost avoided: Licenses harvested × unit cost × period Example: 50 licenses × $500/year = $25,000/year saved
True-down savings: If subscription allows reducing seats: harvested seats × monthly cost × remaining months
Renegotiation leverage: Accurate usage data strengthens negotiation position. “We only need 800 seats, not 1000 as in current contract.”
Indirect benefits:
Audit risk reduction: Proper harvesting = better license position = lower audit exposure
Process efficiency: New license requests fulfilled from pool = faster, less procurement overhead
Budget accuracy: Real usage data = more accurate software budgeting
ROI calculation:
ROI = (Annual savings from harvesting - Program costs) / Program costs × 100%
Example:
- Licenses harvested: 200
- Average license cost: $800/year
- Annual savings: $160,000
- SAM tool cost: $30,000/year
- Labor (0.5 FTE): $50,000/year
- Total program cost: $80,000
ROI = ($160,000 - $80,000) / $80,000 × 100% = 100%Benchmarks:
Well-run harvesting program typically:
- Harvests 5-15% of total licenses annually
- Achieves 60-80% reallocation rate (harvested → reassigned)
- Delivers 10-20% reduction in new license purchases
- ROI > 200% within first year
Table: License Harvesting Maturity Model
| Level | Discovery | Monitoring | Process | Automation | Metrics |
|---|---|---|---|---|---|
| 0 - None | No inventory | No usage tracking | No harvesting | None | None |
| 1 - Basic | Spreadsheet inventory | Manual checks | Ad-hoc harvesting | None | Count of harvested |
| 2 - Reactive | Partial discovery tool | Periodic usage reports | Defined process | Email notifications | Savings tracked |
| 3 - Proactive | Full SAM tool | Continuous metering | Regular harvesting cycles | Workflow automation | ROI calculated |
| 4 - Optimized | Real-time inventory | Predictive analytics | Continuous optimization | AI-assisted decisions | Business impact metrics |
| 5 - Strategic | Integrated ecosystem | Behavioral analysis | Self-service optimization | Full automation with ML | Value realization tracking |
License harvesting is “low-hanging fruit” of IT cost optimization. It doesn’t require cutting capabilities - just eliminates waste. But it requires process discipline and appropriate tools.
Key takeaways:
- 30-40% of licenses in a typical company are unused - huge opportunity
- Harvesting = identification + reclamation + reallocation - systematic process
- Usage data is key - invest in metering
- Communication to users must be empathetic - framing matters
- Automation scales the program - start simple, automate incrementally
- Balance with user experience - too aggressive harvesting = productivity drops
- ROI > 200% is achievable - but requires investment in tools and process
Companies that take harvesting seriously save millions annually without any restriction of access to needed tools. It’s a matter of discipline, not technology.
ARDURA Consulting specializes in Software Asset Management and helps organizations implement license harvesting programs. From current state audit, through tool setup, to ongoing optimization - we help maximize the value of software investments. Let’s talk about optimizing your license portfolio.