The useful way to decide what to delegate to AI is to map your content function to the roles you’d hire if you had budget, then work out which of those roles a machine can actually hold. Drafts, research scaffolding, repurposing and first-pass QA go to the machine. Strategy, final judgment, relationships and voice stay with me, permanently.
Adoption is no longer the interesting question. In the Work AI Institute’s 2026 index, 94% of marketers said they used AI at work while only 70% said it made them more productive, a gap that says most teams bolted AI onto existing workflows without deciding what it was for. Gartner’s 2026 CMO survey shows the same shape from the budget side: 15.3% of marketing budgets going to AI, with only 30% describing their AI capabilities as mature.
I’ve run content functions solo at a few companies, and the reframe that made AI genuinely useful was to stop thinking in tasks and start thinking in roles. A content function needs a researcher, a writer, an editor, an SEO analyst, a repurposer, a designer, a strategist and somebody who talks to people. I’ve been all eight. What you delegate to AI is better decided by asking which of those chairs a machine can sit in without the output getting worse.
Task-level automation gets you a faster version of whatever you were already doing. Role-level delegation makes you name what the role was for in the first place, which is usually where the surprise is.
How do you decide what to delegate to AI?
Three tests, applied per role and not per task, in this order. Most published advice sorts work into automate, assist and keep human, which is a fine starting point; these tests are how I decide which tier a role belongs in.
- Is the work reversible? A bad draft costs an hour. A bad positioning decision costs a quarter and nobody notices for two months. Reversibility is the strongest single predictor of whether delegation is safe, and it’s why the levels-of-control model emerging in martech puts autonomous operation only where objectives are clear, volume is high and stakes are low.
- Is there a checkable output? If I can verify the result against an external reference (a source, a style guide, a spec), delegation works. Where verification needs the same judgment that would have produced the work, I’ve saved nothing and added a review step.
- Does the work require knowing people? Anything depending on what a specific salesperson is struggling with this week, or what the CEO actually meant in that meeting, has an input a model can’t access and can’t infer. Content and copywriting carry the highest automation exposure of any marketing work at around 60%, and this test is what separates the 60% from the rest.
The delegation map
| Role | Who holds it | Why | What goes wrong if you get it backwards |
|---|---|---|---|
| Researcher | AI, with verification | Fast at gathering and structuring; unreliable on accuracy. | Fabricated sources, real-looking citations that lead nowhere. |
| First-draft writer | AI, from my brief and standards | Reversible, checkable, and the blank page is the expensive part. | Publishable-sounding prose with no argument in it. |
| Editor | Me | Editing is judgment about what the piece is for, not grammar. | Copy that passes every check and says nothing anyone needed. |
| SEO and AEO analyst | Split | Data pulls and clustering to AI, the calls on what to target to me. | Keyword lists that satisfy a tool and match no demand anybody has. |
| Repurposer | AI, from the research | High volume, low stakes, rules-based once the source is solid. | Compressed paragraphs posing as native posts, and everyone can tell. |
| First-pass QA | AI, then me | Mechanical checks scale beautifully. | Green checklists on thin content, which is the classic AEO failure. |
| Designer | Split | Templates and variations to AI, the system itself to me. | A feed that looks assembled, never designed. |
| Strategist | Me, permanently | Depends on business context, politics and trade-offs a model can’t see. | A plan that reads well and can’t settle a single argument. |
| Relationship owner | Me, permanently | Sales calls, stakeholder pushback, customer interviews. | The input that makes everything else good disappears. |
| Final judgment | Me, permanently | Accountability doesn’t delegate. | Nobody owns the claim when it turns out to be wrong. |
The four permanent columns are the point of the map. Everything else is negotiable as the tools improve, and those four aren’t, because they’re not capability problems.
What I hand over, specifically
Research scaffolding. Gathering sources, structuring what’s out there, pulling comparable data points. Every figure then gets verified against the original before it reaches a draft, without exception, since one fabricated statistic costs the credibility of the whole piece.
First drafts, from a proper brief. The brief carries the argument, the audience, the claim, the sources and the standards. What comes back is raw material I then rewrite substantially. The value is skipping the blank page, and I’ve written about where this helps and where it fails in the breakdown after a year of daily AI use.
Repurposing from the research, never from the finished prose. Derivatives generated from a published article arrive as compressed paragraphs with the transitions removed. Generated from the research, with the target format’s constraints stated, they come back closer to native.
First-pass QA. Banned vocabulary, punctuation, keyword density, link counts, heading structure, paragraph length.
Structured data work, meaning schema, metadata, formatting and tagging. Rules-based, verifiable, boring, and the clearest case in the whole map for what to delegate to AI: HubSpot’s rule of thumb is that work following strict if-then logic belongs with an agent.
What I’d never hand over
Strategy. A model will produce a very plausible content strategy, which is exactly the trap. A strategy is a decision record built on inputs it can’t see: what sales said last week, which stakeholder will block this, what the company committed to externally, which persona sits closest to a buying decision right now. Without those you get a description of a content programme instead of a plan for one, and the prioritisation calls behind it are the ones in my Content Prioritisation Framework.
Final judgment on anything published. Somebody accountable has to read the piece and decide it’s worth publishing. That’s not a workflow step you can automate away, and when it does get automated nothing looks wrong until a claim gets checked.
Relationships. Customer interviews, sales calls, the conversation where a stakeholder tells you what they actually meant. This is the highest-value input into all the work above it, and it’s the one nobody thinks to protect, because it doesn’t produce a deliverable.
Voice, and not as a style rule, which a model can follow perfectly well. I mean the accumulated set of positions I’m willing to defend. A voice is what you think, so delegating it produces the category consensus in a confident tone, which is the specific quality that makes so much published content interchangeable. The commercial argument for why that matters is in writing quality as a competitive moat.
How do you make AI compound instead of creating cleanup?
By investing in the inputs and not the outputs, which is the difference between a function that gets faster over time and one that generates a permanent editing queue. Most of the compounding comes from three practices.
- Documented standards, written once, reused every time. Brand voice rules, editorial standards, the banned list, the structural spec. Each is a reusable input that raises the floor on everything you delegate to AI afterwards, and building them was worth doing before AI existed. I wrote about producing them from nothing in editorial standards from zero.
- Briefs that carry the judgment. The quality of what comes back is set almost entirely by what goes in: the specific claim, the named sources, the audience, the position. This is the whole discipline of context engineering, and it’s where the skill has moved.
- Verification as a fixed step, not a vibe. Every claim traced to documentation, data or a named person before publish.
The pattern that breaks is the opposite of all three: no standards, thin prompts, no verification, then a permanent cleanup queue eating the time the tools were supposed to save.
Where this breaks down
I get more out of these tools than most teams I’ve worked with, and I still spend a large share of my time rewriting what they produce. The draft is a starting point and not a deliverable, and anyone claiming otherwise is publishing worse content than they think.
The map above is a snapshot. Which roles you can delegate to AI will keep changing, and I’d expect the editor row to come under pressure next. The four permanent ones won’t change, because they’re not capability questions: strategy needs context that lives in conversations, relationships need a person, and accountability needs somebody who can be wrong in public.
The last point is uncomfortable for a solo operator. AI does give you a team you never got budget for, and that’s exactly the argument a company will use for not hiring the second marketer. The counter-argument is that the bar for published content has risen rather than fallen, which I’ve argued in why the bar went up in the AI era, and volume without judgment is now the cheapest thing in the market.
Frequently asked questions
Work that’s reversible, has a checkable output, and doesn’t depend on knowing specific people is safe to delegate to AI: research gathering and structuring, first drafts written from a detailed brief, repurposing built from the underlying research, mechanical QA against a documented standard, and structured data work like schema and metadata. Each of those can be verified against something external, which is what makes delegation safe. Anything where verifying the result requires the same judgment that would have produced it isn’t worth delegating, since the review step costs what the work would have.
Strategy, final judgment on published work, relationships, and voice. Strategy depends on inputs a model can’t access, including what sales reported this week and which stakeholder will block a decision. Final judgment is accountability, and accountability can’t be delegated to a system that can’t be held responsible. Relationships produce the raw material everything else is made from, and voice is the set of positions you’re willing to defend, not a style setting.
Invest in the inputs. Documented editorial standards, briefs carrying the specific claim and named sources, and verification as a fixed publishing step are what make AI output usable on the first pass instead of the third. Teams that skip these get plausible-sounding drafts requiring full rewrites, which is what sits behind the gap between the 94% of marketers using AI and the 70% reporting it makes them more productive.
