FMCG and consumer goods

Who approved this distributor claim, and can we show why?

Agents already sit inside your DMS, your SFA and your trade scheme tools. LeafCraft puts them and your people under one set of rules, with every decision recorded on your side.

One teamYour rulesYour memoryYour budget
Decision request in Microsoft Teams · example dataLeafCraft console
Trusted by
MiVi
mediamint
Bhashini
Neurasix
Wyra

What's changing in FMCG and consumer goods

01

Trade spend is the second largest cost line

Schemes, claims and settlements move money every day, through many hands and several systems.

02

Agents arrived inside DMS and SFA

Vendor updates added agents that read claims, suggest settlements and nudge orders, under the vendor's defaults.

03

Promoters and CFOs ask one question

Who approved this, and can we show why? The answer is spread across tools and inboxes.

Two risks the layer removes

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

Agents you don't know about

In FMCG and consumer goods, 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 FMCG and consumer goods, the agents arrived before the rules did.

In consumer goods, the money moves in small amounts at high volume: claims, schemes, credit holds and settlements. An agent that gets these slightly wrong at scale costs more than a person ever could, and nobody notices until the quarter closes. The layer puts every one of those decisions under a named owner, a limit and a record.

What the record answers hereWhich schemes ran, who approved each claim, and what every settlement cost.
How the layer works

AI and people, one team

Your FMCG and consumer goods 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
A claim settled by an agent nobody named
Every settlement has an owner, AI or person, and a limit
Scheme overlap found at month end
An agent checks a scheme before it goes live, and a person decides
Distributor disputes argued from memory
The record shows who approved what, and why, in seconds
Trade spend on AI seen on the invoice
Cost per claim, per agent and per region, set before it runs
Silence is never a yesEstimated before it runsNothing erased after it's written
Product screen · example dataLeafCraft console
LeafCraft sells no agents, no models and no compute.
NeutralGains nothing from your choice of agent or modelYoursRuns in your cloud, VPC or on-premOpenAny model, any cloud, MCP and A2AEqualBought, built and people, same rules
Why that matters

Questions teams ask

Our DMS vendor already ships an agent. Do we have to replace it?

No. You keep it. A bought agent joins LeafCraft over A2A, MCP, a web address or a custom connector, and then follows the same rules and leaves the same record as the agents you build.

Who on our side should own these rules?

Name one senior owner, with the CIO, the business head and risk at the table. In many promoter-led companies, the MD and the CFO sign off the limits.

Will this slow down claim settlement?

Clean claims within an agent's limit settle without waiting for anyone. Only claims above the limit or outside the rules go to a person, and if that person does not reply in time, the claim moves to the backup you named.

Bring one FMCG and consumer goods process.

We'll map it with you: which roles are AI and which are people, who decides, who checks, what it costs and what gets recorded.