AI sales outreach often promises personalization at scale and delivers the opposite: more messages that sound generic, over-researched, or nothing like the person sending them. Useful automation should carry real context and your own judgment from research through sending and follow-up.

Strawberry is a browser with built-in AI agents. Your companion can learn from messages you have approved, research across the web, and work with context from LinkedIn, email, your CRM, files, meetings, open tabs, and connected apps. Because it works across the places where sales actually happens, it can help with the whole job instead of handing it back to you after generating copy.

What you can build with Strawberry

Your first win might be a thoughtful message to an important prospect or a small batch you are ready to send. From there, your companion can help you:

  • Find the right people and reliable ways to reach them.
  • Research why a conversation might be useful right now.
  • Reach people through email, LinkedIn, and the tools your team already uses.
  • Follow replies, prepare the next step, and keep the CRM up to date.
  • Turn a good process into a reusable skill, sequence, or Routine.

You do not have to build it all at once.

Send personalized outreach that sounds like me

Research, write, review, send, and improve one message, a small batch, or a coordinated sequence.

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.

Start with the relationship and the result

Before writing, get clear on who you are contacting, what relationship already exists, and what you hope happens next. Cold prospecting, warm introductions, event follow-up, re-engagement, partner outreach, and customer communication should not inherit the same message or process.

There are three useful starting points:

  • One message for a personal or high-context situation.
  • A small batch to calibrate the audience, voice, or offer before going wider.
  • A sequence for a repeatable audience where useful follow-ups matter.

Bring together the context that matters

Useful context often lives across email, meetings, CRM, open tabs, LinkedIn, files, and connected apps. Strawberry brings it together without requiring a giant prompt.

Research depth should fit the goal. Important accounts may justify deeper work across company pages, LinkedIn, public databases, and less obvious sources; a familiar audience may need less. Because Strawberry works in the browser, it can follow real sources when the first answer is incomplete. The goal is evidence that improves the reason to reach out—not proof that an agent searched the recipient.

Still need the audience? Find New Customers can build and qualify a small set before writing.

Find me 30 new leads

Find and qualify customers who fit before preparing outreach.

I want to find 30 new leads.

When the audience is clear but the data is not, your companion can find the right person and check missing contact details. It can research the web or use connected enrichment and verification tools. Reliable verification helps protect scaled cold email; a few warm messages may need less.

Enrich a lead or account list

Add, verify, or correct the company and contact data you need before reaching out.

I have a lead or account list that needs better data. Help me decide which fields would make it useful, enrich a small sample for review, and then update the rest after I confirm the approach.

Teach your companion to sound like you

You do not need a long tone guide. Use a simple feedback loop:

  1. Let your companion learn from messages you have sent or examples you choose.
  2. Review a few meaningfully different messages.
  3. Say what sounds right, what feels artificial, and what you would say differently.

For a deeper pass, Learn Your Writing Style can turn approved examples into guidance your companion carries into future work.

Spend a little more time on the first run. Your companion loves feedback; once it learns your voice, audience, and preferences, later batches become much faster.

Personalization does not require a recent post or clever personal detail in every message. Relationship history, segment context, or a clear explanation of why you chose the recipient may be stronger—and often sounds more human than forced praise.

Choose the channel, review the first set, and send

Choose the channel that fits the relationship.

ChannelWhen it may fitHow Strawberry can help
EmailDirect outreach or an existing threadFind and verify contact details, research, write, send, follow replies, and keep the CRM current
LinkedInProfessional discovery, direct outreach, or warm network pathsResearch real profiles and reach out from your logged-in account, with review and account-safety guardrails

Choose where the work should live: chat, inbox, LinkedIn, a sales platform, or CRM. Strawberry can work across them without copy-and-paste.

Before anything goes out, five things are worth a look:

  1. Are these the right people, with contact details you trust?
  2. Do the messages sound like you and fit each relationship?
  3. Is the reason for reaching out clear and credible?
  4. Are the channel, sender, destination, and timing right?
  5. Is your companion preparing drafts or actually sending—and what happens after a reply?

Send personalized outreach that sounds like me

Start with a real audience, review a useful first set, and send when it feels right.

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.

Add follow-ups that do useful work

Thoughtful follow-ups keep promising conversations from being missed. A sequence makes that repeatable: who belongs, what each step adds, when it runs, and what stops or changes it.

A follow-up might deliver something promised, add proof, make the next step easier, address a real objection, or close the loop. It should not repeat the first message because a timer expired. Replies, meetings, opt-outs, bounces, referrals, and relationship changes should alter what happens next.

A sequence can include a phone call or other human step. Your companion can prepare it and carry the outcome forward.

Your companion can carry replies and next steps into the CRM, keeping outreach connected to the rest of sales.

Keep my CRM up to date

Preserve approved outreach, replies, and next steps without silently changing the pipeline.

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.

Save what works and make the next run easier

Once the approach feels right, save the voice, research depth, channels, messages, and follow-up logic as a custom skill. Share an approved message or sequence when teammates need this result, or share the skill when they should reuse the method. If the team needs the same relationship context across outreach and other sales work, share the full companion.

A useful trigger or cadence can become a Routine: prepare weekday drafts, scan replies that should pause future touches, or summarize weekly results and data issues. Start read-only or draft-first, then automate more once you trust the workflow.

For a wider view, use Review Your Sales Pipeline to find the deals and relationships that need attention next.

Review my pipeline and tell me where to focus

Find the deals that need attention and turn them into clear 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.

Open the Send Personalized Outreach skill in Strawberry with one real audience. Your companion can prepare a useful first set and improve it with your feedback before anything is sent.

Official Strawberry skill
name
send-personalized-outreach
description
Research, write, review, send, and improve personalized outreach across email, LinkedIn, and other channels. Use when someone wants to contact known prospects, customers, candidates, partners, investors, or other recipients through one message, a small batch, or a coordinated sequence.

Send Personalized Outreach That Sounds Like You

Help the user get relevant outreach out the door without losing their voice, context, or control. Start with the smallest useful result and expand when helpful. Follow a tailored outreach skill if the user already has one.

Workflow

1. Understand the outreach

Clarify who the user wants to contact, why, what relationship exists, and what they hope happens next. Use relevant tabs, connected apps, files, memory, previous messages, CRM history, and approved materials before asking for context already available.

Understand whether the outreach is relationship-led, campaign-led, or a mix. A warm introduction, meeting follow-up, customer issue, partner conversation, or important personal relationship may deserve one thoughtful message rather than a campaign. In a mixed approach, keep high-context relationships separate from the genuinely repeatable audience.

When meeting notes or a transcript should ground the follow-up, use strawberry/sales/debrief-a-sales-meeting rather than reconstructing what was said. If the meeting still needs to be captured, use strawberry/operations/transcribe-meetings-follow-up first.

If the user still needs recipients, use strawberry/sales/find-new-customers. If a list needs better data or verification, use strawberry/sales/enrich-lead-list.

2. Choose the scope and channels

Align on whether the useful first result is one message, a small batch, or a sequence. When the user is unsure, recommend a small, representative batch they can quickly review and use. Do not force a warm introduction, meeting follow-up, customer issue, or important relationship into a campaign.

Before proposing a larger batch or sequence, inspect the available context and ask only for missing inputs that would materially change the plan. Explain tradeoffs behind scope, cadence, and channels rather than importing generic conventions. Offer rather than require a pilot when the user already has trusted copy and an established process.

Choose channels that fit the audience and relationship. Distinguish a normal LinkedIn connection or message from InMail. Clarify where the work should be reviewed or sent. If a sequence includes a phone call or another manual step, prepare it for the user and carry its outcome forward; do not imply that Strawberry performs the action.

3. Use the right context and voice

Use memory, approved sent messages, and selected examples to understand how the user writes. Read strawberry/general/learn-writing-style when a deeper pass would materially improve the work. Take positioning, proof points, claims, pricing, and sensitive details from approved context.

Choose research and personalization depth based on the goal, stakes, available context, audience, and scale. Infer it when clear; align with the user when the tradeoff matters. Use relationship or account context, relevant changes, and credible reasons to reach out. Do not force a recent detail or invent familiarity, pain points, intent, achievements, or reasons to buy.

Private context may guide the decision to reach out, but do not reveal it in recipient-facing copy unless its use is clearly appropriate and attributable. Avoid personalization that makes someone feel monitored.

4. Draft and calibrate

Draft a small set that represents meaningful differences in recipients, channels, or message types. Make each message natural for its channel, suited to the relationship, and grounded in facts the user can inspect when needed.

Incorporate the user's feedback before expanding. Skip calibration when they already have trusted copy and a straightforward setup.

5. Prepare and send

Prepare drafts, records, recipients, or a sequence in the agreed destination only when asked. Check relevant prior outreach, CRM history, opt-outs, do-not-contact records, and ambiguous identities. For an ambiguous person, confirm the match from multiple signals such as current role, company, location, or prior work rather than guessing. Clean recipient and company fields so credentials, pronouns, emojis, or profile taglines do not leak into greetings or message copy.

Before contacting anyone, show the sender, recipients, content, channel, timing, and whether enrollment starts sending automatically. Get confirmation for that exact scope. One confirmation may cover a fully defined batch or sequence; ask again after any material change.

For scaled cold email, surface material verification, sender, domain, authentication, volume, or platform issues. Keep this lightweight for ordinary one-to-one outreach. On LinkedIn, work sequentially at a human pace and stop on warnings, challenges, rate limits, identity ambiguity, or unexpected states.

6. Deliver and follow through

Execute only the approved scope. Return the messages with their intended recipients, channels, status, and any unresolved sending issues. Treat drafting, enrollment, sending, and recording as separate states. When accurate activity history matters, verify what was actually sent rather than treating a draft, enrollment, or CRM row as proof of delivery.

When requested, help manage replies, opt-outs, bounces, referrals, and booked meetings so the outreach changes when the situation does. Record approved activity and next steps when useful.

7. Add follow-ups and make the next run easier

After the first useful message or batch is accepted or sent, briefly explain that thoughtful follow-ups can keep promising conversations from being missed. Offer to plan a sequence then, or earlier when the user already wants the full process.

When building a sequence, agree on who belongs in it, where it will live, what each touch contributes, its timing or event trigger, the approval scope, and what should stop or change the sequence. Each follow-up should add something useful, make the next step easier, deliver something promised, address a real objection, or close the loop. Do not send a reminder merely because a timer expired.

Include timing and response logic only when building a sequence.

After the user has improved a useful result, offer to save the accepted voice, channels, personalization approach, messages, destination, and follow-up logic as a custom skill. Once the workflow is trusted and has a useful trigger or cadence, suggest a concrete Routine such as a weekday outreach review, reply-triage scan, or weekly outreach review. Keep early Routines read-only or draft-first unless the user explicitly approves a broader scope.

Use strawberry/sales/review-sales-pipeline when the user wants to find which deals or relationships need attention across the wider pipeline, rather than manage an existing outreach queue.