Case studies
Two studies are published. Both are about systems we built and run ourselves, which means every claim in them is one we can evidence line by line. Client work is not published here, because publishing a client outcome requires their approval and verified numbers, and we have neither on file for this build.
That is a deliberate gap rather than an oversight. An agency page full of unnamed clients and round percentages is worth nothing to you, since none of it can be checked. Ask us for a reference instead and we will connect you with someone who can talk.
Published
Written by the people who made the calls, including the ones that were wrong.
Internal build
SpinFlow.ai is our own enterprise AI platform. We built its frontend on the same stack we recommend to clients, so every constraint we describe in a sales conversation is one we have already hit ourselves.
Read the case studyInternal operations
Lingows runs core parts of its own operation, research intake, content pipelines, lead routing, and QA, through automation with human review gates. This is a description of the mechanics: what we automated, what compounded, what we left alone, and where it broke.
Read the case studyClient studies are gated
A client study only publishes here when three things are true. The client has approved the write-up in writing, the numbers come from an account we can point at, and the period covered is stated so nobody can read a seasonal spike as a trend.
Until then this slot stays empty. No anonymised composites, no illustrative figures, no stock testimonial.
Because we only publish work we can evidence. Client outcomes need written approval and verifiable account data before they go on a public page, so our published studies cover systems we built and operate ourselves. References are available on request.
Related
Start with a diagnosis. The measurement plan is built before the work starts, not after.
