Insight / signal

Agentic loops are ops, not magic

You do not have an operating system. You have a slot machine with better grammar.

Everyone wants an AI agent at the moment.

Fair enough. The promise is attractive: less admin, faster delivery, cheaper experimentation, fewer people stuck doing soul-sapping repetitive work. I get it. I run agents every day. Some are genuinely useful. Some need watching like a toddler with a nail gun.

The problem is the word “agent” has become too big. It now means everything from a glorified prompt to a workflow that can investigate a production bug, change code, run checks, and report back with a proposed fix.

Those are not the same thing.

The useful idea underneath the hype is much simpler: the loop.

A human gives the system a goal. The agent does a bounded piece of work. It reviews or scores the result. It feeds that back into the next step. A human stays close enough to steer, approve, reject, or stop the thing before it wastes money or breaks something.

That is an agentic loop.

Not magic. Ops.


The last couple of days have been a decent signal for this. OpenAI published fresh Codex case studies with Notion and Nextdoor. Notion used it to one-shot specs and ship AI Voice Input to the web. Nextdoor used it for hard-to-reproduce engineering issues — the kind of debugging work that can swallow days.

There is the obvious caveat: these are vendor case studies. They are meant to make the product look good. Fine. Read them with one eyebrow up.

But the pattern is still useful.

The value is not “we bought an AI tool”. The value is “we changed the shape of work so the tool can do something specific, repeatable, and checkable”.

That matches what the stronger AI-native org thinking shows too. It is not people replaced by bots. It is people, agents, and context. People bring judgement, taste, trust, and commercial intent. Agents run the repeatable execution. Context acts as the shared brain so the system is not starting from zero every five minutes.


Wide-open loops are dangerous and expensive. They make assumptions. They burn tokens. They wander off.

The useful loops are narrower: code review, SEO checks, proposal generation, customer feedback synthesis, QA, reporting, research scans.

Boring work, basically.

That is where the money is.

A business owner does not need a sci-fi agent that “runs the company”. That is mostly theatre. They need five or six controlled loops that remove drag from the work they already do every week.

A sales loop that turns a discovery call into a draft proposal, then checks it against the client’s goals and the company’s offer rules.

A content loop that pulls from real source notes, drafts a piece, checks for banned claims and beige LinkedIn nonsense, then hands it to a human with taste.

A support loop that spots repeated customer questions and turns them into website updates, onboarding fixes, or sales objections.

A QA loop that checks a landing page before it goes live: broken links, vague copy, missing proof, weak CTA, tracking problems.

None of this requires pretending the agent is a member of staff. In fact, that metaphor can make things worse. Staff have judgement, accountability, memory of politics, awareness of risk, and the ability to ask awkward questions in a meeting. Agents have none of that by default.

What they can do is execute a well-defined loop faster than a human wants to.


The catch is that someone has to design the loop.

That means deciding what the job is. Not “improve marketing”. More like: “read these five client inputs, produce a one-page campaign brief, check it against this offer, flag missing proof, and stop before sending anything externally”.

It means giving the system real context. Past work. Client notes. Brand rules. Offer boundaries. Examples of good and bad. The awkward bits humans usually keep in their heads.

It means defining what good looks like. This is the bit most teams skip because it feels slower than typing a prompt. But without it, the agent is guessing. You do not have an operating system. You have a slot machine with better grammar.

And it means keeping humans in the places where humans still matter: judgement, trust, taste, ethics, commercial calls, final approval.


This is where I think the agency conversation gets interesting.

If your agency model is still built around producing more assets, AI is a threat. More drafts are cheap now. More mediocre posts, emails, decks, landing pages, and reports are not a premium service. They are landfill with a nicer font.

The better model is the operating layer.

Instead of selling “we will write your campaign”, you build the campaign loop: research, positioning, message testing, asset creation, QA, publishing, follow-up, measurement, learning, next iteration.

The deliverable is not just the output. It is the system that makes better output easier next time.

That matters because most companies are not short of AI tools. They are short of reliable work design. They have ChatGPT, Copilot, Claude, Gemini, Perplexity, automation tools, half-built zaps, three people experimenting in separate tabs, and no shared definition of what good looks like.

So they get speed without control.

That is a bad trade.

The real advantage is not having the newest model for two weeks before everyone else. That window closes fast. The advantage is knowing where to put the model inside the business so it compounds rather than creates more mess.


A decent AI loop should pass a few basic tests:

Is the task narrow enough that the agent can finish it without inventing half the brief? Does it have the context it needs? Can we score the result? Is there a human approval point before anything risky happens? Do we know what this costs to run? If it fails, does it fail safely?

If the answer is no, do not call it an agentic workflow. Call it an experiment.

Experiments are fine. Just label them properly.


For business owners, the practical next step is not to build a giant AI transformation plan. Pick one repeated workflow this week. Something annoying, frequent, and valuable enough to matter.

A proposal.

A client report.

A landing page QA check.

A sales follow-up.

A weekly customer insight scan.

Map the human version. Write down the inputs, the decisions, the checks, and the final approval. Then build the smallest loop that helps with one part of it.

Not the whole company. One loop.

That is the bit the hype misses. AI adoption is not a motivational poster. It is plumbing. It is small systems, connected properly, with humans still in charge where judgement matters.

The companies that understand that will quietly get faster.

The ones chasing autonomous magic will get bigger bills and weirder mistakes.