Client names withheld, numbers are not
Most of our clients are under NDA, so we publish the sector, the constraint, the decision and the measured result. The parts that prove competence are the parts we are allowed to show.
Aggregate figures, level five disclosure
Blended across engagements so no single client is identifiable from the numbers.
Median of the published performance engagements
Zero unplanned production stoppages
At hand over
Enforced in CI
Ten published, eighteen we cannot show
Deleting nine apps beat rebuilding the store
A Shopify storefront carrying fourteen apps, losing mobile buyers before the page finished painting.
- Mobile LCP
- -69%
- CLS
- -89%
- Conversion
- +28%
Website engineering · 5 weeks
Most traffic landed on pages nobody could buy from
Strong organic volume, weak pipeline, and a content library built on a publishing calendar rather than on intent.
- Enquiries
- +140%
- Indexed pages
- -68%
- Enquiry cost
- -24%
Growth · 12 months
Regulatory reporting that stopped eating nine days
Monthly regulator submissions assembled by hand across four systems, with no audit trail back to source.
- Cycle time
- -97%
- Restatements
- -100%
- Traceable rows
- +88pp
Data and intelligence · 9 months
Referral triage inside a boundary data cannot leave
Manual triage of inbound patient referrals, under a data residency rule that ruled out every hosted AI product.
- Triage time
- -85%
- Auto routed
- +68pp
- Misroutes
- -79%
AI and automation · 11 months
A tracking portal that stopped queueing behind itself
Peak hour timeouts on a shipment tracker, caused by a vendor system nobody was allowed to touch.
- p95 response
- -89%
- Throughput
- +290%
- Tickets
- -54%
Platforms and integration · 14 weeks
Replacing a system that was never allowed to stop
An AS/400 running the production line, with no maintenance window and nobody left who had written it.
- New line setup
- -88%
- Modules migrated
- +6
- Stoppages
- 0
Platforms and integration · 8 months
Three engineers, no leadership, always firefighting
A capable small team shipping constantly in the wrong direction, with founder attention as the only architecture.
- Unplanned work
- -22pp
- Engineers
- +4
- Incidents
- -84%
Leadership and assurance · 6 months
The chatbot we talked them out of building
Losing deals to response time, with every proposal assembled by hand from prior engagements.
- Turnaround
- -96%
- Hours returned
- +58
- Win rate
- +11%
AI and automation · 7 weeks
Images were eighty percent of the page weight
A property portal where the product is photography, and the photography was what made it unusable on mobile.
- Page weight
- -84%
- Mobile LCP
- -71%
- Enquiry rate
- +41%
Website engineering · 10 weeks
A two week assessment that moved a six month deadline
SOC 2 Type II required by an enterprise buyer, with a target date the organisation had no path to.
- Controls mapped
- +72
- Open gaps
- -70%
- Audit date
- defined
Leadership and assurance · 2 weeks
Sectors behind the portfolio
Counts include unpublished engagements. Every row is work delivered, not a market we would enter.
How much we publish, and why it varies
We publish at the highest level each contract allows, not the lowest. Where you see a sector instead of a name, that is the ceiling of the agreement.
| Level | What is published | Requires |
|---|---|---|
| 1 | Named client, logo and attributed quote | Written permission on file |
| 2 | Named client, no figures published | Written permission on file |
| 3 | Sector, size band and region | Permitted by most NDAs |
| 4 | Sector category only | Permitted in all cases |
| 5 | Aggregate across engagements | Permitted in all cases |
How we measure
Every figure on this site traces to a source artifact: a Lighthouse run, an APM export, a CRM report, dated and held internally against the case reference.
- Comparison windows are equal length and stated on the figure
- Nothing is rounded up. 38 percent is published as 38 percent
- Ranges are used where precision would identify the client
- A build fails if any published figure has no source recorded
Attributed by role and sector
They focused on bottlenecks before writing a single feature.
Head of Operations, logistics
The audit trail became usable for the first time.
Finance Director, fintech
Performance work produced results faster than a rebuild would have.
Founder, direct to consumer retail
Your engagement would be published the same way
You choose the disclosure level in the contract, before we start. Most clients pick level three and approve the wording before anything goes live.