Automation wins and cost savings

Document efficiencies and tool consolidations quantified by money saved. Use this to track wins from vendor reviews, seat optimizations, and automation (e.g. replacing one tool with another, cutting unused licenses).

Related: tools snapshot) — full tool list, owners, costs, and optimization status as of the last review.


How to log a win

For each entry, capture:

FieldDescription
WinShort title (e.g. “Loom → Zoom Clips”, “ChatGPT Team seat reduction”)
BeforeTool(s) / cost / behavior before the change
AfterTool(s) / cost / behavior after
Annual savings$ saved per year (or one-time if applicable)
DateWhen the change took effect (YYYY-MM-DD)
NotesHow we did it, source of truth (e.g. software review, usage report)

Recorded wins

1. Loom cancelled — async video via Zoom Clips

FieldValue
WinLoom cancelled; everyone uses Zoom Clips for async video
BeforeLoom: 5 seats, ~1,200/yr
AfterZoom Clips (included in existing Zoom); no separate Loom cost
Annual savings~$1,200
Date2026-03-06 (per software review: “Canceled effective on Mar 6, 2026”)
NotesFrom Feb 2026 software review; Loom row set to Inactive, Action = Cancel.

2. ChatGPT Team — seat reduction (pending)

FieldValue
WinReduce ChatGPT Team seats based on usage (zero-usage and low-usage users removed)
BeforeTBD — current seat count and annual cost from billing
AfterTBD — reduced seats after removing users identified by OpenAI Team CSV report (zero-usage enabled users, optional low-usage review)
Annual savingsTBD — fill after cuts (e.g. $30/seat/month × seats removed × 12)
DateTBD
NotesUsage exports and scripts/openai-team-csv-report.ts used to identify candidates (e.g. Zoran Selinger, Pranav, Elizah Pineda — zero usage; Greg Stoutenburg, J, Sheshu, Ashwini — low usage). Remove from workspace then reduce seat count in ChatGPT Business billing.

Adding new wins

  1. Append a new numbered section under Recorded wins.
  2. Use the table format above (Win, Before, After, Annual savings, Date, Notes).
  3. If the win comes from a vendor/software review, note the review date and that the snapshot lives in knowledge/company/finance/software-review-YYYY-MM-DD.csv (or the current filename).
  4. When you run the software review again, add a new CSV with the review date and optionally add a row here pointing to it.