Become an SDR/BDR · Beginner · ~7 hours

Sales Development & Prospecting

Practise the day-to-day craft of researching accounts, creating outreach and building qualified pipeline.

Status: Catalogue ready. This lesson version is available in review mode while subject-matter, accessibility and assessment checks are completed.

Evidence-led prospecting

Account research and relevance

40 min

course progress0 of 3 lessons complete

By the end of this lesson

Build a short account brief from approved, business-relevant information.
Distinguish an observation from an assumption when preparing outreach.
Connect a potential business issue to a respectful reason for contact.

Research for a conversation, not a performance

Prospecting starts before the first message. The purpose of account research is not to collect every detail about a company or to prove that a salesperson has searched the internet. It is to decide whether a conversation could be relevant and to prepare a useful opening. A good researcher can explain why this organisation may have a situation worth exploring, what is still unknown and which person might have a sensible perspective. If that reasoning cannot be made clearly, more research will not necessarily improve the outreach. Use a small, repeatable brief. Record the organisation's market, the team or workflow that may be affected, a recent business signal from an approved public source and one hypothesis about a problem. A signal might be a new regional launch, a change in leadership, a growing support operation or a published investment in a process. It is not proof that the company needs a particular product. Write it as an observation: “The company announced expansion into two regions.” Then write a hypothesis separately: “The operations team may be reviewing how it coordinates reporting across regions.” This separation protects the prospect from overconfident personalisation. It also makes the next question better. The opening can acknowledge the signal and ask whether the related challenge is relevant, instead of pretending to know the company's internal priorities. Do not use personal information that is irrelevant, sensitive or obtained in a way that would make the recipient uncomfortable. Professional relevance is about the work, not surveillance.

Choose a narrow reason to reach out

A prospecting message becomes easier to read when it has one reason for existing. Begin with a business context the recipient may recognise, connect it to a possible consequence and offer a low-pressure way to test relevance. For example: “Teams expanding across regions sometimes find that weekly reporting becomes harder to reconcile. Is that something your operations group is reviewing, or is it not a priority this quarter?” The message does not claim that the sender knows the answer. It gives the recipient a simple way to correct the hypothesis. Avoid a long catalogue of product features, vague praise and generic claims about transformation. These increase the reader's work because they must figure out why the message arrived. The same applies to excessive personalisation. Mentioning a specific business signal can be useful; repeating details from a profile simply to look observant is not. A message should be recognisable as relevant even if the recipient skims it on a busy day. Account research also includes a stop decision. If the organisation is outside the intended market, the use case is clearly unsuitable or the available information is too weak to support an honest hypothesis, pause rather than force a message. A smaller list of well-reasoned accounts creates better learning than a large list built on copied attributes.

Keep research usable for the team

Research has value when another team member can understand it quickly. Use a consistent record with fields for source, date, observation, hypothesis, possible stakeholder and open question. Link to the approved source where company policy permits, and avoid pasting unnecessary personal data into the CRM. If a source is old or ambiguous, label it as such. A record that shows its uncertainty is more trustworthy than one that sounds certain but cannot be checked. The brief should also support learning. After outreach, record which hypothesis was useful, which was wrong and what language the recipient used. This is not a reason to blame the prospect or to optimise for replies at any cost. It helps the team refine its understanding of the market and notice when a message is repeatedly irrelevant. If a person asks not to be contacted, respect that request and follow the organisation's suppression process. For a learner, the key habit is to stop writing after the brief answers three questions: why this account, why this role and why now enough to ask. “Why now” does not require manufactured urgency. It can simply mean that a current signal makes a short exploratory question reasonable.

Workplace example

Harbourlight Systems has announced that it is opening a second service centre. A learner notices this public signal and hypothesises that the support operations team may be reviewing how requests are routed. Their brief cites the announcement, labels the hypothesis as unconfirmed and proposes a message asking whether routing consistency is a current priority. It does not claim that Harbourlight has a problem or that the learner knows the support team's internal plans.

Try this walkthrough

1.Select one fictional account and write its market, relevant team and one public business signal.
2.Write an observation and a separate hypothesis, using labels that make the difference obvious.
3.Draft a three-sentence message with one reason for contact and a low-pressure question.
4.Review the draft for irrelevant personal detail, unsupported claims and an easy opt-out or correction path.

Watch for these traps

Treating a public announcement as proof of an internal priority.
Adding personal details that do not improve the business relevance of the message.
Researching indefinitely instead of choosing a testable hypothesis.
Using a generic product description before explaining why the conversation may matter.

Practice studio

Make a decision. Test a response. Leave evidence.

Use the case from this lesson to practise judgement without creating a score or changing your course record.

Scenario decision

Harbourlight Systems has announced that it is opening a second service centre. A learner notices this public signal and hypothesises that the support operations team may be revi…

Choose a response

Branching roleplay

A colleague asks you to move this situation forward. What do you say next?

Evidence workspace

Draft a short known / assumed / next note from the fictional case. Use fictional details only.

KnownAssumedNext step

This is a session-only practice draft. It is not saved, graded or added to your learning record. Never enter real personal or confidential information.

Practical assignment

Create a one-page account brief for fictional Harbourlight Systems. Include two approved observations, one clearly labelled hypothesis, a possible stakeholder, an open question and a respectful three-sentence outreach message. Annotate any detail you chose not to include and explain why it was not relevant.

Pass this lesson's knowledge check before recording it as complete.

Portfolio evidence

Practical portfolio project

Create a fictional target-account list, research three contacts, build an outreach sequence and complete a handover note.

Turn the practical project into a bounded evidence record. Save a draft while you work, then submit it for human review when it is ready.