Sales teams rarely have the full picture in one place. The CRM shows part of it; the rest is spread across emails, meeting notes, LinkedIn, company websites, and the other tabs your team uses. Pulling that picture together again for every prospect, meeting, and follow-up takes time.

Most sales AI sees one slice of that picture: a CRM record, a call, or whatever you pasted into a chat. Strawberry works across the browser and apps your team already uses. It can open the current sources, use your logged-in tools, bring the account history together, and keep it available for the next task.

What Strawberry can help you do

Not sure where to start? Your companion can look at the sales work you have open and suggest a useful skill to try first.

/getting-started-with-sales-in-strawberry

Use the work and context already in front of you to choose a useful first Sales skill.

View skill

Find and reach the right customers

Prospecting can start with a new market or a list already sitting in your CRM. Strawberry can research across company sites, LinkedIn, directories, and logged-in tools, show why each prospect fits, and move from a checked sample to the full list you asked for. The same research can then feed contact enrichment and outreach without another round of copy-and-paste.

  1. Find the part of the market worth pursuing

    Compare segments, companies, and current signals before you spend time building the list.

  2. Build the prospect list

    Strawberry checks a varied sample with you, then completes the list at the scale you asked for.

    /find-new-customers

    Find me leads that match my ICP.

    View skill

  3. Find the right people

    Add the contacts and details needed for outreach or qualification without padding the file with fields you will not use.

    /enrich-lead-list

    Fill in the missing fields on this lead list.

    View skill

  4. Turn the research into outreach

    Draft a single message, a batch, or a coordinated sequence in your voice. You review sending and enrollment separately.

    /send-personalized-outreach

    Write personalized outreach for this list.

    View skill

Prepare for and follow up on customer conversations

Good meeting prep and follow-up depend on the same account story. Strawberry can pull together the calendar invite, CRM, email thread, call history, LinkedIn, and current company news before the meeting. Afterward, it can use the transcript or notes to draft the follow-up and update the next steps. You do not have to brief a different tool at every stage.

  1. Learn what matters before the call

    Go deeper on the company, people, relationship, or recent changes when they could affect the conversation.

    /research-an-account

    Research this account and find me a way in.

    View skill

  2. Walk in prepared

    Bring the account history, meeting goal, open questions, and useful evidence into one short brief.

    /prepare-for-sales-meetings

    Prepare me for my next sales meeting.

    View skill

  3. Follow through while the details are fresh

    Turn the transcript or notes into the follow-up, next actions, and CRM changes that need review.

    /debrief-a-sales-meeting

    Turn my last sales call into next steps.

    View skill

  4. Build what the buyer needs next

    When an email is not enough, create a one-pager, deck, or tailored page from the same account context.

    /create-a-sales-asset

    Create a one-pager for this account.

    View skill

Review pipeline and keep the CRM current

The CRM is useful only when it reflects what is actually happening. Strawberry can compare the record with recent meetings, email, commitments, and account signals, then show where deals are stuck and prepare the updates that would make the pipeline trustworthy again.

See where deals need attention

Review the activity and commitments behind each stage to find stalled deals, missing next steps, and the actions most likely to move them forward.

/review-sales-pipeline

Review my pipeline and tell me where to focus.

Keep the record current

After a meeting or follow-up, prepare the exact field changes and show the source before applying them.

/keep-crm-updated

Update my CRM from this week's activity.

Know what matters today

Bring today's meetings, messages, risks, and commitments into one short sales brief.

/prepare-a-daily-brief

What deserves my attention today?

Share a clear sales picture

Turn the reviewed pipeline into a concise update for leadership or the team.

/prepare-a-status-update

Write a status update on my current work.

Reuse what works

As you correct real work, your companion can remember the sources you trust, how you qualify accounts, your writing style, the CRM fields that matter, and where you want to review changes. The next prospect list, brief, or follow-up can start closer to the way your team actually works.

  • Share an approved result when a teammate only needs the output.
  • Turn a workflow into a team skill when everyone should use the same sources, judgment, and review points.
  • Create a Routine after the trigger, destination, permissions, and stop conditions are clear.
/set-up-shared-team-workflow

Turn this workflow into something my team can run.

View skill

You do not need to automate the whole sales process at once. Pick one job that repeats this week, make the result genuinely useful, and build from there. Strawberry becomes more valuable as the research, conversations, and records stop resetting between steps.

Run your whole company from one place

Connect customer growth with company visibility, fundraising, hiring, and the rest of the founder's work.

Market like a team of ten

See how audience insights, campaigns, content, and performance can support the same customer journey.

Run an AI-native ops team

Connect sales meetings and pipeline work with daily attention, open loops, status updates, and team workflows.

Try this starter pack in Strawberry

/getting-started-with-sales-in-strawberry

Get Started with Sales in Strawberry

Help the user see how their companion can support the whole sales journey, not just one isolated task. Briefly paint the bigger picture, explain what makes Strawberry different, and then help them choose one useful place to begin.

Paint the picture

Explain that Strawberry gives the user more than a chat box. Because Strawberry is a browser, the user and their companion can work together in the websites where sales happens. You can learn from their tabs, work inside websites, and bring together context from email, calendar, CRM, meetings, files, connected apps, and the public web. Your memory helps you get to know their customers, preferences, writing style, and way of working over time.

Show how the pieces can connect: finding customers can lead into account research, meeting prep, follow-up, CRM updates, and pipeline decisions. This can grow into a powerful way to run sales, but the best place to start is usually one real piece of work.

Keep this introduction brief, friendly, and inspiring. Do not turn it into a feature tour.

Find a good first win

Start with what the user wants to accomplish. If they already have a real task in mind, follow their lead. If they are unsure, offer a small set of useful starting points:

  • find promising new customers;
  • research an account and find a way in;
  • get ready for an upcoming meeting;
  • send personalized outreach that sounds like them;
  • recommend a first win from their open tabs, connected apps, and other available context;
  • tell you what they already have in mind.

Adapt the choices and wording to the conversation rather than treating this list as a script or a closed menu. If the user asks for a recommendation, look through their available context (e.g. apps, tabs, memory) and suggest a small, prioritized set of strong options and explain why they fit. If there is little useful context, briefly suggest a relevant app they could connect and explain what it would unlock. Do not turn this into a setup checklist or make connecting apps a requirement before helping.

Use a focused skill when it fits

First understand the result the user wants. If a focused Official Skill fits, read it and adapt it to their situation. If another collection owns the workflow, use that skill instead. If no existing skill fits, help using your normal capabilities rather than forcing the task into the closest workflow. A useful process that repeats can later become a custom skill.

  • Research an account and find a way in: read strawberry/sales/research-an-account. Use it whether or not a meeting is already scheduled. Start from the decision or conversation the research should help with.
  • Prepare for an upcoming sales conversation: read strawberry/sales/prepare-for-sales-meetings.
  • Turn a conversation into next steps: when a transcript or notes exist, read strawberry/sales/debrief-a-sales-meeting. Strawberry can capture supported conversations without adding a visible meeting bot when the meeting still needs a reliable record.
  • Review the pipeline and choose what to do next: read strawberry/sales/review-sales-pipeline. Begin with a review the user can react to before suggesting a recurring version.
  • Map a market, segment, territory, or account universe: read strawberry/research-analysis/map-a-market. Use it for market-entry and landscape decisions, then move to strawberry/sales/find-new-customers only when the user accepts the market definition and wants a qualified prospect list.
  • Find and qualify new customers: read strawberry/sales/find-new-customers. Start with a small, varied sample, invite feedback, and explain the tradeoff before widening the search.
  • Enrich a list the user already has: read strawberry/sales/enrich-lead-list.
  • Send personalized outreach that sounds like the user: read strawberry/sales/send-personalized-outreach. Agree on the channel and destination, show a few representative messages, and get approval before sending or enrollment.
  • Create a customer-facing sales asset: read strawberry/sales/create-a-sales-asset. Use the account and meeting context already available to recommend and create the simplest useful format for the next customer decision.
  • Clean or update CRM records: read strawberry/sales/keep-crm-updated.

When several options fit, recommend a small prioritized set and explain why they fit the user's situation instead of listing every skill.

Teach through the work

Help the user become better at working with their companion while you work together:

  • Context and memory: explain that good context leads to better work. Use their feedback to learn what matters, and let them know that memory helps carry useful context into future chats.
  • Small loops: for subjective, expensive, or high-volume work, begin with a small result. Ask what they like and what they would change before doing more.
  • Skills: after feedback reveals a repeatable way of working, offer to save the useful criteria, tone, sources, fields, steps, and review points as a custom skill. Do not save the first result automatically.
  • Team collaboration: once a personal workflow works and would help others, explain how a shared Sales companion can carry the team's context, memory, and skills across the immediate team.
  • Routines: after the workflow is trusted and has a real trigger or cadence, offer to make it a Routine.

Connect the journey over time

After a useful result, suggest one natural next step when it would genuinely help. Examples:

  • account research -> meeting preparation -> follow-up -> approved CRM update;
  • small prospect sample -> feedback -> wider search -> enrichment;
  • market landscape -> accepted target market -> qualified prospect search;
  • account research and writing examples -> outreach sample -> approved sequence;
  • account research or meeting context -> customer-facing asset -> approved delivery;
  • pipeline review -> prioritized next actions -> later weekly Routine;
  • a workflow shaped through feedback -> custom skill -> shared Sales companion when useful.

When the user returns, build on what they already do with their companion. Help them improve a workflow, connect the next part of sales, or try something more ambitious instead of restarting onboarding.

Keep the user in control

Research, drafting, sending, and changing records are different steps. Never treat approval of one as approval of the next. Before sending messages, enrolling contacts, changing CRM records, or sharing private context, confirm the people, records, destination, and scope. Keep important sources and uncertainty visible when they affect a sales decision.

You have done the job when the user understands what is possible, completes a useful first workflow, and knows the most relevant way their companion can help next.