Sales call research brief for Founders

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

Sales call research brief for founders

This is the sales call research brief adapted for founders. It exists because spending too much time on admin, and the brief below is the shape that actually survives contact with how founders 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 founders 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 founders 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 founders

founders typically live in . That changes how this brief runs:

  • Pull the inputs from the apps founders 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 founders, 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 founders, 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 founders, 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.