ai-roi-audit
Audit whether the organisation's AI spend actually paid — measured against baselines, not vendor math or vibes. Use when a CFO asks what the AI tools returned, when renewing AI contracts, when consolidating overlapping AI subscriptions, or to build the measurement plan before the next spend. Produces an ROI audit with per-tool verdicts (keep/consolidate/cut), the honest-measurement method behind each number, and a baseline plan for whatever can't be scored yet. To forecast ROI before an investment use roi-estimator; this skill measures what already happened.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/ai-roi-audit && cp -r /tmp/ai-roi-audit/exports/openclaw/ai-roi-audit ~/.claude/skills/ai-roi-auditSKILL.md
# AI ROI Audit Skill
Every org now spends real money on AI tools, and most justify it with adoption counts ("80% weekly active!") — which measure enthusiasm, not return. This skill audits what the spend *returned*, using methods that survive a sceptical CFO: baselines, counterfactuals, and quality deltas, with "we can't know yet" said out loud where it's true.
## What This Skill Produces
- A **per-tool verdict table**: keep / consolidate / renegotiate / cut, each with its evidence
- The **measurement behind each number** — method, baseline, confidence — so the audit is checkable
- A **hidden-cost ledger** (the part vendor ROI decks omit)
- A **baseline plan** for every "unknown", so next year's audit has data
## Required Inputs
Ask for (if not already provided):
- **The AI tool inventory with costs**: subscriptions, API spend, seats — and utilisation if known
- **What each tool was bought to do** (the promised outcome, from the original business case if it exists)
- **Available evidence**: usage data, before/after metrics, time studies, quality data, anecdotes (labelled as anecdotes)
- **The decision at stake**: renewal? consolidation? budget defence? (calibrates depth)
## Audit Method
1. **Reconstruct the promise.** Per tool: what outcome justified the purchase — time saved, quality improved, headcount avoided, revenue created? A tool without a stated outcome gets audited against the best-fit guess, *flagged as retrofitted*.
2. **Score with the strongest method the evidence allows**, in descending order of credibility:
- **Natural experiment** — teams/periods with vs without the tool, same work (best available in most orgs)
- **Before/after with baseline** — the metric before adoption vs after, seasonality noted
- **Task-level time study** — 10-20 real tasks timed with/without (cheap to run *during* the audit — do it rather than skip to tier 4)
- **Structured self-report** — users estimating time saved, discounted (self-reported AI savings run ~2× actuals; say so)
Never present a tier-4 number with tier-1 confidence. Every figure carries its method and a confidence label.
3. **Count the hidden costs.** Verification time (humans checking AI output), rework from AI errors that shipped, licence sprawl (seats bought > seats active), integration/prompt-maintenance time, and training time. These come off the gross benefit — an ROI audit that skips them is a vendor deck.
4. **Convert honestly.** Time saved → money only via a stated loaded rate *and* a stated assumption about what the time became (more output? earlier finishes? — different values). "Saved 400 hours" that nobody redeployed is capacity, not cash; label which one you're claiming.
5. **Verdict per tool.** Keep (positive with tier ≤2 evidence) · Consolidate (positive but duplicative — name the overlap) · Renegotiate (positive but mispriced vs utilisation) · Cut (negative or unmeasurable after a fair baseline attempt). Ties break toward the tool with a measurement plan.
6. **Leave the audit better than you found it.** Every "unknown" verdict gets a baseline plan: the metric, how it's instrumented, and the review date. The first audit is mostly this; that's a finding, not a failure.
## Output Format
### AI ROI Audit: [org/team] — [period]
**Total AI spend:** [sum] · **Verdict summary:** [n keep / n consolidate / n renegotiate / n cut / n unknown]
| Tool | Annual cost | Promised outcome | Measured return | Method (tier) | Confidence | Verdict |
|---|---|---|---|---|---|---|
**Hidden-cost ledger:** [verification, rework, sprawl, maintenance — quantified where possible, listed where not]
**The math shown:** [for each material number: baseline, method, conversion assumptions]
**Baseline plan for the unknowns:** [tool → metric → instrumentation → review date]
**One-paragraph CFO summary:** [net position, the two decisions to make, and what will be measurable by next audit]
## Quality Checks
- [ ] Every figure carries its measurement method and confidence — no naked numbers
- [ ] Self-reported savings are discounted and labelled as self-reported
- [ ] Hidden costs appear as line items, not a caveat sentence
- [ ] Time→money conversions state the loaded rate and the capacity-vs-cash claim
- [ ] Every "unknown" has a baseline plan with a date — the audit compounds
## Anti-Patterns
- [ ] Do not use adoption or engagement as return — usage is a cost signal until an outcome moves
- [ ] Do not accept vendor ROI calculators as evidence — reconstruct from your own data or score it unknown
- [ ] Do not average across tools into one triumphant number — the verdict is per-tool or it decides nothing
- [ ] Do not claim headcount avoidance without the counterfactual hiring plan that was actually cancelled
- [ ] Do not punish honest "unknowns" by cutting them reflexively — cut requires a *failed* measurement attempt, not a missing oneDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.