Most consultants already have plenty of context. It is spread across meeting notes, email threads, an RFP portal, research tabs, and past deliverables. The tedious part is bringing the right pieces into the next decision without rebuilding the project each time.

Strawberry works in the same visible browser as that material. Your companion can use what is already open or connected, follow research into logged-in sites, and carry what matters into a proposal, recommendation, brief, or deck without rebuilding the engagement for each new task.

What Strawberry can help you do

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

Turn research into a decision

A market map, company list, or interview summary usually gets the client only partway. They still need credible options, the tradeoffs between them, and a recommendation they can challenge.

Your companion chooses the right research path: mapping an unfamiliar market, extracting repeated data across many pages, investigating a company, or comparing a smaller set visually. Because the research happens in Strawberry's visible browser workspace, you can inspect the sources, correct the direction, or take over in a logged-in site while it works.

The recommendation keeps evidence, client claims, calculations, and inference distinct. It can become a memo, deck, workshop artifact, or supporting spreadsheet, depending on how the client will make the decision.

Build the recommendation

Turn the research into credible options and a defensible recommendation, keeping the evidence, client claims, calculations, tradeoffs, and inference clear in the artifact the decision needs.

Skill Turn research into a client recommendation

Move cleanly from sale to delivery

Before the client accepts the work, the proposal says what is being promised: the intended outcomes, work, responsibilities, timeline, fees, and terms. Strawberry uses the real opportunity record and leaves missing pricing, authority, ROI, or legal language visible instead of guessing.

After acceptance, the same reviewed context becomes the engagement brief, including the scope, stakeholders, milestones, evidence standards, and client restrictions. The delivery team does not have to reconstruct the agreement during kickoff.

  1. Define what is being promised

    Turn the real opportunity or RFP into the outcomes, work, responsibilities, timeline, fees, terms, and open questions.

    Skill Create a client proposal

  2. Turn the proposal into an engagement brief

    Carry the scope, stakeholders, milestones, evidence standards, and client restrictions into one engagement brief.

    Skill Start a client engagement

Use meetings to keep the work moving

Before a meeting, Strawberry can start from the calendar and pull in the few decisions, commitments, documents, or changes that should affect the conversation. After a reliable transcript or set of notes is available, the debrief separates discussion from decisions and turns accepted commitments into proposed follow-through.

A daily brief connects that meeting loop to the rest of the consultant's work: which calls need preparation, which promises are due, and which risks or messages deserve attention. Follow-up emails, status updates, CRM changes, and project updates stay separately reviewable.

Reuse what works

Feedback helps your companion learn which sources you trust, what a useful result looks like, and how you want drafts reviewed. Once the method works, save it as a custom skill or a sanitized team skill. Client details stay with the client they belong to.

  • Share an approved artifact when someone only needs the result.
  • Share a sanitized team skill when colleagues need the method but not another client's context.
  • Create a Routine when the sources, trigger, output, ownership, and review step have settled.
Research deep enough to bet onSee how source finding, extraction, synthesis, comparison, and reporting can support deeper client work. Run an AI-native ops teamSee how daily briefs, meetings, updates, open loops, and shared workflows support delivery. Automate your sales pipelineConnect new-business research, meetings, proposals, follow-up, and CRM work before delivery begins.
Official Strawberry skill
Copy skill file Download skill file
name
getting-started-with-consulting-in-strawberry
description
Help consultants use Strawberry across business development, client meetings, proposals, engagement setup, research, recommendations, and follow-through. Use when an independent consultant, boutique firm, or internal consultant wants a useful first workflow or a connected way of working across an engagement.

Getting Started with Consulting in Strawberry

Help the user complete one useful piece of consulting work, then show how the context can carry into the next step. Do not require a full workspace setup or force the whole consulting lifecycle into the first conversation.

1. Understand the work they do

Learn enough to route the user well: the kinds of clients or internal stakeholders they advise, the decisions and deliverables they own, whether they work independently or with a boutique team, and the live work they want help with now. Use context already available before asking questions.

The first result may come from business development, an active engagement, or the user's own daily work. Internal consultants can begin directly with meetings, research, recommendations, status, or team workflows without going through pricing, acquisition, or contract steps.

2. Choose one useful starting point

Offer a small, prioritized set of relevant options, then help the user complete one:

  • For a concise view of today's priorities, client meetings, messages, commitments, and risks, use strawberry/operations/prepare-a-daily-brief.
  • For an upcoming client, workshop, steering, delivery, or internal meeting, use strawberry/operations/prepare-for-meetings. When prospect, partner, account, or pipeline judgment is central, use strawberry/sales/prepare-for-sales-meetings.
  • For a completed general meeting, use strawberry/operations/debrief-a-meeting. Use strawberry/sales/debrief-a-sales-meeting when commercial judgment and CRM follow-through are central.
  • For a live opportunity or RFP, use strawberry/consulting/create-a-client-proposal.
  • When accepted work needs one reliable working brief, use strawberry/consulting/build-client-brief, displayed as Start a Client Engagement.
  • When research needs to become options and a client decision, use strawberry/consulting/turn-client-research-into-recommendations.

If none fits, complete the smallest useful result directly and use it to learn what should become a tailored workflow later.

3. Start from the context that already exists

Strawberry can work across visible tabs, logged-in sites, approved connected apps, meetings, files, chats, memory, and the web. It can follow links across the real sites where the work lives, keep the evidence visible, and let the user inspect or take over. Use only the sources that can materially improve the result. When an app connection would save repeated setup or improve reliability, explain the benefit; continue from tabs, files, or supplied context when a connection is unavailable.

Keep every client's sources, facts, calculations, learned context, artifacts, and access separate. Do not carry one client's confidential material, commercial terms, or strategy into another engagement or into a reusable team method.

4. Connect research to the decision

Choose the shared research skill that fits the job rather than creating a Consultant version:

  • strawberry/research-analysis/research-a-company for a sourced brief on one company;
  • strawberry/sales/research-an-account when the company matters as a commercial relationship;
  • strawberry/research-analysis/map-a-market for boundaries, categories, and relationships;
  • strawberry/research-analysis/extract-web-data for repeated fields across many rows;
  • strawberry/research-analysis/create-beautiful-slide-deck when accepted research should end as a visual presentation.

When the client needs a point of view, continue to strawberry/consulting/turn-client-research-into-recommendations. Keep evidence, client claims, calculations, and consultant inference distinct. Use a deck for a client readout, a spreadsheet for structured comparisons or transparent calculations, and a CSV or dataset for a large research run.

5. Carry the engagement through meetings and follow-through

Treat meetings as a loop: prepare from the calendar and relevant client context, capture a reliable record where supported, debrief what changed, prepare the follow-up, and propose the right status, task, project, or CRM changes. Do not record planned work as completed work.

Use strawberry/operations/prepare-a-status-update for a source-backed engagement update and strawberry/sales/keep-crm-updated when an approved relationship change belongs in the CRM. Treat the brief, debrief, message, assignment, status update, and system change as separate reviewable actions.

6. Deliver to the right place

Before recommending any sharing path, establish the audience, access model, and destination. Internal review, client delivery, CRM or project changes, sending, publishing, and legal acceptance are different states. Approval of an artifact does not approve the next state automatically.

Choose the smallest sharing step that helps: share the approved artifact, share a sanitized method as a team skill, or share the full companion when a team genuinely needs its ongoing context, memory, and several connected workflows.

7. Improve the next engagement

Use feedback from real work to remember trusted sources, evidence standards, decision criteria, voice, formats, and review preferences. Offer a custom skill after those choices have been accepted, not before the user has something useful to react to.

Suggest a draft-first Routine only for a stable recurring job such as a weekday daily brief, pre-meeting preparation, a trusted research refresh, or a client status update. Define the cadence or trigger, systems checked, output, destination, approval behavior, and stop conditions. Stop when client identity or access is unclear, a required source is unavailable, evidence conflicts, or the underlying decision or scope has changed.

Suggested outcome

Complete one useful consulting result now and leave the user with a clear next step. As the work continues, let the same reviewed client context support research, meetings, proposals, recommendations, deliverables, and controlled follow-through without making the user rebuild it at every handoff.