# AI automation for marketing agencies (/docs/answers/ai-automation-for-marketing-agencies) --- type: Document title: AI automation for marketing agencies description: "How much of a marketing agency's delivery AI can take over: what automates, what stays with the owner, three counted runs, and how to count your own agency." status: stable order: 1 generated: { by: "process:claude-code", at: 2026-08-31T06:30:00Z } verified: - { by: "human:rrizwan98", at: 2026-08-31T07:00:00Z } ksor: audience: [public] owner: human:rrizwan98 approval: { by: "human:rrizwan98", at: 2026-08-31T07:00:00Z } trust_tier: human-reviewed build_id: sha256:29a7cfca69186e9d9939db2ba7c8df2502e12724e0562328fda366616971799f dirty: true --- A marketing agency can hand most of its delivery to AI systems and keep every judgement call with people. Counted honestly, service runs adjacent to agency work land between 64% and 80% of steps: research, first drafts, builds, checks and reporting automate, while pricing, creative direction and the client's yes stay human. The figure for your agency comes from [counting your own run](../method/count-your-own-workflow.md), never from copying someone else's number. ## What automates in an agency, and what does not A step automates when it is repeatable, checkable, reachable and either reversible or gated. Those four conditions are defined on [what automates](../method/what-automates.md); applied to common agency work they sort like this: | Agency work | Usually | Why | | --- | --- | --- | | Intake questions on a new brief | AI | The same questions every time, and a checkable, complete answer set | | Competitor and market research | AI | Defined sources, a written output a person can verify | | First drafts: copy, ads, pages, posts | AI | Produced against the brief, checked at a gate before anything ships | | Building the page or campaign in the tools | AI | Reachable by API or connector, reversible before publish | | QA passes and pre-flight checks | AI | A checklist is the most automatable object in an agency | | Weekly client reporting | AI | Same numbers, same shape, every week | | Pricing and scope | DECISION | Risk and judgement; it stays with the owner | | Creative direction | DECISION | Taste is not a checklist | | The client relationship | DECISION | Trust is built by a person | | Final sign-off before publish | DECISION | The gate that makes the rest safe | ## Three counted runs close to agency work These are from the record's [worked counts](../method/worked-counts.md): illustrations counted with the method, not client engagements. Every percentage is a **could be**, the share a system could own once built. | Run | Could be | What stays human | | --- | --- | --- | | A web-design studio delivering a landing page | 73% | Brief, design direction, sign-off | | An agentic AI service building a client's agent | 73% | Scope, plan approval, go-live | | A recruitment agency screening for one role | 64% | Brief, shortlist, interview, offer | The spread is the honest part. Recruitment counts lower because judging a person is a decision, and pretending otherwise would inflate the number. ## What an AI-native agency looks like One marketing agency runs this way now. How it is built is not published; the shape is. Work enters from the pipeline, AI staff produce at their stations, one person reviews scored deliverables at defined gates, and the work goes back out. The owner's day stops being production and becomes direction: setting standards, judging output, talking to clients. The path from one automated task to that shape is a ladder, not a leap; the rungs are on [from one task to a company](../method/from-one-task-to-a-company.md). ## Count your own agency Four steps, from [count your own workflow](../method/count-your-own-workflow.md): 1. Write one real run down, one line per step, from enquiry to delivered. 2. Tag every step **AI**, **DECISION** or **TYPING**. Count only the steps your side performs; what the client does is not yours to automate. 3. Count two numbers: **today** (AI steps over total) and **could be** (AI plus TYPING over total). 4. Mark the gates where a person must say yes. If steps are missing, the six questions on that page pull them out. When you want the run counted with you, the [workflow audit](../audit/overview.md) does exactly that; [what to bring](../audit/what-to-bring.md) lists the six answers that make it fast. You can also attach this record to ChatGPT, Claude or Codex and ask it to build your step table with you: the addresses are at [razarizwan.com/access.html](https://razarizwan.com/access.html). ## Common questions **Will clients accept AI-produced work?** Clients accept outcomes. The gate structure is the honest answer: nothing ships without a person's sign-off, so what the client receives has been reviewed by the person they trust. **Does this replace my team?** It changes the seats. Production hours shrink; review, direction and client time grow. The counted runs above all keep every judgement call with a person. **What does it cost to build?** This record holds no pricing. The audit ends with your own two numbers and a scoped plan, and that is the right place for the cost conversation, because it depends on your run.