Back to blog
Methodology·10 min read

How to Audit Your AI Stack in One Afternoon

Why a structured audit matters

The difference between "reviewing your AI tools" and "auditing your AI stack" is methodology. A review is subjective — you look at each tool and decide if it "feels" worth it. An audit is systematic — you apply consistent criteria, collect data, and produce documented recommendations.

This matters because subjective reviews are influenced by who's loudest in the room, who adopted the tool first, and who has the most emotional attachment to it. An audit produces the same result regardless of office politics.

The five-phase process

Phase 1: Inventory (30 minutes)

Open a spreadsheet. For every AI tool your business uses, capture:

  • Tool name
  • Monthly cost
  • Number of licensed users vs. active users
  • Primary use case (one sentence)
  • Who owns the subscription

Include shadow AI — tools people are expensing or paying for personally and using for work. These are often the most interesting findings.

Phase 2: Baseline (varies)

For each tool's primary use case, document what the process looked like before AI:

  • How long did the task take?
  • What was the error rate or revision rate?
  • What was the output volume?
  • What did it cost (in time or money)?

If you don't have historical data, estimate conservatively. A rough baseline is better than no baseline.

This is the step most teams skip entirely. It's also the step that makes everything else possible. Without baselines, your audit produces opinions. With baselines, it produces numbers.

Phase 3: Evaluate (1-2 hours)

For each tool, score it on the five evaluation criteria:

  1. **Task-AI fit** (1-5): Is this the right kind of task for AI?
  2. **Adoption** (1-5): What % of intended users actually use it?
  3. **Impact** (1-5): Is there measurable improvement vs. baseline?
  4. **Alternative cost** (1-5): Is this tool the best option for this job?
  5. **Risk** (1-5): What's the dependency risk if this tool disappears?

A weighted average produces a score per tool. Tools scoring below 3.0 are candidates for action.

Phase 4: Decide (30 minutes)

Based on scores and your judgment, assign each tool one of four labels:

  • **KEEP** — Scoring above 3.5, clear value, keep as-is
  • **OPTIMIZE** — Scoring 2.5-3.5, potential exists but implementation needs work
  • **REPLACE** — Low score but the underlying need is real; find a better tool
  • **CUT** — Low score and the need is questionable; cancel

Phase 5: Plan (30 minutes)

Document your decisions and create a 30/60/90 day plan:

  • **30 days**: Cancel CUT tools, start REPLACE evaluations
  • **60 days**: Implement OPTIMIZE changes, trial replacement tools
  • **90 days**: Re-evaluate OPTIMIZE tools after changes

What this afternoon audit produces

At the end, you have:

  • A complete inventory of your AI stack
  • A cost baseline (total spend, per-user spend)
  • A scored evaluation of each tool
  • Clear keep/optimize/replace/cut decisions
  • A 90-day action plan

That's more than most organizations have after months of "thinking about AI strategy."

Going deeper

This article gives you the process. The AI Automation Audit System gives you the tools: pre-built spreadsheets with scoring formulas, ROI calculators, decision matrices, report templates, and a methodology guide that goes deeper than what fits in a blog post.

But the process above is enough to start. Try it this week.

Liked this? Get more by email.

Practical AI evaluation insights. No spam.