Sales prospect research is the process of checking a company, its relevant contacts and current evidence before deciding whether and how to approach it. For B2B SaaS teams, the output should be a short, sourced account brief.
A useful prospect research brief should help the next person decide whether to contact an account and what can honestly be said. It should not make them repeat the research or read a long collection of unrelated facts.
For SaaS sales and RevOps teams, that means recording account fit, role relevance, source evidence, uncertainty and the next decision.
Use the checklist below as a working record. It is an editorial template you can adapt to your process, not a description of a particular CRM integration or automated scoring model.
1. Confirm the account
Start with the company’s domain and what it actually sells.
Check whether its product, customers and operating market match the account you intended to research. Similar names, subsidiaries and acquired brands can create confusion.
Record a reason for account fit that another reviewer can evaluate. “SaaS company” is usually too broad to explain why a particular offer is relevant. “Sells a usage-based product to finance teams and is introducing a separate enterprise motion” gives a reviewer something concrete to check.
If you cannot establish that you have the right business, stop. Additional research on the wrong company does not improve the brief.
2. Check the person’s current role
Record the person’s current company, role and the source supporting that information. A previous job title is not current authority.
Then distinguish role fit from buying authority. A RevOps manager may understand a workflow without owning the budget. A VP of Sales may sponsor a project without being the person who maintains the relevant data.
Use a field for “likely involvement” and another for “confirmed involvement.” Do not quietly treat the former as the latter.
3. Find evidence related to the offer
Look for facts that help explain why the product could matter to this account. Possible starting points include company announcements, product documentation, leadership statements and relevant job descriptions.
Check the source in context. If an announcement describes international expansion, it supports that expansion. It does not automatically support a claim about staff shortages, missed targets or software dissatisfaction.
The buying-signal guide explains how to separate an observed event from an interpretation.
4. Preserve the date and the source
Each material observation needs a URL and a date checked. If the event has a known date, record it separately from the page’s publication date.
If the page has no clear date, record “unknown.” Do not substitute today’s date for the date of an event.
Keep a short paraphrase of what the source supports. The purpose is to make the claim inspectable without copying entire articles into the CRM.
5. Write the relevance in one sentence
Use this structure:
The source says [observation]. This may be relevant to [specific workflow] because [connection to the offer]. We still need to establish [unknown].
A fictional example:
The company says it is combining regional account ownership. This may be relevant to assignment reconciliation because our product compares ownership records across systems. We do not know which reconciliation process it currently uses.
If the connection requires several unsupported steps, keep researching or reject the candidate. More confident language will not close the evidence gap.
For a worked decision process, use the signal-based selling worksheet. It shows how to turn a company event into a contact, research-further or reject decision without treating the event as proof of buying intent.
6. Decide what not to say
Add a short boundary to the brief. This prevents a writer or automated workflow from turning tentative context into a factual claim.
For the example above:
Safe: the company has announced a change to account ownership.
Safe as a question: whether reconciliation work is already covered.
Unsupported: the company has duplicate records or is losing revenue.
Unsupported: the prospect is looking for a new platform.
This field is especially useful when research and message creation happen in different tools or are owned by different people.
If the gap is in your software rather than the brief, use the B2B prospecting tools selection guide to compare research evidence, outreach controls and workflow fit. Its evaluation worksheet separates documented capabilities from results you still need to test.
7. Make the handoff actionable
A copyable account brief:
Account
What to record: Company name, domain and business description
Fit
What to record: Relevant use case and exclusions checked
Contact
What to record: Current role and supporting source
Observation
What to record: One material fact from the source
Source
What to record: URL, publication/event date where known, date checked
Relevance
What to record: Direct connection to the workflow your offer addresses
Unknowns
What to record: Missing information that affects the decision
Message boundaries
What to record: Claims the evidence does not support
Decision
What to record: Contact, research further or reject
Ownership
What to record: Reviewer and next action
Review trigger
What to record: A date or event that should cause the brief to be checked again
Worked example: a research decision
This is a fictional training record, not a real prospect or a Rhycon customer result. It shows how to keep a missing fact visible.
Account: An illustrative SaaS company combining regional sales teams.
Offer: Software that reconciles account ownership across systems.
Observation: A sample company announcement describes a move to one account-ownership model.
Source and date: A real record must include the original URL, event date where known and date checked. This example does not supply a real source.
Relevance: Combining ownership models may require comparing account assignments.
Unknown: Whether reconciliation is already covered, and who owns that work.
Decision: Research further. Verify the announcement and the responsible role before outreach.
Message boundary: Do not claim the company has broken CRM records, budget or an active buying project.
Keep suppression and contact restrictions in the systems that enforce them. A good research note should not override an existing decision not to contact someone.
8. Use a stopping rule
Research is complete when there is enough verified information to make the next decision. It does not need to become a full company history.
Stop when the account is clearly unsuitable. Stop when the available evidence is too weak to support the proposed angle. If outreach is justified, stop collecting unrelated facts once the brief supports a clear, honest message.
Teams can set a research time budget, but should adjust it to the account’s value and complexity. There is no universal number of minutes that makes a brief good.
Review the record at the next stage
Before writing, check that the source still supports the planned opening. Before passing a conversation to an account executive, add what the prospect actually said; do not let the original research hypothesis stand in for qualification.
The qualification guide separates those stages. The email examples show how the brief can become a message.
See how Rhycon works through the interactive homepage walkthrough.
Download the free B2B prospect research scorecard (Excel workbook in a ZIP file).