Why there are no client logos on this site
Most IT services sites open with a wall of logos. Ours doesn't, and the reason is worth explaining — because it also tells you how we'll treat your name.
If you've compared a few IT services companies recently, you'll have noticed the pattern. Somewhere in the first screen there's a row of greyed-out client logos, usually with a line like "trusted by industry leaders". Ours doesn't have one, and enough people have asked about it that it's worth writing down.
The short version
We don't publish a client's name or logo without their written permission. Not many of our clients have given it. So the wall would be short, and a short wall padded out with logos we don't have permission to show would be worse than no wall at all.
That's it. There's no clever positioning behind it.
Why the permission bar is high
There's a widespread assumption in this industry that using a client's logo is fair game once you've invoiced them. It isn't, for three reasons.
Trademark is the boring one. A company's logo is their mark. Using it to promote your business implies an endorsement they haven't given. Most won't chase you over it, which is not the same as it being fine.
Confidentiality is the real one. A good share of our work sits under an NDA that predates any conversation about marketing. When we've built a lending platform or audited someone's infrastructure, the fact of the engagement is itself information about them — what they were worried about, what they were investing in, sometimes what they were about to launch.
And then there's the signal it sends. If we'd put your competitor's logo on our homepage without asking, you'd be right to wonder what we'll say about you at the next pitch.
What we do instead
Three things, none of which are as visually satisfying as a logo grid.
We describe the shape of work without identifying who it was for. You'll see that on our service pages: "a distributor running stock, pricing and dispatch across shared sheets" rather than a company name. It's enough to recognise your own situation in, which is the only job that section actually has.
We publish case studies only where a client has agreed in writing, and we let them read it first. That's why our case studies is a slow-growing list rather than a content-marketing engine.
And we offer references properly. Ask during scoping, and where a client has said yes, we'll arrange an introduction to someone in a similar situation to yours. A fifteen-minute conversation with a real customer tells you more than thirty logos ever could.
The trade-off, honestly
This costs us. Logo walls work — they're a fast credibility heuristic, and buyers use them. Not having one means we're asking you to evaluate us on the way we talk about the work instead, which is slower and harder.
We think that's the right trade. An IT partner will end up holding your source code, your infrastructure credentials and quite often your customer data. How a company treats information that isn't theirs is worth knowing before you hand any of that over, not after.
If you want proof of what we can do, ask us to scope something. The first conversation is free and the document is yours either way — including if you take it to someone else.
- how we work
- trust
- marketing