Share the context
At onboarding, share your brand documents, visual style, tone of voice, audience, offers and examples of good work. We organize them into the agent’s working context.
Client deadlines keep pushing your own marketing back. Give your AI specialist the business and brand context upfront. It prepares the recurring work; your team guides and approves.
Set up and maintained by Octocrew. Priorities and approvals stay with your team.
Illustrative Slack demo · choose a task
Before adding another marketing channel, check three things: a clear audience, a useful offer and someone to review the work.
01 / Before the work begins
Before the first task, we give your specialist a working understanding of your business: what you sell, who you serve, how your brand speaks and what success looks like. That context carries into the ongoing work.
At onboarding, share your brand documents, visual style, tone of voice, audience, offers and examples of good work. We organize them into the agent’s working context.
We connect the tools your role needs through supported APIs: ad accounts, analytics, email or CMS. Together, we set access, budget limits and approval rules.
The agent prepares the work; you approve or leave corrections. Your feedback refines its working instructions and brand context for the next tasks. Update the context as your business changes.
02 / The recurring work
Once your agent has the context, it can take on the recurring work in its role. You review the output and guide what happens next.
Turns your knowledge base and approved client material into a regular content pipeline.
Article drafts, case outlines and page updates grounded in your expertise.
Repurposes your articles, expertise and approved stories into consistent social content.
Channel-ready posts and a publishing calendar for your agency.
Builds recurring newsletters from your latest insights, services and approved content.
Newsletter previews with links, audience and send timing checked.
Updates agreed pages in your connected CMS as positioning, services and case material evolve.
Service and case page previews with a record of checked changes.
Reviews your agency’s connected ad accounts and prepares the next campaign improvements within your goals and limits.
Campaign reviews, ad drafts and proposed adjustments for approval.
03 / See the handoff
Illustrative example, not a client result. The first workflow is agreed around your tools and review process.
Use the agency’s existing article about a client problem. Keep client names and claims within the permissions you have.
A practical checklist, one misconception and a short expert take. Review each post’s copy, source link and proposed date.
Your operator checks facts, tone and client permissions. Corrections return to the draft before publishing.
Publish in the agreed channels. Review the results to decide what the next batch should change.
This Social Media example starts with an existing article. Writing the article or an email campaign is a separate role scope.
04 / Client work
Marketing agency · 18 people
The published case describes the agency’s own content, social, ads, email and reporting running with part-time oversight. People keep positioning, brand decisions and final sign-off.
This is evidence of an operating setup for own marketing. The case’s time-saving figure is an estimate; its method and measurement period are not published. It does not establish a multi-client delivery offer.
Read the agency caseThese cases describe individual crew implementations. Today’s five standard roles have their own agreed scope; historical crew configurations are not a standard bundle.
A separate conversation
Describe one client workflow, who operates it and who approves the output. We confirm access, context separation, the number of environments, support responsibility and commercial scope before proposing a setup.
Multi-client access, white label and reseller arrangements are not automatically included in a standard subscription. A fractional CMO can direct the work; the delivery model still needs to be agreed.
Discuss a client workflowStart with one useful task and its specialist. Add another role when there is a clear need, a working operator and an agreed scope.
Your business context, brand documents, visual style, tone of voice and the tools your role needs. During onboarding, we connect supported APIs and agree permissions, priorities and who approves the work.
Your team owns priorities and approvals. Any automatic action needs explicit permission and agreed limits; it is not the default for every workflow.
We assess the specific environment, operator, client permissions and approval path first. Multi-client, white-label and partner arrangements need an explicitly agreed scope.
Standard implementation, onboarding and maintenance are included. Third-party platforms, media spend and model usage are separate. See current pricing for the role you choose.
We'll clarify the role, operator, tools, permissions, and first scenarios. If a standard role fits, we price it clearly; if not, we'll say so.