A deal desk that answers sales from the margin, the history and the bands.
The deal desk works the discount requests your commercial director works today. It checks each one against the bands, the margin rule and the account’s history, decides what its band allows, and routes the rest.
Discount requests raised on opportunities in your CRM by the account team.
It reads opportunities, account history, past discounts, price lists and margin rules. It writes the approval status on the request.
You set the discount bands and the margin rule. It approves inside its band, counter-proposes where a smaller discount or different terms would fit, and routes anything above.
It never sends a quote, never agrees terms with a customer, and never overrides the margin rule. The quote goes out from a person.
“Decide discount requests against our bands and margin rules. Approve within your band, counter-propose where a smaller discount or different terms would fit, and route anything above your band to the commercial director. Report to the commercial director.”
The floors no configuration can weaken
Seven limits sit under every level, level 5 included. Your own limits can only tighten them.
A person decides. The threshold is yours to lower, never to remove.
Nothing is signed, agreed, or terminated without a person.
A relationship is not a record to be closed. It stops with a person.
Reporting lines, roles, and who is accountable are set by people.
No AI employee can raise its own level or anyone else’s.
Anything leaving the organisation is gated, whatever the level.
Handled under your rules, with a person deciding on anything that acts on it.
A renewal approved inside the band, and a new deal countered.
Months later, finance can open either decision and see what it knew, what it was allowed to approve, and why it chose as it did.
Replay: months on, finance opens this record and sees the margin, the band and the counter exactly as they stood on the day.
Sales waits for the one person who can approve.
Routine requests are answered within its band, and only real exceptions wait.
Why a customer got a discount is lost by renewal time.
Every discount replays as it stood, with the margin and the band of that day.
Margin is checked after the deal is signed.
Margin is checked before approval, every time.
Two weeks on last month’s discount requests.
It proposes a decision for every discount request your team handled last month. You compare its proposals with what your people decided, and nothing in your systems changes.
Two-week retrospective evaluation
You see where it would have approved, countered or routed, and where it would have disagreed with your team, with the margin behind each.
Budgeted like an operational role · Zero token metering
Expenditure is tied to completed operational outcomes, not token consumption or prompt volume. A high-volume month or quarter never generates a variable surprise bill, providing fixed annual forecasting for CAIOs, CFOs, and Procurement leads.
Discount approvals
The pilot role. Routine discounts within the first band, everything else routed with a counter where it fits.
Customer credits
Decides credit requests from business customers within policy and its limit.
Credit limits and order holds
Decides orders over a customer’s limit on its payment record.
