Forecasting is required when you don't have Profitdrive
Most searches for forecasting, a fractional CFO or a controller are a search for the same thing. Forward numbers the leadership team can trust, that stay current when the pipeline moves.
The search is usually a proxy for something simpler.
A consulting firm rarely wants a forecast for its own sake. It wants to know whether to hire ahead of the pipeline and what the bench costs if a deal slips. Behind a search for forecasting, a fractional CFO or a controller, the wish is familiar. Somebody, or something, to produce forward numbers that can be relied on and keep them current.
The hire is one answer. A fractional CFO brings judgement, a controller brings discipline to the close, and nothing here argues against either. What both are often asked to do first is rebuild the forward view every month from whatever the firm's systems will export. That is the part worth questioning. It spends the judgement you hired on assembly, and the decisions in between are still made on the previous version.
A separate exercise, rebuilt from exports, out of date on arrival.
A forecast in a services firm is a document. Somebody exports the pipeline, asks the practice leads about utilisation and which projects will extend, puts salaries and overhead on top, and a week later there is a spreadsheet P&L. It is hard to trace back to its assumptions, and it is out of date the moment it arrives.
It has to be rebuilt because the pieces sit with different functions. Sales holds the funnel, delivery the project plans, HR what people cost, finance the overhead and the targets. A forecast gathers those four views into one, by hand, for a moment. Between rebuilds the decisions do not wait. You hire against work that does not land and carry the salaries for two quarters. You turn down work you could have taken, because on paper your people were committed. Or you let someone good go because the actuals surprised you and the outlook looked worse than it was. Or the reverse. Each of those was made on a version that was already old.
How old is the version your team is working from today?
So the question is not how to forecast better. It is whether the forward view has to be a separate exercise at all.
A byproduct of connected operations, not a monthly project.
Profitdrive takes a different path. It is designed from operating experience inside services firms at scale, and the monthly rebuild above was part of that experience, seen from the finance and operations side. It connects the pieces each function holds and lets one outlook come out of them. Outlook is the product's name for the forward view.
Each opportunity carries a priced and staffed delivery shape. When the deal is won the deal model becomes the project plan, with the same roles, people and days. People cost is held by grade and dated, and an open role carries a cost while it is unfilled. Because the plan knows who is on what, a person's week opens with their assignments as rows, and accepted time lands as delivered cost against the project. SG&A sits in the same view.
From those, the forward P&L follows, month by month, from revenue through delivery cost and Non-Billable Production Cost (the bench, internal-project and leave-related cost that does not attach to client delivery) to Operating Income. When a deal slips, a project extends or a grade changes, the outlook moves that day. Nobody rebuilds anything.
The same months are shown in three cumulative views. Contracted is the signed work, staffed as planned, with its people cost. With extensions and change requests adds the continuations delivery expects. With pipeline adds the priced and staffed opportunities at full value, so you can see what winning them would do to revenue, to margin and to the bench.
The two questions from the first section sit between those views. Contracted shows what the bench costs if nothing more lands. With pipeline shows who would be short if it does, which is the hire-ahead question with its cost attached.
And every figure can be opened. Behind a month's revenue sits the project, behind the project the deal it came from, behind the cost the person and the rate that applied that month. That is the difference between a forecast and an outlook. A forecast is a number somebody has to explain. An outlook is a number you can open.
Put plainly, a firm on Profitdrive always has a financial outlook without ever doing a forecast. It is a modelled view of what the firm already knows, not a prediction.
Not a hire, not a finance function in software, and not your books.
Profitdrive does not replace a fractional CFO or a controller. It does not bring judgement, set the targets, or take the call when the outlook says the work is not coming. Someone still has to, and if you hire that person they start from a live view instead of a spreadsheet.
It is not artificial intelligence claiming to be your finance function. The outlook is built from your own deals, plans, people and overhead, and every figure shows what sits behind it.
And it is not your accounting system. Whichever ledger you run, Xero, MYOB or another, keeps the books. Xero is the first accounting system connected, and no other is connected today. Sync runs when you choose, your finance lead maps and accepts what arrives, and nothing it brings in writes the outlook. Showing accepted Xero months beside the outlook is in verification and unavailable today. Your accounting system looks back. Profitdrive looks forward.
The mechanism in full, and how it is priced.
The approach walks the whole path, and the financials page shows the forward P&L in the product. The evaluation guide says where a services platform or a resourcing tool is stronger, and where Profitdrive is. Profitdrive is priced by seat, matched to what each person does; the seat model has the card.
Before you brief a fractional CFO, a controller or a spreadsheet, ask where the numbers would come from. If the answer is the pipeline, the project plans, the people and the overhead, your firm already holds all four. The question is whether they are connected, or whether somebody gathers them every month.
So the question is not who should build the forecast. It is what your leadership team would do with a forward view that never needed building.
The demo runs on a firm where that view is already there. It is free and ready to use, and you are welcome to look around it.