Logo soup is what happens when a group of customer, partner, or sponsor logos appears together without any visual consistency, producing a cluttered wall of mismatched shapes, sizes, and weights that's hard to read and easy to ignore. The term applies to two related problems: a design issue (logos that clash because of inconsistent aspect ratios and formats) and a messaging issue (a slide or page full of client logos that fails to build the trust it's meant to create). Both versions weaken the credibility signal the logos were supposed to send in the first place.
Logo soup shows up in two places: on websites and in sales decks.
On a website, it's the "trusted by" or "as seen in" row where a dozen partner or customer logos get thrown together and stretched, squeezed, or padded until they no longer look like a coherent set. It's a marketing technique comprised of a giant pile of logos mashed up so tight that the onlooker cannot make out any single logo (Urban Dictionary). A square icon logo towers over a wide wordmark, a heavy, filled-in logo overpowers a thin outline logo next to it, and the whole row looks assembled by accident rather than design.
In a pitch deck or sales presentation, logo soup means something slightly different but equally damaging: a slide packed with recognizable client logos that's meant to reassure a prospect but instead reads as self-congratulation. Logo soup slides act as a form of social proof, saying "look at all these big customers we've helped in the past, certainly, we can help you too" (Ethos3).
The design version of logo soup is almost always a file-format problem hiding as a design problem. Logo assets rarely arrive consistent. Marketing sends over a folder of partner logos as a chaotic mix of file formats, each with its own quirks: some perfectly cropped SVGs with transparent backgrounds, others PNGs with mysterious padding baked in, one with a thick confident stroke, another a thin wordmark that barely registers (Sanity). Line them up naively and the result looks less like a curated set and more like a ransom note.
Three specific issues combine to create the mess:
None of this is a taste problem. It's a measurement problem, which is why manual tweaking in a design tool never holds up once new logos get added.
The sponsorship and events version of logo soup has a different root cause: undifferentiated recognition. When every sponsor, regardless of contribution, gets the same-sized logo in the same row, the listing stops communicating anything specific. If an organization secures many supporters, these logo arrays can begin to resemble a word search puzzle, and being listed as one of many says there is nothing special about a sponsor except maybe that they gave more (Pitcher Group).
The instinct behind logo soup is reasonable: show the audience you've worked with respected names, and credibility should follow. In practice, the tactic often backfires, particularly in sales contexts.
The core issue is a narrative mismatch. What the seller is saying and what the buyer is hearing are two totally different things: the seller thinks they're communicating that they can help the prospect, but the buyer sees a list of massive global organizations and thinks, "how can they help me? I'm nothing like these big companies" (Ethos3). A small or mid-market prospect looking at a wall of enterprise logos doesn't feel reassured. They feel like the wrong audience.
This isn't just a hunch. Gong analyzed data on social proof selling and found a 22% lower close rate when it's used in sales calls (Ethos3). The mechanism behind that number tracks with the design problem too: a logo dump, whether on a slide or a webpage, points attention back at the seller instead of the buyer. Dig into logo soup slides and it all points back to the seller, saying "look at us, look at what we've done," which is really a bit self-serving (Ethos3). A prospect evaluating a SaaS tool doesn't want a highlight reel. They want to see themselves in the story.
This matters directly for Seedling's audience of early-stage SaaS founders. In the earliest sales motion, before a company has case studies for every segment, it's tempting to lean hard on a handful of recognizable logos to borrow credibility. Done carelessly, that logo section becomes noise instead of proof, and it can actively work against a founder trying to close a first cohort of customers who don't see their own size or industry represented in the wall of names.
The fix depends on which version of the problem you're solving.
For the design version, the practical answer is mathematical normalization rather than manual resizing. One documented approach uses proportional normalization based on aspect ratio, pixel density analysis so a dense wordmark doesn't visually overpower a thin logomark, and a center-of-mass calculation for optical alignment (Hacker News). The underlying formula takes a logo's aspect ratio, raises it to a scale factor, and multiplies it by a base size, which dampens extreme shapes without forcing every logo into an identical box. Applying this kind of formula (or using a component library built on it) turns a manual Figma chore that breaks every time a new logo arrives into a system that self-corrects.
For the messaging version, curation beats trying to include everything. Instead of listing every logo you can legally use, select the two or three that are most relevant to the specific prospect or audience segment in front of you, and pair them with context rather than a bare image. If logo soup and social proof selling don't work on their own, transformation does: painting the picture of where a customer is now versus where they can be (Ethos3). A single named customer with a specific outcome typically outperforms twelve unnamed logos.
For sponsorship and events contexts, the fix is structural rather than visual: connect each sponsor to a specific property, program, or benefit instead of a shared listing. The first step in avoiding logo soup and providing more value to sponsors is to develop a properties map, identifying the programs, facilities, and other aspects of the organization available for sponsorship (Pitcher Group). A gold sponsor tied to a named stage or session reads as a partnership. The same sponsor buried in a row of thirty logos reads as a rounding error.
It's worth separating logo soup from social proof itself, because the two get conflated. Social proof, done well, is specific: a named customer, a quote, a measurable result, or a logo placed next to context that explains why it's relevant to the visitor looking at it. Logo soup is what social proof becomes when specificity gets replaced by volume, when the goal shifts from "show this one detail matters" to "show as many names as possible."
The practical takeaway for anyone building a landing page, pitch deck, or sponsorship package is that fewer, better-placed logos with context will nearly always outperform more logos with none. If a "trusted by" section exists purely to fill space, it's worth asking whether it's building trust at all, or just adding visual noise that a normalization formula can tidy up but can't make persuasive on its own.
Some common questions, answered
Logo soup is a group of customer, partner, or sponsor logos displayed without visual consistency or meaningful context. Mismatched shapes, sizes, weights, and formats create clutter, while an excessive wall of names can weaken the credibility and social proof it was intended to provide.
Logo soup directs attention towards the seller rather than helping buyers see themselves in the story. Prospects may find a wall of enterprise logos irrelevant to their size or industry, while Gong data cited in the article found a 22% lower close rate when social proof was used in sales calls.
For visual consistency, normalise logos using aspect ratio, pixel density, and optical alignment instead of manually forcing identical dimensions. For stronger messaging, choose two or three relevant logos and add context, such as a specific customer outcome; in sponsorship settings, connect each sponsor to a named programme, property, or benefit.