Most companies have more analytics and dashboards today than ever before. Margin by region, discount by rep, and maybe even price realization by product family are all refreshed overnight and are a click away. Yet a surprising number of monthly or quarterly business reviews still end the same way. Someone points out a red metric or trend, everyone agrees it looks bad, and the action item is for someone to “dig into that.” Translation: do more analysis.
Earlier in this series we laid out the six things a real pricing system has to do. The fourth was turning analysis into a recommended action, and we kept it short there. This piece goes further into what that step requires, because it’s where a lot of good analysis quietly stops.
A red metric on a dashboard is not actionable
A dashboard is built to answer “what happened?” and it does that well. What it can’t answer on its own are the questions a pricing manager needs settled before changing anything. Which customers and products? By how much? Why those and not others? What should the policy allow? Who should sign off? Each of those usually takes a separate drill-down, often in a separate tool, done by the one analyst who (hopefully) knows where the data lives.
That’s why so many dashboard findings age out. By the time the analysis is finished, the quarter has moved on and the original question has been replaced by a new red metric.
There’s also a trust problem. A chart that says margin is down invites a debate about the chart. Which cost is it using? Are rebates included? Is that the right comparison period? A recommendation that shows its working moves the discussion on to the decision itself.
What “actionable” looks like
A recommendation someone can act on, and defend later to finance or to a customer, usually carries five things:
- Scope: the specific customers, products, or agreements involved, named rather than described.
- Size: the dollar impact if it’s carried out, and how much of that is reachable now versus later.
- Reasons: why these accounts and not others, traced back to the transactions, costs, and terms behind it.
- Limits: the pricing policy it stays inside, such as corridor floors and targets, the largest increase allowed for one customer, and contract terms that can’t be reopened yet.
- An owner: the person who approves it and the person who carries it out.
When one of these is missing, the recommendation tends to go back for another round. Without a size, it doesn’t get prioritized against everything else on the list. Without reasons, it rarely survives the first question from sales.
The same finding, two ways
Here is an illustrative example. A distributor’s quarterly review shows pocket margin in its Central region down 1.1 points on about $72M of annual sales, or roughly $790K a year.
Action item: someone to “dig into that” before next month.
- Scope
- 38 accounts in two product families, about $14M of annual sales
- Size
- About $640K a year at an average increase of 4.6%$510K reachable this quarter · $130K at six renewals
- Reasons
- Buying below the corridor floor; the transactions behind each account are attached
- Limits
- Inside the region’s policy; six contract prices held until renewal
- Owner
- Regional pricing manager approves
Mix: about $150K, to a sales conversation about product focus.
Only the recommendation says who acts, on which accounts, and for how much. Illustrative: a distributor’s Central region, $72M of annual sales, pocket margin down 1.1 points.
On the dashboard, that’s one red metric and a trend line. The obvious next questions go on the action list: is it price, cost, or mix, and which customers are driving it?
As a recommendation, the same finding arrives already broken down:
- About $150K of the slip is mix, with more volume going to a lower-margin product family, and that belongs in a sales conversation about product focus.
- The rest traces to 38 accounts buying two product families below the corridor floor, together about $14M of annual sales.
- Bringing those accounts back to the corridor target means an average increase of about 4.6%, worth roughly $640K a year.
- Six of the 38 accounts are on contract pricing until renewal, so the recommendation splits them out: about $510K is reachable this quarter, and about $130K waits for those six renewal dates.
- Every increase sits inside the region’s policy limits, so the approver is the regional pricing manager. The transactions behind each account are attached, so anyone can check the reasoning.
Nothing about the second version required a smarter analyst. It required the analysis to happen where prices, costs, terms, and policy are already connected, so the drill-down doesn’t start from scratch every month.
A (human) person still makes the call
A recommendation is the starting point for a decision. There might be more recent insights that are not represented in data anywhere yet. The pricing manager may know that two of those accounts are in the middle of a competitive bid, or that a large customer is about to consolidate its spend. A good recommendation makes it easy to act on that knowledge: exclude accounts, change the size of the step, or stage the increase over two quarters, and see the revised impact before approving.
What matters is that the change, and the reason for it, is recorded with the recommendation. The next person who looks at those accounts can see what was proposed, what was decided, and why.
Checking whether the decision held
The last part happens afterward. Ninety days after the Central region change, two questions matter: did realized prices on invoices move by the amount approved, and did those accounts keep buying at the volumes the recommendation assumed?
When the answer is no, the gap usually sits between the approved price and the invoiced price, through an old quote, a manual override, or a rebate that wasn’t adjusted. That gap is the subject of the next piece.
Tracking results also improves the next recommendation. Over a few cycles you learn which kinds of moves hold, which segments push back, and how much of a predicted impact usually shows up on the invoice.
Where to start tomorrow
Take the last three red numbers from your monthly or quarterly business review. For each one, check whether anyone acted on it, and how long it took to get from the chart to a specific price change. Then ask which of the five pieces above was missing when it stalled.
In most companies the same piece goes missing every time, and that’s the place to fix first.
Next in the series: the price you promised is not always the price they get.
At Revomo, this is the job of Decision Optimization, now in early access with selected customers. It recommends prices within the guardrails you set, explains each one, and keeps any override, the approval, and the measured result on one record. Findings that start the process come from Analytics & Insights. If you’d like to see what your own short list of decisions would look like, our margin assessment is a free first look.
