How to Read a Listing Like a Buyer Who's Bought Before

Experienced buyers read listings sideways – what is highlighted, what is missing, what is being defended.

Your first listing, you read like a prospectus: top to bottom, every line, getting steadily more excited. Your tenth, you read sideways – what is highlighted, what is missing, what the seller is quietly defending. The gap between those two readings is measured in wasted weekends and the occasional five-figure mistake, because the most expensive thing a first-time buyer does is take a marketing document at its word.

That is what a listing is. A marketing document, written by someone trying to sell, describing an asset only they have seen from the inside. This is the oldest problem in second-hand markets – George Akerlof got a Nobel Prize for describing it in The Market for Lemons – and in small digital deals it is sharper than usual, because there is no dealer, no inspection, and no warranty. There is a page of text, some charts, and you.

The good news: sellers leak information constantly, in what they choose to write down and what they choose not to. You can learn to read the leaks. This piece is the method.

Reading order matters

An experienced buyer does not read a listing in the order it was written. The seller arranged that order to frame the asset. Reading it top to bottom means accepting the frame before you have seen the facts.

Read in this order instead. Financials first – the revenue chart, month by month, before a single word of prose. Then the traffic source mix, because where the customers come from tells you how durable the revenue is. Then the tech stack, briefly, mostly to check for anything that would make the handover painful. Then the seller's stated reason for selling. And only then, last, the product description – the paragraphs the seller wrote most carefully, read once you already know what the numbers say.

The effect of reading the description last is hard to overstate. Read it first and it colours everything: the revenue dip becomes "a temporary setback", the single traffic source becomes "a strong organic presence". Read it last and it becomes what it is – the seller's account of numbers you have already formed a view on. Where the account and the numbers diverge, you have found your first question.

Signal density: what is in the listing, and what is not

Every credible listing answers seven questions explicitly. A seller who understands what they are selling knows a serious buyer needs all seven answered before sending a message, whether or not a platform requires it.

• What does it earn, month by month, over at least a year? Absent, or compressed into a single average: the trend is unflattering. Averages are where declines go to hide.
• Where does the traffic come from, in rough proportions? Absent: concentration. In our experience the pattern most likely to sink a small content site after transfer is revenue that depends on one traffic source – and sellers know it, which is why the vague ones write "organic growth" and stop there.
• How is the revenue collected, and can it be shown at source? Absent: the numbers are self-reported summaries. A screenshot is a claim. A processor export or read-only dashboard access is evidence.
• How many hours a week does it take, doing what? Absent: more than the seller wants to say, or the honest answer is "it depends", which means founder-dependence.
• Exactly what transfers – code, content, domains, accounts, subscriber lists? Absent: the seller has not thought about handover, or something important does not transfer. Either way you are inheriting the problem. (What makes a project transferable is its own subject.)
• What does it depend on that the seller does not control? Absent: platform risk the seller would rather you discovered later. An asset built on someone else's API, algorithm, or app store prices differently, and sellers know that too.
• Why sell, and why now? Absent: the honest answer is unattractive. There are many good reasons to sell a working asset – burnout, a new job, a bigger project. A seller who offers none invites you to assume the worst, and you should at least test it.

A listing missing one of these is normal – sellers are founders, not dealmakers, and most are writing their first listing. A listing missing three or more is telling you how the rest of the process will go. The gaps are not accidents. They are the parts of the story the seller decided not to volunteer, and in a document whose whole purpose is persuasion, the unvolunteered part is where the risk lives.

The defensive paragraph

Here is the most useful single trick in listing analysis. Every listing written by a seller who knows their asset contains one paragraph that exists to pre-empt a question – the question the seller has already been asked, or dreads being asked, or has asked themselves at 2am. Find it. It is rarely hard to spot: it is the paragraph where the prose stops describing and starts reassuring.

"Traffic dipped earlier this year after a search update but has since stabilised." "The recent churn was a one-off from sunsetting a legacy plan." "Runs itself in five hours a week." That last one is the classic of the sub-$50k bracket, and the honest version is "five hours a week if nothing breaks". Ask what breaks.

The defensive paragraph is not a lie. Most sellers are not dishonest – they are selling, which is a different thing, and pre-empting a hard question is what any competent seller does. But the paragraph tells you, with unusual precision, where the seller believes the deal's weakness is. They have done your risk assessment for you and published the executive summary. Read it as exactly that.

A worked example. Take a fictional micro-SaaS listing, an invoicing tool at $900 MRR, listed around $30k. Four lines from the listing, with the experienced buyer's silent annotation under each:

"Profitable micro-SaaS for freelance invoicing. $900 MRR at 96% margin, runs on autopilot."
Margin quoted before trend. Expect the revenue chart to be flat or drifting down – a growing chart would have led.

"Built on a modern stack, recently refactored, fully documented."
A paragraph this early about code quality usually means there is less to say about revenue. And the code is the cheapest part of what you are buying – a competent developer can rebuild an invoicing tool faster than they can rebuild its customer base.

"Traffic dipped in the spring after a search update but has since stabilised."
The defensive paragraph. "Stabilised" is doing heavy lifting – stabilised at what level, for how long, and what share of revenue came through that channel? This is the question the seller expects. Ask precisely it.

"Selling to focus on a new venture."
The most common why-now and the least informative. Compatible with everything from a healthy pivot to quiet abandonment. The call will tell you which; the listing will not.

Twenty seconds of reading, and you have three sharp questions and a working theory of the deal. That is what reading sideways buys you.

What the numbers do and do not survive

Sellers rarely invent numbers. They reframe them. Knowing which metric is being quoted, and what it conveniently includes, is most of the game – in signalling terms, the cheap signals are the summary metrics, and the expensive ones are the raw exports.

A seller quoting ARR on a business with no annual contracts is signalling either inexperience or selective presentation. Both matter. Neither is disqualifying, but each changes how much weight the rest of the listing can bear.

Two ratios resist reframing, which is why experienced buyers compute them first. Revenue per visitor: a site with meaningful traffic and thin revenue has a monetisation problem no adjective fixes, and the inverse – decent revenue on modest traffic – is often the quiet mark of a real asset. And the most recent three months against the same three months a year ago: trailing averages and cherry-picked windows both dissolve against that one comparison. If the listing does not let you compute these two numbers, that is itself an answer.

Then ask for the source – the underlying export, rather than a tidier screenshot. Processor data, read-only analytics access, the raw thing. How a seller responds to that request tells you most of what the diligence phase would, several weeks earlier and free. In deals this size, trust is built in exactly these small mechanical moments, and a seller with clean numbers is usually pleased to be asked.

The five-minute scan

All of the above compresses into a protocol you can run on any listing before deciding whether it deserves a message. Five minutes, fixed order, no skipping ahead to the parts that excite you.

1. Revenue chart. Shape of the line, and the latest three months against the same period last year. Ignore the averages.
2. Traffic mix. Named sources with proportions, or vague hand-waving? One source above roughly two-thirds means the deal is a bet on that source.
3. Find the defensive paragraph. It is there. What is it defending?
4. The transfer list. What conveys, what does not, and whether anything important – the newsletter, the domain, the developer – is missing from it.
5. The why-now. Does the stated reason fit the shape of the revenue chart? A "new venture" over a two-year decline does not fit. A new job over a plateau does.

A listing that survives the scan has earned a discovery call. Most will not survive it, and that is the point – the scan exists to make sure the listings eating your evaluation time are the small number that deserve it. Curation helps here: listings on Indiemaker arrive pre-screened, which shrinks the noise, but no platform can read a listing for you. Evaluating the shortlist is still your job. The scan is how you keep that job small.

One more thing, for the sellers who have read this far and are feeling slightly exposed. Everything above is also a writing guide. Answer the seven questions before anyone asks. Put the defensive paragraph's subject in plain view with the numbers attached, and it stops being defensive – it becomes disclosure, and disclosure is what serious buyers pay for. The buyers you want are reading you sideways. Write the listing that survives it.