Testimonials and case studies
A testimonial tells a story. A case study measures.
Anyone can line up ten happy clients saying "we had a great experience": it costs half a day and proves nothing. This page explains what we publish instead of testimonials, with what method we measure it, and where to find the cases in full.
What you'll find where
Here: how we measure, what makes a result verifiable by a third party, and the numbers that don't flatter us.
On /casi/: the cases told in full — problem, diagnosis, architecture, maths, result — with their figures.
On /prove/: the network's numbers as a whole, re-read as of the date shown.
Three pages, three different jobs. None of the three repeats the others.
The criterion
Why we don't publish a wall of smiling faces
Not because happy clients don't exist. Because a testimonial, the way it's normally used, doesn't carry the one piece of information a decision-maker needs.
What a testimonial is
It's the account of an experience, told by whoever lived it. It has real value: it says what it was like to work together, whether the people showed up, whether the promises were kept. Those are things a number doesn't say.
What it doesn't say is how much. It has no time window, no calculation method, isn't comparable to anything else, and no one can verify it. It's a statement, and it's worth as much as the trust you have in whoever makes it.
What a case study is
It's the same story with four things added: the starting point, the window in which the measurement was taken, the method used to count the numbers, and the caveats that scale them down.
That last one is what sets a case study apart from a brochure. If part of the result is attributable to a condition that no longer exists, we say so before anyone else discovers it — and we also say what the number is worth net of that condition.
We chose the lowest, most defensible truth over the prettiest lie.
It's the discipline's Fifth Law, the law of measurement: only the curve tells you whether trust is established or still to be verified, and one well-chosen data point proves nothing.
The method
How we count, when we count
Three rules, always the same, for every number we publish — on the site, in a case study or in a newspaper article.
-
01 We don't estimate
We count the records
A case's revenue isn't a summary figure interpreted after the fact: it's the sum of the referrals that succeeded, entered one by one into the APP by the partners who made them. Every row exists before anyone had an interest in adding it up.
-
02 We don't declare
We notarise
Every referral receives a certificate: the document's fingerprint goes on the Ethereum blockchain. It proves that document existed at a specific moment and wasn't modified afterward — the minimum for a third party to verify instead of having to take our word for it.
-
03 We don't round
We state the window
Every number carries the period in which it was measured and the method used, written down. A number without those two things doesn't go on the site, not even when it's a good one — especially when it's a good one.
The proof in reverse
Three numbers a testimonials page would never publish
We put them here because it's from the uncomfortable number that you can tell whether the good ones were measured or picked.
6%
Matches that get no response
Last 30 days as of 13/08/2026 · we published it when it was 10% and it hurt us
0 out of 61
Companies that reached the highest level on the scale
Stoic Analyses completed between 9 March and 7 August 2026 · the fifth rung has never been reached by anyone
2,141
Qualified Connectors, against a target of 3,250
As of 13/08/2026 · the target stated after the July event wasn't reached: between sign-ups and departures the network is stable
None of these three numbers helps sell anything. They're here because the promise is to publish them anyway, at regular intervals, with the same method we use to publish the others. A number that only comes out when it's convenient isn't evidence.
Where to continue
The cases, and the network's numbers
The case studies
The stories in full, with the starting problem, the architecture built, the measured figures, and the caveats that scale them down.
The network's numbers
How many Connectors, how many reachable companies, how many matches delivered and with what outcome — each with the date it was read.
The first step
The most useful case study to read is your own
AIRA-SCAN© measures the relational capital your company already has and tells you where the gap is: ten questions, three minutes, no sign-up.
Then the extended report arrives by email and within one working day someone calls you: you look at the result together and assess whether the AIRA-DX© Stoic Analysis makes sense for your company. It's free and limited to twelve a week, so it isn't owed to whoever does the check-up: it's decided together.
Prefer to just talk it through? The number is 0549 888808.