Find prospects with the Dopia plugin

Install the free Dopia plugin in Claude, Cowork, Claude Code or Codex, then give it your website to find people who said in public they have your problem.

The Dopia plugin adds one skill, find-prospects, to the agent you already use. Give it your product's website and it comes back with a short list of people who have said, in public, that they have the problem your product solves. Every row carries what they said, when, a link to check it, and a way to reach them. The plugin is free and open source, and it works without a Dopia account.

It runs in the Claude app on the web and desktop, in Cowork, in Claude Code and in Codex. It is listed in Anthropic's directory for Claude, so in most cases you install it by searching for Dopia.

Before you begin

  • In the Claude app or Cowork: a Pro, Max, Team or Enterprise plan. Free plans cannot install plugins. On Team and Enterprise, an organization Owner adds the Dopia connector for the organization first; each member then connects their own account.
  • In Claude Code: sign in with your Claude account to install from the directory. With an API key, use the terminal commands under Install it instead.
  • In Codex: the Codex CLI. The Codex in the ChatGPT desktop app reads the same configuration, so it sees the plugin too.
  • A Dopia account is optional. Without one the list is written as a file. You can create an account later, from inside the connection step.
  • A browser the agent can use helps a lot. Many public pages — review sites, job boards — load only in a real browser. In the Claude app, turn on Claude in Chrome; Claude Code can use it too.

Install it

The Claude app and Cowork

Open Customize → Plugins → Discover, search for Dopia, and press Add. You can also open the Dopia plugin in the Claude directory directly.

Claude Code

Add the plugin in the Claude app as above. Claude Code, signed in with the same account, picks it up the next time it starts. This needs Claude Code 2.1.273 or later.

Signed in with an API key, or would rather use the terminal? Run /plugin marketplace add dopia-ai/plugins, then /plugin install dopia@dopia-plugins, and choose user scope so it is there in every project.

Codex

Run codex plugin marketplace add dopia-ai/plugins, then codex plugin add dopia@dopia-plugins. The @dopia-plugins part is required.

Connect Dopia (optional)

Connecting is what lets the plugin save the list as a page you can send, and keep the people it finds as records. Skip it and everything else works the same.

  • The Claude app and Cowork: open the plugin's Connectors tab and press Connect. Adding a plugin does not connect it for you — this is the step people miss.
  • Claude Code: run /mcp, pick Dopia, and approve.
  • Codex: run codex mcp login Dopia.

A Dopia page opens in your browser and lists four permissions: read your CRM, create and update records, read the pages in your library, and save a new page. Connect Dopia to Claude explains each one and how to take them back.

Run it

Point it at your own product:

  • Claude Code: /dopia:find-prospects yourcompany.com
  • The Claude app and Cowork: pick find-prospects from the / menu, or just ask — "Find people complaining about the problem yourcompany.com solves."
  • Codex: ask in plain words — "find prospects for yourcompany.com".

A run is research, not a lookup: expect it to take a while and to read a lot of pages. It asks you at most one question, and only when two readings of your product would send it looking in completely different places.

Before it starts collecting, it tells you which places it will look and which of them it cannot read — a site behind a login, or one that needs a browser it has not been given. That is your chance to turn a browser on, or accept a shorter list.

What you get back

A report named prospects-<date>.md, or printed in the conversation where the agent cannot write files. Every row in the list has:

FieldWhat it is
WhoThe person or business, with a profile or website.
How to reach themAn address, profile or contact form someone published — and the page it was read from.
EvidenceWhat they said or did, marked as their own words or as a dated event.
Date and linkWhen it was said, and a link that opens the page it was said on.
Why nowOne line on what makes this the moment to write.

Rows are ordered by how likely each one is to buy. Around the list the report adds:

  • How it read your product — who it thinks buys, and the test it derived for a good fit. If that reading is wrong, the list will be too; correct it and run again.
  • Two short sections you can overrule — people it judged to be in your own line of business, and strong signals that are older than it normally accepts.
  • The buyers' own words, grouped by the problem they describe.
  • What it searched, including the searches that found nothing, and the limits of the run.

Keep what it finds

If Dopia is connected, the plugin offers two things at the end of a run, once:

  • Records — each person as a company and contact in your workspace, with the quote, its date and its link on the record.
  • A page — the list published to your Dopia library, private until you switch sharing on. A shared page opens for anyone with the link, no account needed, and you can see who opened it.

Nothing is written to your workspace until you say yes. A page and records are separate: publishing the list does not create records.

What it will not do

  • Contact anyone. It does not write or send messages, connect, follow or comment. What you do with the list is up to you.
  • Get around a login. It reads public pages only, never asks for a password, and takes another route when a page is gated. On sites that carry people's identities, it reads only through the browser you give it, at the pace a person reads.
  • Guess. It never makes up an email address from a pattern, and a row without evidence does not ship.

Your data

  • The research runs inside your own Claude or Codex, under that plan and that company's terms. The pages it reads are fetched by your agent.
  • Dopia receives nothing from the plugin unless you connect it. Once connected, Dopia receives only the tool calls you agree to — the records or the page — and not your conversation.
  • The plugin's code is public at github.com/dopia-ai/plugins.

The full policy is at dopia.ai/privacy.

Remove it

  • The Claude app and Cowork: Customize → Plugins, open Dopia, and remove it. Claude Code drops a plugin it synced from there the next time it starts.
  • Claude Code, installed from the terminal: /plugin uninstall dopia@dopia-plugins.
  • Codex: codex plugin remove dopia@dopia-plugins.

Removing the plugin does not end the Dopia connection. To revoke it, go to Settings → MCP → Connected apps in Dopia and press Disconnect.

Troubleshooting

  • Claude Code does not show the plugin after adding it in the app. Claude Code syncs plugins when it starts, and only when you are signed in with the same Claude account. Restart it, or install from the terminal instead.
  • The plugin runs but never offers a page or records. Dopia is not connected in this app. Follow Connect Dopia, then ask it to publish the list it just made.
  • It says a lane needs a browser. Turn on Claude in Chrome, or another browser tool your agent supports, and run again.
  • The list is shorter than you hoped. Check how it read your product in the report's header. If the buyer it assumed is not your buyer, say who is and run again.
  • The approval page says the request is invalid. Remove the connector in the app, add it again, and approve from the page that opens.

Still stuck? Email contact@dopia.ai.

Up next

Contact support

How to reach the Dopia team when you're stuck, hit a bug, or have a question the handbook doesn't answer.

Did this answer your question?