Financial planning and analysis turns a commercial argument into a number, and the weakest part of that number is usually the demand assumption underneath it. Sena measures what consumers in each market are choosing, so the volume line arrives with evidence attached.
FP&A owns the number a company commits to: the revenue plan, the budget under it, the variance report against it, and the reforecast when it moves. Three properties of the evidence available to that work leave the commercial half of the case unsupported.
The revenue line starts from what happened and extends forward. That works while the market behaves as it did, and breaks in the quarter it matters, because the file records last year's choices and holds zero rows on this year's.
A regional plan frequently carries one market's assumptions across every country in it. Where the reason a shopper buys differs by market, a single growth rate applied across twelve of them is twelve separate errors averaging to a plausible total.
A miss arrives as a number, and the explanation is assembled from whatever evidence is on hand: price moves, promotion timing, and a competitor launch. The shopper who changed the purchase is the one party holding the answer, and that party goes unasked.
Sena supplies the consumer half of the plan: what people are buying in each market, why, and what would move them. The finance half stays where it is.
Recorded purchase in each planned market, so the growth rate rests on what consumers did, ahead of what the model extended.
Every figure names its market and its capture week, so a regional plan carries twelve reads where it previously carried one.
When actuals diverge, the shoppers in that market state what changed, so the reforecast starts from a cause, over a correlation.
Financial planning and analysis is the corporate discipline that converts commercial intent into a committed number and then holds the business to it. Four activities sit inside it: the annual plan, the rolling forecast, variance analysis against actuals, and the decision support that sits between them. This page treats that sense.
The corporate function runs on a calendar. A plan is set, a forecast refreshes against it monthly or weekly, variance is explained, and the plan reforecasts when the gap holds. Each of those four steps takes a demand assumption as an input, and in most companies that assumption arrives as a single growth percentage.
Where the plan spans markets, the assumption needs to arrive per market.
What consumers in that market are buying today is recorded ahead of the modelled shipment history.
Which way the choice is moving, and whether the movement is the category or one item inside it.
How many shoppers a price, pack, or availability change would move, sized before the plan commits to it.
Planning platforms handle consolidation, driver logic, scenario mechanics, and the audit trail well. The number those systems consolidate still arrives from somewhere, and for the revenue line it usually arrives from sales judgement and last year plus a percentage. A planning platform holds zero fields for why a shopper in a given market chose one item over another, because that signal sits beyond every system it connects to.
| Output | What it settles | Where it goes wrong |
|---|---|---|
| Market demand base | What is selling now, per market. | Read off shipments to the trade. |
| Direction of travel | Which way the choice is moving. | One region-wide growth rate. |
| Price sensitivity | How far volume moves on price. | Modelled from list-price history. |
| Variance cause | Why actuals diverged. | Assembled from adjacent figures. |
Four collected inputs sit under the case, assembled market by market as the plan needs them.
| Input | What it answers |
|---|---|
| Receipts | What consumers in that market bought, and at what price. |
| Store captures | Whether the planned item stood on the shelf at all. |
| Geo-verified photos | The shelf as it stood, dated and placed. |
| Stated preference | Which change would shift the purchase, and by how much. |
The team's own numbers join separately. The planning model, ledger extracts, shipment history, and price files connect through 250+ integrations, so the consumer read lands beside them.
Three questions sit outside any ledger or planning model, and each one changes the plan.
Three sibling pages carry the work either side of this one. Financial forecasting carries the rolling view this plan refreshes against. Financial analytics is the measurement layer the plan is read on. Financial performance management manages delivery once the number is committed.
Real people share what they buy and prefer, under explicit consent. Sena captures it directly at the source, so every figure traces back to where it came from whenever a number comes under question.
The same consumer supplies the purchase and the reason for it, and every figure names its market and its week, which is what lets a plan cite it.
A regional commitment breaks into the markets it covers, each with its own recorded base.
Every growth rate in the model opens onto the consumers whose purchases produced it.
The volume a change would shift is sized from the stated response, ahead of the plan carrying it.
A plan built on shipment history can state what was left in the warehouse and struggles to state what consumers took off the shelf. Sena builds every figure on this page from real-world signals captured when the plan needs it, from the fixture photographed in the market through to the shopper stating what would move the purchase.
The purchase and the price paid are recorded together, so a growth assumption has a real transaction standing behind it.
Images captured in real outlets establish what stood on the shelf, so a volume miss divides into weak demand and absent stock.
Signal arrives from the consumer network under explicit consent. The change that would shift a purchase is named by the person who would make it.
The planning model, ledger extracts, shipment history, and price files connect over 250+ integrations, and the consumer read lands beside them.
Market and capture week travel with every figure, so a growth rate in the plan opens onto the consumers who produced it.
Prior plan cycles with shipment history and price files, period by scanned period.
Four teams argue from the same demand read, and each one needs a different cut of it before the number goes on the page.
The committed number. Needs the demand assumption evidenced per market.
The business case. Needs the sensitivity sized before approval.
The growth plan. Needs the direction of consumer choice by market.
The guidance. Needs the variance cause stated, over inferred.
The same paired read, run against whatever each industry commits volume to.
The demand base per market, with the pack gap sized.
Occasion demand by market, set against what the range carries.
Own-label substitution, sized before the plan commits.
Account switching, measured per planned market.
One mechanism, applied per market and per planning cycle. Each step is documented, which is what carries a demand assumption through an audit of the plan.
Purchase and stated reason come from one consumer, so a recorded base arrives with its explanation.
Sena reports the base and its direction per market, with the regional total held beside it, so a single growth rate becomes visible as an average.
Shopper volume behind a change is counted per market, and the plan commits to that count.
Most FP&A revenue lines run on shipment history plus sales judgement, and the consumer sits beyond both. Sena supplies the consumer input that the planning model consolidates.
| Capability area | Typical setup | Sena |
|---|---|---|
| The demand base | Extended from shipment history. | Recorded purchase, per market. |
| The growth rate | One figure applied region-wide. | Held per market, from real choice. |
| Price sensitivity | Modelled from list-price history. | Sized by stated response. |
| Shelf availability | Assumed present. | Photographed in the market. |
| Variance cause | Assembled from adjacent figures. | Stated by the shoppers who moved. |
| A change the market omits | Beyond reach. | Sized before the plan commits. |
| Evidence in an audit | A model assumption. | Open any figure onto the consumers behind it. |
Three points in the planning cycle where the model needs a number the ledger holds zero rows for.
Replace a region-wide percentage with a recorded base per market, so the plan commits to twelve figures over one.
Ask the shoppers in the market that missed what changed, so the reforecast starts from a cause.
Measure how many shoppers a price or pack change would move before the case goes for approval.
An evidenced assumption settles the commercial half of the plan. The four decisions below are what a finance team runs around it.
Every finance decision Sena answers, in one place
The forward view inside
Holds the rolling forecast the plan is refreshed against.
Explore financial forecasting 02Delivery against the number
Manages the business to the plan once it is committed.
Explore financial performance management 03The measurement layer under
Supplies the measurement the plan and its variance are read on.
Explore financial analytics 04The outcome against peers
Compares the financial result the plan produced against the sector.
Explore financial benchmarkingThe walkthrough takes one revenue line in one region, breaks it into the markets it covers, reports the recorded consumer base in each, and sizes one scenario while the finance team watches.
Name the revenue line and the markets it plans across, and we will evidence the demand assumption under it.