The logo wall is a hypothesis
A customer logo in a deck asserts that the company bought, that they are still customers, and that the relationship is meaningful. The slide distinguishes none of the 3, and all of them are testable before you have any access at all.
A logo on a slide asserts 3 things at once: that the company bought, that they are still customers, and that the relationship is meaningful. The slide distinguishes none of them.
Consider a vertical SaaS business presenting 20 enterprise logos on its second slide. Six were paid proofs of concept that ran 90 days and did not convert. Four are live but represent one team of 11 people inside organizations of 40,000. Two churned 14 months ago and the logo was never removed. Eight are exactly what they appear to be. The deck is not lying in any individual instance. It is answering a different question than the one a buyer is asking.
The base rate matters here, because it sets how much a logo wall can be trusted to age. The 2026 Aleph and Benchmarkit benchmarks, drawn from 342 SaaS and AI-native companies reporting full-year 2025 results, put median gross revenue retention at 84%, down from 88% the year before, with the bottom quartile at 76% and the top quartile at 91. At the median, a company loses roughly a sixth of its existing revenue each year before it wins anything new. A logo wall is a photograph of a moment, and the moment moves.
What you can check before anyone grants you access
Case studies carry dates and job titles. A case study whose named champion left the customer 2 years ago, and who was never replaced by a new named contact in any later material, describes a relationship that may have ended with that person.
Press releases and award submissions name customers more precisely than sales decks, because someone checked them. Compare the 2 lists.
Job adverts are unusually honest. A company that names accounts in a customer success job specification is telling you which relationships need active management, which is a different and more useful list than the logo wall.
The customer’s own procurement disclosures, where they exist, are definitive. In public sector and regulated verticals a contract is a matter of record, including its value and its end date.
Review site coverage tells you something about the shape of the base, though not much on its own. A company presenting 20 enterprise logos with 4 reviews has either a quiet customer base or a smaller one than the wall suggests, and which of those it is takes another check to establish.
Why this belongs before the LOI, not during it
The logo question is cheap to test and expensive to get wrong. If a meaningful share of the wall turns out to be pilots and lapsed contracts, the revenue base is smaller and younger than the deck implies, and so is every projection built on it. That is a conclusion worth reaching before you spend exclusivity, not during it.
It is also the rare commercial question that does not need seller cooperation. The evidence sits outside the company, in what other people have already published about it.
More insights
The tender was written for someone
In B2B software the best product does not always win the deal. Most buyers have a favorite before they speak to any vendor, requirement documents tend to describe the product the authors already know, and in many markets relationships and local presence count as much as features. For a buyer of a SaaS company, that changes how a pipeline and a win rate should be read.
Sold through someone else
A B2B2B software company sells to a partner, and the partner then has to sell to its own business customers. That puts 2 sales cycles, an onboarding project and a revenue share between the product and the revenue. The model can reach further than a direct team ever could, but a plan that counts signed partners as if they were selling will overstate it.
Last updated