This practice launched in 2026. Rather than dress up someone else's numbers or publish a
stock photo with an invented quote, here is exactly what we can prove today, what we will
publish when we can, and what we are offering the first companies who let us.
Everything below marked illustrative is a worked example showing the format a real
study will take. It is not a client and not a result. When we have real ones, they replace
these and this notice disappears.
What we can prove today
Our own site, audited by our own engine, published in full.
Including the checks we fail. It runs hourly, records its rubric version, and links the
raw JSON so you can check the arithmetic yourself.
It is not a substitute for a client result and we are not pretending it is. But it does
demonstrate the one thing a case study would: that the engine runs, produces evidence,
and that we will publish a number we did not choose.
46 of 49 scored dimensions passing. Two failures and one
partial, all published with the reason.
verified · not illustrative
The format
What a real study will contain.
Three worked examples, in the shape the real ones will take. Same rubric version at both
ends, evidence for every claim, and the things that did not improve reported alongside
the things that did.
B2B SaaSillustrative
Content invisible without JavaScript
A single-page application where the product and pricing pages returned an empty shell to
any crawler that did not execute JavaScript. AI assistants described the company using a
three-year-old press release, because that was the only readable source.
Readiness before
31
Readiness after
84
Fix
server rendering + text version
Engineering time
~2 weeks
Ecommerceillustrative
Structured data contradicting the page
Machine-readable prices and stock levels that had drifted away from what shoppers
actually saw. Assistants comparing products quoted stale prices and flagged items as
available when they were not.
Readiness before
47
Readiness after
79
Fix
schema regenerated from source
Engineering time
~1 week
Professional servicesillustrative
Accidentally blocking every AI crawler
A hosting default, never reviewed, that disallowed all AI user-agents. The firm had been
invisible to AI assistants for eleven months and had attributed the traffic decline to
market conditions.
Readiness before
22
Readiness after
71
Fix
crawler policy rewrite
Engineering time
~1 hour
These three are worked examples, not clients. The scenarios are drawn from failure patterns
the audit is built to detect; the numbers show what the report looks like, not what anyone
achieved.
Founding clients
Be one of the first three, and pay less for it.
We need real results to publish. You need this done at a lower price. That is a
straightforward trade and we would rather make it openly.
Thirty per cent off the audit and the first three months of any retainer, in exchange
for permission to publish the before and after — named if you are comfortable,
anonymised by sector if you are not. You approve every word before it goes up, and you
can withdraw permission at any point.
If the audit finds little worth fixing, we will say so and publish that too. A study
showing a site was already in good shape is still an honest study.