A sales pipeline review should help you decide what to do next. Too often, it becomes a tour of CRM fields while the most useful context still lives somewhere else.

Strawberry is a browser with built-in AI agents. Your companion can work with your CRM alongside recent emails, meetings, calendar events, files, open tabs, and connected apps. That makes it possible to review not only what the pipeline says, but what has actually happened around each deal—and turn that context into a useful plan for the week.

What you can build with Strawberry

A first review can be simple: take one pipeline view, find the deals that deserve attention, and leave with a short list of next actions. As your companion learns how your team sells, the workflow becomes more useful.

It can prepare the team before a pipeline meeting, bring recent customer conversations into the room, spot when the CRM no longer matches reality, draft follow-ups, and prepare approved updates. Over time, that becomes a weekly sales rhythm rather than a report rebuilt by hand.

Review my pipeline and tell me where to focus

Review a real pipeline or useful slice and get clear priorities, risks, and next actions.

Review my current sales pipeline and help me decide where to focus this week. Use the CRM plus relevant recent email and meeting context, explain the biggest risks and opportunities, and show proposed CRM corrections separately before changing anything.

Start with the decision you need to make

You do not have to audit the entire CRM. Start with the decision in front of you: which deals need attention, what may slip, where someone should step in, or what the team should cover next.

Begin with a connected CRM view, export, spreadsheet, pasted list, or smaller set of opportunities. A connection makes the workflow easier to repeat, but is not required for a useful first review.

Bring the conversation back into the pipeline

The CRM is an important source of truth, but it rarely contains the whole truth. A deal may look inactive even though a meeting happened yesterday. A next step may look current even though the customer changed it in an email. A close date may still be in the future even though a key decision has slipped.

Because Strawberry can work across your logged-in tools, your companion can connect the pipeline with recent threads, meeting transcripts, calendar events, notes, documents, and account research. It can explain what deserves attention while keeping CRM facts separate from interpretation.

Look for changes that affect what you do next

A useful pipeline review does not need a universal health score. What counts as stale or risky depends on the sales cycle, stage, relationship, and way your team works.

Instead, look for signals that should change a decision:

  • No clear next step or owner.
  • A close date or stage that no longer fits the evidence.
  • A promising deal with fresh momentum.
  • An important stakeholder, approval, or unanswered question holding things up.
  • A relationship that has gone quiet for this kind of deal.
  • Missing or conflicting information that makes the current plan hard to trust.

The point is to explain why something matters and what could move it forward.

Leave with a plan, not another dashboard

A good review should make five things clear:

  1. Which deals deserve attention now?
  2. Why did they rise to the top?
  3. What is the next useful action, and who owns it?
  4. Which deals should be monitored, reconsidered, or qualified out?
  5. What needs correcting in the CRM?

Some priorities need deeper account research; others are ready for outreach. Keeping those as clear next steps lets the review stay focused.

Research an account and find a way in

Investigate the company, relationship, and evidence behind a priority deal.

Research this account and help me understand the company, our existing relationship, what matters now, and the most useful way forward. Start with the context already available and give me a concise sourced brief before offering a deeper pass.

Send personalized outreach that sounds like me

Turn the next move into a thoughtful message or follow-up.

Help me send personalized outreach to this list. Use what you know about my voice and context, research only where it will help, and start with a small set I can review. Before sending, show me the exact recipients, messages, channels, and timing—and explain when thoughtful follow-ups or a sequence would be useful.

Keep proposed CRM changes separate from the analysis, with the source and reason behind each one. Approve the right updates without silently changing stages, close dates, or activity history.

Keep my CRM up to date

Review and apply approved changes from pipeline work, emails, and meetings.

Help me keep my CRM current from recent emails, meetings, and sales activity. Use the CRM and context already available, then show me a small set of proposed updates with their sources so I can correct the mapping before anything changes.

Turn the review into a weekly sales rhythm

Tell your companion which risks matter, how your stages work, and what the team wants before a pipeline meeting. Share the approved brief with the people joining the review while keeping sensitive notes and proposed CRM changes separate. The next review can begin with that context.

Once the workflow feels right, share the accepted review method as a team skill when others should reuse it. If the team needs the same pipeline and customer context across several sales workflows, share the full companion. A weekly Routine can then check the agreed pipeline view, bring in recent conversations, prepare the review, and draft updates before the team meets. Start read-only or draft-first.

Open the Review Your Sales Pipeline skill with one real pipeline or useful slice. Your companion will help you find the decisions that matter now—and make the next review easier.

Official Strawberry skill
name
review-sales-pipeline
description
Review a sales pipeline to identify priority deals, material risks, missing context, CRM hygiene issues, and the next actions most likely to matter. Use for a weekly pipeline review, pipeline meeting preparation, deciding where to focus, or finding deals that are stuck, neglected, or inaccurately represented.

Review Your Sales Pipeline

Turn pipeline data and recent deal context into a clear view of where to focus next. Start with a useful review; do not force a scoring model or recurring setup on the first run.

Workflow

1. Understand the review

Clarify the pipeline or useful slice, period, and decision. It may cover the user's deals, a team, segment, quarter, or short list. Use existing review habits and stage definitions when available rather than importing a generic methodology.

If the request is broad, recommend a manageable first review such as the current open pipeline or the deals most likely to need attention this week.

2. Bring together the real deal context

Start with the CRM or supplied pipeline view. If it is not connected, use an export, spreadsheet, pasted list, or useful subset and explain what connecting it would unlock.

Add relevant approved context from recent email, meetings, calendar, files, tabs, memory, and connected apps. Use it to clarify momentum, commitments, objections, stakeholders, and next steps, but do not silently overwrite CRM-owned facts such as stage, amount, owner, or close date.

3. Agree on what deserves attention

Use the team's qualification bar, sales cycle, stages, and review habits when known. Otherwise, propose a light starting approach and let the user correct it. Useful signals may include:

  • an unclear or overdue next step;
  • a stage or close date that no longer matches the evidence;
  • recent momentum or a timely opportunity that deserves focus;
  • a deal waiting on one stakeholder, decision, approval, or unanswered question;
  • a relationship that has gone quiet relative to this team's normal cycle; or
  • missing, conflicting, or stale information that could change the decision.

Do not treat a universal number of inactive days, a fixed weighting formula, or a health score as truth. Explain the reasoning behind each material flag.

4. Review and prioritize the pipeline

Match evidence to the correct account and opportunity. Separate facts, reasonable hypotheses, and missing context. Focus on the few deals or patterns that should change what the user does next.

Recommend a practical next action for each priority deal when the evidence supports one: who should do what, by when or in what situation, and toward what outcome. Some deals should be monitored or reconsidered rather than given more activity.

5. Make the review easy to act on

Lead with the priorities. A useful output normally includes:

  • the review scope, sources, and freshness;
  • the few deals to focus on now, with the evidence and recommended next action;
  • material risks, blockers, or gaps that need a decision;
  • deals to monitor, reconsider, or qualify out when useful; and
  • proposed CRM corrections or missing fields, kept separate from the analysis.

Use a compact table when comparing several deals. Avoid false precision, padded lists, and scores that hide the underlying judgment.

6. Review changes before updating anything

Keep the first review read-only. Show proposed changes with their source and reason, then ask for approval of the specific records and fields before using strawberry/sales/keep-crm-updated to write them back.

Do not create tasks, change records, or contact anyone without approval for that action. When a priority deal needs deeper research, use strawberry/sales/research-an-account; when the next move is outreach, use strawberry/sales/send-personalized-outreach.

7. Make the next review easier

After the user corrects the priorities and signals, offer to share the approved review brief with the relevant teammates before the pipeline meeting. Keep sensitive notes and unapproved CRM changes separate.

Offer to save the accepted scope, definitions, output, and review behavior as a custom or shared team skill. When teammates need the same pipeline, customer context, and several Sales workflows, offer to share the full companion. Once trusted, suggest a weekly Routine that checks the agreed CRM view plus recent meetings and email, prepares a brief before the pipeline meeting, and drafts proposed updates. Keep early Routines read-only or draft-first unless the team approves more.