Use cases
AI employee for marketing ops
Tobiloba Odejinmi · 9 Jan 2026 · 6 min · 1,153 words
Direct answer
A marketing ops employee researches a topic, drafts the piece, and keeps the calendar from going quiet. Good looks like a brief and a draft a human can edit in one pass. Escalate claims, legal, pricing, and anything with a customer name. Do not automate publish or paid spend first. Measure shipped work and edit time, not word count.
- The job is the ops pile: briefs, drafts, and a calendar that does not die.
- A person still owns claims, legal copy, and the publish button.
- Do not start with ads spend or a full site rewrite.
- Measure pieces shipped and minutes to edit, not “content generated”.
What is marketing ops work, really?
It is the work around the work. The brief that never got written. The calendar that went quiet. The same product page rewritten from memory. The asset list for a webinar. People call this content. A lot of it is filing and first drafts.
An AI employee here should take a topic you already decided to ship, pull the sources you point it at, and return a draft in the shape you already use. Then it should put that draft in the CMS or the doc the editor already opens. If it lives in a chat window, it will die there.
Anthropic’s 2026 survey had 57% of agent work as multi-stage and 60% in reporting. Marketing ops is multi-stage: brief, research, draft, file. Treat it as a workflow, not a magic writer. The writer is one step.
What does a good marketing ops employee look like?
Good looks like a brief with sources and a draft that an editor can fix in one sitting. The facts are cited. The banned phrases are absent. The title is a title, not a slogan. The file is in the right folder with the right status.
It also looks like a calendar that does not go empty because someone was on the road. A reminder is not glamorous. Empty weeks are how sites go quiet, then someone declares a “content reset”. I would rather have a boring Thursday post than a reset.
Keep the voice short. I write the way I talk in a review. If the draft sounds like a press release, it failed. Give the employee three live examples and a list of words I will not print. That list includes the usual slop. You already know them.
- Brief and sources stored with the draft
- Draft in the CMS or doc the team already uses
- Status the editor can see without asking
- No publish without a person
What should escalate?
Anything with a number you have not published. Anything with a customer name. Anything that sounds like a medical, legal, or financial claim. Anything that needs a partner to sign off. The employee can draft the paragraph. A person sends it.
Escalation is a state handoff. The editor gets the draft, the sources, and the reason it stopped. “Needs legal” is a reason. “Mentions 10mg loan volume” is a reason until someone checks the last approved figure. We have $3.4 million out and more than 6,000 providers. I still want a person on that sentence when it leaves this site.
Do not escalate “the tone feels off” as a queue. That is editing. If you make legal the tone police, they will become a bottleneck and then people will go around them.
What should you not automate first?
Do not automate the publish button. Do not automate paid spend. Do not let it spin up ten site pages from a sitemap and call it a launch. Those mistakes are public and expensive.
Do not start with a full blog rewrite. Start with one recurring format: a weekly note, a changelog, a product FAQ. If you cannot name the format, you are asking for a writer-shaped toy.
Skip personalisation theatre. “Dynamic copy for every segment” is how you get twelve wrong versions and no owner. One true draft, then a person decides if a second version is worth it.
How do you measure publishing and ops work?
Slots filled on the calendar you already had. Time from brief to draft. Edit minutes to ship. Factual corrections after publish. Those numbers tell you if the week got lighter. “Words generated” tells you nothing.
If edit time does not fall, the drafts are not good enough. Do not add more volume. Fix the brief and the examples. I have watched teams drown editors in first drafts and then say AI did not work. AI produced volume. The process produced a second pile.
Once a month, pick three shipped pieces and ask: would we still stand behind this if a customer forwarded it to their lawyer. If the answer is no, the gate is too loose.
How do you keep this from becoming another tab?
Plug it into the CMS, the calendar, and the drive you already have. The same rule as Zeeh: if another team cannot use it before lunch, you still have work to do. Marketing tools love new logins. New logins are how this becomes a graveyard.
Name an owner. Someone who can say why a draft is still sitting. If the owner is “the AI”, you will find out on the week the calendar is empty and nobody knows who to ping.
I sold Shopl after Techstars. The work that survived diligence was the boring systems, not the pitch. A marketing employee is the same. Logs, sources, a person on publish. If that is in place, the drafts can be fast. If it is not, speed is just a way to be wrong in public.
Questions people ask
What should a marketing ops AI employee do?
Take a brief, pull the sources you already trust, draft the piece in your shape, and file it where the team already edits. It can also remind you that Thursday is empty. It should not publish, spend, or invent a case study.
Can it write in our voice?
It can follow a short list of rules. Short sentences. No banned words. Same structure as the last three posts. A 40-page brand book will not save a draft that has no facts. Give it examples, not a manifesto.
What has to stay with a person?
Customer names, numbers you have not published, legal claims, medical claims, and the publish click. Also anything that quotes a partner. If you cannot point to a source, it stays in draft.
Will this replace the writer?
It replaces the empty week and the first pass. Someone still has to decide if the piece is true and worth shipping. If you fire the editor, you will publish junk and then blame the model.
How do we measure it?
Calendar slots filled. Time from brief to first draft. Minutes a person spends to make it shippable. Pieces that go live without a factual correction in a week. Word count is not a metric. It is a temptation.
Written by
Tobiloba Odejinmi
Head of Engineering at 10mg Health. I have run engineering at Zeeh Africa and sold Insurpass and Shopl. I still write the code. If you have one process that still runs on people copying things, we can look at it in thirty minutes.
