Prospecting · July 2026

Prospecting with Claude, without the research black hole

Reps lose whole mornings to research and still send something that could have gone to anyone. Founders do the same work in the gaps between hiring, support and shipping. The bottleneck is not writing. It is deciding who is worth writing to today.

Prospecting has five jobs inside it, and they fail for different reasons. Building a list fails on vague criteria. Research fails on repeating the homepage back to yourself. Triggers fail because everyone gets the same funding alert on the same morning. Scoring fails because everything ends up a four out of five. Prioritising fails because a list of forty accounts is not a plan for a Tuesday.

Claude is genuinely good at four of those. It is not good at inventing information you did not give it, which is the constraint the whole page works around. What follows is the order that works, with the prompts, and a note on which line in each prompt is carrying the weight.


Start by writing the ICP down

Most teams have an ICP that lives in someone's head and comes out differently every time. That is survivable in a sales meeting and fatal when you hand it to a model, because “good fit” then means whatever the model assumes it means. Ten minutes spent turning it into a checkable rubric improves every prompt after it.

ICP

Turn a rough ICP into criteria a model can apply

Here is how we describe our best customers today:
{paste your rough notes, or three customer names}

Here is what those accounts had in common at the time
they bought: {paste}

Rewrite this as a scoring rubric with 6 to 8 criteria.
Each criterion must be checkable from public
information or from a CRM field. No criteria like
"innovative" or "growth-minded".

Then list our three strongest disqualifiers, and for
each one tell me the evidence that would prove it.

The line that does the work is “checkable from public information or from a CRM field”. Without it you get an ICP full of attitudes, and every account scores well because nobody can prove otherwise.


Research an account in three minutes, not thirty

The mistake is asking for research and accepting a summary. A summary of a company website tells you what their marketing team decided to say. What you need is the delta: what changed recently, who owns the problem now, and whether there is a reason to move this week.

Cap the output length. A 250 word brief gets read before a call. A 900 word brief gets skimmed for the first line and closed. Salesgear's guide to running Claude across a sales workflow makes the same point about prep: the constraint is what a rep will actually read between meetings.

Research

The three minute account brief

Account: {name}. I sell {product} to {buyer title}.
Here is what I have: their careers page, their last
two press mentions, and the CRM record.
{paste}

Give me, in under 250 words:
1. What changed at this company in the last 90 days
2. Who is likely to own the problem I solve, by title
3. One thing that is true here and not true at a
   typical company this size
4. The single fact that justifies contacting them
   this week rather than next quarter

Cite which source each point came from. If a point
is inference, write [inference] in front of it.

Point 4 and the [inference] tag are the two lines that matter. Point 4 kills accounts that are not ready, and the tag stops a plausible guess turning into a first line you cannot defend on a call.


Triggers: what they actually tell you

A trigger is only useful if it changes what your buyer is measured on. Most of what alerting tools surface does not. Here is how the common ones tend to hold up.

SignalWhat it usually meansWorth acting on
Job postingA problem got big enough that someone approved headcount for itOften, and few competitors read past the skills list
Funding roundMoney exists, priorities may not be set for another quarterRarely on its own, and everyone contacts them the same week
New exec in a relevant functionSomeone is expected to change something within two quartersYes, roughly 30 to 90 days in rather than week one
Product launchA new motion needs supporting, often with the old toolingYes, if what you sell supports the motion they just launched
Award or listicle mentionTheir PR agency did its jobNo
Triggers

Read a job post for a real trigger

Here is a job description {company} posted this week:
{paste the full posting}

Ignore the skills list. Tell me:
- What broke or got too big that made this role
  necessary
- Which team the role reports into, and what that
  says about who owns budget
- What tools the posting implies they already run
- Whether this is a replacement hire or a new
  function, and how you can tell

Then write one sentence I could open with that a
competitor reading the same posting would not write.

“Ignore the skills list” is the whole prompt. The skills list is the part every tool summarises. The reporting line and the tools named in passing are where the actual buying context sits.

Triggers

Separate a real trigger from noise

Here are 12 events my alerts flagged this week
across my accounts:
{paste: funding, launches, exec hires, layoffs,
office moves, award wins}

For each one, answer two questions:
a) Does this change what {buyer title} is measured on
   in the next two quarters? Yes or no.
b) If yes, what would they now be trying to fix?

Sort into: act this week, watch, ignore. Be willing
to put most of them in ignore.

The permission in the last sentence is deliberate. Ask a model to rank twelve events and it will find merit in all twelve. Telling it that a mostly-ignore answer is acceptable is what gets you an honest three.


Scoring, then the only question that matters

Scoring a list is where models are most eager to please and least useful by default. Left alone they will rate almost everything mid-to-good, because nothing in the request penalises a flat answer. Two instructions fix it: make unknowns explicit, and ask to see the spread of scores before the list.

Qualify

Score and rank a list against the rubric

Scoring rubric: {paste the rubric from earlier}
Disqualifiers: {paste}

Here are 40 accounts with firmographics and any
history we have:
{paste}

Score each out of 10 against the rubric, with one
line of reasoning quoting the field that drove the
score. Show the distribution before the list.

Rules:
- Anything hitting a disqualifier scores zero and is
  listed separately
- If a criterion cannot be checked from what I gave
  you, mark it unknown rather than assuming
- Do not smooth the scores to spread them evenly

“Show the distribution before the list” is the check. If 34 of 40 accounts land between 6 and 8, your rubric is not separating anything and the ranking underneath it is decoration.

A ranked list is still not a plan. The last step is the one people skip: turn the ranking into a short list of accounts you will touch today, and a defensible reason to park the rest until something changes.

Priority

Decide who to work today

Here are my 15 highest scoring accounts, with the
last touch date, who we spoke to, and any trigger
from this week:
{paste}

Split them into three groups:
- Work today: something changed, and I have a reason
  to contact a named person
- Work this month: fit is there, no reason yet, tell
  me what I should watch for
- Park: say plainly why, and what would bring it back

For the work today group only, give me the person to
contact and the one fact the message should hang on.
Keep that group to five or fewer.

Capping the group at five is what makes the output usable. An unlimited priority list is just the same list in a different order, and you will still start at the top and run out of morning.


The honest limit

Claude cannot see anything you did not give it. That single fact sets the ceiling on every prompt above. If you paste a careers page and two press mentions, you get a brief built on a careers page and two press mentions. No amount of rewording produces the deal history, the last three email threads, or the fact that this account churned two years ago under a different owner.

You will feel the ceiling in a specific way: the research is fine, but you are spending longer assembling the paste than reading the output, and two people researching the same account get different answers because they pasted different things. At that point the fix is access, not prompting. Salesgear has a practical write-up on giving AI tools live access to sales data that covers what to connect first and what to keep out.

A useful rule while you are still pasting by hand: anything the model states as fact should be traceable to something in your prompt. If you cannot point at the line it came from, do not put it in an email. It will be the sentence the prospect replies to.


What this actually saves you

Not the writing. The writing was never the expensive part. What this saves is the deciding: which twelve of your forty accounts have anything happening, which five deserve a message before lunch, and which twenty you can stop feeling guilty about until something moves.

A rep who does this properly starts the day with five names and a reason for each, instead of a list and a vague intention. A founder gets their prospecting into the 25 minutes they actually have. If you want the rest of the prompts in one place, the outreach prompt collection is a reasonable starting set to fork.

Once you know who and why, the next problem is what you say to them. That is a different set of prompts and a different failure mode.