Logo clouds — 105 examples
A logo cloud borrows credibility from recognisable customers in a single glance. These examples show how SaaS sites present 'trusted by' bands — balanced, legible, and placed where they reinforce the pitch.
A logo cloud works on recognition speed, not scrutiny — a visitor doesn't read each name, they register in under a second whether the row contains brands they already trust, and that impression transfers to the unfamiliar product they're currently evaluating. That's why placement right below (or inside) the hero tends to outperform placement further down the page: it front-loads trust before the visitor has decided whether to keep reading. Consistent sizing and a monochrome or single-tone treatment matter more than they look like they should, because uneven logo sizes or a rainbow of brand colors reads as a hastily-assembled row rather than a curated one — and a short framing line ('Trusted by teams at') gives the row context instead of leaving a bare grid of marks that a visitor has to interpret unassisted.
Grafana's "logo cloud" is entirely compliance badges. Windsurf's is integration partners, not customers. A real look at how the same section slot gets reused for at least three different trust signals.
We read 24 real SaaS About Us pages against the same seven-module checklist — team photos, named people, stat tiles, timelines, investor walls, hiring CTAs, manifestos — and counted what's actually there. Only one page uses a timeline.
Dropbox's contact form asks for eleven things. Warp's asks for one. We counted the fields, the routes and the published email addresses on 25 real SaaS contact pages — and not one of them promises a response time.