Operations teams are the glue between people, systems, and decisions. That often means keeping fourteen tabs open, moving information between tools, and spending the day on urgent coordination while strategic work gets whatever time is left.

Strawberry can take on the repetitive parts without hiding consequential changes. Start with one recurring burden, complete it safely, and keep the process once it works.

Choose a repeatable job with a clear finish

Start with a task that happens often and has a visible result: an organized inbox, a resolved support queue, a completed onboarding checklist, or meeting follow-ups in the right system.

A morning brief is a useful first example: combine approved email, calendar, Slack, and task context into urgent messages, work due today, external-attendee research, and a concise source-linked plan.

Organize my inbox and keep it at zero

Use this to create a repeatable way to process the inbox.

I want to organize my inbox and build a reliable way to keep it at zero.

Automate repetitive support work

Use this to remove repetitive support work while preserving judgment.

I want to automate repetitive support work without losing our tone or judgment.

Compile reports and close follow-up gaps

Recurring reports often require several systems. Gather independent sources in parallel where safe, reconcile duplicates and conflicts, and deliver the accepted structure to the team’s chosen Sheet, Notion page, document, or communication destination.

Follow-up work can compare meetings with sent communication, identify unresolved commitments, and draft the next message with the relevant context. The user reviews communication before it is sent.

Prove the report with one real run before turning it into a recurring job. Keep source links and unresolved discrepancies visible so the team can audit what changed.

Turn every meeting into notes and follow-ups

Turn meetings into decisions, owners, and reviewable follow-up.

I want every meeting turned into clear notes and follow-up actions.

Research the practical details

For trips, events, or vendor planning, compare dates, costs, locations, relevance, flights, accommodation, distances, and practical logistics. Keep live prices, source links, and uncertainty visible rather than presenting options as confirmed bookings.

Automate the repetition, preserve control

Let Strawberry prepare, organize, and propose actions. Keep approvals around sensitive communication, access changes, and irreversible updates until the process is trusted.

Once a result is accepted, preserve the team’s sources, report structure, destinations, ownership, and review rules. Create a Routine only after a successful reviewed run.

Onboard and offboard teammates reliably

Use this for repeatable team access and handoff checklists.

I want to make teammate onboarding and offboarding reliable and much less manual.

Set up a shared team workflow

Turn an accepted operational process into a shared team workflow.

I want to turn a workflow that works into a clear shared process for my team.

Official Strawberry skill

name: getting-started-with-operations-in-strawberry
description: Best practices for anyone getting started with operations in Strawberry. Use when helping a user choose, set up, or expand recurring queues, handoffs, reports, support, or shared team workflows.

Getting Started with Operations in Strawberry

Strawberry can connect email, calendars, project tools, documents, team communication, and dashboards to reduce repetitive coordination. This is not a fixed methodology. Enter wherever the user or team has a real bottleneck, choose one small valuable result, and skip what already works. Over time, help them adopt only the adjacent workflows that genuinely suit how the operation runs.

Set up Strawberry around the process

Start with what eats the user's time each day or week. While the starting point is broad, ask one short question at a time and offer concise choices when useful. Ask whether the user wants to answer a few questions, let Strawberry look through relevant connected apps, or combine both. Before looking, explain briefly what would be useful to find—for example, an existing report template, the dashboards it draws from, or where the team tracks owners and deadlines. No particular source or connected app is required unless the chosen result depends on it.

Learn the owners, inputs, decisions, exceptions, approvals, audience, destination, and success criteria for the chosen result. Use approved examples to understand writing style, escalation rules, and report structure. Before substantial work, summarize the intended process and open uncertainties in a concise plan, then wait for the user to confirm or adjust it.

Start with one concise briefing

A morning brief is often a useful first result. With approval, Strawberry can combine urgent or unanswered email, today's calendar, external-attendee research, team communication that needs attention, and tasks due today. Let the user choose what belongs, highlight priorities, and include working links so the result feels like a briefing rather than an essay. For deeper meeting preparation, read strawberry/sales/prepare-for-calls.

Review the first briefing together and preserve the accepted sources, priorities, depth, and format. Do not schedule it yet.

Turn recurring reporting into a repeatable workflow

For a report or summary, learn how the user currently compiles it: the reporting period, source dashboards, metrics, audience, format, and destination. When available and approved, a previous report or template is often the fastest calibration. Gather independent sources in parallel only when their scopes are clear, then reconcile them into the user's preferred format with working source links. For project or client reporting, read strawberry/operations/build-client-progress-report-project-tools.

Review one complete report before preserving its accepted sources and format. Offer to prepare a sendable draft, but do not send it or schedule recurring preparation without approval.

Calibrate recurring queues

Strawberry can triage incoming work against user-owned rules and prepare replies in an established style. Read strawberry/operations/reach-inbox-zero for inbox organization and reviewable drafts, or strawberry/operations/automate-customer-support when the repeated queue is customer support. Start with a small representative sample so the user can correct urgency, routing, tone, and source-grounded accuracy before a full sweep. Nothing sends, auto-files, auto-replies, or changes an external record without approval.

Support decisions with reviewable evidence

Strawberry can compare vendors against agreed criteria while preserving source links and open questions. Read strawberry/venture-capital/do-due-diligence-vendor-or-supplier for vendor work. When a decision needs repeated fields from websites, agree on the schema and scope, then read strawberry/research-analysis/extract-web-data to create a reviewable dataset.

Close handoffs, then connect the team

After a useful meeting, Strawberry can turn what was actually said into decisions, open questions, owned actions, and a follow-up draft. Read strawberry/operations/transcribe-meetings-follow-up; nothing sends or writes to an external system without approval.

When an accepted individual process should become shared, read strawberry/operations/set-up-shared-team-workflow to make owners, destinations, field meanings, privacy boundaries, and approval behavior explicit, then verify one real handoff before scaling. For joining, changing roles, or leaving the team, read strawberry/recruiting/onboard-offboard-teammates.

Other things to try

These are useful discovery ideas, not complete standalone workflows:

Summarize a long contract or vendor agreement before a decision.
Create a concise weekly summary from approved team and project context.
Find unresolved follow-ups by comparing recent meetings with sent communication.
Prepare the logistics, attendees, and priorities for a business trip or event.

Make the process reliable

Run the process manually on a small sample and confirm missing-data behavior, exceptions, and escalation paths. Save the accepted process as a user- or team-owned skill, including its sources, destinations, owners, field meanings, privacy boundaries, and approval behavior. Add a Routine only after the team trusts the inputs, decisions, handoffs, and review behavior.