Agency campaign factory

Use Slab5 to help agencies run repeatable campaign work across multiple clients while keeping each client workspace isolated.

Use case

An agency launches monthly campaigns for multiple SaaS clients. Each campaign needs CRM context, a launch checklist, CMS drafts, social posts, assets, approval gates, and campaign reporting. The agency wants repeatability without losing client-specific governance.

Prompt

Create a customer expansion campaign for the Atlas client workspace. Pull CRM context for target accounts, create campaign tasks, draft a landing page and three social posts, register creative assets, pause for client approval, and prepare a campaign reporting dashboard.

Flow

1. Select the client workspace.
2. search_companies and search_contacts identify target accounts and stakeholders.
3. create_marketing_campaign creates the campaign record.
4. create_task creates production, review, and launch tasks.
5. create_entry drafts the landing page or blog post.
6. create_marketing_post creates channel-specific social drafts.
7. create_asset_upload_intent registers image, video, or attachment assets.
8. AgentGrid workflow synthesizes campaign copy and launch plan.
9. Approval gate pauses for client review.
10. create_bi_dashboard or create_bi_report prepares reporting structure.

Agency value

This pattern lets an agency productize delivery:

• One template can be reused across many clients.
• Each client has isolated records, tools, approvals, and audit history.
• Review gates reduce accidental publishing or client-facing mistakes.
• Campaign work produces durable CRM, CMS, task, asset, and BI records.
• Account managers can inspect run history instead of asking where work stands.

Controls

Use one workspace per client. Give the campaign agent:

crm:read
tasks:write
cms:write
assets:write
bi:write
activity:write
agentgrid:write

Do not give agents cross-client access. Keep publishing actions behind approval gates until the client has reviewed the draft and decision reason.