# The Vanished-Logo Read: Displaced, Delisted, Restructured, or Artifact

*Score any logo that vanished from a competitor's customer page on six dimensions and assign one of four verdicts, with a named second signal behind every Pursue Now.*

- Canonical URL: https://www.refolk.ai/guides/vanished-logo-read-competitor-customers
- Pillar: Sales and go-to-market
- Format: Framework
- Published: 2026-11-08
- Last reviewed: 2026-11-08
- Reading time: 19 min
- Keywords: competitor removed customer logo, how to tell if a competitor lost a customer, find accounts that left a competitor, competitor churn signals, monitor competitor case study page changes

## Key takeaways

- Only 45-59% of signed contracts in Common Paper's benchmarks included any publicity right, so a vanished customer logo shows a change in marketing permission before it shows anything about the contract.
- A Pursue Now verdict on a vanished competitor logo requires a named second signal: a removed script or verification record, a dated review naming the switch, or the account appearing in your own pipeline.
- In one DNS analysis, over 80% of domains kept at least one legacy verification TXT record, so a competitor's record that is still present proves little, while one that disappears is strong evidence of departure.
- Report a logo's removal date as a range between the last archive capture showing it and the first capture without it, never as a single day, because archive cadence varies widely.
- Time displacement outreach to the account's renewal date, not the removal date: evaluation windows open 60-120 days before renewal, and 95% of auto-renewed contracts carry only a 30-day non-renewal notice.
- In Refolk's index, 678 US professionals hold customer marketing, advocacy or reference titles against 261 in competitive intelligence, a 2.60 to 1 ratio between the people who run logo walls and the people who watch them.

A logo has just dropped off a competitor's customer page, and you need to decide whether that account really left them and belongs in this week's pipeline. This guide is for founders, account executives, SDR leads and competitive-intelligence analysts who make that call one logo at a time. It gives you six scored evidence dimensions, four verdicts with a set action for each, and one hard rule: no Pursue Now without a named second signal.

## What does a vanished logo actually prove?

On its own, a vanished logo proves that a page changed. It does not prove that a contract ended. Use it as a reason to run this read, and never treat it as the answer.

The pages that rank for "competitor removed customer logo" fall into two camps. Signal vendors treat a removed logo as a trigger to act on. A more cautious competitive-intelligence writer treats it as late confirmation, arguing that "by the time it happens the relationship has usually already ended". That writer also notes that "no study we could find quantifies logo removal as a churn indicator." Both camps are guessing, because nobody has published how often a removal reflects a real departure.

The contract mechanics are published, though, and they all point the same way. Common Paper's standard Cloud Service Agreement (CSA) is a widely used open SaaS contract template, and it grants logo rights by default. The provider may use the customer's name and logo "to identify the customer as a user of the product, for example on a customer list webpage." That default is easy to strike out. Common Paper publishes a replacement clause that reads: "Neither party may publicly announce the existence of this Agreement without the prior written approval of the other party." Some vendors also reverse the default in their own terms, so that the provider may use a customer's logo "only with Customer's prior written consent."

| Item | Value | Source |
|---|---|---|
| Signed CSAs with publicity rights, earlier benchmark | 59% | Common Paper |
| Signed CSAs with publicity rights, later benchmark | 45% | Common Paper |
| Change between benchmarks | -14 points | Derived |
| Renewal evaluation window | 60-90 days before renewal | Displacement playbook |
| Renewal evaluation window | 90-120 days before renewal | Incumbent-selling guide |

The earlier benchmark sampled more than 150 US-based B2B SaaS companies. Taken together, the two figures mean roughly half of signed contracts gave the vendor no publicity right at all. Many paying customers can never appear on a logo wall. A customer whose right lapses, or who withdraws it, can disappear from the wall and keep paying. Nobody has measured that second group. I also could not confirm whether logo rights survive termination under the CSA. If the competitor publishes its terms, read its publicity clause before you read its customer page.

> A missing logo tells you about marketing permission first and about the contract last.

#### What a vanished logo could be measuring

1. **Rendering** - Carousel, lazy-loaded grid, filter, or an image the archive never captured
2. **Page programme** - Redesign, featured-logo rotation, or consolidated customer pages
3. **Publicity permission** - No clause, a struck clause, or a lapsed or withdrawn right
4. **Corporate identity** - Acquisition, rename, or dissolution of the account
5. **Contract** - The account actually left the competitor

*You only reach the contract layer after ruling out every layer above it.*

## The six evidence dimensions and how to score them

Five of the six dimensions are scored 0, 1 or 2. The sixth, the corporate-event check, is a yes/no gate. A 2 supports a real departure. A 0 points to an artifact (a change that comes from how the page is built or published, not from the customer) or to a customer who is still paying.

| Dimension | 0 | 1 | 2 |
|---|---|---|---|
| Removal mechanics | Logo still on the domain | Off the wall, case study still live | Gone everywhere, case study 404 |
| Archive history | No capture shows the logo | Range wider than 90 days | Range within 90 days |
| Page-wide context | Bulk redesign | Rotation, several in and out | Isolated removal |
| Live install | Competitor script still firing | Nothing found, or only a TXT still present | Dated removal or named replacement |
| Switch testimony | None | Undated, or one team at a large account | Dated, named, matches account |
| Corporate event | Gate: no | n/a | Gate: yes routes to Restructured |

### Removal mechanics

**What it proves:** the logo is gone from the whole domain, not just from the spot where you last saw it. **When it lies:** the logo has moved into a JavaScript carousel, a lazy-loaded grid, a second page of results or a filtered view. If the case-study URL still loads, cap this dimension at 1. The competitor is still publishing the story, so the wall change is probably cosmetic.

### Archive history

**What it proves:** the logo was there and then it was gone, inside a dated window bounded by two captures. **When it lies:** the archive's "closest" capture "does not prove the page stayed unchanged between captures", and a blank capture often means the content loaded through JavaScript the archive never saved. I set the cut between 1 and 2 at 90 days because that is the lookback at least one signal vendor uses for this signal. Tighten it if your own data supports a narrower range. A dated screenshot from your own team counts as a capture.

### Page-wide context

**What it proves:** whether this account was singled out. Diff the same pair of captures and count every logo added and every logo removed. **When it lies:** an isolated removal can still be a lapsed publicity right. This dimension rules out redesigns. It cannot rule out a withdrawn permission.

### Corporate event

**What it proves:** the company behind the logo still exists in the form you remember. Search UK Companies House, SEC EDGAR and the press for an acquisition, rename or dissolution inside the removal range. Also check the logos added in the same diff for the parent company's mark. **When it lies:** a small rename may never reach a registry. If the domain now redirects somewhere else, treat that as a yes until you have checked.

### Live-install corroboration

**What it proves:** the competitor's product is no longer running at the account. Sources include:

- Technology-detection indexes that record a first-detected and a last-detected date for each technology. At least one says it refreshes weekly.
- DNS TXT verification records and CNAMEs. Open-source scripts such as site-b2b-intel fingerprint vendors from these.
- Job posts at the account that name a replacement product.
- For developer products, a public repository that removed the competitor's SDK.

**When it lies:** it can mislead in both directions. A TXT record that is still present only means the account "has an account", not that it is a happy paying customer. A website tag that has disappeared may only mean the product moved off the website. A record that disappears is strong evidence. A record that is still present is weak, unless a competitor script is still firing on the site, which scores 0.

### Switch testimony

**What it proves:** someone at the account says they moved. Review sites ask reviewers "What did you switch from?" The answer is attached to the product the reviewer moved to, so search reviews of likely replacement products, not the competitor's own reviews. **When it lies:** a reviewer at a large company may speak for one team, not the whole account. Finding no testimony tells you little. One review-analysis vendor reports that of over 20,000 competitor reviews across nine platforms, 1,900+ name the product the reviewer left, which is fewer than one in ten.

> **Rule:** No Pursue Now without a named second signal
>
> A logo removal is never enough on its own. Every Pursue Now must name a removed script or record, a job post naming a replacement, a dated review describing the switch, or the account appearing in your own pipeline.

## Which verdict does the score produce?

Apply five rules in order and stop at the first one that matches. Each verdict comes with one set action, so the score turns straight into work.

1. **Removal mechanics is 0.** Artifact so Ignore.
2. **Corporate event is yes.** Restructured so Re-Resolve the Entity.
3. **Live install or switch testimony scores 2, and removal mechanics and archive history each score at least 1.** Displaced and Pursue Now. Whichever dimension scored 2 is your named second signal.
4. **Page-wide context is 0 and nothing scored 2.** Artifact so Ignore.
5. **Anything else.** Delisted but Likely Still a Customer.

Rule 3 deliberately comes before rule 4. A redesign can sweep a real departure off the page along with everything else. When that happens, the second signal carries the case and the logo drops out of the evidence. Rule 5 is the default because of the contract mechanics above. If the removal is confirmed and nothing else shows a departure, the likeliest explanation is permission. A live competitor script still firing on the account's site makes Delisted close to certain.

| Verdict | Typical score shape | Action this week |
|---|---|---|
| Displaced and Pursue Now | Removal and archive at least 1, plus a 2 on live install or testimony | Find the renewal owner and work the renewal window |
| Delisted but Likely Still a Customer | Removal confirmed, no 2 on corroboration | No displacement pitch, add to watch list |
| Restructured so Re-Resolve the Entity | Corporate event is yes | Identify the parent, rerun the read against it |
| Artifact so Ignore | Removal 0, or bulk redesign with no 2 | Log the reason and close |

#### Removal confidence against departure evidence

Horizontal axis runs from No departure evidence to Named, dated departure evidence. Vertical axis runs from Removal unconfirmed or bulk to Removal confirmed and isolated.

| Quadrant | What it means |
| --- | --- |
| Delisted, likely still a customer | Watch list, re-check before the renewal window |
| Displaced | Pursue now against the renewal date |
| Artifact | Ignore and log the reason |
| Departure without a clean removal | Work the second signal, the logo is not your evidence |

*Corporate events sit outside this grid, so check for them before you place a logo on it.*

Write every read down in the same shape. A shared record lets a second person check your verdict, and it stops the same logo being raised again next quarter.

**Vanished-logo read record**

```
VANISHED-LOGO READ
Account:
Competitor page URL:
Last capture showing logo:
First capture without logo:
1 Removal mechanics (0-2):      evidence:
2 Archive history (0-2):        range width in days:
3 Page-wide context (0-2):      logos removed in same diff:    logos added:
4 Corporate event (yes/no):     link:
5 Live install (0-2):           signal and date:
6 Switch testimony (0-2):       source, date, reviewer role:
Verdict:
Named second signal (required for Pursue Now):
Renewal date or estimate:
Action and owner:
Re-check date:
```

*One record per logo. Paste it into the account's CRM notes and fill every line, writing "none found" rather than leaving a gap.*

## How to run the read on one logo, step by step

The read has seven steps and takes about 75 minutes, split between a rep and a CI analyst. Steps 1 to 3 settle whether the removal is real. Steps 4 to 6 settle what it means. Step 7 turns the scores into a verdict.

#### The vanished-logo read

1. **Confirm the removal on the live page** - Render the page with JavaScript on, click through every carousel slide, paginated view, filter and site search, and check the case-study URL for a 404 or redirect. Done means the logo is absent everywhere on the domain.
2. **Pull the archive history** - Run a CDX query on the URL with collapse=digest and find the last capture showing the logo and the first without it. Done means a removal range bounded by two named captures.
3. **Check the page-wide context** - Diff the same pair of captures and count every logo added and removed, watching for a parent company's logo among the additions. Done means isolated removal, rotation, or bulk change.
4. **Check for corporate events** - Search registries and the press for an acquisition, rename or dissolution inside the removal range. Done means a yes or no with a link.
5. **Look for live-install corroboration** - Check the account's domain for removed tags with last-detected dates, removed TXT or CNAME records, and job posts naming a replacement. Done means a dated signal, or "none found".
6. **Look for switch testimony** - Search reviews of likely replacement products and public posts for someone at the account naming the switch. Done means a dated, named source whose role and company size match the account, or none.
7. **Assign the verdict and action** - Apply the five verdict rules in order and write the named second signal into the record for any Pursue Now. Done means one verdict, one action, one owner and a re-check date.

For step 2, the Internet Archive's CDX API returns these default fields for each capture: urlkey, timestamp, original, mimetype, statuscode, digest and length. `collapse=digest` drops consecutive identical captures, so each row left in the result is a capture where the page actually changed. `filter=` takes a regular expression for a single field, and a leading `!` inverts it. `from=` and `to=` set the date bounds.

**CDX query for a competitor's customer page**

```
https://web.archive.org/cdx/search/cdx?url=competitor-domain.com/customers&collapse=digest&filter=statuscode:200&from=YYYYMMDD&to=YYYYMMDD
```

*Replace the domain and path with the exact page URL and set the dates a little wider than the window you suspect. Remove the filter line if you also want to see redirect captures.*

Take the two timestamps that bracket the removal and open them in the archive's Changes tool. It diffs two snapshots of the same URL and highlights what was added and removed, which gives you step 3 directly. If the API rejects you with HTTP 429, slow down and run it from an ordinary connection. One tester had the very first call from a datacenter server IP refused.

Step 5 is often the slowest step, because a job post naming a replacement tool is a dated signal that sits on a careers page nobody indexes by competitor. The same post also tells you who now owns the decision. Searching for the people behind those posts in [Refolk](/) collapses two lookups into one.

I ran this search: `Heads of RevOps at mid-market US companies that recently posted jobs naming a new CRM after leaving their previous one` - [see the full result list](https://www.refolk.ai/s/tkat8ravkr).

*Returns named RevOps leaders at accounts whose job posts already name a replacement CRM, which gives you both a dated live-install signal and the person who owns the next renewal.*

## How the vanished-logo read goes wrong

Every dimension has a way of misleading you, and most of the errors push toward a false Pursue Now. Run the check listed for each failure before you trust the score.

1. **Removal mechanics: carousels and lazy loading.** A logo pushed into a JavaScript carousel or a lazy-loaded grid looks deleted in an archive capture. *Check:* render the live page yourself, then open the logo image URL directly in the Wayback Machine. Images are separate files and were often captured on different dates, or never captured at all.
2. **Archive history: false precision.** Gaps between snapshots make a removal date look exact when it is not. During one documented stretch, archiving trouble cut page captures among news publications by 87 percent over five months. *Check:* always report a range between two captures, never a single day.
3. **Page-wide context: the redesign sweep.** A redesign trims 30 logos and one of them happens to be your target. One signal vendor's own documentation warns that competitors "redesign their sites, rotate featured logos, and consolidate customer pages for reasons that have nothing to do with churn." *Check:* count every removal in the same diff before you score.
4. **Publicity lapse: still paying, no longer shown.** With publicity rights in only 45-59% of contracts in Common Paper's benchmarks, many customers are never eligible for the wall. A lapsed or withdrawn right can take a logo down mid-contract, and nobody has measured how often that happens. *Check:* look for a live tag or TXT record that still points at the competitor.
5. **Live install: misleading in both directions.** A stale TXT record suggests the account is still a customer after it has left. A removed website tag suggests it has left when the product may simply have moved off the website. Treat a removed tag as a reason to investigate, not as proof that the contract ended.
6. **Switch testimony: one team speaking for many.** A reviewer at a large company may describe one department's switch. *Check:* match the reviewer's company size and role to the account before you score a 2.
7. **Corporate event: the parent's logo.** After an acquisition, the child's logo is often replaced by the parent's. That is not churn. *Check:* search the registries before any outreach.
8. **Timing: acting on the wrong clock.** The removal date tells you almost nothing about when to call. As one incumbent-selling guide puts it, "Reaching out 30 days before renewal when the prospect already committed to renewing is too late."

**80%+ - Domains with at least one legacy verification TXT record**

In one security firm's DNS analysis, so a competitor's record that is still present proves very little on its own.

> **Watch out:** Presence and absence are not equal evidence
>
> Companies rarely clean up old TXT records, so a record that is still there should never pull a Delisted read toward Pursue Now or away from it. Only a record that disappeared, with a date, scores 2.

## When should you act on a Pursue Now?

Act on the account's renewal clock, not on the date the logo disappeared. A Pursue Now verdict means you start this week, and what you start is finding the renewal date and the person who owns it. It does not mean sending a displacement pitch today.

The reason is the notice period. In Common Paper's earlier benchmark, 95% of auto-renewed contracts gave customers a 30-day non-renewal notice period. By the time a logo comes down, the account may already have served notice and signed with a replacement. Practitioners put the evaluation window at 60-90 days or 90-120 days before renewal. That window is the one you are aiming at.

What you do this week depends on what the second signal told you:

- **The replacement is named and it is not you.** Your target is now the replacement's first renewal. Log it, estimate the date, and start building the relationship well ahead of the window.
- **The departure is confirmed but no replacement is named.** The account may still be evaluating, so open the conversation now.
- **The account appeared in your own pipeline.** Treat it as an active opportunity and brief the owner on what the read found.

Set expectations with whoever owns the number. One glossary reports competitive displacement at a 6-9 month sales cycle with a 15-20% win rate. A clean Pursue Now improves your timing and your opening line. It does not shorten the deal.

For Restructured verdicts the first job is different. Find out which entity now holds the contract, and who at the parent runs the tool, before anyone writes a word. [Refolk](/) handles that re-resolution in plain English. Ask for the IT or RevOps owners at the acquiring company and you get the people who now sit where the old buyer sat.

## Who owns the logo wall, and why it matters for your read

The people who maintain logo walls are mostly customer-marketing staff, and in the US they outnumber competitive-intelligence staff by more than two and a half to one. That matters because the removal decision probably follows marketing workflows, such as reference permissions and case-study refreshes, not the contract system. Whether customer-marketing teams remove logos without CI being involved is unverified.

**2.60 : 1 - US customer-marketing staff per competitive-intelligence staff**

In Refolk's index, 678 US professionals hold customer marketing, advocacy or reference titles, against 261 in CI analyst, manager or lead roles.

| Market | Customer marketing, advocacy, reference | Titled "Customer Marketing Manager" (n=25) |
|---|---|---|
| United States | 678 | 76% |
| United Kingdom | 267 | 92% |
| US to UK multiple | 2.54x (derived) | n/a |

| Function, US | Count | Most common title in sample |
|---|---|---|
| Customer marketing, advocacy, reference | 678 | Customer Marketing Manager (19/25) |
| Competitive intelligence | 261 | CI Analyst (13/25) |
| Ratio | 2.60 : 1 (derived) | n/a |

In Refolk's index, "Customer Reference Manager" never appeared as a top title in samples of 25 profiles in either country. If you are looking for the people who run reference programs, search for Customer Marketing Manager. The current employers in the US sample include Starburst, Synthesia, Kantata, Profisee and Exterro. The UK sample includes Gearset, SUSE, ZeroFox and Google Cloud.

This gives you the cheapest calibration available, which is your own company. Ask your customer-marketing team how many logos they took down in the last year and why. If most were permission or refresh decisions with the customer still paying, you have local evidence for leaving Delisted as the default verdict. No published study gives you that number, so measure it at home.

## Keeping the read current

A verdict is a snapshot. Delisted and Pursue Now both decay, so every record carries a re-check date, and the re-check repeats steps 5 and 6 only. The removal itself does not change. The evidence around the account does.

Set the re-check for a Delisted account to land before its estimated renewal window, so a departure that shows up late still reaches you in time. Re-check a Pursue Now when the replacement's first renewal approaches. Technology-detection indexes that say they refresh weekly will show a removed tag within days of it happening. TXT records and review sites have no published lag, so check them by hand. Nobody has published the typical gap between a contract ending and any of these signals changing. Note what you observe in your own records, and adjust your re-check timing to fit.

Archive cadence differs a lot from page to page, so if a competitor's customer page is captured rarely, take your own dated screenshots of it. Then your next read starts with a tight range instead of a wide one.

#### Before you file the verdict

- [ ] The logo is absent from the live, JavaScript-rendered page, every carousel slide, every paginated view, site search and the case-study URL.
- [ ] The removal date is written as a range between two named captures, not a single day.
- [ ] Every logo added and removed in the same diff has been counted, including any parent company's logo.
- [ ] A registry and press search for an acquisition, rename or dissolution inside the range returned a linked yes or no.
- [ ] Live-install evidence is dated, or the record says "none found".
- [ ] Any switch testimony matches the account's company size and the reviewer's role.
- [ ] Every Pursue Now names its second signal in the record.
- [ ] Every Pursue Now carries a renewal date or estimate and a named owner.
- [ ] Every Delisted account carries a re-check date that falls before its estimated renewal window.

## Frequently asked questions

### Does a competitor removing a customer logo mean the customer churned?

No, not by itself. A removed logo proves the page changed, not that the contract ended. Common Paper's benchmarks found publicity rights in only 45-59% of signed contracts, and a customer can withdraw permission while still paying. Treat the removal as a prompt to check the other five dimensions, and only call it a displacement when a second signal, such as a removed script or a dated review naming the switch, backs it up.

### How do I find out when a logo was removed from a competitor's website?

Query the Internet Archive's CDX API for the page URL with collapse=digest, which drops consecutive identical captures, then find the last capture showing the logo and the first without it. That pair gives you a date range, not a date. Open the logo image URL directly in the archive too, because images are captured separately and sometimes not at all.

### What counts as a second signal for a Pursue Now verdict?

A second signal is dated evidence of departure that does not come from the logo wall. Valid examples are a competitor script or tag removed from the account's site, a verification TXT or CNAME record that disappeared, a job post naming a replacement product, a dated review from someone at the account naming the switch, or the account showing up in your own pipeline.

### Should I reach out as soon as I see a competitor's customer logo disappear?

Reach out this week only if the read returns Pursue Now, and frame the outreach around the account's renewal date, not the removal date. With a 30-day non-renewal notice in 95% of auto-renewed contracts, the account may already have chosen a replacement by the time the logo comes down. Evaluation windows open 60-120 days before renewal, so that is the clock to work against.

### What do I do if the account was acquired around the time the logo vanished?

Score it Restructured and re-resolve the entity before any outreach. After an acquisition the parent's logo often replaces the child's on the same page, which is not churn. Confirm the deal in a registry or press link, find out which entity now holds the contract and who owns the tool, then run the read again against the parent.

### How long does a vanished-logo read take?

Roughly 75 minutes for one logo, going by the time estimates for each step: 10 minutes to confirm the live removal, 15 for archive history, 10 for page-wide context, 15 each for corporate events and live-install checks, and 10 for switch testimony. The verdict itself takes a few minutes once the scores are written down.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/guides/vanished-logo-read-competitor-customers*