| name | prepare-for-sales-meetings |
| description | Prepare a concise, actionable brief for an upcoming prospect, customer, partner, or other sales meeting. Use when someone wants to combine calendar, relationship, account, and recent sales context before a conversation. |
Prepare for a Sales Meeting
Help the user walk into a sales conversation knowing what matters, what they want from it, and what
to ask. Start with a brief they can scan quickly and go deeper only when it will help.
Workflow
1. Identify the meeting and useful outcome
Start from the calendar when the user refers to an upcoming, next, or named meeting. Resolve the
event, timing, participants, relationship, and purpose from available context. Use attendee names,
email addresses, company domains, and relationship context to match the right people and account
before combining records. Ask only when the match is unclear.
If Calendar is not available as a connected app, briefly explain that connecting it makes meeting
and attendee matching faster, more reliable, and more credit-efficient. Still offer to continue
from an open tab, meeting link or invite, or details the user provides.
Understand what the user wants from the conversation. Calibrate the work to the minutes remaining,
the importance of the meeting, the context already available, and the user's known preferences. If
the meeting is imminent, deliver the essentials immediately. With more time, prepare the standard
brief; go deeper when the stakes justify it or the user asks. Do not spend the available window on
low-value research or make the user design the format first.
2. Bring together the context already available
Use the calendar event alongside relevant email threads, CRM history, prior sales meetings and
notes, files, tabs, connected apps, memory, and shared team context. Prioritize what has happened in
the relationship, open commitments, recent account changes, and anything that could affect this
conversation.
Once the attendees and account are known, gather independent context in parallel when possible.
Recent email, CRM context, and prior meeting notes often matter more than broad web research close
to the meeting, but use only the sources that fit the situation.
Do not make every source a prerequisite or ask the user to repeat context already available. If
missing email, CRM, or meeting context materially limits the brief, suggest connecting the relevant
app and explain what it would improve. Continue with a useful first result when possible.
3. Research only the gaps that matter
Research the people, account, market, recent activity, tools, or another topic only when it could
improve the conversation. Because Strawberry works in the browser, follow useful links across
company sites, LinkedIn, logged-in tools, documentation, news, databases, and other relevant sources
when a shallow result is not enough.
Use strawberry/sales/research-an-account when the account or stakeholders need deeper
investigation than a concise meeting brief. Keep facts, relationship context, and hypotheses
distinct, and make important gaps or contradictions visible rather than filling them with guesses.
When recent relationship and account context already answer the important questions, do not add web
research merely because more research is possible.
4. Build a brief the user can actually use
Default to a one-screen, bullet-led brief in chat that the user can scan before the meeting and
refer to during it. Lead with the desired outcome and the few things most likely to change how they
handle the conversation. Adapt the structure and omit anything that does not help. A useful default
is:
- Who: attendees and essential relationship or account context;
- Why now: the purpose and latest meaningful interaction;
- Where things stand: the deal, commitments, open questions, or blockers;
- Bring this: the most useful anchor, example, or promised item;
- Ask: a few questions or points worth testing; and
- Aim for: the desired outcome, decision, or next step.
Keep supporting details and source links directly beside the bullet they support so the user can
verify something without hunting through an appendix. If deeper preparation is useful, preserve
the concise main brief and add only the extra notes that justify their space.
5. Review and share the brief
Let the user correct the depth, priorities, sources, and structure after a real brief. Preserve
private notes and sensitive hypotheses separately from anything intended for others.
When collaboration would help, offer the smallest relevant step: share the approved brief with the
people joining the conversation, share the accepted preparation method as a team skill, or share
the full companion when teammates need ongoing access to the same sales context, memory, and
several workflows. Confirm the destination and scope before sharing.
6. Complete the meeting loop and make preparation repeatable
Strawberry can capture supported conversations without adding a visible meeting bot when the user
wants a reliable record. When a transcript or reliable notes are ready, use
strawberry/sales/debrief-a-sales-meeting for a sales debrief and follow-through. Use
strawberry/sales/keep-crm-updated for approved CRM changes.
After feedback, offer to save the accepted sources, depth, priorities, format, destination, and
review behavior as a custom or team skill. When preparation has a useful trigger or cadence,
suggest a Routine that checks the agreed calendar events plus relevant email, CRM, prior meetings,
and account changes, then prepares the brief in the chosen destination. Stop and ask when the
meeting or participant match is unclear, private context may be exposed, or the preparation depends
on a decision only the user can make.
