Updated April 2026
Tech Stack Audit Checklist: A Step-by-Step Guide for Engineering Leaders
The audit framework that engineering leaders print out and bring to their quarterly review. Vendor-neutral, step-by-step, with specific actions at each stage. Typical timeline: 2-4 weeks.
The 6-Step Audit Process
Inventory Everything
2-3 daysCreate a complete list of every tool, service, and subscription in your stack. Pull data from SSO provider, expense reports, credit card statements, cloud billing consoles, and procurement records. Do not rely on any single source. The goal is to find the shadow IT that nobody tracks.
Action Items
- Export SSO application list with last login dates
- Pull all recurring charges from corporate credit cards and expense tools
- Export cloud provider service lists from AWS/GCP/Azure consoles
- Survey team leads: ask each manager to list tools their team uses daily
- Check app store purchases on company-managed devices
Categorize and Assign Ownership
1-2 daysGroup every tool into categories (infrastructure, CI/CD, monitoring, security, collaboration, data platform, productivity). Assign an owner to each tool: this is the person responsible for the contract, the renewal, and the decision to keep or cut it.
Action Items
- Create categories that match your stack layers
- Assign a single owner (not a team, a person) to each tool
- Record contract renewal dates and terms for every subscription
- Flag tools with no clear owner for immediate review
Measure Usage
3-5 daysFor each tool, determine actual usage. The goal is to answer: is this tool actively used, and by how many people? Tools with less than 50% utilization are candidates for downsizing. Tools with less than 10% utilization are candidates for elimination.
Action Items
- Pull SSO login frequency data for the last 90 days
- Request usage reports from vendors (most enterprise tools provide admin dashboards)
- For cloud resources: check CPU utilization, memory usage, and API call volumes
- For SaaS tools: compare active users to licensed seats
- Survey teams on tool criticality (critical, useful, rarely used, never used)
Calculate True Cost of Ownership
2-3 daysFor each tool, calculate the total cost including hidden costs. The subscription fee is just the start. Add training time, maintenance burden, integration effort, and the cost of context-switching between tools.
Action Items
- List subscription or usage cost per month
- Estimate engineering hours spent maintaining or administering the tool
- Factor in training cost for new hires
- Calculate integration maintenance cost (API connections, data syncs)
- Apply the hidden cost multiplier (typically 1.3x to 1.5x for complex tools)
Identify Redundancy and Waste
1-2 daysCross-reference your inventory to find overlapping tools, unused licenses, and tools that can be consolidated. Look for tools that solve the same problem for different teams.
Action Items
- Map tools that overlap in functionality
- List unused licenses by tool (seats assigned but not active for 30+ days)
- Identify tools that auto-renewed without review
- Find contracts that are up for renewal in the next 90 days (negotiation window)
- Calculate total waste: unused licenses + duplicate tools + unreviewed renewals
Make Decisions and Act
1-2 daysFor each tool, make one of four decisions: keep as-is, downsize (reduce licenses), consolidate (merge with another tool), or cut (cancel entirely). Then create an execution timeline.
Action Items
- Keep: no action needed, schedule next review
- Downsize: reduce license count to match actual usage (plus 10% buffer)
- Consolidate: pick the winner, create migration plan, set deadline
- Cut: initiate cancellation, ensure data export if needed
- Create a 30/60/90-day execution timeline with owners for each action
Audit Spreadsheet Template
Use these columns to track every tool in your stack. This becomes your single source of truth for the audit and for ongoing governance.
| Column | Description |
|---|---|
| Tool Name | The product or service name |
| Category | Infrastructure, CI/CD, monitoring, security, collaboration, data, productivity |
| Owner | The person (not team) responsible for this tool |
| Annual Cost | Total annual subscription or usage cost |
| Contract End | When the current contract expires |
| Auto-Renew? | Yes/No. If yes, note the cancellation deadline |
| Licensed Seats | Number of seats purchased or allocated |
| Active Users (90d) | Number of users who logged in within the last 90 days |
| Utilization % | Active users / licensed seats |
| Alternative | Competing tool or open-source option |
| Decision | Keep / Downsize / Consolidate / Cut |
| Notes | Any relevant context for the decision |
Vendor Negotiation Playbook
Once you know what to cut or renegotiate, here is how to approach vendor conversations.
Time it right
Start negotiation 60-90 days before renewal. Vendors are most flexible when they risk losing you. Starting too late limits your leverage.
Get competitive quotes
Before negotiating, get pricing from 2-3 alternatives. You do not need to switch; you need evidence that you could. Vendors respond to credible alternatives.
Lead with usage data
Show the vendor your actual utilization. If you are using 60% of your licenses, ask to right-size. Vendors prefer to reduce seats and keep the customer than lose the deal entirely.
Ask for multi-year discounts
If you plan to stay, commit for 2-3 years in exchange for 15-30% discount. This is the easiest concession for vendors to make because it guarantees their revenue.
Request payment flexibility
Annual upfront payment often gets 5-10% additional discount. Quarterly payments can ease cash flow if needed.
Expect 15-30% savings
A well-prepared negotiation with competitive quotes and usage data typically achieves 15-30% savings. Exceptional negotiations with strong alternatives can reach 40%.