Agents + outreach · How the chain works

Your website is somebody else’s prospecting input.

30 September 2026 · didntask.ai field notes

“I noticed your Westbourne project” sounds like somebody took a look. But a system can retrieve that project name, put it in a table and drop it into a pitch without the sender ever opening the page.

The tools already connect

Exa’s MCP integration connects search and webpage retrieval to tools including Claude Code and Codex. Its documented uses include company research and fetching page content. Firecrawl documents search, scraping and structured extraction, alongside integrations for coding agents. These are general research capabilities, not evidence that a particular user or vendor sends spam. Exa MCP; Firecrawl documentation; Firecrawl’s Claude Code integration.

How research can become a mailing list

The following is our illustration of what those capabilities can enable. It is not a measured campaign or a claim that every tool performs every step.

1. Find businesses.A search tool returns candidate company pages.
2. Read and extract.A retrieval tool turns public pages into text or structured fields.
3. Organize a prospect list.An agent can turn available public business/contact information into rows for an operator to review.
4. Draft the “personal” part.A model uses a project name, location or service description in the opening line.
5. Hand it to an outreach workflow.Sending requires separate mail tooling and authorization. Access to search is not permission to contact someone.

Firecrawl’s structured-extraction documentation shows how page content can become defined fields. Our inference is that the same general capability can feed prospecting workflows. We are not providing a recipient list or running one.

The problem is who still has to do the thinking

Useful research can help somebody make a thoughtful offer. It can also supply just enough detail for a mass-generated message to look considerate. The output alone doesn’t tell you which happened.

The recipient still has to check the offer, interpret the claim, work out whether the sender means it and decide whether a reply is worth the time. Automation can reduce the sender’s effort while leaving that work with the reader. That is the imbalance we object to.

The same issue can appear outside sales: an operator delegates a complaint, asks for a stronger tone, and forwards a long response without checking it. The grievance may be real. The recipient shouldn’t have to dig through generated padding to find it.

What you can do about it

Reduce unnecessary public contact information. Request removal from databases that distribute your details. Set crawler preferences with realistic expectations. Use separate public addresses and mailbox controls. These steps address different parts of the chain.