Beta

Sales call research brief for Sales Reps

The sales call research brief adapted for sales reps. Body, role-specific tweaks, common pitfalls, and how to run it with Strawberry.

This is the sales call research brief adapted for sales reps. It exists because spending too much time on admin, and the brief below is the shape that actually survives contact with how sales reps work day to day.

What this brief is for

Purpose: give a sales rep a one-page brief on the prospect, the company, and the deal before a discovery call. For sales reps specifically, the value is that it turns a recurring admin task into a 5-minute repeatable artifact. This isn't a generic template - the items below are tuned for sales reps and the tools they actually live in.

The sales call research brief (brief)

  • Company snapshot - what they do, size, recent funding or PR moves
  • The buyer - role, tenure, public posts, mutual connections
  • Deal context - prior touches, CRM stage, open opps, last activity
  • Three angle hypotheses - why now, why us, why this workflow
  • Five questions to ask in the first ten minutes

Adjustments for sales reps

sales reps typically live in a CRM (HubSpot, Salesforce, Pipedrive), Apollo or ZoomInfo, LinkedIn, Gmail or Outlook. That changes how this brief runs:

  • Pull the inputs from the apps sales reps actually use, not generic SaaS exports.
  • Anchor on recent activity in the prospect or company - it's the highest-signal field for this role.
  • Skip items that don't apply to your weekly cadence; this is a starting shape, not a contract.

The most common way to mess this up

Treating the brief as a script - it is a research artifact, not a sales monologue. For sales reps, this shows up as spending the saved time on more admin instead of higher-leverage work. Build the brief into your week, not as a one-off.

How Strawberry runs this brief

Strawberry generates the brief by reading LinkedIn, the company website, recent news, your CRM, and prior email threads in parallel - then drafting in your team's brief format. For sales reps, Strawberry uses your live tabs and connected apps - so the brief is filled with your real context, not a placeholder.

When to use this, when to skip

Use this brief when the work recurs (weekly, per-prospect, per-meeting). Skip it when the situation is novel and judgment-heavy - the brief is a baseline, not a substitute for thinking.

Caveats

Strawberry holds back on sending email, updating CRM records, or changing shared systems until a human approves the action. Treat the agent as a fast first-draft author, not an autopilot.

Sales call research brief

1 company snapshot

Step 1

company snapshot - what they do, size, recent funding or PR moves

2 the buyer

Step 2

the buyer - role, tenure, public posts, mutual connections

3 deal context

Step 3

deal context - prior touches, CRM stage, open opps, last activity

4 three angle hypotheses

Step 4

three angle hypotheses - why now, why us, why this workflow

5 five questions to ask in the first ten minutes

Step 5

five questions to ask in the first ten minutes

FAQ

How long does this brief take to fill out?

For sales reps, a first pass runs in 10-20 minutes. With Strawberry doing the data pulls, it drops to 2-5 minutes per artifact.

Can I customise this for my team?

Yes - the shape above is a starting point. Strip items that don't apply, add items that match your weekly cadence.

What is the biggest mistake?

Treating the brief as a script - it is a research artifact, not a sales monologue.

Run the sales call research brief in 5 minutes with Strawberry

  1. Open the source you want to verify

    Pull up the raw list in a CRM (HubSpot, Salesforce, Pipedrive) or paste it into the Strawberry chat field. For sales reps this is usually 20-80 rows, not a full enrichment dump.

  2. Ask Strawberry to run the checklist line by line

    Use the paste-ready prompt below. Strawberry opens the relevant tabs (a CRM (HubSpot, Salesforce, Pipedrive), Apollo or ZoomInfo, LinkedIn), runs each check, and writes findings into a structured table you can keep.

  3. Resolve the obvious fails first

    Bounced emails, role-bot patterns (info@, sales@), and duplicates against a CRM (HubSpot, Salesforce, Pipedrive) are the cheap wins. Strawberry flags these in seconds and proposes a clean version.

  4. Have Strawberry write the fixes back

    Once you approve the corrections, Strawberry updates the rows in a CRM (HubSpot, Salesforce, Pipedrive) or your sheet. It does not push changes without your approval - this is a guardrail, not a limitation.

  5. Save the run as a routine if you do it weekly

    sales reps who run this checklist every Monday should save the workflow as a Strawberry routine. The next run is one click and the agent uses the same prompt with fresh data.

Paste-ready prompt for sales reps

You are helping a sales rep run the sales call research brief.

Inputs:
- A list pulled from a CRM (HubSpot, Salesforce, Pipedrive)
- Our ICP definition (ask me if unclear)

For each row, run these checks and return a table:
- company snapshot - what they do, size, recent funding or PR moves
- the buyer - role, tenure, public posts, mutual connections
- deal context - prior touches, CRM stage, open opps, last activity
- three angle hypotheses - why now, why us, why this workflow
- five questions to ask in the first ten minutes

Then write a short summary at the top: how many passed, which checks were the top failure reasons, and a clean version of the list with only the rows that pass every check.

Do not send anything or update any system. Stop after the table and wait for me to review.

Paste this into Strawberry's chat field. Strawberry will open the source list, run the checks, and write the table back. No sends, no auto-writes.

When this is NOT a fit

Use a different workflow if you only have a handful of rows to check (under 10). At that point the checklist is overkill - sales reps can eyeball them faster than spinning up an agent. The sales call research brief earns its keep at 20+ rows or when you're going to repeat the run weekly.

Skip it entirely if the list came from a trusted source you already validate at intake (an inbound form with double opt-in, for instance). Running it again is busywork.

3 mistakes to avoid

  1. Treating the brief as a script - it is a research artifact, not a sales monologue. This is the most common failure for sales reps. Strawberry catches it but only if you actually run the dedup step against the live system, not a stale export.
  2. Treating the agent as autopilot. sales reps who let Strawberry send or write back without review end up with worse data than they started with. The point of the checklist is the review, not the run.
  3. Generic talking points, fake-personalised openers, and CRM activity that does not match reality. No checklist saves you from this. If the inputs are bad, no amount of verification turns them into something useful.

Honest tradeoff

The sales call research brief adds 5-10 minutes to every list. That's the cost. The benefit is the rows that hit send are cleaner, your domain reputation stays intact, and you stop emailing customers you already work with. For sales reps sending more than one list a week, the math is obvious. For one-off lists, ask whether the volume justifies the discipline.

Download