Sales and trade

Who approves when an agent changes a price or pays a claim?

Agents now draft quotes, shape schemes and check distributor claims. LeafCraft gives each of those decisions a named owner, a limit and a record.

One teamYour rulesYour memoryYour budget
Product screen · example dataLeafCraft console

What's changing in sales and trade

01

Agents touch price, schemes and claims

CRM and DMS vendors shipped agents that propose discounts, approve schemes and settle claims.

02

Every discount is a margin decision

An agent with no limit on discounts is a sales team with no limit on discounts.

03

Customers and distributors dispute from memory

When the question is who approved this price, the answer must be on record.

Two risks the layer removes

The agents you can't see, and the model that gets retired.

Agents you don't know about

In sales and trade, agents arrive through vendor updates and team pilots. LeafCraft finds all of them, gives each an owner, and brings it under your rules or removes it.

How discovery works

A model that gets retired

An agent built straight on one model has to be rebuilt and re-approved when that model is retired or repriced. On LeafCraft you switch the model for that agent in config and keep everything else. Months and a budget, saved.

Agent tied to one model
  • The model is retired or repriced
  • Prompts, tests and sign-offs rebuilt
  • Months of work, a new approval cycle
  • The history stays with the old tool
MonthsA rebuild budget
Agent on LeafCraft
  • Pick another model for that agent
  • Switching is a config change
  • Test it against your own record first
  • Rules, limits, owner and memory stay
HoursNo rebuild
TimeHours to switch, not months to rebuild
CostNo rebuild budget, no new approval cycle
MemoryThe record carries over to the new model
Your choice of model

Why it matters now

In sales and trade, the agents arrived before the rules did.

Sales and trade move the money that shows up as margin. Agents now propose prices, approve schemes and pay claims. The layer gives each one a limit it earned, a named person above that limit, a checker that is never itself, and a record that settles any dispute in seconds.

How the layer works

AI and people, one team

Your sales and trade team, with AI on the org chart.

Does the work
Decides
Checks
AI drafts. A person decides. Another agent checks.

The agent prepares the case. Your person makes the call and writes why. A separate audit agent checks the decision against your rules.

Same rules for every seatNo one checks their own workOne named ownerCost set before it runsBoth reasons recorded
No one checks their own workAgent or person. Maker and checker are never the same.
One named owner per decisionNever "the system".
Authority earned from the recordWidens with clean work. Narrows after mistakes.
People stay where they workSlack, Teams, WhatsApp (coming) or email. Their reply moves the work on.

What changes for you

Today
With LeafCraft
Discounts proposed by an agent with no limit
Limits per agent, widened only by the record
Schemes approved in a chat
Escalation to named people, by value and impact
Price disputes argued from memory
Who approved which price, and why, on record
Agent spend hidden in trade budgets
Cost per claim, per scheme and per region, set first
Silence is never a yesEstimated before it runsNothing erased after it's written
Decision request in Microsoft Teams · example dataLeafCraft console

Questions teams ask

Can a person still own pricing?

Yes. Any role can be a person or an agent. Many teams keep pricing with a person and let an agent check it.

What if the manager is on leave?

If the person you named does not reply in time, the work moves to the backup you named. Nothing is paid on silence.

Does the agent get a sales manager's access?

No. Every agent has its own login with only its role's access, never the access of the person who set it up.

Bring one sales and trade process.

We'll map who does the work, who decides and who checks, set the cost limits and show you the record.