What your BI already does
It reports spend against volume, by promotion and period, accurately. It tells you the two numbers moved together.
Your systems show that spend went out and volume went up. Sena sets the baseline underneath both, so each promotion carries the profit it actually added.
Spend went out and volume went up. Whether the second followed the first stays open.
Which promotions added incremental profit, which moved volume around, and where the next budget goes.
FMCGBeveragesSnack FoodsPersonal CareSpirits
Sena, the Decision AI from Rwazi.
Decision AI with access to real-world dataA promotion ran and volume rose twelve percent. Your BI reports both figures accurately. Four things could be true inside that one number.
People who would have bought nothing bought something. This is the case the spend was approved for, and it is one of four.
The same shoppers bought earlier and in bulk, then stayed away for a month. The quarter reads flat and the promotion reads successful.
Total demand held steady while it shifted between a grocery chain and a convenience one. Two territories now disagree about who grew.
Seasonality, a trend, or a competitor’s own gap would have delivered much of it anyway. The promotion took credit for the calendar.
Separating the four needs trade spend, sales history, a modelled baseline, and market conditions read at once. Your BI holds the first two.
Upload the promotion calendar with its mechanics, timing, target stores, and cost, alongside volume, revenue, and margin by SKU, territory, channel, and week. Sena reads your ERP exports and your CSVs.
Sena models what each SKU would have sold on a clean week, from your own history, seasonality, and trend. Every later number is measured against this line.
For each promotion Sena splits the rise four ways: incremental, pulled forward, moved between channels, and baseline. Then it prices the incremental share after the cost of the promotion.
Sena checks whether the discount reached the shopper or stopped at retailer margin. Add a store read and the shelf price confirms it directly.
Sena ranks every promotion by true incremental return, then models what moving spend from the weakest mechanics to the strongest is worth.
See which promotions earned their spend last quarter
See how Sena builds a baseline →The decomposition works the same on a temporary price reduction, a display programme, a multipack, and a gift with purchase, and the ranking is what makes them comparable.
| Capability | Role in this use case |
|---|---|
| Sena (Decision AI) | Core engine. It reads your trade spend and sales data, models the baseline, decomposes each lift, prices the incremental share, ranks every promotion, and models a reallocation. |
| Sena Connect and Integrations | Core. Brings your promotion calendar and sales history in by CSV or Excel upload. A direct ERP or CRM pipeline follows once you validate the POC. |
| Sena Computer Vision | Optional. Verify at the shelf whether a promotional price reached the shopper, which turns the pass-through rate from an inference into a reading. |
The engine runs on your own numbers. The optional store read is what closes the pass-through question, which your own data alone leaves open.
It reports spend against volume, by promotion and period, accurately. It tells you the two numbers moved together.
The baseline underneath them, and the split of the lift into incremental, pulled forward, channel-shifted, and already-coming volume.
A store read on the promotional price, so the pass-through rate rests on the shelf, where your own data can only assume it.
Sena
Illustrative interface. Numbers are an example, not a Rwazi result.
The core user. Set the trade budget against measured incremental return, mechanic by mechanic.
Revenue management solutions →Design the mechanics that actually pay, and retire the ones that only look busy.
Hold trade spend to a P&L standard, with an auditable baseline behind every claimed return.
Plan promotions with a retailer using return data, and allocate co-op funds against it.
Sales solutions →See how a promotion on one SKU moves the rest of the category, and plan the calendar around that.
A demo takes about 20 minutes. For most use cases, the first decisions land days after kickoff.
Every counterfactual carries the history it was built from, so finance can audit the line before the budget moves against it.
Add a store read and you see whether the discount reached the shopper, which your own data can only infer.
Find the low-margin products that carry your whole portfolio.
See the use case → UC · PricingSee the real in-store price of your products in the markets you sell in.
See the use case → UC · Portfolio & SKUModel what happens before you cut, add, or reposition a SKU.
See the use case →Tell us the decision you are weighing, and we will bring the market read to the conversation.
Bring the decision in front of you and we will run the first read against it on the call.