Portfolio Demand vs Capacity View
Build an internal tool that rolls up resource demand across all your projects by role and compares it to your real capacity month by month, so you can see exactly where you've promised more work than you can staff.
A login-protected portfolio dashboard that aggregates resource demand by role and period, highlights the months and roles where demand exceeds capacity, lets you run a simple add/defer-a-project what-if, requires your resource/PMO lead to approve the view before it's used for planning, and exports the result as a clean CSV.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- Your per-project resource demand and your capacity-by-role numbers in a spreadsheet or CSV (no system integration required)
The problem this kills
You run a portfolio of projects, and every project manager swears their plan is fully staffed. But nobody is adding it all up. Three projects all need a senior data engineer in October. Two more lean on the same QA lead in Q1. The numbers live in five different spreadsheets, each with its own column names, and reconciling them by hand takes a day you don't have - so you don't, and you find out you're over-committed when a delivery slips.
The result is the worst kind of surprise: a capacity crunch you could have seen coming months earlier. You commit to work you can't actually staff, then scramble to hire, borrow, or descope under pressure.
This tool does the adding-up for you. It pulls every project's demand into one place, lines it up against what your teams can actually deliver, and shows you the exact months and roles where you've written checks your headcount can't cash.
What you'll build
A simple, login-protected web dashboard for your PMO. You import two things - a list of resource demand from each project (which role, how many hours, over what dates) and your capacity by role (how many people-hours each role can deliver per period). The tool aggregates demand by role and time period, compares it to capacity, and paints a clear picture of where you're green, where you're tight, and where you're over-committed.
It handles the messy reality of real portfolios: part-time and split allocations are summed correctly, the same project/role/period can't be double-counted, and you can run a quick what-if - "what happens to October if we add this new project, or defer that one?" - without touching your source data.
Before any view gets used for planning, your resource or PMO lead reviews the demand-vs-capacity gaps and approves it. And you can export the whole portfolio view as a CSV for your steering deck or your existing planning system.
What's inside the Implementation Plan
The plan is a single file you paste into an AI coding agent (Claude Code), and it builds the tool with you step by step.
It opens by interviewing you about your business - how you track resource demand today, which roles and skills you plan by, the exact column names and conventions in your spreadsheets, your typical and peak project counts, how you define a "period" (month, sprint, quarter), and the edge cases that always trip up portfolio math (part-timers, shared resources, contractors, ramp-up). It reads back a short tailored spec and waits for your thumbs-up, so what you build fits your portfolio - not some generic template.
From there it walks you through standing up the database, the import screens for demand and capacity, the aggregation and over-demand highlighting, the what-if scenario tool, the approval gate, and the CSV export - each step ending with a ready-to-paste prompt.
The governance it includes (this is the point)
This isn't a throwaway spreadsheet macro. The plan builds in real controls from the start:
- Login so only your team can open the tool.
- Row-level security so each organization only ever sees its own portfolio data.
- A complete audit trail - who imported what, who ran which scenario, who approved which view, and when.
- A human-in-the-loop approval gate - the tool aggregates and flags the gaps, but your resource/PMO lead must review and approve a view before it counts as the planning baseline.
- Duplicate guards so the same project/role/period demand can't be imported twice and quietly inflate your numbers.
Who it's for
Portfolio managers, resource directors, PMO leads, and delivery executives who need one trustworthy picture of demand against capacity across many projects - and who are tired of stitching it together by hand.
You've got this - paste the first prompt and let the agent interview you.