Revenue & Margin Planning

A commercial plan that knows what moves it.

Build the revenue and margin plan from your own actuals, forecast demand, compare pricing scenarios against a baseline, then track the plan against actuals each time your data refreshes.

Planning & Forecasting / Decision Models / Fittings margin simulation
The baseline
Fittings actuals from April to September 2026 set the baseline: about $325K of gross margin a month on 248,000 units at $4.19.
The pressure
A 12% rise in resin cost lifts unit cost from $2.88 to $3.05 and takes margin down to about $283K a month by March.
The plan
A 4% price increase forecasts 2.4% fewer units and brings margin back to about $317K. That scenario becomes the plan the team tracks from October.
01 · Start from actuals

Start the plan from what actually sold.

The model reads six months of fittings sales, keeps them as actual periods, and plans the next six. The baseline is today’s price and cost, with nothing changed.

Data & Time

Point the model at your history and set the horizon.

Choose the source, a monthly grain and the date the forecast starts. Units, revenue and cost are summed from your own sales data, so the plan starts from what the business actually did.

Inputs

Name the levers the plan depends on.

Price change, unit cost and price elasticity are inputs with a fallback value. The baseline uses those defaults, so every other case is a change from it.

How it works: sources, periods and the baseline
Sources
A decision model reads a dataset, price list or view. A view can first combine sales history with costs and other data in Data & Context Studio.
Actual and forecast periods
A date column and a forecast start date split the horizon. Periods before it are actuals; the model calculates the rest from its variables.
Breakdowns
Results can split by source dimensions, such as region or product group. This example keeps the fittings line as one total.
No separate budget object
Revomo has no budget, target or quota object. The plan is the model’s baseline and scenarios, built on your data.
02 · Forecast demand

Forecast what fittings will sell next.

A demand forecast for each fittings product gives the units the plan works from, with a likely range and a record of how each run scored.

Forecast results

About 50,800 couplings in October, likely 46,900 to 54,700.

History rows show actual demand. Forecast rows show the expected value and the low and high ends of the range 8 in 10 outcomes should fall inside.

ResultsFittings demand forecast
Versions

See what each run tried, and what it kept.

Each run scores several methods on past periods and keeps the best. Version 4 kept gradient boosting, at 7.9% weighted error.

How it works: methods, accuracy and the plan
Methods
Simple, damped-trend and seasonal smoothing, ARIMA and seasonal ARIMA, Prophet, and gradient boosting per series or pooled across all series. The run keeps the best method, or an average of methods if you choose.
Accuracy
Methods are scored on rolling tests over past periods, as weighted error (WAPE) or scaled error (MASE). Lower is better. The range is calibrated on the same tests.
Into the plan
A view can read forecast results as a source (Predictive Model Results), so forecast units can sit beside your actuals in the view the decision model reads.
Updates
A forecast runs on demand, or on each source refresh if you switch that on. It is not a live stream.
03 · Compare scenarios

Compare the cases before you commit to one.

The decision model at the top of the page puts three cases on one chart: the baseline, a 12% resin cost rise, and the same rise with a 4% price increase. Here is how each case is defined, and how wide its outcome could be.

Scenarios

Name each case and change only what differs.

A scenario starts from the baseline inputs. One raises unit cost by formula; the other raises it and sets a 4% price change.

Uncertainty

See how wide the outcome could be.

Give an uncertain input a range and each scenario runs many trials. With the increase, March margin lands between about $285K and $349K in 90% of them.

How it works: baselines, elasticity and calculation
Baseline
Each decision model has one baseline scenario. Optimistic, pessimistic, cost shock or tariff cases are scenarios you name; Revomo does not supply preset ones.
Elasticity
The -0.6 elasticity is an input. Estimate it from your own data with a price elasticity model in Predictive Modeling, then enter it as the input’s value.
Comparison
Compare the selected scenario with the baseline, or all scenarios at once, as series on one chart, with each output’s difference from the baseline beside it.
Calculation
Results recalculate when you calculate the model. When an input changes, the model shows that a new calculation is needed rather than updating on its own.
04 · Commit and track

Agree the plan, then hold actuals against it.

Publish the chosen scenario, keep the forecast version it was built on, and compare each month’s actuals with the plan in a view. Three months in, fittings margin is $14,170 under the $937,510 plan to date (1.5%), and December is the month to look at.

Data / Views / Fittings plan vs actual

Plan from the chosen scenario, actuals from the sales history, variance as formula columns. December is 3.5% under plan, still inside the range the trials showed. Illustrative data.

  • Plan joined to actualsThe view reads the decision model’s results for the chosen scenario and joins monthly actuals on the period.
  • Variance you defineVariance and Variance % are formula columns, and a formatting rule marks any month more than 2% under plan.
  • Current when the data isRefresh the view after new actuals load and every month updates. It is not a live stream.
Publish

Publish the plan everyone works to.

Publishing gives the model’s results a read-only page, with the chosen scenario against the baseline, ready to print.

Version in use

Keep the forecast the plan was built on.

A January refresh trained version 5, which scored worse, so version 4 stays in use. You switch versions only when you choose to.

How it works: plans, records and alerts
No plan lock
Revomo has no plan object or plan lock. A decision model’s results stay as calculated until someone calculates it again, and role permissions decide who can edit it.
A fixed record
To keep a copy of the agreed plan that cannot move, download the plan view and load it as a dataset, then join actuals to that copy.
Forecast versions
A retrain on source refresh replaces the version in use only when the new one is at least as accurate. Any kept version can be put back in use.
Alerts and drivers
Revomo does not alert on its own when actuals miss the plan, and does not split a variance into price, volume and mix by itself. Add formula columns for the drivers you track, and report them in Analytics & Insights.
05 · What powers it

What powers it.

The capabilities that do the work, what every subscription adds, and where to start.

Capabilities it uses

In every subscription

Start here

Related solutions: Price Increase Management, Cost, Tariff & Freight Recovery, Customer & Product Profitability.

FAQ

Common questions

Does this replace our FP&A tool or ERP planning module?

No. Revomo holds the commercial plan: revenue, price and margin built from your own sales data, with scenarios. Consolidation, currency conversion and corporate budgeting stay in your FP&A tool or ERP. Revomo reads from and publishes back to the systems that run the business; it does not replace them.

How is the forecast produced? Is it a black box?

No. A demand forecast tries several methods on each series, scores each on past periods and keeps the best, and each version shows what it tried and its error. In the plan itself, every lever is a named input, and each scenario shows which inputs it changes from the baseline.

How is this different from planning in spreadsheets?

The baseline, the forecast and the actuals read the same data in one place. A scenario changes only the inputs that differ from the baseline, forecasts keep their versions, and plan against actual is a view that updates when the data refreshes, rather than a file rebuilt every month.

Can we lock the plan once it is agreed?

Not with a separate lock. A decision model’s results stay as calculated until someone calculates it again, and role permissions decide who can. Publishing gives everyone a read-only page of the results. For a fixed copy, download the plan view and keep it as a dataset.

Will Revomo alert us when actuals miss the plan?

Not on its own. The plan against actual view updates when its data refreshes, and a formatting rule can mark any month under your threshold. Reports and dashboards in Analytics & Insights can show the same view to the people who need it.

What data do we need to start?

Sales history by month, with product, customer and quantity, plus price and cost for revenue and margin. Load it as files or connect a supported source in Data & Context Studio. Which plan, forecasts and scenarios to build first is agreed in the Activation and Success Plan.

Plan on drivers, not vibes.

Bring this year’s plan and last quarter’s miss. We’ll walk through a baseline, scenarios and plan against actual on sample data.

Plate B2 · Series 2026