Find competitor customers with Clay and Claude, starting from evidence

Clay has a template for it. You enter a competitor's URL and Claygent finds its customer page and extracts the customers, so you can position your prospecting. That works only for competitors who publish customers. A second tutorial, from GrowthExe, runs the other way: it adds Clay's Get Competitors for a Company action to a list of companies you already have, then writes each competitor to its own table.

Anvendor's guide takes a third route and imports companies detected using a competitor into Clay through the HTTP API. All three give you a list. None says which accounts are worth contacting this month, and that is the part Linkeddit supplies.

Clay has a competitor review monitoring page that describes watching G2, Capterra and TrustRadius for churn indicators from competitors' customers, and a related action for finding their unhappy customers. Linkeddit stores reviews from those three sites and Trustpilot, as each site shows them, with the rating and the date, so Claude can read them over the connector.

Plan for sparse data. On the test project, the Fathom Analytics monitor had stored one review, a 5 star Trustpilot review from March 2023, and its G2 and Capterra fetches returned no results. The signals were more useful: Fathom's AI assistant launch was a high priority move dated 1 October 2026. A launch is a reason to review that competitor's customers, but it is not evidence that they are unhappy, and the prompt makes Claude label which is which.

No. Anvendor says competitor use establishes relevance to your category, not a paid contract, dissatisfaction or an intention to switch, and that coverage varies by service and company. Its guide says to keep the evidence date with each row and add a specific reason your offer could help before contacting anyone.

That is why the prompt asks for one line per company citing the Linkeddit evidence and marks companies whose only reason is that they use the competitor. Those go to the bottom of the list. The accounts with a dated review or a recent move go first.

The question comes up among founders. A B2B SaaS founder on Reddit asked: "How do you get someone to entertain switching when they’re not actively unhappy?" A competitor customer list cannot answer that. Dated public reviews that show a specific complaint are the closest evidence you can attach to an account before you write to it.

Linkeddit does not write the outreach, and neither does this guide. The point of the evidence is that you can say something specific and true. If a competitor shipped an AI assistant on 1 October 2026, that is a fact you can reference with its source link. If a customer review is from 2023, say nothing about it as if it were current.

Ask Claude to draft from the evidence only, with the link and date, and to leave a placeholder where the evidence is missing. Clay's connector description mentions drafting personalized outreach, so the drafts can happen in the same chat, but you read and send them yourself.

Review the list as a whole before anyone is contacted. Remove companies that are already your customers, companies in markets you do not serve, and any account where the evidence is older than you would be comfortable citing. Ask Claude to show the removed rows and the reason for each, so the final list can be defended.

Keep a record of why each account was chosen. Anvendor's advice to add a specific reason your offer could help before contacting anyone applies to every list this prompt produces.

The Agent Index lists Clay's find-and-enrich tools as consuming credits and includes a get-credits-available tool, so the balance check belongs first. Anvendor's guide recommends starting with one batch of ten accounts, keeping auto-update off during setup, and running one row first to check the person and company before the rest.

Add contacts last. Enriching people for a company you have not yet decided to pursue is the most expensive way to find out it was a poor fit. Linkeddit itself is a flat $60 a month and spends nothing in Clay, since Claude only reads its data.