Your Company Doesn't Operate on a Calendar. So Why Does Your Forecast?

Most financial forecasts are built around time.

January. February. March. Q1. Q2. Year-end.

But that isn't how pre-revenue life sciences companies actually operate.

They operate around milestones.

An IND filing. A manufacturing run. First patient in. Completion of enrollment. A clinical readout. A regulatory submission. The next financing.

Those milestones drive when activities happen. And when activities happen drives when cash is spent.

Yet most forecasts are still built by assigning those activities to specific months on a calendar.

What happens when a milestone moves?

Consider a company forecasting the start of a clinical trial in March.

The forecast may include CRO costs beginning in March, clinical hires starting beforehand, manufacturing activities leading up to the trial, and additional spending triggered once enrollment begins.

Then the trial moves three months.

The forecast needs to change with it.

In a traditional model, someone has to identify every assumption affected by that delay and manually update it. And it isn't necessarily as simple as shifting three columns to the right.

Some costs occur a certain number of months before a milestone. Others begin after it. Some are one-time payments. Others trigger recurring spend. Hiring, manufacturing, clinical, regulatory, and other activities may each have different relationships to the milestone that drives them.

The more complex the forecast becomes, the more dependencies there are to identify — and the easier it is for something to get missed.

And when something gets missed, it isn't simply a modeling inconvenience.

Your runway forecast can be wrong.

If costs don't move when the milestones driving them move, projected cash needs can be misstated. Spending can appear earlier or later than it will actually occur. The forecast may show enough capital to reach an important milestone when the company actually has a funding gap — or show a funding gap that has actually shifted.

For a pre-revenue company dependent on external capital, those are meaningful differences.

Start with the milestone, not the month.

Instead of asking:

“What will we spend in March?”

start by asking:

“What do we need to accomplish, and when does the related spending occur relative to that milestone?”

It's a fundamentally different way of building a forecast.

The milestone comes first. The calendar follows.

If an IND filing moves, the activities dependent on that filing should move with it. If a clinical milestone changes, the costs tied to that milestone should follow. If a hiring decision is triggered by a particular stage of development, its timing should reflect when that stage is actually expected to occur.

The result is a forecast that reflects how the company actually expects to progress — and how much capital it will take to get there.

Runway isn't just cash divided by burn

For pre-revenue companies, runway isn't simply about how many months of cash are left.

The more important question is:

Do we have enough capital to reach the milestones that matter?

A company may technically have 18 months of cash remaining. But if it needs 22 months to reach the milestone required to support its next financing, that is a very different situation from a company with the same cash balance and a major value-inflection point six months away.

Timing matters.

And so does understanding what happens when that timing changes.

A three-month delay could defer certain costs while extending others. It could change hiring needs, manufacturing timing, clinical spend, or the timing and size of the next financing.

Management needs to understand those impacts while there is still time to make decisions — not discover them months later when actual cash begins to diverge from the forecast.

A forecast should be a decision-making tool

At Fractional Finance Solutions, we build and manage forecasts for pre-revenue life sciences companies whose timelines are constantly evolving.

Milestones move. Development timelines change. Priorities change. Financing assumptions change.

The forecast needs to keep up.

A useful forecast shouldn't simply tell management what the current assumptions cost. It should help answer questions such as:

What happens to our cash and runway if this milestone moves?

How much capital do we need to reach the next value-inflection point?

When do we need to raise it?

Which activities are driving our cash requirements?

What can we change if the timeline or available capital changes?

Those are the questions that turn forecasting from a finance exercise into a strategic decision-making tool.

The problem that led us to build Forcestra

For years, I encountered the same challenge while building and managing forecasts for FFS clients: the companies were milestone-driven, but the tools available to forecast them were calendar-driven.

So I began building our forecasts differently.

Instead of starting with dates and independently assigning activities to months, I developed a methodology that connected spending to the milestones actually driving it. When a milestone moved, the related activities could move with it.

That methodology became the foundation for Forcestra™.

What began as a better way to forecast for FFS clients ultimately became something larger: a technology platform built specifically for milestone-driven companies. Forcestra is now a separate company and is preparing for its beta launch in October.

The premise behind it is simple:

When a milestone moves, the forecast should move with it.

Forcestra connects activities to the milestones that drive them. When milestone timing changes, the related activities can move with it, allowing the financial impact to flow through the forecast and providing an updated view of cash needs and runway.

Forcestra wasn't created because we wanted to build another forecasting tool.

It was created because the way milestone-driven companies are traditionally forecast doesn't match the way they actually operate.

And when capital is finite, that disconnect matters.

Because the goal of forecasting isn't to perfectly predict what your company will spend in March.

It's to understand what it will take to reach the next milestone, how much capital you'll need to get there, and what happens when the timeline changes.

Your company doesn't operate on a calendar.

Your forecast shouldn't either.