Ask better questions. Move commercial decisions forward.
Explore your commercial data, understand what changed and work through the next step, with answers grounded in your business context and actions governed by your permissions.
One question, followed through to the result.
A pricing lead asks where an illustrative distributor is leaking margin, then works through the response. Move between steps with the strip, or choose a follow-up.
Where is Northeast Distribution leaking margin?
Discounts and freight. $200K a year is recoverable, and the first two causes hold 84% of it.
Checked 4 sources · 2,140 records
- Reading 24 months of invoices2,140 records
- Joining price lists, freight and rebate programs
- Walking list to pocket for Northeast Distribution
- Comparing each step to the peer benchmark and your policy
- 1Discounts beyond policy184 accounts$92KCustomer pricing →
- 2Freight billed below cost41 lanes$76KCost and freight recovery →
- 3Rebate programs past their term2 programs$32KRebates and SPAs →
Recoverable = above the peer benchmark and inside your policy ·
Model the recovery. Keep the volume loss under 1%.
+$214K a year for −0.8% volume, inside your 1% limit. The corridor and freight terms close the two largest leaks and a list realignment adds the rest; the lapsed rebate programs are left out of the pricing model. Each lever is live.
Model run · 3 levers · 1% volume limit
- Loading the volume response modelbacktest error 4.1%
- Reading corridor floors and contract locks
- Simulating three levers inside the 1% volume limit
Volume response model · 24 months of invoices · backtest error 4.1% · run-rate chart: plan effective Oct 1, floor $1.90M
What happens if we act on October 1?
Pocket margin reaches 22.6% by March against the 22.4% goal, inside the forecast band, with volume holding inside the 1% limit.
Forecast · 6 months · 80% band
- Projecting pocket margin by month from the plan
- Fitting the forecast band80%
- Checking the goal+200 bps by March
Forecast · pocket margin as % of revenue · from the volume response model · band at 80% · goal +200 bps
Find the best moves inside our floors and contracts.
+$214K a year from 1,412 targeted moves, none of them a blanket increase. Each move stays inside its corridor, and 37 more SKUs are held to contract.
Optimizer · 1,449 SKUs · 37 held to contract
- Scoring 1,449 SKUs against corridor floors
- Holding 37 SKUs to contract
- Solving for 1,412 moves inside the volume tolerance
Optimizer · 1,412 moves across 1,449 SKUs · corridor floors, contract locks, volume tolerance ≤ 1.0% · solved in 2.4s
Draft the price action and the quote guardrails for approval.
Both are drafted and waiting for approval. One price action with the 1,412 moves, and four guardrail rules that matched as expected on six sample quotes. Approval and publishing follow your approval workflow.
Drafts saved · price action and 4 rules · dry run on 6 quotes
- Reading the 1,412 moves from the optimizer
- Saving them as a draft price actioneffective October 1
- Drafting four rules for the quote guardrails ruleset
- Dry-running the draft rules on 6 sample quotes
- Listing the approvals your policy requires
- Draft
- Approved
- Published
| # | Region | Account class | Pocket margin | Price move per account | Result |
|---|---|---|---|---|---|
| 1 | any | any | < 18% | any | Block the quote |
| 2 | Northeast | National account | any | > 2% | Route to the RVP |
| 3 | Northeast | any | any | > 4% | Route to the RVP |
| 4 | any | any | any | any | Allow |
Week 12. Did it work?
+205 bps realized against +218 modeled since the price action was published: 94% capture, a $201K annual run-rate against $214K modeled. The gap is two national-account exceptions, both signed and on the record.
Tracked · 12 weeks · 2 exceptions
- Reading the price actionapproved, published October 1
- Reading invoices since publish12 weeks
- Comparing realized to modeled by week
- Listing signed exceptions on the record
Realized against modeled · basis points by week since publish · from invoices · two signed exceptions on the record
Available actions follow your permissions and the relevant approval workflow. Illustrative data: the distributor and every figure are a worked example, not customer results.
Understand the answer. Take the next step.
Answers point to the records behind them, and the changes Copilot prepares go through your approval workflow.
- ExploreAsk follow-up questions and examine the records behind an answer.Copilot reads datasets, price lists, analyses and their definitions through its tools, and can open the record an answer drew on.
- PrepareDraft proposed changes for review.For example, a price action with its evidence, or rules for a ruleset with a dry run on sample quotes. A draft waits for the people who approve it.
- Act with controlUse the actions your role permits, where you are working.On a page, Copilot can open a record, a preset or the page’s editor, or run the page’s own update flow at your request. Approving and publishing follow your approval workflow.
How Copilot works with the page you are on
When Copilot answers on a page, it can ask that page to act: refresh the record, open the page’s editor prefilled, run the page’s own update flow, open a registered preset, move you to a record, or switch to one of the page’s tabs. The page decides whether it supports the request, and an unsupported request is refused rather than simulated.
Permission is checked on the server before a request is made, references to records are read-only, and links stay inside Revomo. These page requests sit alongside Copilot’s tools for reading records, running the engines and saving drafts; they are not the whole of what it can do.
For recurring and event-triggered work, explore Agents & Automation
Answers grounded in your commercial context.
Copilot answers in your terms because it reads the same foundation the rest of Revomo uses. An answer is only as sound as the data and definitions behind it, which is why each one points to its source.
- Your commercial recordsCustomers, products, prices, costs and agreements, with lineage from a figure back to the record behind it.
- Your business meaningThe definitions, units, formulas and relationships your team sets in Data & Context Studio. Copilot reads each column’s description and tags when it answers.
- Your permitted scopeCopilot’s tools are filtered to your role before the model sees them, so answers and actions stay within what you may see and do.
Your team sets up and reviews the definitions and mappings; suggested column types and tags stay editable.
- Explore Data & Context Studio How the foundation is prepared
- Explore Revomo AI How the intelligence architecture works
Start with the question you need answered.
UnderstandAnalytics and datasets
- Why did margin change this quarter?
- Which customers pay different prices for the same item?
EvaluateScenario planning and models
- What would a 3% price increase mean for this segment?
- Which agreements constrain our response?
Scenario answers come from Revomo’s planning and price-response models, not from the language model alone.
Follow throughApprovals and automation runs
- What is waiting for approval?
- Which items were excluded, and why?
“Revomo’s intelligent and adaptive platform ignited a vision of pricing as a catalyst for financial growth.”
Bring your next commercial question.
See how Copilot helps your team explore the evidence and work through the next step.