Strategic prospecting is a plan for choosing suitable accounts, finding a relevant reason to contact them and reviewing what happens next. Define who the offer can help and what evidence supports that view. A well-researched account is still a prospect, not a confirmed buying opportunity.
Define which accounts are worth investigating
Describe the customer problem your offer addresses and the conditions under which it is useful. Consider requirements such as location, company size or existing systems only where they affect suitability. Include reasons an account would be a poor fit.
Use experience with current customers as evidence, but check what made those relationships work. A familiar industry or similar headcount does not establish the same need. Record assumptions you need to test in a conversation.
Make the selection criteria usable by another colleague. They should be able to explain why an account was included without relying on a vague label such as “high potential”.
Find the people connected to the problem
Identify roles that may use, assess or approve the offer. Treat a job title as a starting point for research rather than proof of decision authority. Ask for guidance when responsibilities are unclear.
Check whether someone on your team already has a relationship with the account. Coordinate outreach so several sellers do not independently approach the same person with conflicting messages.
Research enough to explain relevance
Review current company information and note the source and date of material facts. Look for a connection between the account’s work and the problem you address. Personalisation should make that connection clear, rather than show how much information you found about an individual.
A funding announcement, expansion or leadership change may raise a useful question. It does not establish budget, need or readiness to buy. Avoid writing as though a public event proves an internal problem.
If a data provider supplies an activity or intent signal, check what the signal actually represents. Use it as a reason to investigate, not as a confirmed account requirement. Verify contact details before relying on them.
Write an opening the recipient can assess
Explain who you are, why you are contacting this person and what you are asking. Keep the claim about your offer specific and supportable. Give the recipient enough context to decide whether a conversation is relevant.
For a fictional example, a seller offering reporting support might write: “We help teams document how figures move into their weekly sales report. Is that process something you are reviewing, or does it sit with someone else?” This asks about a possible need without claiming that the recipient has a reporting problem.
Use the rapport-building guide for preparation and conversation habits once contact is established. A familiar tone should not imply a relationship that does not exist.
Choose channels and follow-up deliberately
Select a channel that fits the context and the recipient’s preferences where known. Do not assume every account needs a sequence across email, phone and social media. Decide what a follow-up would add before scheduling it.
Keep a record of replies and agreed next steps. Stop scheduled messages when a response needs a person’s attention. Respect requests to stop and avoid contacting someone through another channel simply to get around their refusal.
For introductions, ask whether the existing contact is comfortable making one and provide accurate context they can share. A referral creates an introduction; it does not establish that the recipient wants to buy.
Define the handover into an opportunity
Agree what the team needs to learn before recording an active opportunity. That might include a confirmed problem, a relevant use case and a reason for further discussion. Keep unanswered questions visible.
Pass on the original reason for contact, what the person actually said and any commitment made. Assign the next action to someone. The pipeline-management guide explains how to keep that evidence useful during later reviews.
Review replies and outcomes together
Track attempts, replies and meetings with clear definitions. Separate a relevant response from an automated reply or a request to stop. A booked meeting also needs checking for suitability; volume alone does not show that the targeting worked.
Review a sample of unsuccessful attempts as well as successful ones. Check account fit, the reason for contact and the clarity of the request. Compare similar groups and record changes to the audience or message before drawing conclusions.
Fix the process before adding tools
Identify the specific gap a tool should address, such as duplicate records or missed replies. Check who owns the information and how updates reach the people using it. Test stop rules and handovers before expanding automation.
Choose one improvement from the review and check its effect. Better account criteria or a clearer question may be more useful than a larger contact list. Keep the plan open to what prospects tell you, including evidence that the offer is unsuitable.
