Researching prospects used to mean twenty browser tabs and a note you half-trusted. An AI agent can do the reading instead, as long as it hands back a brief you can check. This guide shows the workflow: one account, one research call inside your editor, a short brief, and a source and date on every fact. The result is a message that is accurate and specific.
What does it mean to research prospects with an AI agent?
Researching prospects with an AI agent means a research tool reads an account's public sources for you and returns a short, structured brief instead of a page of blue links. The agent runs where you already work, an editor or a chat, and the brief is the output you act on. The standard it has to meet is the same one a careful rep meets by hand: every fact carries a source and a date, and a field the sources do not support stays empty.
The phrase is shared with fundraising, which is worth knowing before you search for tools. In nonprofit work, prospect research means estimating a donor's capacity and inclination to give, and much of what ranks for the bare term is written for development teams. Everything below is the sales version: a company, a buyer, and a dated reason to start a conversation.
Why run prospect research inside Claude Code or Cursor?
Running research inside Claude Code or Cursor keeps the work in one place. The brief lands in the same window where you write the message, so there is no CSV export and no second tab to reconcile. Teams that adopted an AI editor for other work often find there is no native way to pull account data into it. That gap is the reason to add a research tool the agent can call directly.
The point is not novelty. It is that the research and the writing stop being two separate jobs. When a rep researches in one app and writes in another, facts get retyped and dates get dropped. When the agent returns the brief in the chat, the fact and its source sit next to the sentence you are about to send.
What is the workflow, step by step?
The workflow is five steps and runs in one session: name the account, call the research tool, read the brief, open the sources that matter, and keep only the facts you can back. The agent does the fetching and the structuring; you do the judging. That split is the whole method, and it is what separates a usable brief from a confident guess.
In practice it looks like this. You give the agent a domain, a work email, or a person and company name. The agent calls the prospect research API, or the same capability through the MCP server. A brief comes back in 20 to 90 seconds.
You read it and open the one or two sources the message will lean on. Drop anything you cannot confirm. The facts that survive are the ones that go in the email.
This is the same shape as the manual method, the hand-researched version of the same brief; the agent compresses the reading, not the judgment.
Which facts should the agent return?
A useful brief returns a small, fixed set of fields. It names what the company sells and to whom, its size and stage, and what changed recently. It names who owns the problem you solve, the one dated trigger that connects a change to that problem, and the source and date behind each one. Nine facts cover almost every account, and you rarely need all nine before you have a reason to write.
The field that matters most is the trigger. It is a recent, dated change, such as a funding round pulled from a feed like the funding rounds API, a new executive, or a hiring burst, tied to the problem you solve. It answers why now, the question a cold message most often fails to answer, and the one an AI call screener asks first, which is why funding signals beat dial volume. Sources that estimate a priority are leads to verify, as HubSpot's guide to prospect research and LinkedIn's advice on researching prospects both argue: check the buyer's own words first.
Why does every fact need a source link and a date?
Every fact needs a source link and a date, because a claim without one is impossible to check. An unchecked claim is how a congratulations lands on a role the person left last year. The source makes the claim auditable, and the date tells you whether it is still true. Together they let you send a short message and defend every line of it.
One operator building a research agent put the rule plainly: a tool's summary is a lead, and evidence only starts when the source page is read in full.
The practice generalizes past agents. The Model Context Protocol, the open standard that lets an agent call a tool like a research server, is documented at modelcontextprotocol.io. It defines how the call happens, not what you trust.
The discipline of reading the returned source is on you. A brief that returns a confidence score and leaves unsupported fields null gives you somewhere to apply it.
How do you check a brief before it reaches an email?
Checking a brief is five fast questions: is there a link, is the source primary, is it dated, does the date fall inside the window the message claims, and does the person still hold the title. A brief that passes those is safe to quote; one that fails any of them gets the failing fact cut, not softened. The agent made the facts cheap to gather, which is exactly why they are worth a second to verify.
Run the check by hand on your first ten briefs before you trust the format at scale. You are not re-doing the research; you are confirming that the agent's citations say what the brief says they say. Once the format holds up across ten accounts, you can read later briefs faster and open only the sources the message will rest on.
Manual research versus an agent: what actually changes?
What changes with an agent is speed and consistency, not the standard. A rep with browser tabs and an agent with a research tool both have to produce sourced, dated facts; the agent just reads faster and returns the same shape every time, which makes briefs comparable across a list. What does not change is the judgment, the fit call, and the decision to leave a field empty.
Sellers are already asking where this line falls. In one r/SaaS thread, an operator lists researching prospects among the tasks they do by hand. They ask which parts of sales can genuinely be automated, beyond the demos:
The honest answer is that sourcing and structuring automate well, while the fit call and the final wording still want a person. For the manual side of the same work, how to decide who even belongs on the list before any research starts, this walkthrough covers the ground:
How much does agent-run prospect research cost, and does it scale?
Agent-run research scales on three numbers: the time per brief, the number of calls, and the share of facts that ship without a source. A brief takes 20 to 90 seconds, you make one call per account, and the only facts that reach a message are the ones with a link and a date behind them. That last number should be zero without a source, whatever the volume.
Cost follows the same logic. You pay per completed brief, listed on per-record pricing, so the spend tracks the accounts you actually research rather than a seat you may not fill. Agents can run the same research through the MCP server, which exposes the submit and get steps as tools, so the work happens inside the conversation where the message is written. Research more than a handful of accounts a day, or let an agent draft your first touches, and that is where moving the reading off a person starts to pay.
Frequently asked questions
These are the questions teams ask most often when they move prospect research into an agent. They are answered in the order they come up: what it is, whether to trust it, how to run it, how long it takes, and which interface to use.
What does it mean to research prospects with an AI agent?
It means a research tool reads an account's public sources for you and returns a short, structured brief instead of a page of links. The requirement does not change: every fact still needs a source and a date, and a field the sources do not support comes back empty.
Does an AI agent invent facts about a prospect?
It can, which is why the only safe format returns a source link and a date beside every field and leaves unsupported fields empty. Check the citations on your first ten briefs by hand before you trust the format at volume.
How do you run prospect research inside Claude Code or Cursor?
Connect a research tool that speaks the Model Context Protocol, then ask the agent to research an account by domain or by name. The tool returns the brief in the chat, so the research sits next to the message you are writing, with no export step.
How long does an agent take to research one prospect?
An API brief takes 20 to 90 seconds per account. That is our documented range, not a measured average across every account. A manual pass on a named account runs closer to twenty minutes once you open and read each source yourself.
Is an API or an MCP server better for prospect research?
Use the API when another system consumes the brief, such as a CRM or a sequencer. Use the MCP server when a person or an agent does the research in an editor. Both return the same brief with the same sources, so the choice is about where the work happens.