The awkward part of sales meeting preparation is rarely finding one more fact about the company. It is pulling together the context that already exists: who is joining, why the meeting is happening, what happened last time, where the deal stands, and what you promised to bring.

Strawberry is a browser with built-in AI agents. Your companion can work across your calendar, email, CRM, previous meetings, files, open tabs, connected apps, and the web, then turn the useful parts into a concise brief you can keep open during the meeting. When the meeting starts in five minutes, it should move quickly. When the stakes are higher and there is time to prepare, it can go deeper.

Start with the meeting that is actually happening

A useful brief starts with the real event, attendees, relationship, and outcome—not a generic company profile. Calendar is usually the fastest and most reliable starting point because it identifies the meeting and gives your companion exact names, email addresses, timing, and invite context.

Connecting Calendar can make this faster, more reliable, and more credit-efficient. It is not a prerequisite. Strawberry can also begin from an open tab, a meeting link or invite, or the details you provide.

Match the preparation to the time and stakes

Not every meeting deserves the same amount of research. The useful question is not “How complete can this brief be?” It is “What will help most in the time available?”

SituationUseful preparation
The meeting is imminentDeliver the essentials now: who, why, latest interaction, where things stand, one useful anchor, and the desired outcome.
There is time for a standard passAdd relevant email, CRM, prior-meeting, account, and stakeholder context without turning the brief into homework.
The meeting is important or the user asks for depthInvestigate meaningful gaps, recent changes, stakeholders, product or market context, and questions worth testing.

When deeper work is useful, your companion can deliver the short brief first and continue researching underneath it. You should not miss the useful answer because the complete answer is still being assembled.

Use the relationship context that matters

Recent relationship context often matters more than broad web research. The latest email may contain an unanswered question. The CRM may show the actual stage and owner. Previous meeting notes may contain a promise or objection that should shape this conversation.

Once Strawberry knows the attendees and account, it can check independent sources in parallel and bring back only what affects the meeting. If email or CRM context would materially improve the result, your companion can suggest connecting the relevant app and explain why. It should still produce a useful first brief from what is available.

When an important gap remains, being a browser matters. Strawberry can open the real company site, move through LinkedIn or another logged-in tool, follow documentation and useful links, and investigate beyond the first search result. If the account needs a deeper investigation, use Account Research rather than forcing all of that work into every meeting brief.

Create a brief you can keep open during the meeting

A meeting brief should help in the conversation, not only before it. Keep the main view to roughly one screen and use bullets you can find again at a glance.

  • 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 strongest anchor, example, or promised item.
  • Ask: a few questions or points worth testing.
  • Aim for: the decision, outcome, or next step.

Keep useful evidence and links beside the bullet they support. If you need to verify a detail or open the latest thread mid-meeting, it should be one click away—not hidden in a source appendix or buried in several pages of research.

Teach your companion what good preparation looks like

The first brief gives you something real to react to. Tell your companion what deserved more attention, what it could have left out, which sources you trust, and how you like to prepare. It can remember those preferences so later briefs become faster and feel more like the way you would prepare yourself.

Once the format works, save the accepted approach as a custom or team skill. Share an approved brief when teammates need this result, share the skill when they should reuse the preparation method, or share the full companion when the team needs the same customer context and several connected sales workflows.

When the workflow is trusted, a Routine can check the agreed calendar events at the right lead time, combine the useful email, CRM, meeting, and account context, and deliver each concise brief in chat. If the meeting or attendee match is unclear, it should stop and ask rather than prepare for the wrong conversation.

Carry the context through the meeting

Preparation is the beginning of the meeting loop. Strawberry can transcribe the conversation without adding a meeting bot. Afterwards, your companion can turn what was said into a sales debrief, follow-up, CRM changes, and the next piece of work—without making you reconstruct the relationship again.

Open Prepare for a Sales Meeting with one real event. Your companion can give you a brief that fits the time you have now, then learn how to make every future meeting easier to walk into.

Official Strawberry skill

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

Use strawberry/operations/transcribe-meetings-follow-up when the user wants to capture the meeting. 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.