Niblin builds a driver-based forecast from an AI baseline on your own history, re-cuts it every month after close, and shows which drivers matter most to profit and cash.
See how Niblin models it
Baseline
Every forecast starts from an AI baseline built from your own orders and costs, spread into drivers by channel and month. Your edits sit on top, and removing an edit brings the baseline back.

Rolling
Each month the cycle opens, closed months switch to actuals, and the forecast rolls forward. When the CFO locks it, that version is committed and becomes the comparator for the next.

Change events
A new channel, fee, tariff, supplier or promo is a change to an input, not a modelling project. The working forecast takes it on, and committed versions keep their pinned assumptions.

Sensitivity
Niblin runs a sensitivity analysis on every driver, moving each one alone and measuring the effect on net revenue, contribution, EBITDA, net income and closing cash. Drivers are ranked so the team plans the ones that matter.

Link your stores, marketplaces, ad platforms and accounting system so actuals land from the source.
Niblin builds an AI baseline from your history and spreads it into drivers for each channel.
Planners adjust the drivers they own, with every change tracked against the baseline.
After close, the cycle rolls forward and the CFO locks the committed forecast.
A spreadsheet forecast works well for one channel and a handful of drivers. It gets harder to keep honest as channels, fees and SKUs multiply and every month adds another copy of the file.
| Spreadsheet model | Niblin | |
|---|---|---|
| Baseline | Spreadsheet modelTrend formulas you maintain | NiblinAI baseline built from your own history |
| Monthly re-cut | Spreadsheet modelRoll columns forward by hand | NiblinCycle opens and closed months switch to actuals |
| Version control | Spreadsheet modelFile names and saved copies | NiblinCommitted versions keep their assumptions |
| New channel or fee | Spreadsheet modelRewire formulas and links | NiblinA dated change to an input, no rebuild |
| Which drivers matter | Spreadsheet modelAd hoc flex tests | NiblinDrivers ranked by effect, with a tornado view |
| Audit trail | Spreadsheet modelCell comments, if anyone adds them | NiblinEvery edit tracked against the baseline |
The forecast is re-cut monthly, after the books close. Closed months switch to actuals and the horizon rolls forward. Between cycles, change events such as a new channel, fee or tariff update the working forecast so it never waits for the next re-cut.
Niblin builds an AI baseline from your own orders, prices, discounts, returns and costs, by channel and month. It is a starting point, not a black box: you can see the baseline, your edits on top of it, and where history was too thin to support a value.
Sensitivity analysis moves one driver at a time to show how much each one moves profit and cash. Scenarios change several assumptions together, such as entering a retail chain or raising prices. Sensitivity lives with the forecast; scenarios have their own planner.
Yes. Each channel carries its own drivers, fees, returns and payment timing, so a retail account, Amazon and your Shopify store are forecast on their own terms and then rolled up. Adding a channel does not mean rebuilding the forecast model.
Learn the method
Related solutions
A rolling, driver-based forecast for every channel you sell through.
See how Niblin models it