Sales call research brief for Sales Reps

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 . 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.