getting-started-with-sales-in-strawberry

name	getting-started-with-sales-in-strawberry
description	Help someone get started with Sales in Strawberry. Show what's possible, recommend a useful first task, and help them build toward a connected sales setup over time.

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.