Use this as a working guide, not a passive read. Skim the sections, copy the frameworks, then connect the advice to a real role, interview, call, or account you are working on this week.
Account research should help you decide whether to contact someone and what useful question to ask. A long list of company facts does neither by itself. The practical output is a brief that separates public evidence from your interpretation, names a relevant business role, and gives you a reason to stop if the fit is weak.
This guide is for SDRs working a defined account list. It is narrower than an enterprise account plan: the goal here is to prepare the first outreach, not map an entire buying process. All sample companies and messages below are fictional.
Start with fit, before personalization
Confirm the account is in your assigned territory and plausibly matches your team's customer criteria. Check basic requirements such as business model, geography, use case, or an essential technical dependency where public information is available. If an account fails a necessary requirement, document why and move on.
Do not assume every growing company needs your product. Hiring, funding, or a new office can be a reason to investigate, but none proves that a buyer has a problem, a budget, or a desire to speak with you.
Use a six-field brief
Download the account research template. Complete one row per account with a source and a date so another rep can distinguish current evidence from stale notes.
- 1Fit: The specific customer criterion this account appears to meet.
- 2Fact: A directly observed statement from a relevant public source.
- 3Source and date: Where the statement appeared and when you checked it.
- 4Hypothesis: A possible operational implication, explicitly marked as unconfirmed.
- 5Buyer role: The function likely to understand that workflow, subject to confirmation.
- 6Question: A short way to test relevance without presenting your hypothesis as fact.
Prefer the company's own pages, public documentation, and current job postings for basic business context. Verify that a job posting is still active before using it as a current signal. Never include sensitive personal facts merely because you found them online.
Work through a fictional example
Imagine Northstar Scheduling, a fictional software company, publishes a role for a revenue operations manager supporting two regions. The observed fact is the job description's stated scope. Your hypothesis might be that cross-region reporting involves coordination. You do not know whether the process is difficult or whether their current tools are inadequate.
A useful first question could be: “How does your team keep reporting definitions consistent across the two regions?” A weak message would claim, “Your reporting is broken as you scale.” The weak version treats your guess as inside knowledge.
An original email opening might read: “I saw the revenue operations role mentions supporting both regions. We work on reporting handoffs, and I was curious how your team keeps the definitions aligned today. Is that part of your remit?” Use this only if every statement about your own offering and the account is true. Add the identification and unsubscribe details required by your organization and applicable rules.
Set a stop rule for research
Choose a time budget with your manager based on account value and your team's workflow. A short exercise can begin with ten minutes, but that is a practice constraint, not an industry benchmark. Stop when you have enough evidence to ask a relevant question or enough evidence to disqualify the account.
When the timebox ends with no useful signal, do not invent one. Use a truthful role-based message if your team supports that approach, move the account to later research, or ask for help. The brief should make this choice visible.
Coordinate before contacting several people
Salesforce's account-based selling lesson describes a coordinated approach to selected accounts involving multiple stakeholders. For an SDR, a practical application is checking account ownership and existing conversations before adding outreach. Personalizing several messages does not justify sending conflicting messages from different reps.
Review the brief after a response. Replace your hypothesis with confirmed information, record a stop request promptly, and update the next action. Track useful conversations and disqualifications, not just how many fields you filled in.
Turn the brief into a repeatable workflow
Try the template on three eligible accounts and ask a teammate to identify which statements are facts and which are assumptions. If they cannot tell, rewrite the notes. Then compare the message with the brief: every personalization claim should have a source or be phrased as a question.
For a broader sequence covering targeting, message design, and follow-up, see the account-based prospecting playbook path. Start with the free worksheet and preview; a paid PDF is useful when you want more structure, not when the real obstacle is an unclear target market.
