The financial infrastructure that supported a Series A valuation is not the infrastructure that will defend a Series C.

I am Josh, and welcome back to the City Shift Finance podcast.

Today we are discussing what good financial planning and analysis actually looks like as venture-backed companies scale through Series B, C, and D, and why the failure to rebuild the finance function at each of these stages is one of the most expensive structural mistakes a growth company can make.

The misunderstanding begins in how organizations define what the finance function is supposed to produce at each stage of growth, and the gap between that definition and the actual analytical requirement of the business is where financial performance quietly deteriorates.

When a company is operating on seed capital, the finance function is primarily oriented toward tracking cash, maintaining the books, and ensuring the runway calculation reflects the actual spending rate; the analytical requirement is narrow because the business itself is narrow, and the decisions being made are few enough that a single person with a well-maintained model can cover the territory.

When the company raises a Series A and commits to a set of investor expectations around revenue growth and unit economics, the requirement shifts materially, because the finance function now needs to connect hiring and spending decisions to revenue outcomes with enough precision to identify when the plan is deviating before the deviation becomes a board-level conversation, and that connection requires a revenue model built from operational drivers, not a top-down projection that grows by a fixed percentage because the investor deck said it would.

By the time a company reaches Series B, the complexity of the operation has changed in a way that the finance function built for the previous stage cannot absorb.

Multiple revenue streams are operating simultaneously, the cost structure has developed layers of fixed and variable expenses that do not move linearly with headcount, and the board expects financial reporting that extends beyond trailing actuals to include segment-level margin analysis, cohort-level retention data, and scenario modeling that reflects the actual cost structure flexibility of the business rather than a theoretical adjustment that would require decisions the organization is not positioned to make.

The infrastructure that worked when the company had thirty employees and one product line begins to fracture when the company has one hundred and fifty employees and a pricing matrix that varies by customer segment, contract length, and product configuration; and the fracture is rarely visible in the accounting, which continues to close accurately, but in the forecast, which begins to lose its connection to the operational mechanics of the business.

The first signal that the FP&A function has fallen behind the business is the deterioration of the forecast.

When forecasting is treated as a periodic exercise rather than a continuous discipline, the annual plan is built in December, approved in January, and used as the measuring stick for the rest of the year; when the market shifts in March, the commercial operation adapts, but the financial plan does not, and the variance explanations provided to the board begin describing what happened without explaining what the business is going to do about it.

Good FP&A at Series B and beyond operates on a rolling forecast that absorbs new operational data continuously, adjusting the forward view of the business based on the actual behavior of the market rather than the assumptions made during the annual planning cycle, so that when a revenue driver changes, the financial consequence of that change is visible before it reaches the income statement.

The second signal is a disconnect between what the financial model says and what the commercial operation is actually doing.

In a finance function that has kept pace with the business, the model is built on operational drivers, meaning revenue is tied to pipeline conversion rates, sales cycle lengths, and average contract values; operating expenses are tied to headcount capacity, vendor contracts, and the actual cost of acquiring and retaining customers.

When the finance function has not kept pace, the model is built on top-down assumptions, revenue is projected to grow by twenty percent because the board expects twenty percent growth, and when the numbers are missed, the organization cannot identify whether the failure occurred in marketing lead generation, sales execution, or pricing strategy, because the financial model was never connected to the operational mechanics that produce revenue in the first place.

This disconnect becomes particularly consequential when a company prepares for a Series C or Series D fundraise.

Growth-stage investors at these rounds evaluate the maturity of the finance function as a proxy for the maturity of the management team, and the questions they ask are not accounting questions; they are questions about the relationship between customer acquisition cost and lifetime value across different customer segments, about the cash flow implications of a delayed product launch or a shift in payment terms, about what happens to the runway under a bear case that reflects actual cost structure flexibility rather than a theoretical reduction.

The organizations that cannot answer these questions with precision, from a financial model that is connected to the operational reality of the business, enter the fundraising conversation in a reactive position, and the cost of that position is measured in valuation compression and in the terms attached to the capital they raise.

The companies that build strong FP&A capabilities share a recognizable characteristic in how they treat the function.

They embed the FP&A team in the commercial operation rather than isolating it in a reporting function, so that pricing changes are evaluated financially before they are implemented, new product features are modeled for margin impact before they are built, and the financial guardrails that allow operational teams to move quickly are established in advance rather than discovered after the capital has been spent.

The technology stack evolves from static models to dynamic planning platforms as the business grows, but the technology is deployed to support the process rather than to substitute for the analytical judgment that the process requires; and the planning cadence shifts from an annual exercise to a continuous discipline that keeps the financial picture of the business current enough to inform the decisions that are actually being made.

The transition from Series B to Series D requires the finance function to shift from explaining the past to predicting the future, and the organizations that fail to make that transition lose their strategic flexibility in a way that compounds over time.

Capital allocation decisions get made against outdated assumptions, margin compression is discovered after the cash has already been spent, and the fundraising conversation becomes a process of managing investor concerns rather than presenting a financial narrative that the management team controls.

The reporting keeps confirming that the accounting is accurate, while the financial performance of the business quietly deteriorates because the decisions driving that performance are being made without adequate financial context; and by the time the gap between the accounting reality and the strategic requirement becomes visible in the numbers, the cost of rebuilding the finance function is almost always larger than the cost of maintaining the discipline would have been.

Thanks for tuning in.