Meeting prep prompt for Recruiters

The meeting prep prompt adapted for recruiters. Body, role-specific tweaks, common pitfalls, and how to run it with Strawberry.

Meeting prep prompt for recruiters

This is the meeting prep prompt adapted for recruiters. It exists because spending too much time on admin, and the prompt below is the shape that actually survives contact with how recruiters work day to day.

What this prompt is for

Purpose: feed Strawberry the prompt that produces a usable meeting prep doc in under 60 seconds. For recruiters 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 recruiters and the tools they actually live in.

The meeting prep prompt (prompt)

  • The meeting context (calendar invite, attendees, agenda)
  • The goal of the meeting in one sentence
  • The three signals you need (recent news, role change, prior contact)
  • The format you want back (one-page markdown, slack-ready bullets, CRM note)
  • The guardrails (no fluff, no fictional details, source-cited)

Adjustments for recruiters

recruiters typically live in . That changes how this prompt runs:

  • Pull the inputs from the apps recruiters 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

Leaving the goal vague - a meeting prep prompt without a goal produces generic context, not decision-ready prep. For recruiters, this shows up as spending the saved time on more admin instead of higher-leverage work. Build the prompt into your week, not as a one-off.

How Strawberry runs this prompt

Strawberry runs the prompt against your live calendar, email, and CRM - so the output is grounded in your actual history with the contact. For recruiters, Strawberry uses your live tabs and connected apps - so the prompt is filled with your real context, not a placeholder.

When to use this, when to skip

Use this prompt when the work recurs (weekly, per-prospect, per-meeting). Skip it when the situation is novel and judgment-heavy - the prompt 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.

Meeting prep prompt

1 the meeting context

Step 1

the meeting context (calendar invite, attendees, agenda)

2 the goal of the meeting in one sentence

Step 2

the goal of the meeting in one sentence

3 the three signals you need

Step 3

the three signals you need (recent news, role change, prior contact)

4 the format you want back

Step 4

the format you want back (one-page markdown, slack-ready bullets, CRM note)

5 the guardrails

Step 5

the guardrails (no fluff, no fictional details, source-cited)

FAQ

How long does this prompt take to fill out?

For recruiters, 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?

Leaving the goal vague - a meeting prep prompt without a goal produces generic context, not decision-ready prep.