For Sales, RevOps and trade marketing heads

Agents are acting on customers, prices and claims. Who approves when it matters?

Agents now sit in your CRM, DMS, SFA and trade scheme tools. LeafCraft gives every price, scheme and claim decision a named owner and a clear limit.

One teamYour rulesYour memoryYour budget
Decision request in Microsoft Teams · example dataLeafCraft console

What's changing for you

01

Agents act on customers, prices and claims

Inside your CRM, CPQ and DMS, under the vendor's defaults.

02

Every discount and scheme is margin

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

03

Disputes need a record, not a memory

Who approved this price. Who approved this claim. Answer in seconds.

Two risks the layer removes

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

Agents you don't know about

In your company, 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

What keeps you up

1

Prices sent without an approver

A quote or discount sent by an agent reaches the customer. There should be a named owner and a limit behind it.

2

Wrong claim payouts

A claim paid in error leads to a dispute with a distributor. Fixing it later costs more than checking it first.

3

Freedom from a vendor update

An agent gets new powers because the vendor shipped a release, not because it earned them on your accounts.

Why it matters now

One layer under every agent and every person.

You want agents to move faster than your pipeline, and you want every price, scheme and claim to have a named owner above a limit. The layer gives each agent a limit it earned, routes the rest to the people you name, checks every call with someone other than the agent, and keeps the record that ends a dispute.

How the layer works

What LeafCraft gives you

01

A named owner for every decision

Each quote, scheme and claim has one owner, an agent or a person. The reasons of both are kept side by side.

02

Limits earned from the record

An agent approves on its own up to a set amount once its record earns it. Above that, it recommends and a person decides.

03

High impact calls escalate

Large discounts and unusual claims go to the manager, then to senior leaders, by complexity and impact.

04

Your people stay in their tools

Sales managers get requests on Slack, Microsoft Teams, WhatsApp (coming soon) or email, and their decision moves the work on.

What changes for you

Today
With LeafCraft
Discounts with no limit
Limits per agent, widened only by the record
Schemes approved in chat
Escalation to named people, by value
Disputes argued from memory
Who approved what, and why, on record
Agent spend hidden in trade budgets
Cost per claim and per scheme, set first
Silence is never a yesEstimated before it runsNothing erased after it's written
Product screen · example dataLeafCraft console

Ask any AI agent vendor

Five questions for your next vendor meeting. They are the ones your auditor and your board will ask you. Ask them first.

  1. Who owns each price, scheme or claim decision your agent makes?
  2. Above what amount must your agent ask a person, and can I change that limit?
  3. Does your agent get more freedom because of a release, or because of its record on my accounts?
  4. Can you replay how one claim was approved, with the reasons?
  5. Can I export every decision, override and escalation if we change vendors?

Questions teams ask

Does this replace our CRM or DMS?

No. Agents read and write to the systems you already run. LeafCraft adds the rules, the limits and the record around them.

Can an agent check a claim my team prepared?

Yes. A person can do the work and an agent can check it, or the other way round. No one checks their own work.

Can we start from a template?

Yes. There are ready-made agent teams for sales, proposals and quote-to-cash, with sign-offs and an audit agent already in place.

Bring your hardest question.

We'll answer it on one of your own processes, with the record to show for it.