For most of the twentieth century, financial planning tracked a business whose economics were legible from its balance sheet. Cost was dominated by things you could count: plant, inventory, headcount, distribution. Value accrued roughly where spend occurred, and a year was a reasonable unit of foresight because the physical world changed at the pace of physical investment. The annual budget, the capital appraisal and the monthly variance report were fit instruments for that reality. They are increasingly ill-fitting for the business that has actually emerged.

Two shifts explain the misfit. The first is that value has moved into intangibles: code, data, customer relationships and the accumulated capability of teams. These do not depreciate on a fixed schedule, they do not sit still to be counted, and the accounting conventions that govern them were designed to be conservative rather than informative. Worse, the accounting standards treat internally generated intangibles inconsistently: research is expensed as incurred, some development is capitalised under strict conditions, and much of the capability that genuinely drives value, the tacit knowledge held by a durable product team, never appears on the balance sheet at all. A statement of position that omits a company's most valuable asset is a poor map for anyone trying to steer by it. The second shift is that the cadence of consequence has compressed. A pricing change, a competitor's feature, a shift in cloud consumption or a regulatory ruling can alter the economics of a product line inside a quarter, well before a budget cycle can register it. Planning built to be revisited once a year now sets policy against conditions that no longer hold.

The result is a quiet crisis of relevance in the finance function. Budgets are negotiated hard, then ignored the moment they diverge from reality, which is quickly. Business cases are written to clear an approval gate and never revisited, so the benefits they promised are neither tracked nor delivered. Meanwhile the operating model that finance is meant to steer has itself gone digital, funded continuously, measured in flow rather than milestones. The discipline that matters now is not tighter control of a fixed plan but faster, more honest connection between strategy, the drivers that express it, and the money that follows. That is the shift underway, and it is why financial analysis, planning and control deserve to be reconsidered from first principles rather than automated as they stand.

Economics precedes accounting. Accounting records what happened in a form auditors can trust; it is not built to explain why margin behaves as it does. Financial analysis worth the name starts from the economic structure of the business: which activities create value a customer will pay for, which costs are truly variable with volume, and where scale improves or erodes the unit. We reason in drivers before we reason in ledgers, because a plan expressed as accounts is a plan you cannot interrogate.

The unit is the atom of a digital business. Aggregate profit hides everything that matters. The discipline of unit economics asks what it costs to acquire, serve and retain one customer, or to run one transaction, one tenant, one API call, and what that unit contributes over its life. In a digital enterprise the marginal cost of an additional user can be close to nothing while the marginal cost of an additional feature is entirely staff time, and confusing the two produces both reckless growth and misplaced thrift. A business that knows its unit economics can price, scale and cut with intent; one that does not is guessing at portfolio level.

Strategy must be expressed as numbers or it is not yet a strategy. A statement of intent that cannot be traced to a driver, a target and a movement in the financial model is a slogan. The core act of planning is translation: from an outcome the business must achieve, to the operational drivers that would evidence it, to the financial consequences those drivers imply. Done well, this makes strategy testable. When a driver moves against plan, the model shows what it costs and what assumption failed, and the conversation becomes evidential rather than political.

Control is a feedback loop, not a gate. The purpose of control is to shorten the distance between a decision and knowing whether it worked. Traditional control optimises for the prevention of unauthorised spend; modern control optimises for the speed and quality of learning while keeping spend accountable. The two are not opposed, but where they conflict the loop should win, because a business that learns faster than it errs will outperform one that merely errs within budget.

Rolling forecasts displacing the annual budget. A growing number of organisations have stopped treating the budget as a single annual truth and moved to a rolling forecast that always looks the same distance ahead, refreshed monthly or quarterly. The budget does not disappear entirely, but its role narrows to setting boundaries and intent, while the forecast carries the operational conversation. The value is not in the artefact; it is in the discipline of continually confronting the plan with new evidence rather than defending a number set before the year began.

Funding products, not projects. The project, with its fixed scope, temporary team and terminal date, was built to deliver a defined change and then dissolve. Digital capability does not behave that way: software that matters is never finished, and disbanding the team that understands it destroys value. The pattern gaining ground is persistent funding of long-lived product teams against outcomes, with money allocated to a stable capability and steered by results, rather than released against a project plan and clawed back at its end.

FP&A modernisation and connected planning. Financial planning and analysis is being rebuilt around models that connect operational drivers directly to financial outputs, so that a change in a demand assumption or a staffing plan flows through to margin without a manual reconciliation. This is partly a technology story, as planning platforms replace the sprawling spreadsheet, but the substance is the driver model beneath it. The prize is a single, shared representation of how the business works, one that operations, commercial teams and finance can all reason over.

Cost transparency for digital operations. As consumption of cloud, data and platform services has grown, so has the need to see where that cost lands and what it buys. The practice of treating variable technology spend as a first-class managed cost, attributed to the products and teams that incur it and reviewed as a matter of routine, has moved from novelty to expectation. It reconnects engineering choices to financial consequence, which is precisely the connection that opaque, centrally absorbed technology budgets used to sever.

Capital allocation as a continuous portfolio. The habit of committing a whole year's investment in a single autumn round is giving way to smaller, more frequent allocation decisions, with funding staged against evidence rather than granted in full at the outset. Money follows demonstrated progress, and an initiative that fails to show it is stopped early rather than carried to the end of a plan that has already ceased to make sense. This treats the investment book as a live portfolio to be rebalanced as facts arrive, not a fixed slate to be defended once set, and it rewards the willingness to change one's mind in the face of new information rather than punishing it as inconstancy.

One financial spine. The reasoning of the business should rest on a single, governed model of drivers and definitions, not on a lineage of spreadsheets whose owners have left. When revenue, cost and volume mean the same thing everywhere, forecasts reconcile, actuals compare and disputes become about substance rather than method. The spine is a semantic asset before it is a system: agreed definitions, consistent hierarchies, and a clear line from operational metric to financial statement.

Driver-based models over line-item extrapolation. A plan built by growing last year's lines by a percentage encodes no understanding and answers no useful question. A driver-based model, in which outputs follow explicitly from volumes, rates and unit costs, can be interrogated: change the assumption, see the consequence. This is what makes scenario analysis cheap and honest rather than a special project, and it is the difference between a plan you can defend and one you can only assert.

Benefits with named owners and a measurement plan. Every business case should nominate the person accountable for each benefit, the baseline against which it will be judged, and the point at which it will be measured, all fixed before approval. Value realisation is designed in at appraisal or it does not happen. A benefit with no owner and no baseline is a decoration on a document, and it will be treated as such the moment attention moves on.

Cost transparency by allocation, not apportionment. Shared costs should be attributed to what consumes them through a traceable driver, so a team can see and influence its own bill, rather than smeared across the organisation by a convenient percentage. Apportionment keeps the peace by making cost nobody's responsibility; allocation creates responsibility by making it legible. The design principle is that anyone accountable for a cost must be able to see how their decisions change it.

Scenarios as the default, not the exception. A single-point forecast projects false confidence and invites the argument that it was always going to be wrong. Building the model so that a small set of scenarios, a downside, a base and an upside, can be produced on demand changes the conversation from prediction to preparedness. Planning is then about the decisions that hold up across futures, which is the only kind of planning that survives contact with a real one.

Benefits evaporation. The business case is approved on a promise of value, the money is spent, and the benefits are never measured because no one owns them and no baseline was captured. The programme is declared complete on delivery of scope rather than on realisation of value, and the organisation slowly learns that the numbers in a case are ceremonial. Nothing corrodes investment discipline faster.

The budget as both ceiling and floor. A budget used as an entitlement means teams spend to the line to protect next year's allocation, and a budget used as a hard ceiling means genuine opportunities are refused because they arrived in the wrong quarter. Treated as an unbreakable annual contract rather than a statement of intent, the budget optimises for the defence of numbers over the interests of the business.

Precision theatre. Elaborate models carried to two decimal places, built on assumptions no one has examined, mistaking the appearance of rigour for the substance of it. Effort pours into the arithmetic of the forecast while the drivers that actually determine the outcome go unchallenged. A model is only as good as its weakest assumption, and precision applied to a guess is merely a well-dressed guess.

Project accounting for product work. Funding durable capability as if it were a temporary project produces a familiar pathology: teams assembled and dissolved, knowledge discarded at each boundary, capitalised effort that quietly never ends, and a restart cost paid again and again. The accounting treatment shapes the operating model, and the wrong treatment institutionalises waste.

Allocation opacity. Costs absorbed centrally or smeared by apportionment so that no team can see, question or influence what it consumes. Consumption then rises without friction because it is free at the point of use, and the eventual response is a blunt central cut that penalises the disciplined alongside the profligate. Opacity does not save money; it defers and enlarges the bill.

The forecast as a negotiation. When the forecast is used to set targets and judge performance, people forecast the number they can safely commit to rather than the number they actually expect. The instrument meant to reduce uncertainty becomes a bargaining position, and finance loses its clearest window on reality. Separating the honest forecast from the committed target is the only reliable guard against this.

We begin with the economic question, not the reporting one. Before touching a planning tool or a chart of accounts, we work with the business to establish how it actually makes money: the units that matter, the drivers behind them, and where margin is genuinely created or lost. That understanding becomes a driver-based model that expresses strategy in numbers, so that intent and consequence are visible in the same place. We would rather ship a simple model the business trusts and can interrogate than an elaborate one it cannot.

From there we build the financial spine: agreed definitions, a consistent hierarchy, and a traceable line from operational metric to financial statement. We move the organisation from a defended annual budget towards a rolling forecast held against that spine, and we design the appraisal of transformation so that benefits carry named owners, baselines and measurement dates from the outset. Where the operating model has gone digital, we help fund durable product teams against outcomes rather than releasing money against project plans, and we make technology and platform cost legible by attributing it to what consumes it.

We are deliberate about the human system around the numbers, because the failure modes above are behavioural before they are technical. We separate honest forecasts from committed targets, we give control the character of a fast feedback loop rather than a slow gate, and we return to business cases after the money is spent to ask what value actually arrived. Our work is judged not by the sophistication of the model but by whether decisions improve: whether the business allocates capital more intelligently, sees its costs more clearly, and holds itself to the benefits it promised.

We work in the grain of the organisation rather than against it. That means starting where the pain is sharpest and the evidence nearest, proving the approach on a single product line or business unit before extending it, so that conviction is earned rather than mandated. It also means leaving capability behind us: the model, the definitions and the habit of confronting the plan with fresh evidence should belong to the client's own people, not to the consultant who happened to build them. An engagement that leaves an organisation dependent on us has failed on its own terms, however accomplished the artefact it produced.

What distinguishes our work in financial analysis, planning and control is that we treat it as an instrument of strategy rather than an exercise in stewardship. We are equally at home in the economics of a digital product, the mechanics of a driver-based model, and the politics of a budget conversation, and we insist that the three stay connected. We do not hand over a forecasting tool and leave; we change how an organisation reasons about money, so that the connection between strategy, drivers and cash outlasts any single planning cycle and any particular piece of software.

Two things make that possible. The first is breadth held together: many advisers can build a model, and many understand a digital operating model, but the value lies in insisting that the economics, the model and the governance around it form one argument rather than three separate deliverables handed to three different audiences. The second is a refusal to sell complication. We are as willing to retire a report, decommission a spreadsheet or simplify a chart of accounts as to build something new, because the aim is an organisation that reasons more clearly about money, and clarity is more often served by subtraction than by addition.

There is also a practical corollary that changes what the work is permitted to assume. When an engagement calls for a capability that does not yet exist, it need not wait on a procurement cycle or a vendor's roadmap. The Nashua 360 Enterprise Platform is built to accommodate almost any feature at pace, through extreme vibe coding: what is needed is described in plain language and generated quickly, but always within firm architecture principles and under stringent quality assurance, so that speed never comes at the cost of coherence, security or control. The effect is strategic rather than merely convenient. It moves the make-or-buy line, keeps optionality cheap, and lets the architecture follow the strategy rather than the strategy bending to whatever happened to be on a shelf.

The measure we hold ourselves to is simple and unforgiving: a year after we have worked with you, are decisions demonstrably better informed, is cost genuinely transparent to those accountable for it, and are the benefits that justified investment actually being realised and tracked. None of these tests can be passed by a better template alone; each depends on the connection between strategy, the drivers that express it and the cash that follows holding firm under pressure, which is the discipline we exist to build. If financial planning has become a ritual you perform rather than an instrument you use, that is the gap we close, and it is where the difference shows.