Methodik
·
6 MIN
Where a coding agent earns its keep outside engineering
Claude Code's real value outside engineering is not code. It is letting marketing and ops encode their own procedures.
LOCATION
Worldwide
SERIES
AI Tooling & Dev Harnesses
AUTHOR
Aashwin Shrivastava
PUBLISHED
The most useful thing we do with a coding agent at iiterate has little to do with code.
Claude Code is built for engineers, but the work it has quietly taken over for us sits in marketing and the back office: the repeatable, rule-bound jobs nobody enjoys. The reason it fits there is simple. Someone who knows a procedure, the brand rules, the month-end checklist, the way we tag a campaign export, writes that procedure down once in plain language, and the agent runs it against real files. No software project, no developer in the loop. This piece is what we have learned about where that pays, where it does not, and how to start without regret.
01.
The real shift is not coding. It is writing the procedure down
For a non-developer, a coding agent is a way to turn a repeatable procedure into something a machine executes, without building software first.
The mechanism that makes this work outside engineering is Agent Skills. A skill is a small folder: a plain-language instruction file, optionally a script or two, and the reference material it needs. The agent only sees a skill's name and one-line description until your task needs it, then reads the full instructions on demand. Simon Willison, who documented the format when it shipped in October 2025, put the economy of it plainly: each skill costs only a few dozen tokens until the moment it is used (simonwillison.net, Anthropic).
The consequence is the part that matters for a Mittelstand team:
🔸 The author is a domain expert, not a coder.
The person who knows the process writes the skill, the way they would brief a new hire.
🔸 Connectors give it real reach.
Through MCP, an open connector standard, the agent can read and act in actual systems, a spreadsheet, a shared drive, a ticket queue, under access you grant.
🔸 You decide the blast radius.
It only touches what you let it touch. That permission boundary is the whole game, and we come back to it below.
02.
Three boring jobs where it actually pays
The wins are unglamorous and repeatable. Three patterns have held up for us and in the public record.
Marketing variants at volume. Anthropic's own Growth Marketing team wired two specialised sub-agents to read a CSV of hundreds of live ads, flag the underperformers, and write fresh variants inside strict character limits, minutes of work instead of hours. A companion Figma plugin generates up to 100 layout variations per batch by swapping headlines and descriptions (claude.com). It is their own team, so read it as proof the pattern works, not as your number.
Back-office data tidying. The dull middle of the week: reconciling a card statement into an expense sheet, cleaning a messy list, drafting a recurring report from a template. One solo, non-technical founder on r/SaaS described running effectively his entire SEO operation through Claude, reporting 1.54 million search impressions and 12,900 clicks in three months with no engineer and no agency (r/SaaS). One person's report, but a telling one.
Internal tools built by the person who needs them. Anthropic's legal team prototyped a small "phone tree" that routes a question to the right lawyer, built by a product lawyer who does not write code (claude.com). The interesting part is not the tool. It is who built it, and that they did not file a ticket to do so.
We have written before about where AI actually earns its place in a business rather than where it demos well (iiterate); this is the same test applied to one tool.
03.
Why marketing and ops, specifically
These functions fit because their work is repeatable, rule-bound, and already lives in files.
That maps cleanly onto what a skill can hold. A brand-guidelines skill carries the palette, the type rules, and the tone of voice. A procedure skill carries the close checklist or a compliance step. A template skill carries the document itself. Anthropic ships a working brand-guidelines skill as a public example, with colour, typography, and layout rules an agent applies on request (GitHub, Anthropic).
The recurring finding across these reports is that domain expertise drives the result more than coding skill does. That is the Mittelstand's quiet advantage. The person who knows the process is already in the building, and a skill is just their process, written down.
04.
Where it is the wrong tool
A coding agent is the wrong tool the moment the work stops being repeatable, checkable, or safe to hand a broad-access agent. The honest risks, in the order they bite:
Blast radius. An agent with file and system access can delete the wrong folder or send the wrong message. Give it least privilege: read-only first, one folder, a copy of the data, not the original. Security teams have catalogued what goes wrong when this step is skipped (Docker, Oso).
Confident wrong answers. It will state a figure it did not verify, in fluent prose. Keep a human gate on anything that leaves the building.
Governance and data. The moment it touches personal or client data, GDPR and the EU AI Act apply. Know where the data sits and who can be audited before you connect it, which is the same control question behind running models you own rather than rent (iiterate).
Provenance. Most polished case studies, including two in this article, are vendor-published. Read them as evidence the work is possible, not as evidence of your return.
05.
How to start without regret
Start small, on work you can afford to get wrong.
Pick one task that is repeatable and rule-bound, and that is not your most important process.
Write the procedure as a plain-language skill, the way you would brief a capable new hire on their first day.
Give least-privilege access: read-only, one folder, a copy of the data.
Keep a human gate on anything that goes out the door or touches a person's data.
Measure on the boring metric, hours saved on the dull task, not on how the demo felt.
Done this way, the wins are small and they compound, which is the opposite of how this technology is usually sold. The question worth sitting with is not whether a coding agent can do marketing or ops work. It is which of your procedures you have actually written down, because that, not the model, is what decides how far this goes.
