Startup Budget

What a startup budget is

A startup budget is a forward-looking plan of how much money your company will spend, how much it expects to bring in, and how long the cash in the bank will last. For an early-stage company it is less an accounting record and more a survival instrument: it answers the only two questions that matter before you have profit — how fast are we spending, and when do we run out?

Unlike a corporate budget that fine-tunes margins, a pre-seed or seed budget is built around uncertainty. You will not hit your numbers exactly. The point is to size your spending against a realistic plan so you can raise, hire, and ship without driving the bank balance to zero by surprise. (This guide is educational and is not financial, tax, or investment advice.)

Operating expense categories

Most early-stage spending falls into five buckets. Group every line item under one of them so the budget stays readable as it grows:

• People — salaries, contractor fees, payroll taxes, benefits, and employer pension or insurance contributions. For almost every software startup this is by far the largest category.
• Software & tools — the SaaS stack you run the business on: code hosting, design tools, CRM, analytics, email, project management, and any per-seat licences that scale with headcount.
• Marketing & sales — paid acquisition, content, events, sales commissions, and the tools that support them. Early on this is often small and experimental; treat it as a dial you can turn, not a fixed cost.
• Infrastructure — cloud hosting, third-party APIs, data storage, and usage-based vendor fees. These scale with users, so model them as variable rather than flat.
• General & administrative (G&A) — rent or co-working, legal and accounting, insurance, banking and payment fees, and miscellaneous office costs. Small in dollars but easy to forget.

Why headcount is the biggest cost

In a typical software startup, people account for 60 to 80 percent of total spend. That makes headcount the single most important lever in the whole budget. One mid-level engineer can cost more per year than your entire software, infrastructure, and marketing stack combined.

The practical consequence: the fastest way to extend or shorten your runway is to change the hiring plan, not to cancel software subscriptions. When you model the budget, build the headcount plan first — name each role, its start month, and its fully-loaded cost (salary plus the roughly 15 to 30 percent on top for taxes, benefits, and overhead) — and let the rest of the budget follow from it. A hire who starts in month seven costs you five months of salary in a twelve-month plan, so start dates matter as much as salaries.

Gross burn vs net burn

Two numbers describe how fast you are spending, and confusing them is a classic early-stage mistake.

• Gross burn is your total cash going out each month — every expense, regardless of any income. It is the honest picture of how expensive the company is to run.
• Net burn is gross burn minus the cash coming in (revenue, and sometimes grants). It is what actually drains the bank account each month.

Example: if you spend $50,000 a month and collect $12,000 in revenue, your gross burn is $50,000 and your net burn is $38,000. Investors usually ask about net burn because it drives runway, but you should track both — gross burn shows your true cost base, and a company that talks only about net burn can hide a bloated cost structure behind early revenue.

Calculating runway

Runway is the number of months you can operate before the cash runs out, assuming spending continues at roughly the current rate:

Runway (months) = Cash in the bank / Net monthly burn

If you have $456,000 in the bank and burn $38,000 net per month, your runway is about 12 months. The honest version uses your average net burn over the coming months rather than a single month, because burn usually rises as you hire. A common planning rule is to start raising your next round when you have 6 to 9 months of runway left, since fundraising itself takes time and a near-empty bank weakens your negotiating position.

Scenario planning and common mistakes

A single budget is a guess. Build at least two or three versions so you are not caught flat-footed:

• Base case — your honest, most-likely plan.
• Downside case — revenue comes in slower and a hire or two slips; what does runway look like, and where would you cut?
• Upside case — you raise or grow faster; what would you accelerate, and what would it cost?

Common mistakes to avoid:

• Forgetting fully-loaded headcount cost — budgeting base salary only, then being surprised by payroll taxes, benefits, and equipment.
• Treating variable costs as fixed — cloud and API bills grow with usage; a flat line understates burn.
• Being over-optimistic on revenue — model conservatively; surplus is a pleasant surprise, a shortfall is an emergency.
• No buffer — leaving zero contingency means one slipped invoice or surprise bill breaks the plan.
• Setting it and forgetting it — a budget that is not revised as reality changes stops being useful within a quarter.