Reconciled p.17
Q3 price-increase scenario: Retail category
+3.4% margin vs. prior period · illustrative
Use case
Revenue growth management
Model pricing, discounting, and mix decisions against the same reconciled revenue base finance already trusts, so a margin scenario recomputes deterministically instead of getting rebuilt from scratch.
Built on revenue actuals already reconciled from
- PDF filings
- Bank statements
- ERP exports
- ZATCA e-invoices
- Excel schedules
The old way
Pricing decisions shouldn't outrun the actuals behind them.
- A price or promotion change gets modeled in a side spreadsheet that never reconciles back to the ledger.
- Margin impact gets estimated after the fact, once the reconciled numbers finally land.
- Category and mix assumptions live in one team’s workbook, and finance’s forecast lives in another.
- By the time a pricing recommendation reaches the board pack, the actuals behind it have already moved.
One model, priced and reconciled
Watch a pricing scenario recompute against the reconciled base.
A guided walkthrough of a live model: every margin line on screen still carries its own citation.
Margin moves with the price
Change a discount, a promotion, or a mix assumption and the dependent margin and forecast lines recompute automatically against the same reconciled revenue base.
Evidence, not a guessed optimum
Every pricing recommendation traces back to the actuals it was computed from: no invented benchmark or "optimal price" score bolted on.
One segmentation, every team
Category and customer segments are defined once in the definitions library and reused consistently across finance and go-to-market reporting.
Key features
Built for pricing, promotion & mix decisions that hold up
Pricing and mix scenarios, modeled not guessed
Test a price change, a promotion, or a category mix shift in plain language: margin and forecast lines recompute against the same reconciled revenue base, never a detached copy.
FY24 base
Category growth
Pricing actions
Mix shift
Promotions
FY25 forecast
Finance, sales, and category teams on one model
Pricing, sales, and category owners all read from the same governed definitions, so a discount decision and the finance forecast never quietly disagree.
Fast, evidence-grounded calls
The Analyst agent answers a pricing question in plain language over your model, always citing what it computed from.
Margin and revenue move together
Add a pricing or promotion assumption and the margin line updates in the same view as the revenue forecast: no separate tab, no manual reconciliation.
FY24
Category
Pricing
Mix
Promotions
FY25
Not a rating. A chain.
Every pricing figure in this plan can show its own proof.
- 1 Filed
- 2 Extracted
- 3 Reconciled
- 4 Cited
- 5 Exported
Reconciled p.22
Promotion ROI: trade-spend reconciliation
−8.1% spend vs. prior period · illustrative
Reconciled p.9
Category mix shift: FY2025 forecast
+5.6% revenue vs. prior period · illustrative
Keep exploring
Discover more planning use cases
Sales & operations planning
Demand, supply, and financial plans connect on one reconciled model instead of three spreadsheets stitched together each cycle.
See it in actionProduct profitability analysis
Product and segment margin draws on the same canonical cost and revenue data, with lineage back to every source transaction.
See it in actionDemand & inventory planning
Demand assumptions connect straight into the financial forecast, so inventory calls and cash-flow forecasts stay consistent.
See it in actionFrequently asked
Questions about revenue growth management.
What does "revenue growth management" mean here, without a pricing-optimization engine bolted on?
It means pricing, discounting, and mix scenarios run against the same reconciled revenue base finance already trusts, with dependent margin and forecast lines recomputing automatically, not a proprietary "optimal price" score. Optimization claims we can’t evidence stay off this page on purpose.
How does a pricing or promotion scenario actually recompute?
Change an assumption (a discount, a promotion, a category mix shift) in plain language, and the deterministic engine recomputes every dependent line across the model. The base case itself stays untouched until you decide to adopt the scenario.
Where do the margin and mix figures come from?
From actuals that have already been reconciled to the printed subtotal on their source document, then rolled up through the same definitions library used everywhere else in the model, never a separately re-keyed pricing spreadsheet.
Can I trust a pricing recommendation without a benchmark score attached?
Every figure behind a recommendation opens onto its own citation and reconciliation check. We’d rather show you the traceable number than invent a benchmark or an "optimal price" figure we can’t evidence.
How does category segmentation stay consistent between finance and go-to-market teams?
Segments are defined once in the definitions library and reused everywhere: finance’s category P&L and the go-to-market team’s reporting read from the same definition, not two drifting versions.
What happens if I change a pricing assumption mid-quarter?
The dependent margin and forecast lines recompute in place (same inputs, same output, every time) and the change stays on its own scenario branch until it’s adopted into the live plan.
Do I need a live ERP connection before I can model a pricing scenario?
No. Excel, CSV, or PDF upload works standalone, so a pricing or promotion scenario can be modeled before any live connection exists.
Get started
Price the next quarter on evidence, not a guess.
Book a walkthrough and we'll model a pricing or promotion scenario against a sample of your own reconciled actuals: margin impact included.