VantageVantage
Aug 20268 min read·deal tombstone page design

How should a deal tombstone page be designed to actually win mandates?

A tombstone page should be filterable by sector, size, and role, and every deal should carry one sentence of context a competitor could not have written. Generic logo walls are worth almost nothing. Here is how to structure a track record that converts a browser into a first call.

Charles Dewitte, Founder of Vantage Digital
Charles Dewitte
Founder, Vantage Digital

A deal tombstone page should be filterable by sector, deal size, and the role your firm played, and every entry should carry at least one sentence of context that a rival advisor could not have written. That specificity is the entire point: a wall of anonymous client logos proves nothing, while a track record that lets a prospect find the deal most like their own does most of the qualifying work before the first call. This piece covers how to structure, write, and constrain a tombstone page so it reads as evidence rather than decoration.

What is a tombstone page supposed to prove?

The term comes from the printed tombstone — the small announcement placed after a transaction closes, naming the parties, the size, and the advisor's role. On a website, the tombstone page is the digital version of that record: the firm's closed-deal history, presented as proof of capability. Its job is not to look impressive in the abstract. Its job is to answer one question a prospect is silently asking — have you closed a deal like mine, recently, in my sector, at my size.

That framing kills the most common design, which is a grid of client logos with no context. A logo wall says the firm exists. It does not say the firm can run your process. The best track records read like a filterable index of evidence, where a founder with a $30M industrials business can isolate the three deals that resemble theirs in under ten seconds.

Why does filtering matter more than layout?

A serious prospect does not want to admire your whole history. They want the subset relevant to them. So the primary interaction on a strong tombstone page is filtering — by sector, by deal size band, by transaction type (sell-side versus buy-side, recapitalization, add-on acquisition), and where relevant by the partner who led it. Each filter is a small act of self-qualification, and every self-qualified prospect arrives at the first call already warm.

This is the same principle that runs through the best PE and M&A firm websites of 2026: information density that an institutional reader can navigate, not a marketing page that flatters the firm. The layout should recede. The data should lead. A dense, well-paced table beats a sparse gallery every time an actual buyer is reading.

The filters should map to the questions a prospect actually asks, not to how the firm files its own deals internally. Sector is the first filter because it is the first thing a founder or sponsor checks. Deal size is the second because it establishes whether the firm operates at their level. Role is the third — a party evaluating the firm for a sell-side mandate wants to see sell-side deals, not a buy-side history that proves a different muscle. Where the firm has coverage partners, filtering by partner lets a prospect find the specific person they would work with, which connects the track record directly to the team page.

Beware of over-filtering. A page with twelve filter dimensions is as useless as one with none, because it signals a firm that has not decided what matters. Three or four filters that correspond to real buyer questions are enough. The goal is not a database interface; it is a fast path from a prospect's situation to the two or three deals that resemble it.

The one sentence that separates a real track record

Each tombstone needs a line of context, and that line is where firms either differentiate or blend in. Weak context restates the obvious: advised the seller on a transaction. Strong context names the thesis and the difficulty: ran a targeted process to a strategic acquirer after two financial sponsors dropped on customer concentration, closing above the initial range. The first sentence any advisor could write. The second one only the advisor who ran the deal could write, and that is exactly why it lands.

Where confidentiality prevents naming the counterparty, the context sentence carries even more weight, because it is the only differentiator left. Anonymized deals are fine — undisclosed acquirer, mid-market business services — as long as the sentence proves the firm understood the situation. This is also where the deal announcement and the tombstone connect: a fresh close should flow from an announcement page into a permanent tombstone entry, and our piece on announcing a closed deal covers that handoff.

Restraint is part of the discipline. Not every engagement belongs on the page. A track record that publishes only the deals that prove the current thesis reads sharper than one that lists everything the firm has ever touched. Curate for signal, not volume.

A logo wall says the firm exists. A filterable track record says the firm can run your process.

How much detail is safe to publish?

The instinct to protect client confidentiality often over-corrects into a page so vague it proves nothing. The resolution is tiering. Publicly announceable deals get full detail — parties, size, role, context. Sensitive deals get anonymized but specific detail — sector, size band, structure, and a context sentence that does not identify the client. The engagement letter and any confidentiality terms govern which bucket each deal falls into, so the rule is legal before it is editorial.

Deal size is the field firms most often hide and most often should not. A prospect uses size to decide whether the firm operates at their level. A page that shows a coherent band — say, transactions between $20M and $150M in enterprise value — instantly qualifies the firm for the right buyers and screens out the wrong ones. Vagueness about size does not protect the client; it just makes the firm look unsure of its own lane. For firms weighing where the tombstone page sits in a larger site, our guidance for M&A advisors and private equity puts it in context.

There is a design temptation worth resisting: turning each tombstone into a full case study with multiple paragraphs, images, and pull quotes. That inverts the ratio. The value of a track record is in the ability to scan many deals quickly and drill into the relevant few, not in reading a marketing narrative about each one. Keep the default view compact — party, size, role, one context sentence — and let a prospect expand a specific deal only when they want more. Density on the surface, depth on demand.

Finally, keep the page alive. A track record that has not gained an entry in eighteen months tells a prospect the firm has not closed anything recently, which is the opposite of the intended message. The fix is the workflow described in our piece on announcing a closed deal: every close flows into an announcement and then into a permanent tombstone, so the page grows as a byproduct of doing deals rather than as a project someone has to remember to do.

FAQ

Frequently asked questions

Should we show deal size if some clients are sensitive about it?

Show size as a band rather than an exact figure where a client is sensitive, since a coherent range still qualifies the firm for the right buyers. Hiding size entirely usually costs more mandates than it protects.

How do we handle deals we are not allowed to name?

Anonymize the parties but keep the sector, size band, structure, and a specific context sentence, so the entry still proves capability. The engagement letter and any confidentiality terms decide which deals can be named.

How many deals should the page show?

Enough to prove the current thesis and no more, because curated relevance reads sharper than exhaustive volume. Filtering matters more than count once the page passes a critical mass of representative deals.

Do prospects really use the filters?

Serious prospects use them to find the deal most like their own, which does the early qualifying work before a call. Casual browsers ignore them, which is fine because they were never going to convert.

Related
Keep reading