Work receipts
A simple proof board for public client work and shipped operating work. Purple Lotus and The Flower Shop are public clients. Under the Conversion Engine a result starts as a baseline with a date range, and the lift comes after it, with the evidence and context attached.
Where proof stands
Purple Lotus and The Flower Shop are public clients. We do not show performance numbers we cannot back. A result starts as a baseline, read from a named source over a stated date range, before anything changes. The lift is published only against it, with the evidence and context next to it.
The standard
Every client result starts as a baseline: the rate, where it was read, and the dates it covers, written down before the first change ships. The lift is published against that baseline, with the client name and the window measured. If one piece is missing, the client can appear but the number waits.
The context
Revenue moves for many reasons. Each receipt will say what the system influenced and what other factors could have contributed, so a buyer can judge it fairly.
The proof now
The current proof is the client list plus the operating receipts below. Performance numbers publish when the evidence is complete enough to inspect.
Operating receipts
Before a public counter is useful, the underlying activity has to be real enough to explain. The operating receipts below show what is already wired.
The internal ledger tracks scorecards, scorecard-to-plan rate, qualified plans, paid-plan movement, Resend email movement, and owner follow-up.
Technical buyers now start with the AI Infrastructure Scorecard before the AI System Plan. That creates useful diagnostic work before a call.
The scorecard and planning paths now return a concrete workflow-gap hypothesis, the evidence needed to confirm it, and the next proof task before asking for a sales call.
The plan collects the business problem first and carries source, vertical, UTM, landing page, and first landing page into the planning record and email automation.
Public proof gate
A public counter is useful only after the underlying work is alive. Until replies, paid-plan movement, and closed revenue exist, the honest public evidence is this ledger.
A counter with no meaningful activity would distract from the real proof. The public live page waits until the ledgers can carry the story.
When the public counter launches, it should not call client revenue ARR. Use operating labels that a finance lead can plan.
Buyer names, reply context, and internal follow-up stay private. Public proof should be aggregated, permission-safe, and clear about what it can prove.
Receipts ledger
This is the public version of the operating habit: name the work, show the evidence, and explain the context around the number.
| Date / window | Receipt | Evidence | Context |
|---|---|---|---|
| Public client list | Purple Lotus | Purple Lotus is a public Conversion System client. We can describe the work category now; performance results will publish when the baseline, date range, and evidence are ready to review. | Performance results publish only with a baseline, date range, evidence, and context. |
| Public client list | The Flower Shop | The Flower Shop is a public Conversion System client. We can describe the work category now; performance results will publish when the baseline, date range, and evidence are ready to review. | Performance results publish only with a baseline, date range, evidence, and context. |
| 2026-05-30 | Internal activity ledger | /admin/live tracks scorecards, scorecard-to-plan rate, qualified plans, owner follow-up, email movement, and paid-plan movement. | The public counter waits until the activity is meaningful enough to explain. |
| 2026-05-30 | Scorecard-first technical path | Technical pages route first to the AI Infrastructure Scorecard, then to the AI System Plan when the gap is serious enough. | The scorecard is a diagnostic. It is not a claim that a sprint is worth doing for every visitor. |
| 2026-06-01 | AI System Fit Preview | Scorecard and plan outputs now carry one likely workflow gap, evidence needed, next proof task, and recommended next action into the buyer dashboard and email automation events. | This proves the diagnostic plumbing, not buyer movement or public performance claims. |
| 2026-09-09 | Conversion Engine ledger | Each measured path has a place for its baseline: the rate, the source it was read from, and the date range. A proof row carries that baseline from the start, cannot be created with a result already filled in, and stays unpublished until someone publishes it deliberately. | The first number published from it will be a menu order flow, with its baseline and date range attached. |
Next step
A result only counts here when a baseline came first. The free plan picks the number to measure in your business before anything changes.
Build my AI system