Rolling Forecast Builder: Trade Your Static Annual Budget for a Living 12-Month Forecast
Import each month's actuals, let AI swap them into your forecast and re-project the remaining months from updated drivers, see a clean bridge versus the prior version — then your FP&A lead approves, locks, and publishes the new forecast.
A web tool where you import the month's actuals, AI swaps them into the forecast and re-projects the remaining months from your updated drivers, you see a forecast-vs-prior bridge, your FP&A lead reviews and approves, and the tool locks and versions the new forecast and exports it as a clean CSV — always keeping a rolling 12-month window.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- A Resend account (free)
- Your current forecast or annual budget (CSV or Google Sheet)
- A monthly actuals CSV from your GL or ERP
- Your driver / assumption inputs (growth rates, headcount, unit prices)
- Claude Code or any AI coding agent
The problem this kills
A static annual budget is stale by March. You set it in Q4, and the moment the year starts, reality drifts: a big deal slips, headcount comes in late, a price change lands, and the number everyone is "managing to" no longer means anything. So FP&A quietly maintains a shadow re-forecast — in a giant, fragile spreadsheet that one person rebuilds every month-end.
That spreadsheet is where the pain lives. Every month they hand-copy the closed month's actuals over the forecast cells, hope they didn't paste into the wrong column, re-drag the formulas, try to remember which cells were manual overrides they meant to keep, and then email a new tab with no clear record of what changed versus last month or why. There's no version history, no approval, and no audit trail — just a date in the filename. You don't need to live like this, and you don't need to be a developer to fix it.
What you'll build
A simple internal web tool that maintains a living rolling 12-month forecast. Each month, you import the monthly actuals CSV for the month that just closed. The tool swaps those actuals into the forecast (the closed month is now fact, not estimate), then re-projects the remaining months from your updated driver and assumption inputs — growth rates, headcount, unit prices, whatever drives your model. It preserves the manual overrides you intended to keep, rolls the window forward so you always look 12 months ahead, and shows a clear forecast-vs-prior bridge: line by line, what moved, by how much, and how much of that was actuals coming in versus a changed assumption.
Then the human gate: your FP&A lead reviews the refreshed forecast and the bridge, and clicks Approve. Only then does the tool lock and version the new forecast and export a clean CSV in the exact columns your reporting pack and GL expect. Last month's version stays frozen and viewable forever.
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 you forecast today, which system your actuals export from and exactly what its columns are named, your account / cost-center / department coding, the drivers that actually move your model, where you keep manual overrides, your typical and peak line counts, and your messy edge cases — and then it tailors the data model, the re-projection logic, and every later step to your answers. This is not a generic template; the agent reflects a short spec back to you and waits for your thumbs-up before it builds anything. From there it walks the agent through the import-and-swap of actuals, the driver-based re-projection, the override-preservation rules, the forecast-vs-prior bridge, the FP&A review-and-approve screen, the lock-and-version step, and the CSV export — each step with a ready-to-copy prompt. There's also a fallback so you can build the whole thing today even with no API to your ERP.
The governance it includes (this is the point)
This is the number the whole company manages to, so it ships with the controls a finance team needs: login so only your team can use it, row-level security so you only ever see your own organization's forecast, a complete audit trail of who imported, edited, and approved which version and when, a hard human-approval gate so no forecast is locked or published until your FP&A lead signs off, and duplicate guards keyed on period and version so the same month's actuals can't be swapped in twice. Manual overrides are explicitly tracked, not silently overwritten — so an intentional adjustment survives the re-projection and a stale one is flagged.
Who it's for
FP&A analysts, finance managers, and controllers moving from a static annual budget to a living rolling forecast — anyone who currently owns the monthly re-forecast spreadsheet and is tired of hand-swapping actuals and losing the history. If you can describe how your model re-projects after a month closes, you can build this.
You've got this — start with the plan, paste the first prompt, answer the interview, and you'll watch your first closed month swap in and the remaining months re-project the same afternoon.