Most sales collateral starts with a scavenger hunt. The useful context is spread across meeting notes, email, CRM, old decks, product material, and someone’s memory. By the time it becomes a one-pager or presentation, it is often generic, stale, or disconnected from the conversation it is meant to move forward.

Strawberry is a browser with built-in AI agents. Your companion can work with the context already available across your tabs, meetings, files, CRM, email, connected apps, and past work—then turn it into a customer-facing asset built for the decision in front of you. That asset might be a one-pager, slide deck, tailored page, interactive calculator, workflow visual, or something else entirely.

Start with the decision, not the format

A useful sales asset has a job to do. It might help a champion explain the idea internally, align a buying group on a pilot, make a proposed workflow tangible, answer an executive’s questions, or help someone decide what happens next.

Begin with the audience, the state of the conversation, and the outcome you want. If those are already clear from the account context, your companion can get to work without making you fill in another brief.

Bring the real account context together

The strongest sales collateral reflects what the customer has actually said: their priorities, questions, language, constraints, stakeholders, and next step. Strawberry can connect that conversation with the rest of the account context across meetings, CRM, email, open tabs, files, research, product material, and memory.

That matters because the asset is rarely a standalone piece of content. It is part of an ongoing relationship. Your companion can carry the context from research into the meeting, from the meeting into the asset, and from the asset into follow-up without asking you to reconstruct the story each time.

Choose the simplest format that can do the job

The format should follow the moment. Your companion can recommend one when it matters, or follow the direction you already have.

FormatWhen it may fit
One-pagerA concise overview, pilot outline, proposal summary, or recap that should be easy to share
Slide deckA narrative you will present, discuss with a group, or build toward a decision
Tailored page or lightweight siteA self-guided experience that brings the story, proof, and next step together
Interactive calculator or workflowA situation where the customer should explore inputs, tradeoffs, value, or a proposed way of working
Another visual or interactive formatA different form better suits the audience, channel, or decision

The goal is not to make the most impressive artifact. It is to make the next conversation or decision easier.

Make it specific without making things up

Specificity comes from the account context, not from adding more adjectives. Use the customer’s own language where it is accurate, show how the proposed work connects to their priorities, and keep the story focused on one useful next step.

Before external material is polished, check the claims that could change what you are comfortable sharing. Customer outcomes, ROI, pricing, security, timelines, product capabilities, and commitments should come from approved sources or remain clearly marked for review.

  • Use evidence and examples that fit the audience and claim.
  • Separate what the customer said from what your team is proposing.
  • Flag only the missing decisions or assumptions that materially affect the asset.
  • Keep a clear next step visible.

Build it with a companion that learns what good looks like

Strawberry can move from the account story into the visual or interactive result, then critique the complete asset for clarity, accuracy, hierarchy, and usefulness. Because the work happens with the surrounding context still available, feedback can be specific: what to emphasize, what feels off-brand, what the customer will care about, and what should be removed.

Spend a little more time on the first asset. Your companion can learn from the version you accept—your narrative, brand direction, preferred sources, claim rules, and review style—so the next one starts much further ahead. Share the accepted creation method as a team skill when others should reuse it, or share the full companion when the team needs the same customer context across several sales workflows.

Carry the context into the next step

Review the finished asset, then decide whether to share it with teammates for feedback or reuse, deliver it to the customer, publish it, or record it in the CRM. These are separate choices; approval of the asset should not silently approve the next one.

Open the Create a Sales Asset skill with one real account and a decision you want to move forward. Strawberry can bring the context together, recommend a useful form, and build something your customer will actually want to use.

Official Strawberry skill

Create a Sales Asset

Turn the context around a real account into a clear, credible asset that helps move the conversation forward. Own the customer-facing story and choose the form that serves it best rather than defaulting to a generic deck or company overview.

Your advantage is the context already available across the user's work. Connect what the customer said, what the team knows, and what should happen next without making the user assemble a new brief from scratch.

Workflow

1. Understand what the asset should accomplish

Identify the account, intended reader, where the conversation stands, and the decision or next step the asset should support. Ask only for the audience and intended outcome when they are not already clear from the conversation or available context.

Keep the work tied to a real sales situation. If the user needs general marketing collateral, internal account analysis, or broad company research rather than a customer-facing asset, use the skill that owns that result.

2. Bring together the account context

Use relevant meeting notes or transcripts, CRM history, email, files, open tabs, memory, product material, prior accepted assets, and approved brand sources before asking the user to repeat what is already available. Prioritize what the customer has said, what the user has promised, and what matters for the next decision.

Use strawberry/sales/debrief-a-sales-meeting when notes or a transcript still need sales-specific interpretation. Use strawberry/sales/research-an-account when important account or stakeholder context is missing. Do not repeat those workflows inside this skill.

3. Recommend the right deliverable

Choose the simplest form that can achieve the outcome. Depending on the audience and moment, that might be a one-pager, slide deck, proposal page, workshop recap, pilot plan, interactive calculator, workflow visual, lightweight site, or another useful format. Treat these as examples, not a menu the user must work through.

Follow a format the user has already chosen unless another approach would materially improve the result. When the choice affects effort, review, presentation, or sharing, recommend an option and briefly explain the tradeoff before doing a large build.

4. Shape the story and check the claims

Build around one decision or next step. Lead with the point the reader should understand, then use only the context, evidence, and detail that help them act. Use the customer's language when it is accurate and appropriate, and adapt the depth and structure to how the asset will be used.

Before polishing external material, check that material claims are supported by approved sources or clearly framed as the customer's stated priorities. Surface only assumptions or gaps that could change what the user is comfortable sharing.

Never invent customer outcomes, ROI, pricing, security claims, timelines, endorsements, success measures, product capabilities, or commitments. Use a clear placeholder or ask for the missing decision when the asset depends on one.

5. Create and critique the asset

Inside Strawberry, read and use the internal strawberry/general/visual-artifact skill to create, critique, and export the visual or interactive result. For a multi-slide presentation, also read strawberry/research-analysis/create-beautiful-slide-deck and keep this skill's account context, narrative, and claim decisions intact.

Follow approved brand material and relevant visual references. Review the complete asset for narrative, accuracy, visual hierarchy, legibility, interaction where applicable, unsupported claims, and whether it makes the intended next step clear. Show the result to the user for feedback before treating it as customer-ready.

6. Deliver and make the next asset easier

Return the reviewed asset in the most useful available shareable format, preserving an editable source when the chosen creation path supports one. Approval of the asset does not approve sending, publishing, hosting, or changing the CRM.

When useful, offer to share the reviewed asset with relevant teammates for feedback or reuse before external delivery. Keep internal sharing separate from customer delivery, public publishing, and CRM changes.

Use strawberry/sales/send-personalized-outreach when the user wants to deliver it and strawberry/sales/keep-crm-updated for approved record changes. After feedback, offer to save the accepted narrative, brand direction, source preferences, claim rules, format choices, and review behavior as a custom or shared team skill. Suggest a Routine only when the user has a real recurring trigger for creating similar assets, and keep early versions draft-first. When the team needs the same customer context and several Sales workflows, offer to share the full companion rather than only the asset or its creation skill.