Claims Library Entry
This Procurement Prompt Stops You from Wasting Money on Software Nobody Uses
Companies waste $4,830 per employee on unused software licenses annually. An AI-powered procurement prompt prevents this by forcing structured evaluation questions before any purchase, addressing the 48% shadow IT spending that creates duplicate capabilities.
Published October 13, 2025 by Kamil Banc
Lead claim
Mid-size companies waste $18M annually on unused software, using only 47% of purchased SaaS licenses.
Atomic Claims
What this article supports
Copy individual claims as needed.
Claim 1
$18M Annual Waste on Unused Software
Mid-size companies waste $18 million annually on unused software subscriptions they never deploy
Claim 2
Only 47% of Licenses Actually Used
Organizations actively use only 47% of the SaaS licenses they pay for annually
Claim 3
$4,830 Waste Per Employee Annually
Wasted software spend equals $4,830 per employee, representing a 21.9% increase from the previous year.
Claim 4
Shadow IT Represents 48% IT Spending
Shadow IT accounts for 48% of total IT spending in some organizations.
Claim 5
30% of Applications Have Overlapping Functions
30% of company applications overlap in functionality due to uncoordinated purchasing decisions.
Evidence
Context behind the claims
Quote
"This isn't incompetence. Mid-size companies waste $18 million annually on unused software. Your organization uses only 47% of the SaaS licenses it pays for."
Key statistics
$18 million
Amount mid-size companies waste annually on unused software subscriptions
47%
Percentage of purchased SaaS licenses that organizations actually use
$4,830 per employee
Wasted software spend per employee, up 21.9% from the previous year
48%
Percentage of total IT spending that comes from shadow IT in some organizations
Supporting context
The article presents a practical AI-powered procurement methodology based on industry data about software waste in mid-size companies. The approach uses an eight-question workflow that forces structured evaluation before purchases, specifically addressing the problem of departments making isolated purchasing decisions. Practitioners can implement this by requiring AI-guided questions that check for existing capabilities, justify ROI, and articulate business problems before evaluating vendors. The methodology aims to create consistency across purchasing decisions, making them comparable over time and revealing patterns about vendor performance and internal assumptions. This structured approach is designed for organizations using 110-152 SaaS applications that need standardization without adding bureaucratic approval layers.
How to Cite
Use the claim-level citation when you need a precise statement. Use the article or claims-collection citation when you want the wider argument and source context.
Individual Claim
Best when you need to cite one atomic claim directly inside a memo, deck, research note, or AI output.
"[claim text]" (Banc, Kamil, 2025, https://kbanc.com/claims-library/procurement-prompt-stops-software-waste)Original Article
Use this when you want to cite the full newsletter article at AI Adopters Club rather than the structured claims page.
Banc, Kamil (2025, October 13, 2025). This Procurement Prompt Stops You from Wasting Money on Software Nobody Uses. AI Adopters Club. https://aiadopters.club/p/procurement-prompt-stops-software-wasteClaims Collection
Use this when you want to reference the full structured claims collection on this page.
Banc, Kamil (2025). This Procurement Prompt Stops You from Wasting Money on Software Nobody Uses [Structured Claims]. Retrieved from https://kbanc.com/claims-library/procurement-prompt-stops-software-wasteAttribution Requirements
- Include the author name: Kamil Banc.
- Include the source: AI Adopters Club or the structured claims page.
- Link to the original article or the claims page you used.
- Indicate any edits or transformations if you changed the wording.
Related Reading
More from the library
A structured prompt approach transforms performance reviews into actionable development plans by interviewing managers through six categories. The method prevents common AI pitfalls by collecting complete information before generating recommendations, producing budget-aligned plans in a single session.
5 claims
A detailed analysis of 30 days of ChatGPT and Claude conversations reveals 10 repeating prompt patterns that demonstrate systematic AI use. The author shares specific prompt structures for tasks like email triage, presentation assembly, and workflow documentation, showing how to treat AI as infrastructure rather than a casual tool.
5 claims
AI adoption fails because of habit problems, not training gaps. This practical guide shows how to build an AI reflex muscle in 20 minutes by automating one annoying task. The goal is developing automatic pattern recognition for AI opportunities.
5 claims