How to Build a SaaS Financial Model for a Series B Raise Your Board Will Approve

At Series B, the financial model you built for your Series A stops being adequate — not because the math changed, but because the job changed. A Series A model is primarily a fundraising artifact. A Series B model is an operating tool that also happens to get shared with investors. Your board will use it to track performance, approve headcount, and hold the executive team accountable across multiple planning cycles. Investors will use it to underwrite a $20–50M check. The model needs to do both jobs at once, and most founders try to solve that with a single spreadsheet built in a week before the raise. That's the gap this article is about.

Before You Start — What You Need in Place

Building the model before you have the underlying data is the most common Series B mistake. Before a cell gets written, three things need to exist:

Actuals you trust. Your accounting system should be producing monthly financials that close within two weeks of month-end. If you're still running on a cash-basis QuickBooks setup or reconciling manually, that gets fixed before the model gets built — not after.

A clear strategic narrative. Series B investors are buying a thesis: you've found repeatable go-to-market, now you're scaling it. The model has to reflect that thesis numerically. If the strategy is "expand upmarket," the model should show ACV increasing, sales cycle lengthening, and CAC rising before payback improves. If the thesis doesn't show up in the numbers, the disconnect becomes the first question in every partner meeting.

Board alignment on the planning horizon. A three-year model built without board input will get revised in the first board meeting after you share it. Build draft assumptions collaboratively — especially headcount and revenue targets — before committing them to a spreadsheet.

Step 1: Build the Three-Statement Model From Actuals

The Series B model starts with a proper three-statement structure: income statement, balance sheet, and cash flow statement, all linked. This is different from the Series A model, which often had only a P&L and a cash runway chart.

Pull 12–18 months of actuals from your GL and load them into the model as the historical baseline. This does two things: it anchors the forecast in real numbers rather than assumptions, and it lets an investor or board member see whether the business is trending toward or away from the plan.

Revenue should be broken down by cohort and product line — not just a single MRR line. Costs should map to your actual chart of accounts, grouped into COGS, R&D, S&M, and G&A. Get this structure right before you start projecting forward.

Step 2: Build Scenarios, Not a Single Base Case

A Series B model with one set of projections reads as either naive or promotional. Boards and investors at this stage expect to see three scenarios built on different assumption sets — not just the same model with revenue nudged up or down.

Conservative case: What happens if net new ARR growth is 20% slower than plan, and CAC rises 15%? This is the scenario that tests whether the business can survive a bad quarter without raising an emergency bridge.

Base case: The plan you're actually running the business against — ambitious but achievable, grounded in pipeline coverage and historical conversion rates.

Upside case: What the model looks like if the new enterprise motion hits quota faster than expected, or if a channel that's showing early signal scales. This isn't fantasy; it should be traceable to specific assumptions that differ from base.

Each scenario should produce a different cash position at month 36, a different headcount count, and a different burn multiple. Scenario planning at this stage isn't about predicting the future — it's about demonstrating that the leadership team has internalized the range of outcomes and built a business that can navigate them.

Step 3: Model Headcount With Timing, Not Totals

The single most consequential input in a Series B model isn't revenue — it's headcount timing. A hire that's modeled in Q2 but doesn't close until Q4 affects two quarters of burn, delays quota contribution, and shifts the CAC payback curve. Most models treat headcount as annual totals. That's not sufficient when you're managing to a monthly burn rate and a board that approves each new role.

Build headcount month by month. For each planned role, include:

• Start month
• Fully loaded cost (salary + benefits + payroll tax, typically 1.2–1.3x base)
• Revenue impact, if any (quota-carrying roles should have a ramp period before they contribute)
• Department and cost category (determines whether it hits COGS, S&M, R&D, or G&A)

This level of detail makes the model defensible in a board conversation. When a board member asks "what happens if we delay two of those Q3 engineering hires," you can answer in real time rather than having to go rebuild the model offline.

Step 4: Tie the Model to KPI Ownership

A Series B model that only produces financial statements is half-finished. The other half is the operating metrics layer: the KPIs each department owns, how they connect to the revenue and cost lines, and how you'll report actuals against them each month. Linking financial projections to operating metrics is what turns the model from a fundraising document into the management system your board expects.

For a vertical SaaS business, the operating layer typically includes:

• New logo count and ACV by channel
• NRR by cohort vintage
• CAC payback by acquisition motion
• Headcount by department and revenue-per-employee
• Burn multiple (net new ARR added per dollar of net burn)

Each of these connects to a specific revenue or cost line in the financial model. That connection is what makes a board meeting productive: you're reviewing why Q1 NRR came in at 108% instead of 115%, not debating whether the revenue number is right.

Common Mistakes Founders Make

Projecting revenue first, then building costs around it. At Series B, costs drive the plan — particularly headcount. Build from the cost structure up, then check whether the implied revenue growth is achievable given the team and channels you're funding.

Using the same model for the board and for investors. The board model lives in a shared drive and gets updated monthly with actuals. The investor model is a snapshot. Conflating the two leads to either over-sharing messy working files with investors or under-sharing the granularity boards need.

Ignoring deferred revenue in the cash model. If you have annual contracts paid upfront, your cash flow timing is different from your revenue recognition timing. A model that doesn't show this distinction will have cash balances that don't match bank statements — a fast way to lose credibility in diligence.

When to Bring in a CFO

Most Series B companies either already have finance leadership or discover mid-raise that they needed it earlier. The signal that it's time isn't the raise itself — it's when the model starts being used for board governance, not just fundraising. If your CEO is spending more than four hours a week on financial reporting, headcount modeling, or diligence prep, the marginal cost of a fractional CFO is almost certainly lower than the opportunity cost of that time.

At Series B specifically, a fractional CFO adds value in three places: building the three-statement model from actuals, owning the scenario planning process with the board, and managing the diligence data room so the raise doesn't consume the executive team for three months. If those three things are already handled internally with confidence, the timing may be right to wait for a full-time hire at Series C.