The logo wall is a hypothesis
Customer logos in a deck are the least verified claim in most software transactions. Some were pilots that never converted, some were single departments inside large organizations, and some are contracts that lapsed a year ago. This is testable before you have any access at all.

A logo on a slide asserts three 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 twenty enterprise logos on its second slide. Six were paid proofs of concept that ran ninety days and did not convert. Four are still live but represent one team of eleven people inside organizations with forty thousand employees. Two churned fourteen months ago and the logo was never removed. Eight are real. The deck is not lying in any individual instance. It is just answering a different question than the one a buyer is asking.
This matters more than it used to. The 2026 Aleph and Benchmarkit benchmarks, drawn from 342 companies, put median gross revenue retention at 84 percent for full-year 2025, down four points from 88 percent the year before, with the bottom quartile at 76 percent. At the median, a company loses roughly a sixth of its existing revenue every 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 two years ago, and was never replaced by a new named contact in any subsequent material, is a relationship that may have ended with that person.
Press releases and award submissions name customers with more precision than sales decks, because they are checked by someone. Compare the two lists.
Job adverts are unusually honest. A company that lists named accounts in a customer success job specification is telling you which relationships require 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 movement tells you about the shape of the base. A company with twenty enterprise logos and four reviews has either a very quiet customer base or a much smaller one than the wall suggests.
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 is pilots and lapsed contracts, the revenue base is smaller and younger than the deck implies, and so is every projection built on top of 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 teardowns
Nobody can state the ROI, so nobody can defend the price
A company that cannot express what its product is worth in the customer's own numbers will discount under pressure, lose renewals it should win, and never raise prices. This is one of the most tractable problems in the first hundred days after an acquisition.
Pricing built before the market changed
Most software companies at this size price per seat, on a model set years ago. Buyers increasingly want to pay for consumption or for outcomes, and investors increasingly prefer it. Moving is valuable and moving carelessly transfers real risk onto the vendor.
Last updated

