Every piece of software in your organization goes through the same journey. Someone needs it, it is approved and bought, deployed to users, used (or not), renewed and eventually retired. Waste and risk enter at specific points in that journey: a duplicate purchase at the request stage, a missing contract at procurement, an idle license during use, an unreviewed renewal, a forgotten subscription after retirement.
Managing the lifecycle means putting a simple control at each stage.
The six stages
1. Request
The cheapest software is the software you already own. Before anything new is bought, check whether an approved product already covers the need. A short, searchable catalog of approved tools prevents most duplicate purchases.
2. Approve
Approval should confirm three things: the business need, the right edition and quantity, and a named owner. Tiering approval by cost and risk keeps it fast for small purchases. Our guide to SaaS approval workflows explains how.
3. Procure
At purchase, capture the contract and its key terms in your SAM system: quantity, metric, price, term, renewal date and notice period. This is the moment information is easiest to collect, and the moment it is most often lost.
4. Deploy
Assign licenses to named people through your identity provider wherever possible. It makes usage measurable and makes reclamation straightforward when people change roles or leave.
5. Use and optimize
Monitor whether licenses are used. Reclaim those that have been idle for a set period, right-size users on premium tiers they do not need, and look for overlapping tools.
6. Renew or retire
Every renewal is a decision point. Review usage, price and fit before the notice deadline, not after the invoice arrives. When a product is retired, cancel the subscription, remove the software, recover any hardware, and close the record, so nothing keeps billing quietly.
Where the money leaks
| Stage | Typical leak | Control |
|---|---|---|
| Request | Duplicate tools bought by different teams | Approved catalog |
| Approve | Premium editions for everyone | Persona-based editions |
| Procure | Contract terms not recorded | Contract intake |
| Deploy | Shared or generic accounts | Identity-based assignment |
| Use | Idle licenses | Quarterly reclaim cycle |
| Renew or retire | Auto-renewal at full volume; forgotten subscriptions | Owner review before notice deadline |
Waste rarely comes from one bad decision. It comes from a good purchase that nobody looked at again.
Retirement: the forgotten stage
Retiring software is not the same as no longer using it. A tool the business stopped using last spring can keep billing for years if nobody cancels it, and installed copies can still count against you in an audit.
Retiring a product properly
How MI One helps
Frequently asked questions
Who owns the software lifecycle?
Ownership is shared: business owners request and use, procurement buys, IT deploys and the SAM function monitors and coordinates renewals.
What is the most important stage to fix first?
Renewals. Unreviewed renewals lock in waste for another full term.
How do we retire software properly?
Cancel in writing before the notice deadline, remove installations, reclaim licenses, and keep the record for audit history.