Agency work becomes expensive when every proposal, kickoff, deliverable, and report starts from scattered context. Strawberry can gather the slow raw material and preserve the agency’s judgment, voice, and approval points.

Start with one result the agency already needs, review it with the user, and keep the accepted process. This is a flexible path through common agency work, not a fixed operating model.

Start with one result the agency can review

Choose a current prospect, client deliverable, report, or meeting. Learn through a few questions, relevant connected apps, or both. Useful examples may include winning pitches, accepted reports, scopes of work, and prior communication, but none is required.

Confirm the client or prospect, desired result, owner, destination, presentation style, and approval boundaries. Keep every client’s context separate, then show the intended approach before substantial work begins.

Win the right clients before scaling acquisition

Strawberry can turn the agency’s fit criteria into a small, reviewable prospect list, explain why each company fits, and prepare outreach in the agency’s accepted voice. A concrete finding about the prospect is usually more useful than a generic capabilities pitch.

Calibrate one prospect or a small sample before expanding the search. Nothing client-facing is sent without explicit approval.

Find my agency 30 new clients

Build and calibrate a reviewable shortlist of prospective clients.

I want to find 30 new clients for my agency.

Send personalized client outreach

Draft reviewable outreach grounded in verified relevance and agency voice.

Help me reach out to these prospective or existing clients in our accepted voice. Use the context we already have, show me a useful first set, and get approval before sending.

Turn client context into strong work

Once a client begins working with the agency, preserve the approved goals, measures, voice, constraints, and source material in a reliable brief.

Use that context to research competitors, audit a website, or create another client-ready artifact. Review one complete deliverable before repeating the process.

Turn client context into a clear brief

Turn approved kickoff context into a reliable client brief.

I want to turn our kickoff documents, scope, emails, and discovery notes into a clear client brief.

Run a competitor analysis

Build a sourced competitor analysis for a client decision.

Audit a client’s SEO and create a beautiful report

Turn an SEO review into a clear, client-ready report.

I want to audit a client’s SEO and create a beautiful, actionable report.

Connect reporting, meetings, and follow-up

Prove the reporting flow with one account. Agree on the cadence, comparison period, destination, and level of detail before reusing it across clients.

Prepare client calls from current account context, then preserve decisions, owners, and follow-up from what was actually said.

Build a client progress report from your project tools

Build a clear account of progress, attention points, and unresolved blockers.

Prepare for Calls

Prepare a concise brief for the client conversations that matter.

Transcribe Meetings and Follow Up

Capture decisions and draft reviewable follow-up after the call.

Make the accepted process repeatable

When a first run works, preserve its accepted inputs, sources, style, review points, and client restrictions as an agency-owned skill. Reuse the method only after loading the next client’s own context.

Bring the process to the team by agreeing on owners, destinations, conventions, and approvals. Add a Routine only after repeated review has made the underlying workflow trustworthy.

Make a client workflow reusable across my team

Turn a trusted individual workflow into a shared agency process.

I want to turn an accepted client workflow into a clear shared process for my team.

Official Strawberry skill

name: getting-started-with-agency-work-in-strawberry
description: Best practices for anyone getting started with agency work in Strawberry. Use when helping an agency choose, set up, or expand client acquisition, delivery, reporting, or team workflows.

Getting Started with Agency Work in Strawberry

Strawberry can help an agency win clients, turn scattered account context into useful work, and make delivery and reporting easier to repeat. This is not a fixed methodology. Enter wherever the user or team has a real bottleneck, interview them candidly until the best starting point is clear, and skip what already works. Over time, help the agency adopt the workflows here that genuinely suit how it wins and serves clients.

Start with one useful result

Choose one task the agency already needs: a prospect workup, one client deliverable, one report, or preparation for a client call. Ask whether the user wants to answer a few short questions, let Strawberry look through relevant connected apps, or combine both. Useful context may include the agency website, onboarding documents, scopes of work, winning pitches, prior reports, sent emails, and connected client systems; do not assume that any particular source exists. When available, examples of work the agency won or the client accepted are useful calibration for structure, voice, and what good looks like.

Learn the service, client or prospect, current deliverable, owner, destination, presentation style, and approval boundaries relevant to that result. Keep every client's context strictly separated. Before substantial work, summarize the understood context, open uncertainties, and intended approach in a concise plan, then wait for confirmation or adjustment.

Win one client before scaling acquisition

Before researching widely, name the prospect or fit criteria, the service being pitched, what a strong angle looks like, and the desired output. Start with one prospect or a small sample so the user can check the bar. Strawberry can then find prospective clients, explain why they fit, and prepare personalized outreach. Read strawberry/sales/find-new-customers to build the reviewable shortlist and strawberry/sales/send-personalized-outreach to draft messages in the agency's accepted voice.

A concrete finding backed by current evidence is often more useful than a generic capabilities pitch. For a visual account teardown, read strawberry/research-analysis/research-companies-create-decks. Nothing client-facing is sent without the user's explicit approval. Once a client begins working with the agency, read strawberry/agency/build-client-brief to turn approved kickoff context into a reliable brief covering the account's goals, measures, voice, and data restrictions.

Produce client-ready work

Ask which deliverable consumes the most time and what a good version looks like. Confirm the decision it supports, scope and depth, and expected artifact before starting. Strawberry can gather the slow raw material, preserve source evidence, distinguish findings from recommendations, and shape the result in the client's agreed format. Read strawberry/marketing/run-competitor-analysis for competitor work or strawberry/marketing/audit-seo-create-report for an SEO review. Review one complete, client-ready deliverable before repeating the process.

Prove the reporting flow with one account

Agree what the client's report includes, its cadence, comparison period, destination, and level of detail. Build one client's report first so the user can check the format and metrics before reusing the flow. Read strawberry/operations/build-client-progress-report-project-tools to turn approved project information into a clear account of what changed, why, what needs attention next, and any unresolved blockers. Preserve source links, and reconcile currencies, date ranges, and metric definitions before comparing platforms or accounts.

Keep meetings and delivery connected

Strawberry can prepare concise client-call briefs, capture decisions and owners during meetings, and turn action items into owned work afterwards. Read strawberry/sales/prepare-for-calls to bring together relevant client results, account changes, relationship history, open items, and useful questions before a meeting. Afterwards, read strawberry/operations/transcribe-meetings-follow-up to capture decisions, action items, and owners, then draft a follow-up that reflects what was actually said. Nothing is sent without the user's explicit approval.

Other things to try

These are useful discovery ideas, not complete standalone workflows:

Prepare a campaign-status brief before each client check-in.
Build a QBR or strategy deck from the quarter's approved account data.
Create a cross-account roll-up that flags overspend, sudden drops, or quiet accounts for review.
Make accepted proposals, decks, reports, and transcripts searchable as the agency's knowledge base.

Grow the accepted process into a team system

When a first run works, preserve its accepted inputs, fields, sources, style, review points, and client restrictions as a user-owned skill. Reuse the method with another client only after loading that client's own context. When the workflow should become a team process, read strawberry/operations/set-up-shared-team-workflow to agree on owners, destinations, conventions, and approvals. After the team trusts the underlying workflow through repeated review, suggest a Routine for preparation rather than premature automation: for example, prepare monthly report drafts, morning client-call briefs, or competitor and account-change alerts. Routines must preserve client separation and every approval boundary; they do not authorize external communication or live account changes.