AI sales prospecting uses AI to help identify relevant accounts, research the people and events around them, and prepare outreach. A useful workflow produces a reason to contact someone, the evidence behind that reason, and a message a person can review.
Start with a narrow customer profile. Collect current evidence. Separate what you know from what you suspect. Then decide whether the account deserves a conversation.
This guide walks through that process using a fictional example: a company selling software that helps B2B teams coordinate customer events. The examples illustrate a method; they are not customer results.
Define the decision before asking for a prospect list
“Find companies that might buy our software” leaves too much room for interpretation. A better brief describes the work you help with and the conditions that make that work relevant.
For the customer-event company, a starting profile could be:
| Question | Example answer |
|---|---|
| Who do we serve? | B2B companies with a recurring customer-event programme |
| What problem do we address? | Coordinating invitations, ownership and follow-up across events |
| What change makes the problem more pressing? | Expansion into additional cities or a growing event calendar |
| Who might own the workflow? | Customer marketing, community or event operations |
| What rules an account out? | No recurring programme, no relevant owner, or an existing conversation that should stay with another colleague |
Company size and industry can narrow the search. The operating problem makes the selection useful.
Prompt to adapt
Turn this offer into a prospecting brief. Identify the workflow we improve, likely account characteristics, evidence that would support a fit, and disqualifying conditions. Separate my supplied facts from your suggestions. List the questions we must answer before building a prospect list.
Review the brief before expanding the search. A precise starting point saves you from researching accounts that were never a good fit.
Collect evidence with a source and a date
For each candidate account, collect only the information needed to make the next decision. Useful sources might include the company's own announcements, current job openings, an event calendar and prior notes your team is authorized to use.
Keep two dates where possible: when the event happened and when you checked the source. A newly discovered announcement can still describe an old event.
Suppose the fictional account Northstar announces customer breakfasts in three cities. That supports a statement about an expanding programme. It does not establish that Northstar has a budget for new software or that its current process is failing.
Research prompt
Using only the supplied sources, prepare a short account brief. For every factual claim, record the source URL or authorized internal reference and its date. Mark missing information as unknown. Put interpretations in a separate section. Do not infer budget, purchase intent or the existence of a relationship from a job title or announcement.
If your AI tool cannot retrieve sources, provide the relevant documents yourself. Ask it to summarize that material rather than imply it has checked the current web.
Turn the event into a testable hypothesis
Research becomes useful when it helps you decide what to investigate next.
For Northstar, the chain could look like this:
- Observed fact: the company has announced events in three cities.
- Working hypothesis: coordinating invitations and follow-up may now involve more people.
- Unknown: whether coordination is difficult, who owns it and what process is already in place.
- Next step: identify the responsible team and check whether the expansion changes its workflow.
This distinction also improves the eventual message. “You must be struggling to manage your events” asserts a problem you have not established. “Does the expansion change how your team coordinates invitations?” invites the prospect to explain the situation.
For more ways to interpret events, see our guide to B2B buying signals.
Check the account's relationship history
A promising new account may already be an active conversation somewhere in your business.
Before choosing a contact, check the records your team is permitted to access. Look for an account owner, an open opportunity, a previous reply, a requested follow-up date or a reason the account was disqualified.
Record the source of relationship context as carefully as public research. “A colleague spoke with Maya” is useful only if the colleague, conversation and relevant detail can be confirmed. Never turn an inferred connection into an introduction.
Contact enrichment can help fill missing information. Treat enrichment as one step in the research process: verify that the person still holds the role and appears relevant to the workflow. A complete record is not the same thing as a qualified prospect.
Decide: research, contact or pause
A simple decision record is often more useful than a score with no explanation.
| Check | What to record |
|---|---|
| Fit | The operating problem your offer could address |
| Timing | The event or conversation that makes contact relevant now |
| Person | Why this person is likely to own or influence the workflow |
| Evidence | The sources supporting the first three fields |
| Relationship | Who on your team already knows the account |
| Next action | Research further, prepare a message, route to the owner or pause |
Leave a field marked unknown when the evidence is missing. If timing is weak but fit is strong, further research may be the right action. If a prospect has asked not to be contacted, pause the outreach.
This is a suggested decision template, not a claim that every field is automatically available in a particular product.
Draft a message around one useful question
Give the AI a clear purpose, a supported observation and a modest next step. Avoid filling the message with every fact the research collected.
Drafting prompt
Write an email of about 80 words to the person described in this brief. Use one verified observation, explain how our offer relates to the workflow, and ask one easy-to-answer question. Do not claim they have a problem, budget or purchase intent. Do not invent familiarity, an introduction or customer results. List the sources used below the draft for internal review.
Illustrative email
Subject: Customer breakfasts in three cities
Hi Maya,
I saw Northstar's announcement about customer breakfasts in three cities. Does that change how your team coordinates invitations and post-event follow-up?
We help B2B teams organize that workflow across events. If this sits with you, would a short outline of our approach be useful?
Jamie
The source notes belong in the internal review record. The message itself should sound like a person making a relevant, honest approach.
Review the work and learn from the reply
Before sending, check the contact, source dates, relationship history, factual claims and requested next step. Confirm the account and channel are appropriate for outreach and that any required review is complete.
Then record the outcome in terms that improve the next decision: wrong owner, no current need, timing later, relevant conversation or qualified meeting. A correction from a prospect is useful research input.
To evaluate this workflow, measure the share of researched accounts that produce a relevant conversation, the time spent preparing an approved message and the reasons accounts are rejected. Track these consistently within a defined cohort. Activity volume alone cannot tell you whether the research was useful.
Put the workflow into practice
Buena brings prospect discovery, account context and personalized email and LinkedIn outreach into one platform. Research and recorded relationship history inform a draft for review, followed by approved outreach through supported accounts.
Start with one customer segment and a small account batch. Use the brief above to make each decision explainable, then refine the process from the responses you receive.
When you need a later message, use the cold email follow-up examples to choose a useful reason to write again.