Back to articles

Essay, AI & Systems

AI belongs inside the work

A team of a few people shipped like a full department. The difference was not talent, it was where the AI lived.

An email agent I built turned raw content into a finished, on-brand, mobile-responsive email in about two minutes, no design step and no code. That is what it looks like when AI lives inside the work instead of beside it. Most teams keep it beside the work, a tab they open to brainstorm before rebuilding everything by hand, which saves a few minutes and changes nothing. Inside the work is different. The agent becomes a step in the production process itself, and a small team starts shipping far more than its size suggests. I built the systems that did exactly that, the email agent, an agentic design setup in Figma, and a content engine that published at real scale. This is what it means, and why it changes what a team of your size can make.

What does it mean for AI to be inside the work?

Beside the work is opening ChatGPT in another window to draft an idea, then rebuilding it by hand in your real tools. Inside the work is different. The agent is a step in the pipeline. It takes an input the team already produces and returns something finished and on brand, ready to ship. The test is simple. Did the AI save someone a few minutes, or did it change what the team is capable of producing at all. Only the second one is worth building.

What does an AI production system actually look like?

Ours had a few agents, each aimed at a real bottleneck. The email agent took the content and the links and returned a complete, mobile-responsive, on-brand email in about two minutes, with no coding and no design step. The person added the tracking, pasted it into the platform, and tested. The design side ran through the systems that keep creative from falling apart, with Figma wired to Claude Code so a designer could dictate direction, have the agent build inside Figma, and shape it until it was right. That one setup turned a content editor into someone who could produce full campaign visuals on their own. And a content engine paired the same approach with our brand and production systems so we could publish resources and pages at a scale that fed brand as a growth channel.

The agent is a step in the pipeline, not a tab you open on the side.
BESIDE THE WORK a novelty next to the process –A separate tab you open –You copy work in and out –On brand only if you make it Outcome: a few minutes saved INSIDE THE WORK a step inside the process ✓A step in the pipeline ✓It returns finished work ✓The brand is built in Outcome: the team’s ceiling rises vs
Two ways to use AI. Beside the work it is a detour you copy in and out of by hand. Inside the work the agent is a step in the pipeline, and that is the difference between saving minutes and changing what the team can make.

Why does this let a small team outproduce a big one?

Because the system carries the part that used to require a specialist. A person who could not design before can now ship on-brand visuals. Work that took a department takes a few people. And the bar does not drop, because the brand is built into the agent rather than left to whoever is using it. That is the difference between a team using AI and an AI production system. One makes individuals a little faster. The other changes the ceiling on what the whole team can make.

How do you build AI into the work without losing the brand?

Encode the brand into the system, not the person. The agent should already know the standards, the components, and the voice, so what it hands back is on brand by default, and you can see the result in the outcomes you can actually measure. Keep a human in the loop to shape and approve, never to redo. And build every agent around a task the team already does, so it slots into the pipeline instead of adding one more thing to manage. Done right, AI does not replace the craft. It removes the parts that never needed a human and gives that time back to the ones that do.

AI beside the work is a demo. AI inside the work is leverage. The teams that learn the difference will ship like they are twice their size, because in every way that matters, they are.

Frequently asked

Frequently asked questions

An AI production system is a set of agents embedded in a team's real workflow, not tools used on the side. Each agent takes an input the team already produces and returns something finished and on brand, ready to ship, so a small team can produce at the scale of a much larger one.

A tool helps a person do a task faster. Agentic design makes the agent a step in the process, like connecting Figma with Claude Code so a designer can dictate direction, have the agent output in Figma, and shape it until it is right, which lets someone who could not design before build full campaign visuals.

No. A well-built system removes the repetitive parts that never needed a human and gives that time back to judgment, direction, and craft. A person stays in the loop to shape and approve, never to redo.

Encode the brand into the system, not the person. The agent should already know the standards, the components, and the voice, so what it returns is on brand by default. Then a human reviews and approves.

It depends on the work, but a typical stack pairs an LLM like Claude or ChatGPT with the tools a team already lives in, such as Figma for design and Webflow for the site, wired together so the agents produce inside the real pipeline.

Yes, that is the point. By carrying the parts that used to require a specialist, an AI production system lets a lean team ship at a volume that used to take a department.

Stefanie Bernal is a Brand and Growth leader who turns brand into measurable growth through brand systems, web, SEO, generative engine optimization (GEO), and AI-built content. She grew from Senior Graphic Designer to Brand and Creative Director, rebranded a B2B SaaS company across three identities, and built the AI production systems a lean team runs every day. Connect on LinkedIn.