Studio Runway Planner
Last reviewed
BeginnerWhat you'll learn
~35 min- Work with an AI agent in plan mode to build a React cashflow planning application
- Model monthly expenses across legal, salaries, contractors, tools, and marketing categories
- Visualize burn rate over time with Chart.js line and bar charts
- Compare funding scenarios (self-funded, Kickstarter, publisher) and calculate runway for each
What you’re building
You have the market analysis, the financial projections, and the storefront economics. Now the scariest question: how long can you actually operate before the money runs out?
Making a game is not a single transaction. It is 24-36 months of payroll, contractor invoices, software licenses, legal fees, and marketing spend. Every month the bank account gets smaller. The number of months between “we start” and “the account hits zero” is your runway. And if your runway is shorter than your development timeline, you are dead before you ship.
Right now, figuring this out means a spreadsheet with 36 rows and a lot of guessing. You are going to build a React application that makes the runway calculation visual, interactive, and scenario-aware. Input your team size, salaries, contractor costs, and overhead. See a month-by-month burn chart. Toggle between funding scenarios — self-funded, Kickstarter, publisher deal — and watch the runway extend or shrink in real time.
Every game studio that shut down mid-development ran out of runway. Not ideas, not talent, not market opportunity. Cash. The studios that survive are the ones that know their number — “we have 18 months of runway at current burn” — and plan accordingly. This tool gives you that number, updated in real time, with scenario modeling so you can see exactly what happens if you add a team member or lose a funding source.
By the end of this lesson you will have a React application with an interactive cashflow planner. It includes expense categories (legal/rights, salaries, contractors, tools/licenses, marketing), monthly burn rate visualization using Chart.js, three funding scenario comparisons, and a prominent runway indicator that answers the core question: “At this burn rate, you have X months before you need revenue.”
Fixed and variable expenses projected over time, with multiple funding scenarios modifying the starting balance and income events. This pattern appears in startup financial planning, project budgeting, and personal finance tools. The key technique is separating expense modeling from funding modeling so you can mix and match scenarios.
The showcase
Here is what the finished planner gives you:
- Expense categories: Legal/Rights Acquisition (one-time), Team Salaries (monthly, per-role), Contractor Costs (variable, per-milestone), Tools & Licenses (monthly), Marketing (ramping toward launch)
- Team builder: Add roles with monthly salary — Lead Developer, Artist, Sound Designer, Producer, QA. See total monthly payroll update in real time
- Monthly burn chart: Chart.js bar chart showing expenses by category per month for 36 months, with a cumulative cash line overlay
- Funding scenarios: Three toggleable panels:
- Self-funded: Starting capital input, no external money, pure runway countdown
- Kickstarter: Campaign goal, estimated net after fees (92% of gross), funds arrive at month 3
- Publisher deal: Advance amount, milestone payments schedule, revenue share percentage post-launch
- Runway indicator: Large, prominent display: “At current burn rate: X months of runway.” Color-coded green (18+ months), amber (12-18), red (under 12)
- Break-even overlay: If you input expected launch revenue (from your storefront simulator), the chart shows when cumulative revenue crosses cumulative expenses
- Export: Download the full cashflow model as a CSV for your accountant or co-founder
Before you start
If your agent is still open from the previous lesson, exit that session first (/exit or Ctrl+D). Create a clean folder for this lesson and open it:
mkdir -p ~/retro-remake/08-runway-planner && cd ~/retro-remake/08-runway-plannerIn Windows PowerShell:
mkdir ~/retro-remake/08-runway-planner; cd ~/retro-remake/08-runway-plannerOr open the folder directly in your desktop agent app. Start your agent the way Workbench Setup showed.
Switch to plan mode
Switch to Plan mode inside your session (Shift+Tab, /plan, or the mode picker) so the agent confirms your monthly expense categories, funding inflow timing, and first-negative-month runway rule before generating files.
The conversation
Say what you want
Ask for the studio cashflow and runway planner in plain English:
I am planning cashflow for a retro remake studio. Help me build an interactive web app called runway-planner that models 36-month team and milestone expenses across three funding scenarios with a burn chart. Ask me what you need first.Answer its questions
Guide the agent’s questions with the expense categories, funding scenarios, and strict cashflow rule:
| If it asks | You might say |
|---|---|
| What expense categories should be pre-filled? | One-time IP/legal/dev-kit costs, monthly team salaries with a 1.3x benefits multiplier, monthly overhead, ramping marketing, and contractor milestones. |
| What are the three funding scenarios to compare? | Self-Funded ($250K start), Kickstarter ($800K goal yielding 92% net in month 3 plus $50K start), and Publisher Deal ($2M milestones). |
| How should runway end be calculated? | At the first negative monthly balance using only funding received by that month; later receipts never erase earlier shortfalls. |
| What should the burn chart and runway indicator show? | 36-month stacked expense bars, a cumulative cash line, and a green (18m+), amber (12-18m), or red (under 12m) runway badge. |
| What interactive controls and exports should it include? | Inline expense editing, team role builder, month-by-month cashflow table highlighting negative months, and a CSV export button. |
ℹReference notes to hand the agent (or check against)click to expand
Pre-fill src/data/defaults.js with these illustrative, editable planning defaults (replace them with quotes and hiring estimates before making funding decisions):
-
One-Time Expenses:
- IP Rights / Licensing:
$150,000(month 1) - Legal Setup (LLC, contracts):
$25,000(month 1) - Dev Kits (PS5 + Xbox):
$45,000placeholder (month 2; confirm real costs with platform holders)
- IP Rights / Licensing:
-
Monthly Team (base salaries; apply the
1.3xbenefits/taxes multiplier once):- Lead Developer / Technical Director:
$12,000/mo(months 1-24) - Gameplay Programmer:
$10,000/mo(months 1-24) - 3D Artist (characters):
$9,000/mo(months 1-24) - 3D Artist (environments):
$9,000/mo(months 1-24) - Animator:
$8,500/mo(months 1-24) - Sound Designer / Composer:
$7,500/mo(part-time months 1-12, full-time 13-24) - Producer / Project Manager:
$9,000/mo(months 1-24) - QA Tester:
$5,000/mo(starts month 12)
- Lead Developer / Technical Director:
-
Monthly Overhead:
- Game Engine License (Unreal royalty or Unity seats):
$500/moplaceholder (check current engine terms) - Software tools (Blender, Substance, Jira, etc.):
$800/mo - Cloud services (builds, CI/CD, storage):
$400/mo - Office / coworking space:
$2,000/mo - Insurance (business liability):
$300/mo
- Game Engine License (Unreal royalty or Unity seats):
-
Marketing (ramping schedule) & Contractor Milestones:
- Marketing: Months 1-12
$500/mo, Months 13-18$2,000/mo, Months 19-24$5,000/mo, plus$15,000launch burst in Month 24. - Contractors: Concept art
$15,000(month 2), Voice acting$25,000(month 18), QA external testing$10,000(month 20) and$10,000(month 23), Localization$20,000(month 22).
- Marketing: Months 1-12
-
Three Funding Scenarios & Cashflow Rule:
- Rule for all scenarios: Runway ends at the first negative monthly cash balance, using only funding received by that month and all scheduled expenses. Later receipts do not erase an earlier funding gap.
- Self-Funded:
$250,000starting capital, no external inflows. - Kickstarter:
$800,000campaign goal; subtract5%Kickstarter fee and roughly3-5%payment processing (8%total perhttps://help.kickstarter.com/hc/en-us/articles/115005028634-What-are-the-fees) for$736,000net arriving in month 3, plus$50,000personal starting capital in month 1 (flag any cash shortfall in months 1-2 before campaign proceeds arrive). - Publisher Deal:
$2,000,000total advance paid in milestones:25%at signing (month 1),25%at alpha (month 12),25%at beta (month 18),25%at gold (month 24), with40%post-launch revenue share noted. Check that each milestone arrives before cash runs out.
Read the plan
Before approving the agent’s plan, check four things:
- First-negative-month runway rule: Runway ends at the very first month where cumulative cash goes negative based on funds received by that month. In the Kickstarter scenario (
$50Kin month 1,$736Knet arriving in month 3), the planner must flag the month-1/month-2 shortfall rather than dividing total funding by average burn. - Benefits multiplier applied once: Team payroll multiplies active base salaries by the configurable benefits multiplier (
1.3xdefault) once, respecting part-time and delayed-start roles (Sound Designer part-time months 1-12, QA starting month 12). - Dual-axis Chart.js burn chart: Stacked monthly expense bars (salaries, contractors, tools, marketing, legal) appear on the left axis with cumulative cash remaining on the right axis and a vertical marker where cash hits zero.
- Interactive scenario & role editing: Toggling line items or removing a role (such as one 3D Artist) immediately updates monthly payroll, the burn chart, the runway indicator, and the CSV export.
If the plan calculates runway as total_committed_funding / average_monthly_burn, steer it before approving:
End runway at the first negative monthly balance using only funds received by that month, so later inflows never erase an earlier shortfall.Approve the plan once all four items are in place, and ask the agent to save a Git checkpoint after the app starts cleanly.
The pre-filled expense data is an illustrative estimate for a 24-month mid-budget action game remake with a team of 7-8 people. The salary figures and overhead lines are editable placeholders; replace them with your own quotes and hiring plan.
What you get
After the AI finishes generating, the project folder structure looks like this:
runway-planner/ package.json index.html src/ App.jsx components/ ExpenseEditor.jsx TeamBuilder.jsx BurnChart.jsx FundingScenarios.jsx RunwayIndicator.jsx CashflowTable.jsx data/ defaults.js styles/ planner.cssFire it up
Ask your agent to install what is needed and start the runway planner:
Install everything needed, start the runway planner, and share the local URL so I can test the funding scenarios.If you prefer to run the commands yourself in a terminal:
cd runway-plannernpm installnpm run devOpen the dev server URL. You should see the planner with all default expenses pre-filled, the burn chart showing 24 months of stacked bars, and the runway indicator showing the self-funded scenario (which will be red — $250K does not last long against the default base salaries times the benefits multiplier, plus overhead).
If something is off
| Problem | Follow-up prompt |
|---|---|
| Burn chart not rendering | The monthly burn chart area is blank. Make sure the chart renders 36 months of stacked expense bars on the left axis and the cumulative cash balance line on the right axis. |
| Funding scenario tabs don’t switch | Clicking the Kickstarter or Publisher tabs does not change the numbers. Make switching tabs display that scenario's funding inputs and recalculate the cash balance, chart, and runway badge. |
| Monthly burn doesn’t update when editing expenses | I changed a salary amount, but the burn chart and runway badge stayed the same. Connect the team builder and expense edits directly to the cashflow calculation so every chart and table updates live. |
| CSV export is empty or malformed | The CSV download button produces an empty file. Include a header row and all 36 months of category expenses, funding inflows, net burn, and cumulative cash balance in the downloaded CSV. |
How it works (the 2-minute version)
-
All expense data lives in React state at the top level. App.jsx holds the master list of expenses, team roles, and funding scenario parameters. Every child component reads from this state and calls setter functions to modify it. When anything changes, everything recalculates.
-
Monthly burn is calculated by iterating month 1 through 36. For each month, the calculator sums: active salaries (checking each role’s start/end month), any one-time costs scheduled for that month, contractor milestones, tools overhead, and marketing at the appropriate ramp level. This per-month array drives both the chart and the table.
-
The burn chart uses Chart.js with a dual-axis setup. Stacked bars on the left Y axis show expense categories. A line on the right Y axis shows cumulative cash remaining. The visual intersection where the line hits zero is your runway — you can see it without reading a single number.
-
Funding scenarios modify the starting balance and inject cash events. Self-funded is simple: starting capital minus monthly burn. Kickstarter adds a lump sum at month 3. Publisher deal adds milestone payments at months 1, 12, 18, and 24. The runway calculation is just “how many months until the balance goes negative.”
-
The runway indicator is a derived value, not a stored one. It recalculates every time any expense or funding parameter changes. This means you get instant feedback: “If I cut one artist, my runway extends by 2 months.” That feedback loop is the whole point of the tool.
🔍The funding gap is the hardest conversationclick to expand
Let us be honest about the numbers in the default scenario:
- Self-funded at $250K: A few months of runway. Not viable for a 24-month project. You would need to keep a day job and work on the game part-time, which means the timeline stretches to 4-5 years.
- Kickstarter at $800K: The default scenario has a cash shortfall before campaign funds arrive in month 3. Reduce costs or secure bridge funding before relying on campaign proceeds, and read runway from the monthly balances. Campaign proceeds do not establish a project’s total development cost.
- Publisher at $2M: Check that each milestone payment arrives before cash runs out; total committed funding alone does not establish runway. You also give up 40% of revenue post-launch. On a hypothetical $30M gross, that is $12M going to the publisher.
The right answer depends on your risk tolerance and your financial situation. The tool does not tell you which to pick. It shows you what each path looks like in cold numbers so you can make an informed decision.
Customize it
Add an early access revenue model
Many indie games launch into early access to generate runway (for example, launching in month 15 at $20 with 5,000 initial monthly units decaying 10% per month after Steam’s 30% cut):
Add an Early Access toggle to the funding scenarios with inputs for launch month, price, starting monthly units, and 10% monthly decay, plotting net EA revenue on the burn chart and recalculating runway.Add a salary planning panel
Compare your role salaries against illustrative, editable planning ranges (Lead Dev $8.3K-$13.3K/mo, Gameplay Programmer $6.7K-$11.7K/mo, 3D Artist $5K-$10K/mo, Animator $4.6K-$9.2K/mo, Sound Designer $4.2K-$8.3K/mo, Producer $5.8K-$10.8K/mo, QA $3.3K-$5.8K/mo; these are not salary survey data, so replace them with current quotes or a cited survey for your hiring location):
Add an expandable Salary Planning Ranges panel to the team builder that compares each role's monthly salary against editable min/max planning bands and shows whether it sits below, within, or above range.Add a “plan B” trigger system
Decide in advance when to pivot:
Add a Decision Points section where I can set a minimum runway threshold that triggers Plan B options (cutting roles, switching to contractors, bridge funding, or early access) and marks the trigger month on the chart.Try it yourself
- Open your agent in a clean folder, switch to plan mode, describe the runway planner, and approve the plan.
- Ask your agent to start the app (or run
npm install && npm run dev). Look at the self-funded scenario first. Feel the red indicator. $250K runs out fast. - Switch to the Kickstarter scenario. Check whether personal capital covers expenses before campaign funds arrive in month 3. With the default inputs, it does not.
- Switch to the publisher scenario. Find the first negative monthly balance and check whether each milestone payment arrives before it.
- Go to the team builder and remove one of the two 3D artists. Watch the monthly burn drop by $11.7K with the default 1.3 benefits multiplier and the runway extend across all scenarios. This is the core tradeoff: smaller team means longer runway but slower development.
- Look at the cashflow table. Find the months where contractor costs spike (concept art, voice acting, localization). Those are the months where your burn jumps. Plan for them.
- Export the CSV and open it in a spreadsheet. This is what you would share with an accountant, a co-founder, or an investor.
Key takeaways
- Runway is the constraint that kills studios. Not bad ideas, not lack of talent. Running out of money before the game ships is a common way indie and mid-budget studios fail.
- Self-funding a studio burn rate requires serious personal capital. With the default inputs (base salaries times the benefits multiplier, plus overhead), $250K of self-funding lasts only a few months; read the exact figure off the planner. Few people have the savings to fund two years alone, which is why external funding matters.
- Campaign proceeds do not establish runway. Check receipt dates against scheduled expenses; the default Kickstarter scenario has a funding gap before campaign funds arrive.
- Publisher advances require cashflow planning. Check payment timing and the contract’s revenue-share terms. A revenue share does not itself transfer equity or guarantee funding through launch.
- The team size to burn rate relationship is the most important lever. Each role adds its salary times the benefits multiplier to monthly burn. Every person you remove extends runway by weeks or months. The tool makes this tradeoff visceral.
What’s next
You have the market analysis, the financial projections, the storefront economics, and the cashflow plan. The business case is built. Now it is time to think about the actual game. In the next lesson, you will build The Mechanics Breakdown — a CLI tool that takes gameplay observations from watching BloodRayne footage and converts them into structured mechanical specifications. Combat combos, blood rage meter, aura vision, enemy patrol patterns — all documented in a format you could hand to a game designer or feed into an engine prototype. The business planning phase is done. The game design phase starts now.