Agency Cash Runway Forecasting: A practical framework for hiring and spending decisions

Operational decision first: before you hire, lock in the answer to two questions with numbers — how your cash balance moves over the next 90 days and how that changes if you add the headcount or contractor costs you’re planning. If those projections still leave you unsure, you don’t have a runway problem so much as an information problem. Run a tight, scenario-driven forecast and you’ll convert uncertainty into a clear choice: hire now, stage the hire, or defer.

• What to include (concrete inputs)
• Opening cash balance: bank and highly liquid accounts you will rely on in the period.
• Recurring revenue (MRR/ARR equivalent): retainer revenues or ongoing subscriptions you can reasonably expect each month, and the cadence those payments arrive in.
• Projected project revenue and timing: expected new project starts, milestone invoices, and when cash will arrive (not when revenue is recognized).
• Outstanding invoices and collection timing: list open invoices and the realistic collect-by date. For forecasting, use the expected payment date rather than invoice date.
• Payroll and contractor costs: payroll schedules, employer-side costs you fund (e.g., contractor gross payments, benefits if applicable), and effective dates for any new hires.
• One-off spends and commitments: software subscriptions, upfront vendor deposits, marketing spends tied to campaigns, or office costs.
• Tax reserve planning: an estimate you set aside for taxes and withholding; treat this as a planning input you control (RunwayStack’s Tax Reserve Planning feature is useful for modeling this), but get professional tax advice for exact obligations.
• Currency and FX timing: if you invoice or pay in other currencies, include expected conversion timing and possible delays (Multi-Currency matters when receipts and payables are mismatched).
• Burn classification: separate fixed (salaries, rent) from variable costs (contractors, ad spend) so you can test what to cut when needed.

• Tradeoffs founders actually make
• Revenue timing vs. revenue amount: large project fees can look attractive on paper but provide less runway value if invoices are delayed. Prioritize the certainty of timing when runway is the decision lever.
• Hire vs. contractor: contractors are flexible but often cost more per hour and require management overhead. A hire increases fixed burn but can lower per-unit cost and improve retention. Model both as separate scenarios rather than an either/or intuition.
• Conservative collections assumptions vs. aggressive growth bets: model both. Conservative assumptions reduce the chance of surprise but can lead to overly cautious decisions; optimistic assumptions can justify earlier growth but increase risk.
• Tax reserve as a liquidity decision: withholding too little inflates available cash today; reserving too much constrains growth. Treat the tax reserve number as a planning lever you can adjust while seeking professional tax guidance.

A lightweight scenario framework (5 steps) 1) Choose horizon and cadence. For hiring decisions pick 90 days as the immediate operational horizon and 12 months for strategic staffing decisions. Use weekly cadence for 90-day horizon and monthly cadence for 12-month. 2) Ingest base-case inputs. Enter opening cash, recurring revenue by period, expected receipts for project income, scheduled payroll/contractor payouts, and explicit one-offs. 3) Define 2–3 scenarios. At minimum: conservative (collections delayed, new revenue delayed), base (most likely timing), and upside (payments arrive on time and new wins land). For hiring, create a variant that includes the new hire’s full cost and a contractor-alternative variant. 4) Run the cash balance forward per period. For each period: starting cash + receipts - payments - tax reserve movement = ending cash. Track when (if) any scenario’s balance becomes constrained relative to planned obligations. 5) Make the decision rule operational. Translate model results into action thresholds like: if the hire scenario causes a crossing of a critical period where you cannot meet payroll without a contingency, delay the hire or choose contractors. If the base-case forecast covers obligations and the upside improves gross margin materially, proceed. The point is to use the model to trigger operational contingencies, not to create false precision.

• Hypothetical arithmetic example (labelled as hypothetical)
• Hypothetical: opening cash $50,000. Monthly recurring revenue $20,000 arriving mid-month. New hire increases monthly payroll cost by $8,000 in month 1. Expected project receipts this month $10,000 paying in 45 days.
• Hypothetical arithmetic: Month 1 ending cash = 50,000 + 20,000 + 10,000 (if collected) - existing payroll - new hire payroll - other expenses. If you model the project receipt instead as arriving in month 2, the Month 1 ending cash falls by $10,000, which may change the hire decision. This is only an illustration of timing effects; use your own numbers as inputs to make the decision.

• Practical tips to reduce model noise
• Use actual bank and accounting exports for Transactions/Expenses and Recurring Revenue where possible to avoid transcription errors.
• Model receipts on expected payment dates, not invoice issuance dates. If a client historically pays late, model their expected date accordingly.
• Break hires into phased costs: recruiting fees and ramped salary or partial-time contracting before full-time hire.
• Keep the model small and auditable — three scenarios with transparent assumptions are more actionable than 20 opaque permutations.

• How tooling can help (where RunwayStack fits)
• Automated ingestion of bank transactions and invoices reduces manual entry and ensures your Opening Cash and Transactions/Expenses feed reflects the truth of your accounts.
• A Recurring Revenue module helps separate retainers from project revenue so you can prioritize stable cash.
• A Scenario Simulator lets you flip between hiring and contractor options without rebuilding the whole model and compare cash balances side-by-side.
• Tax Reserve Planning as a line-item makes the liquidity impact of reserving for taxes explicit so you can plan hires with gross and net impacts clearly visible.
• Multi-Currency support simplifies forecasts when clients and contractors operate in different currencies.

• Decision examples (not prescriptive)
• If hiring increases fixed monthly burn and your conservative scenario shows a near-term cash shortfall, prefer contractors or staged hiring until collections improve.
• If your base-case and upside scenarios both absorb the new hire cost with room for one-off shocks, the risk-adjusted case for hiring strengthens. Use the model to articulate the conditionalities: “We’ll hire X if invoiced pipeline converts at Y% and collections meet expected dates; otherwise we’ll extend the timeline.” That makes the decision reversible and measurable.

Next steps and CTA If you want a practical way to turn your assumptions into numbers, try a purpose-built runway calculator that uses your inputs (opening cash, receipts schedule, invoices, payroll/contractors, tax reserve, multi-currency conversions) and produces scenario comparisons you can act on. The free Agency Cash Runway Calculator (uses your assumptions only) is designed for founder-operators who need a quick, auditable view for hiring and spend decisions.

Publish status: PENDING_REVIEW