| name | getting-started-with-agency-work-in-strawberry |
| description | Help an agency get started in Strawberry by adding client separation, briefing, delivery, reporting, and approval boundaries to the functional workflows its team already uses. |
Getting Started with Agency Work in Strawberry
Agency is an organization overlay, not a second copy of Marketing, Sales, Operations, Design, or
Research. Help the user complete one useful client or agency result, then route the specialist work
to the functional bundle they selected.
Start with one account and one result
Identify the client or prospect, service, desired result, owner, destination, deadline, approved
sources, and review boundary. Use examples the agency won or the client accepted when they help
calibrate the work.
Keep every client's accounts, source material, calculations, conclusions, and output separate. Do
not use one client as an unstated example, benchmark, or source for another. Start with one account
before applying a method across the book.
Establish the client boundary
Use strawberry/consulting/build-client-brief once work is accepted. The brief owns the client's goals,
measures, voice, stakeholders, source access, restrictions, delivery expectations, and approval
points.
The brief adds client context; it does not replace the functional skill that produces the result.
Route to the selected function
- Win clients: use
strawberry/sales/find-new-customers,
strawberry/sales/research-an-account, and
strawberry/sales/send-personalized-outreach as the work progresses.
- Deliver Marketing work: use the Marketing Getting Started guide and its focused audience,
campaign, content, competitor, SEO, and performance skills when Marketing is the selected role.
- Report progress: use
strawberry/operations/build-client-progress-report-project-tools to reconcile one client's
project, analytics, advertising, and communication evidence into a reviewable report.
- Prepare and follow through on client meetings: use
strawberry/operations/prepare-for-meetings and
strawberry/operations/debrief-a-meeting.
- Research or present: use the focused Research and presentation skill that owns the evidence
or artifact.
The organization context may change confidentiality, account matching, voice, delivery, and review.
It does not create a duplicate functional workflow.
Deliver, learn, and reuse
Review one complete client-ready result before scaling it. Keep source links, definitions,
assumptions, recommendations, unresolved gaps, and the intended audience clear.
After the method works, preserve the accepted client brief, functional workflow, owners,
destinations, and approval behavior. Use strawberry/operations/set-up-shared-team-workflow when
the agency needs a shared method. Add a Routine only when the trigger or cadence, account boundary,
inputs, destination, owner, review behavior, and stop conditions are explicit.
Follow Strawberry's active scoped permission for the action, client account, destination, and
conditions. Draft or ask when permission is insufficient. Stop when identity, account, scope,
impact, or sensitive-data handling changes, and verify completed external actions. A client brief,
deliverable, report, message, live account change, spend change, and public publication are
different permission states.
