Why we don't publish invented metrics in case studies

It's common in this industry to see case studies with confident, round numbers — 'increased conversion by 40%,' '3x faster load times,' '10,000 happy users.' Sometimes those numbers are real and well-measured. Often they're not, and there's no way for a reader to tell the difference from the outside.

We've made a deliberate choice not to publish a number we can't stand behind. If a client hasn't given us permission to share their actual metrics, or if attributing a business outcome cleanly to our work would be misleading — because marketing, timing, or a dozen other factors also moved the number — we describe what we built and why, instead of inventing a headline statistic.

This makes some of our case studies read less punchy than a competitor's. We think that's a fair trade. A prospective client evaluating who to trust with a real engineering project is better served by an honest description of the problem and the solution than by a number that can't be verified.

The same principle shows up in how we talk about ourselves generally — no claims about being 'the best' or 'industry-leading' without something concrete backing it up. Credibility compounds slower than marketing copy, but it's the only kind that survives a client actually checking.