Training Budget & Vendor Spend Tracker: Stop Overspending Before It Happens
Track every training dollar — vendor courses, conferences, certifications, tuition reimbursement — against budget by department and category, capture spend requests with a real approval gate, and see remaining budget plus cost-per-learner before the money's gone.
A logged-in tool where you load the training budget by department and category, staff submit spend requests, each one is checked against remaining budget, the budget owner approves (over-budget requests are flagged for explicit sign-off), committed and actual spend is recorded, and you see spend vs budget plus cost-per-learner — with a GL-ready CSV export.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your training budget by department and category (a spreadsheet is fine)
- A list of recent spend requests and vendor invoices (CSV is fine)
- Claude Code or any AI coding agent
The problem this kills
Training money leaks. A manager books a $4,000 conference, someone else approves three certifications by email, a tuition-reimbursement claim lands two months later, and a vendor invoice shows up for a course nobody remembers committing to. By the time finance reconciles it all, the L&D budget is 30% over and the only "system" was a spreadsheet that one person owns, edits live, and forgets to update.
The real damage isn't the overspend — it's the blindness. Nobody can answer the questions that matter mid-year: How much of the Engineering training budget is left? What have we actually committed versus what's already been paid? Which vendor is eating the most? What did it really cost us per person to train the sales team? The spreadsheet can't tell you, because committed-but-not-yet-paid spend and actual invoices live in different tabs (or different heads), and there's no gate stopping a request from being approved when the budget's already spent.
A training budget deserves to be a real, governed tool — one that checks every request against what's actually left before the commitment is made, not a workbook you reconcile in a panic at quarter-end.
What you'll build
A simple internal web app for L&D and finance. You load your training budget by department and category — vendor courses, conferences, certifications, tuition reimbursement, whatever buckets you use. Staff submit a spend request: vendor, amount, number of learners, purpose, category, department. The tool instantly checks it against remaining budget (budget minus what's already committed and actual) and shows the requester and the approver exactly where it lands. The budget owner approves — and if a request would push a bucket over budget, it's flagged and requires explicit over-budget sign-off, not a quiet rubber stamp.
Once approved, the spend becomes a commitment. When the vendor invoice arrives, you record the actual against that commitment (matched by invoice number so nothing is double-counted). At any moment you can see spend vs budget by department and category, committed vs actual, cost-per-learner, and cost-per-vendor — and export it all in your finance/GL format. Tuition reimbursement gets its own rules: eligibility, per-person caps, and clawback tracking if someone leaves.
What's inside the Implementation Plan
The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how your training budget is structured, the exact department and category names you use, how requests get approved today, your tuition-reimbursement rules (caps, eligibility, clawback), how you tell committed from actual, and the messy exceptions (multi-year certifications, refunds, cancelled courses, split-department charges). It reads a short tailored spec back to you and waits for your thumbs-up before it builds anything — so the tracker matches your budget structure and approval rules, not a generic template.
From there it walks the agent through the data model, the budget import, the request-and-check flow, the approval gate with over-budget flagging, committed-vs-actual recording, the spend-vs-budget and cost-per-learner views, and a clean GL-ready export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path that imports your budget and requests from a Google Sheet / CSV and produces a GL-ready spend CSV — so you can build and run the whole thing this weekend with no integration to your finance system at all.
The governance it includes (this is the point)
This tool decides how money gets spent, so the controls aren't optional. The plan builds in login so only your team can use it, row-level security so each organization only ever sees its own budgets and requests, a complete audit trail of who requested, who approved, and when, a hard human-approval gate so no spend is committed until the budget owner reviews it against remaining budget (with over-budget requests requiring explicit sign-off), and duplicate guards so the same spend request or vendor invoice can't be processed — or double-counted — twice.
Who it's for
L&D and training managers, enablement leads, and the finance partners who support them — anyone who owns a training budget, tracks it in a fragile spreadsheet, and keeps losing visibility into what's left. If you can describe your budget buckets and how a spend request gets approved today, you can build this.
You've got this — start with the plan, paste the first prompt, and answer the interview. You'll have your budget loaded and your first spend request checked against it before the weekend's out.