Burn Rate by Department: The Granular View Most Founders Skip

## The Problem With Single-Number Burn Rate Thinking

We've sat across from hundreds of startup founders during financial reviews, and we see the same pattern repeatedly: they know their total monthly burn rate to the dollar, but they have almost no visibility into where that cash is actually going.

"We're burning $150,000 per month," a founder will tell us confidently. But when we ask which department represents the biggest lever for extending runway, they can't answer.

This is the critical gap in how most startups approach their burn rate runway analysis. A single burn rate number tells you *how fast* you're running out of money. Breaking burn rate down by department tells you *why*—and more importantly, *what you can actually do about it*.

Tracking [burn rate runway](/blog/burn-rate-vs-growth-building-the-right-financial-model-for-your-stage/) as a company-wide metric is table stakes for fundraising conversations. But tracking burn rate by department is what separates founders making intelligent cuts from those making panic-driven decisions that cripple growth.

## Understanding Departmental Burn Rate vs. Gross and Net Burn

### The Difference That Matters

Before diving into departmental analysis, let's clarify what we're actually measuring:

- **Gross Burn**: Total monthly operating expenses (salaries, tools, office, marketing, everything)
- **Net Burn**: Gross burn minus recurring revenue (the actual monthly cash reduction)
- **Departmental Burn**: Gross burn allocated to specific functions (Engineering, Sales, Marketing, Operations, etc.)

Most founders focus on net burn for runway calculations, which is correct for understanding months of runway remaining. But departmental burn rate analysis uses a different lens: it shows you which functions are actually consuming resources.

Here's the practical difference: You might have a net burn of $100,000/month, giving you 10 months of runway on $1M cash. But if Sales is burning $80,000/month and generating only $30,000 in MRR, that's a completely different strategic problem than if Engineering is burning $80,000/month and building a product generating $200,000 in MRR.

One department is a growth investment. The other is a cash drain.

## The Departmental Burn Rate Breakdown

### How to Structure Your Analysis

Start by mapping every cost center to a specific department. Your finance system (or spreadsheet, if you're early) should already do this, but most founders haven't actually looked at it systematically.

Here's the core departments we recommend tracking:

**Engineering & Product**
- Salaries and contractors
- Cloud infrastructure costs (AWS, Vercel, etc.)
- Development tools (GitHub, Jira, deployment platforms)
- Third-party APIs and integrations

**Sales & Business Development**
- Salaries (including commissions and bonuses)
- Sales tools (Salesforce, Outreach, etc.)
- Travel and entertainment
- Sales operations costs

**Marketing**
- Salaries and contractor costs
- Paid advertising (Google Ads, LinkedIn, etc.)
- Marketing tools and platforms
- Content, design, and creative services

**Customer Success & Support**
- Salaries
- Support tools (Zendesk, Intercom, etc.)
- Training and onboarding materials

**Operations & Finance**
- Salaries and accounting services
- Finance tools and software
- HR systems and benefits administration
- Legal and compliance

**Overhead**
- Office rent and utilities
- Insurance
- Equipment and furniture
- Miscellaneous corporate costs

In our work with Series A startups, we typically find that the allocation looks something like this for a SaaS company at $200K-$500K MRR:

- Engineering: 30-40% of burn
- Sales & BD: 25-35% of burn
- Marketing: 10-15% of burn
- Customer Success: 5-10% of burn
- Operations & Finance: 5-8% of burn
- Overhead: 8-12% of burn

But your mix depends entirely on your business model and stage. A PLG company might have 15% in Sales and 20% in Marketing. A sales-driven enterprise startup might have 40% in Sales.

### The Key Insight: Burn Relative to Output

Tracking departmental burn is only useful if you measure it against what each department produces.

**Engineering burn** should be measured against:
- Features shipped per quarter
- Product roadmap completion rate
- Infrastructure costs per user (for scaling efficiency)

**Sales burn** should be measured against:
- New ARR generated
- Customer acquisition cost (CAC)
- Sales efficiency ratio (new ARR ÷ Sales & Marketing spend)

**Marketing burn** should be measured against:
- Cost per lead
- Lead conversion rate
- CAC by channel

For a real example: We had a client burning $45,000/month in marketing (30% of total burn). They were generating $12,000 in new MRR from marketing-sourced leads. That's a CAC payback period of 45 months—completely uneconomical. Within the same month, their Sales team was burning $50,000 and generating $85,000 in new MRR. The decision became obvious: cut marketing aggressively, invest more in Sales.

Without the departmental breakdown, they would have just cut both proportionally and missed the real problem.

## The Runway Accuracy Problem: Why Departmental Analysis Matters

### Static vs. Dynamic Runway

Most founders calculate runway using a simple formula:

**Runway (months) = Cash on hand ÷ Net burn**

If you have $1M and burn $100K/month, that's 10 months of runway. This is the number you tell investors, and it's mathematically correct—but operationally misleading.

Here's why: Your burn rate almost never stays flat for 10 months.

In our experience, departmental burn rate changes predictably in ways you can model:

- **Marketing spend** typically scales with revenue goals (increases as you try to accelerate growth or decreases as cash gets tight)
- **Sales hiring** is seasonally dependent (Q1-Q2 hiring surge, Q4 slowdown)
- **Engineering burn** grows with headcount but has variable infrastructure costs
- **Customer Success** scales with customer count (increases as you grow)

When you track departmental burn, you can model how it actually changes month-to-month. If you're planning to hire 2 engineers in Month 3 and 1 sales rep in Month 4, your burn rate isn't flat—it's increasing. Knowing which departments are variable and which are fixed fundamentally changes your runway calculation.

Let's look at a real scenario:

**Month 1-2 baseline**: $100K net burn (mostly fixed costs)
**Month 3**: +$20K Engineering salaries = $120K burn
**Month 4**: +$15K Sales salaries = $135K burn
**Month 5-6**: Revenue accelerates, net burn decreases to $110K

Your actual runway isn't $1M ÷ $100K = 10 months. It's closer to 8.5 months, because your burn increases before it decreases.

This is why we use departmental burn rate analysis to build dynamic runway models instead of static ones. It's the difference between a number that looks good in a pitch deck and a number that actually reflects reality.

## Extending Runway: The Departmental Optimization Path

### Finding Your Highest-Impact Lever

When runway gets tight—and we've coached founders through this—the question isn't whether to cut costs. It's *where* to cut that extends runway without crippling growth.

Departmental burn rate analysis shows you the actual options.

Let's say you're 6 months from running out of cash, and you need to extend to 12 months. You need to cut $X from monthly burn (the math is straightforward). But where?

Options ranked by impact:

1. **Eliminate low-efficiency departments first**: If Marketing is generating $0.50 per dollar spent and has no path to efficiency, that's your first cut. If Sales is 3:1 efficient, preserve it.

2. **Negotiate variable costs before cutting headcount**: Marketing software, cloud infrastructure, and contractor costs are easier to cut without permanent team damage. Reduce your AWS spend or pause a vendor before laying off people.

3. **Cut overhead and overhead-allocated costs**: Office space (go remote), services you don't use, subscription tools you've outgrown.

4. **Scale back growth investment, not core product**: Cut hiring freezes in Sales and Marketing before touching Engineering. A weak product kills growth anyway.

We had a client with 7 months of runway facing a $40K monthly cut requirement. Their breakdown showed:

- Engineering: $50K (core product work, non-negotiable)
- Sales: $35K (generating $120K MRR, 3.4:1 ratio)
- Marketing: $28K (generating $15K MRR, 0.5:1 ratio)
- Customer Success: $20K (scaling with growth)
- Operations: $12K (core function)
- Overhead: $15K (mostly fixed)

We recommended: Cut $30K from Marketing (reduced to $8K), negotiate $8K from infrastructure, and reduce overhead by $2K. Total: $40K. The company extended runway 4+ months without touching Sales or core Engineering.

They still had cash to reach profitability within 8 months—which they did.

## Communicating Departmental Burn Rate to Stakeholders

### What Investors Actually Want to See

Investors don't just want your burn rate number. They want to understand your spending discipline and strategic allocation.

When [preparing for Series A](/blog/series-a-preparation-the-data-room-trap-most-founders-miss/), we recommend presenting departmental burn rate data like this:

**Format**: Show actual vs. budgeted burn by department over the last 6 months, with explanations for variances.

**Key metrics**:
- Burn rate by department (actual and trend)
- Output per dollar burned (revenue per sales dollar, features per engineering dollar, etc.)
- Headcount by department and headcount growth rate
- Months of runway by scenario (base case, conservative, aggressive growth)

**The narrative**: "Our Engineering is burning $50K/month and shipping 3 major features per month. Our Sales team is burning $35K and generating $120K in new MRR. Our marketing efficiency is declining, so we've decided to pause new customer acquisition and focus on retention through Customer Success."

This tells investors you understand your unit economics, make disciplined decisions, and allocate resources strategically.

Vague "we're optimizing spend" talk signals the opposite.

## Common Mistakes We See With Departmental Burn Analysis

### 1. Allocating Overhead Incorrectly

Most founders either ignore overhead or allocate it equally across departments. Neither works.

Your office rent supports everyone, but it shouldn't reduce the apparent efficiency of Sales. Instead, either:
- Track overhead separately as its own department line
- Allocate it proportionally by headcount (if Sales is 30% of headcount, allocate 30% of overhead)
- Better yet: view overhead as a constraint on total burn, not a per-department allocation

### 2. Forgetting to Account for Infrastructure Costs

Engineering departments often underreport their true burn because cloud infrastructure costs sit in Operations or IT.

For a scaling SaaS company, AWS/infrastructure costs tied to your product should roll up to Engineering burn, not be buried in Operations. Otherwise, you're underestimating the true cost of product growth.

### 3. Mixing Up Revenue Attribution

When calculating Sales efficiency (revenue per dollar burned), make sure you're attributing revenue correctly.

If your Sales team closes $100K in MRR, but only half came from direct sales efforts (the rest from inbound or partners), reporting that as $100K in sales-generated revenue inflates efficiency.

Use conservative attribution or explicitly separate channel-sourced revenue.

### 4. Not Updating Departmental Burn Quarterly

Burn rate changes. You hire people, tools get more expensive, contractors wrap up projects. If you calculated departmental burn 6 months ago and haven't updated it, your runway math is built on fiction.

Review and update at minimum quarterly, ideally monthly.

## Building Your First Departmental Burn Rate Model

### The Operational Steps

If you haven't done this yet, here's how to start:

1. **Export your expense data** (from accounting software, credit card statements, payroll)
2. **Create a cost center mapping** (assign every expense to a department)
3. **Build a summary** (total burn by department for the last 6 months)
4. **Calculate trend** (is Marketing growing faster than revenue? Is Engineering burn scaling with headcount?)
5. **Add output metrics** (revenue per sales dollar, features per engineering dollar, etc.)
6. **Model runway scenarios** (base case, 20% reduction, 20% increase)

Your first model doesn't need to be perfect. It needs to be honest and updated regularly.

In our work with founders, we've found that the act of building this model—even roughly—changes decision-making immediately. Founders stop treating "cut burn" as a single lever and start thinking strategically about which departments deserve investment and which don't.

## The Real Advantage: Speed of Decision-Making

Ultimately, departmental burn rate analysis isn't about precision for its own sake. It's about decision speed.

When you're on a tight runway and need to extend it, every week of analysis delays action. But if you already know your departmental breakdown and can see which departments are efficient and which aren't, you can make cuts in days, not weeks.

We've seen founders with this data move from "we need to cut burn" to "we're cutting $40K from Marketing and extending runway" in a single planning session.

Without it, they spend weeks analyzing, second-guessing, and usually make panic-driven cuts that harm both runway *and* growth potential.

## Next Steps

Your [burn rate runway](/blog/burn-rate-vs-growth-building-the-right-financial-model-for-your-stage/) calculation is only as good as the data behind it. Most founders optimize for the wrong metric because they're looking at total numbers instead of departmental efficiency.

Start this week: Pull your last 6 months of expenses and categorize by department. Calculate burn by department. Then ask yourself: Which department returns the most revenue per dollar spent? Which one is a pure cost center? That analysis is your roadmap for the next 6 months.

If you want to stress-test your departmental burn rate model and runway assumptions against your business model and growth targets, [Inflection CFO offers a free financial audit](/). We'll review your departmental allocation, validate your runway math, and show you exactly where your highest-leverage optimization opportunities are.

Because the best runway extension isn't emergency cost-cutting. It's strategic reallocation based on what actually works.