"Maya saved you $X" — measured, never invented

How the measurement works

The ledger compares actual waste and over-ordering against the pre-Maya baseline, and records attributable events when her approved actions change outcomes. Deliberately conservative: undercounting is a feature, because a savings number you can defend is worth ten you cannot.

Where you see it

A savings card on the dashboard, a line in the weekly brief, and an answer whenever you ask her directly. Renewal day arrives with receipts.

The honest caveat

Savings depend on your data being connected and your recipes/inventory in use. With thin data Maya says so — the refusal to fabricate applies to her own report card first.

Why the number is deliberately small

Software ROI claims are usually built to impress: generous assumptions, a favourable baseline, and no way for a customer to check. The ledger here is built the opposite way — it compares measured waste and over-ordering against the prior period, records attributable events only where an approved action actually changed an outcome, and projects forward conservatively.

Undercounting is the design goal. A figure you can walk into a renewal conversation and defend line by line is worth more than a larger one that collapses under a question.

And why it starts at zero

With nothing measured, the ledger reads zero and says zero. No modelled savings, no illustrative figures, no averages borrowed from other businesses. The number becomes meaningful only after enough of your own history exists for the comparison to mean something.

For the same reason this website publishes no dollar-savings claim for Maya at all: there is no measured pilot yet, so there is nothing honest to publish. When there is, it will be stated with its method.