Founders move between meetings, customers, hiring, investor updates, inboxes, and company decisions. Strawberry is most useful when it takes one piece of that work from scattered context to a result you can review.

Start with the pressure that matters now. Strawberry can learn through a few questions, relevant connected apps, or both. Once the first result is useful, keep the accepted sources, format, voice, and review points so the same work gets easier next time.

Start with one result that matters this week

Do not begin by redesigning the company. Pick a result that would make the next week easier: prepare for an important day, find the next customers, make progress on a fundraise, fill a priority role, or remove a recurring piece of administrative work.

Keep discovery light. Strawberry can ask one short question at a time, check relevant approved context in connected apps, or combine both. Before doing substantial work, confirm the result, the important uncertainties, and a concise plan.

Find my company 30 new customers

Build and calibrate a reviewable shortlist of the next customers.

I want to find 30 new customers for my company.

Prepare my next fundraise

Turn the next fundraise into a clear story, target list, and practical process.

I want to prepare my next fundraise with a clear story, evidence, target investors, and a practical process.

Prepare for the day, then close the loop

When attention is the bottleneck, a concise morning brief is a strong first workflow. Strawberry can bring together urgent messages, work due today, and the meetings that need preparation, with links back to the useful source material.

Before an important call, it can turn calendar, company, person, and relationship context into a brief you can scan. Afterward, the transcript can become decisions, action items, owners, filed notes, and a grounded follow-up draft. Messages remain drafts until you approve them.

Prepare me for every call today

Walk into today’s important calls with the context that matters.

I want to be fully prepared for every call today.

Never forget a meeting or follow-up

Turn each meeting into notes, decisions, and reviewable follow-up.

I want meetings transcribed with decisions and follow-ups captured automatically.

Keep company communication moving

An overloaded inbox is a useful place to calibrate Strawberry around your judgment. Define the categories that matter, let it learn your reply style from approved examples, and review a small batch before expanding the workflow.

Strawberry can surface what deserves attention and prepare replies in your voice. It should not send, delete, archive, unsubscribe, or make bulk changes without explicit approval.

Organize my inbox and keep it at zero

Organize the inbox and build a reliable way to keep it under control.

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

Turn company context into decisions and clear artifacts

Investor updates, board materials, company reports, and market decisions often begin with information spread across dashboards, documents, Slack, meeting notes, and the web. Establish which metrics and milestones matter, where they live, who will read the result, and whether an accepted report or deck should set the structure.

For outside research, agree on the decision, scope, evidence standard, depth, and desired output. Keep source links and dates, separate facts from inference, and make uncertainty or conflicting evidence visible.

Create a beautiful slide deck for me

Turn approved source material into a polished, on-brand presentation.

I want to create a beautiful slide deck.

Research companies and create beautiful slide decks

Research companies and turn the findings into a clear visual brief.

I want help researching companies and creating beautiful slide decks.

Grow one accepted result into a company workflow

Review the first result and correct its assumptions, depth, format, tone, sources, and tool choices. If the process proves useful, preserve those accepted choices as a company-specific skill instead of starting from generic instructions next time.

When several people need the same inputs, ownership, destination, or review behavior, turn the individual workflow into a shared one. Verify one real handoff before scaling it. Add a routine only after the underlying process has worked a few times and the team wants it to recur.

Other useful directions include modelling a major decision, mining approved product telemetry for patterns, preparing a weekly KPI review, or assembling a diligence pack. Introduce them when they solve a real problem rather than presenting a long list all at once.

Find 10 engineers like our best ones

Find people for a priority role when hiring becomes the next constraint.

I want to find 10 engineers based on the qualities of our strongest existing people.

Make a workflow reusable across my team

Make a proven workflow reusable across the team with clear review points.

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

Official Strawberry skill

name: getting-started-as-a-founder-in-strawberry
description: Best practices for founders and executives getting started in Strawberry. Use when helping them choose, set up, or expand useful company, communication, research, and team workflows.

Getting Started as a Founder in Strawberry

Start with one result the founder needs, then turn what works into a process the company can rely on. This is not a fixed sequence. Enter wherever the founder or team has a real bottleneck, skip what already works, and suggest the next workflow only when it solves a real problem.

Find one useful starting result

Keep early discovery light. Ask what result would make the next week easier, such as preparing for today, clearing an overloaded inbox, drafting an investor update, or understanding a market decision. Ask one short question at a time until one result is concrete.

Useful context may include approved calendar, inbox, Slack, Drive or Notion documents, CRM, dashboards, past meeting notes, and accepted examples. Treat these as options, not prerequisites. Offer to learn through questions, relevant approved context, or both. Inspect what is already available before asking the founder to repeat it, then confirm the intended result, important uncertainties, and approach in a concise plan before substantial work.

Prepare for today, then close the loop

A concise morning brief can be a useful first result when attention is the bottleneck. With relevant approved context, surface urgent or unanswered messages, work due today, and the few meetings that need preparation. Keep it actionable and include links back to useful sources.

When one conversation matters most, read strawberry/sales/prepare-for-calls. It turns relevant calendar, company, person, and relationship context into a brief the founder can scan before the meeting.

After the meeting, read strawberry/operations/transcribe-meetings-follow-up to turn the transcript into decisions, action items, owners, filed notes, and a grounded follow-up draft. Keep messages as drafts and obtain approval before sending them or making consequential changes in external systems.

Calibrate around the founder's judgment

Review the first result and let the founder correct its assumptions, depth, format, tone, sources, or tool choices. Preserve accepted preferences instead of restarting from generic instructions.

If that first run reveals a larger communication backlog, read strawberry/operations/reach-inbox-zero. It helps the founder define useful categories, learn reply style from approved examples, surface what deserves attention, and prepare reviewable drafts. Nothing is sent, deleted, archived, unsubscribed, or changed in bulk without explicit approval.

Turn company context into a clear artifact

For an investor, board, or company update, establish which metrics and milestones matter, where they live, who will read the result, and whether an accepted report or deck should set the structure. Read strawberry/research-analysis/create-beautiful-slide-deck when the result should be a polished presentation built from the founder's source material. Keep external delivery subject to the founder's approval.

When the artifact depends on outside research, start with the decision, scope, evidence standard, source types, depth, and desired output. Read strawberry/research-analysis/research-companies-create-decks for a sourced visual brief, or strawberry/marketing/run-competitor-analysis for a broader comparison. Preserve source links and dates, distinguish facts from inference, expose uncertainty or contradictions, and interpret the evidence for the founder's decision.

Other things to try

Offer these as discovery ideas once a core workflow is useful, not as complete standalone instructions:

Model a major decision with options, second-order effects, and a recommendation.
Mine approved product telemetry for patterns and surprises.
Prepare a weekly one-page review of company KPIs with suggested next actions.
Assemble a data-room or diligence-answer pack when a round or deal moves, or a quarter-end memo from win-loss and usage trends.

Grow one accepted process into a team workflow

After one result is accepted, preserve its sources, format, voice, review points, and exceptions as a user-owned skill. If several people need consistent inputs, ownership, destinations, or review behavior, read strawberry/operations/set-up-shared-team-workflow. Start from that accepted individual workflow, make privacy and approval boundaries explicit, and verify one real handoff before scaling it.

Add a Routine only after the underlying workflow has worked a few times and the founder wants it to recur. Do not invite teammates, move personal or confidential context into shared files, or automate consequential actions without explicit approval.

When the work becomes primarily sales, recruiting, product and engineering, operations, marketing, research, or another domain, load that domain's Getting Started skill rather than stretching this guide beyond its purpose.