Insights

Why we don't have case studies yet — and what we show instead

Every studio site has a case studies page, and most of them are the least trustworthy part of the site. Vague client names, metrics with no baseline (“40% faster!” — than what, measured how), and testimonials that read like they were written by the agency, not the client. We could produce something that looks like that. We’ve decided not to.

The actual reason it’s hard to skip

Case studies are supposed to answer one question: has this studio actually done the kind of work I need done, and did it go well? For a studio at our stage, being honest about that means being honest that our track record with Dexorus specifically is still short. Padding that out with vague or embellished project write-ups would answer the question with a lie dressed up as evidence — worse than not answering it at all, because it actively misleads.

So instead of manufacturing case studies, we’re doing two things.

Concept Work, labeled as exactly what it is

Where we show work that hasn’t shipped as a paid client engagement — architecture explorations, tools we’ve built for ourselves, speculative approaches to problems we find interesting — we label it plainly: Concept Work, Selected Explorations, or similar. Never dressed up as a completed client project. Never given a fake client name to sound more credible. If you read something on this site and it isn’t obviously a case study, that’s deliberate, not an oversight.

This isn’t just an ethical preference. It’s also more useful to you as a prospective client. A labeled concept piece tells you how we think and what we’d actually do with a problem — which is closer to what you need to evaluate us on than a polished but thin case study would be anyway.

Writing that shows our actual thinking, in public, before you hire us

This Insights section exists for the same reason. A case study shows you the outcome of a decision after the fact, usually with the messy parts edited out. A piece like this one shows you how we reason about a problem before there’s a client relationship shaping what we’re willing to say. You can read how we scope a build, what a week of advisory work actually looks like, or where we draw lines around AI use in delivery — and judge our judgment directly, rather than trusting a curated highlight reel.

What changes once real engagements exist

Once we’ve delivered work for actual clients, and once we have their permission to talk about it, we’ll add real case studies — with real names, real scope, and real outcomes, not sanitized to look better than they were. Until then, the honest answer to “what have you built” is: judge us on what we show you can verify — our positioning, our process, our writing, and the concept work we’re willing to put our own name on — not a fabricated track record. We’d rather be a studio you trust because we didn’t lie to you early, than one you stop trusting once you find out we did.