Good meeting preparation is not a biography of every attendee. It is the small amount of current context that helps you understand the relationship, make a decision, ask better questions, and leave with a clear next step.

Strawberry can connect an approved calendar event with relevant email, CRM or ATS history, prior notes, company context, and current public evidence. The result should be brief enough to scan in a few minutes and specific to the conversation ahead.

Start with the meeting outcome

Confirm which meeting matters, why it is happening, what the user needs to stay on top of, and what a useful outcome would be. A sales discovery call, candidate interview, client review, board meeting, and partnership conversation need different preparation.

Ask how the user already prepares. If they have no preferred format, propose a concise brief and refine it from feedback rather than producing a long generic report.

Gather only relevant, approved context

Useful context may include the event and participants, recent conversations, relationship history, open tasks, CRM or ATS stage, company news, current work, and likely concerns. Not every source is required, and the user should not need to repeat information that is already available and approved.

Match the correct person and organization to the meeting. Separate verified facts from assumptions, preserve useful links, and surface contradictions or important gaps instead of filling them with guesses.

Prepare me for every call today

Use this to assemble a concise, evidence-backed brief for the meeting.

I want to be fully prepared for every call today.

Make the brief actionable

Prioritize the few developments, concerns, questions, and talking points most likely to affect the outcome. A practical brief usually includes participants, relationship context, the purpose of the call, recent developments, open threads, recommended questions, and a desired outcome.

Present the information in scan order, keep uncertainty visible, and adjust the depth after the user reviews a real brief. When others are joining the conversation, share an approved version with the relevant teammates while keeping private notes and sensitive hypotheses separate. Once the format works, preserve the accepted sources, priorities, and structure as a custom or team skill.

Connect preparation to what happens afterward

After the meeting, turn what was actually said into decisions, open questions, action items, and a grounded follow-up draft. Keep messages and external updates reviewable until the user approves them.

When the workflow is trusted, meeting preparation can be collected into a morning briefing or prepared at an agreed cadence without changing the evidence and approval standards.

Never forget a meeting or follow-up

Use this to capture the conversation without a meeting bot.

I want meetings transcribed with decisions and follow-ups captured automatically.

Turn this sales meeting into clear next steps

Use the transcript or notes to prepare a sales debrief and complete the follow-through.

Debrief this sales meeting using the transcript or notes. Tell me what changed, prepare the right follow-up and next actions, and show any proposed CRM updates separately before changing anything.
Official Strawberry skill
name
prepare-for-calls
description
Prepare concise, actionable briefs for upcoming sales, customer, client, candidate, pitch, board, or diligence calls using relevant approved context.

Prepare for calls

Use this as a starting point for preparing different kinds of calls. Adapt the brief to the meeting and to how the user prefers to prepare.

Context, setup, and planning

Confirm which calls to prepare, the desired outcome for each, and what the user needs to stay on top of. Ask how they usually prepare. If they have no preference, propose a concise starting format and refine it from their feedback.

When relevant, available, and approved, useful context can include:

  • the calendar event, meeting topic, and participants;
  • the person's role, tenure, background, recent work, public activity, portfolio, or GitHub when relevant;
  • company or market background, recent news, funding, leadership changes, hiring activity, and known tools;
  • relationship history, prior notes or conversations, open threads, CRM or ATS stage, client results or account changes, and notes from colleagues;
  • signals, likely concerns, pain points, or questions that matter for this meeting.

Offer to gather this through a few questions, approved sources, or both. Do not treat every source as a prerequisite or ask the user to repeat information that is already available.

Agree where the brief should live and whether preparation is on demand, before individual calls, or collected into a morning or evening briefing.

Execution

  1. Match the correct participants and relationship history to each meeting.
  2. Separate verified facts from assumptions. Surface contradictions or important gaps rather than filling them with guesses.
  3. Prioritize the few developments, concerns, questions, and talking points most likely to affect the outcome.
  4. Include working links to useful source records when they help the user move quickly.
  5. Present a clean brief that can be scanned in a few minutes, then adjust its depth and format from the user's feedback.

Suggested outcome

Produce one concise, actionable brief per call with participants, relationship context, purpose, recent developments, likely concerns, recommended questions, and a clear desired outcome.

Suggested next steps

  • Read strawberry/sales/research-an-account when the account or stakeholder needs deeper investigation than a concise meeting brief.
  • When the approved brief would help others joining the conversation, offer to share it with the relevant teammates in their agreed destination. Keep private notes and sensitive hypotheses out of the shared version.
  • After the format is useful, preserve the user's preferences as a custom or shared team skill. After a few successful runs, offer to schedule preparation at their preferred cadence.
  • Read strawberry/operations/transcribe-meetings-follow-up when the user wants to capture the meeting. Once a transcript or notes are ready, read strawberry/sales/debrief-a-sales-meeting for sales-specific interpretation and follow-through.
  • Read strawberry/sales/keep-crm-updated when approved meeting context or next steps should be reflected in the CRM.