The Agent Stack for Web3 Studios

Most design studios using AI right now have one agent. It's Claude or ChatGPT with a blank system prompt. Everyone uses it for everything. Writing copy. Reviewing strategy. Brainstorming names. Analyzing competitors. Summarizing calls. Drafting proposals.

It's like hiring one person and making them your designer, strategist, copywriter, accountant, and project manager simultaneously. That person would be mediocre at everything and excellent at nothing.

That's what your single generic AI assistant is right now.

The alternative: build a team of specialized agents. Each with a defined role, a distinct personality, clear boundaries, and specific context about your studio's standards, clients, and way of working.

Not 12 copies of ChatGPT with slightly different prompts. Twelve teammates who know their lane.

The Four Layers

The stack organizes into four layers based on what part of the studio each agent supports.

Layer 1: Creative Core touches the work directly.

Scout is your creative strategist. Before any project begins, Scout maps the landscape. Competitors, cultural context, audience behavior, positioning gaps. Scout doesn't just collect information, it synthesizes. The one insight that changes the direction, not 80 slides of obvious observations.

Muse is your creative director. It reviews work against the brief, the brand system, and the studio's quality bar. Muse doesn't design. Muse directs. Specific feedback, honest pushback, and references from architecture, fashion, and film, not just other websites. "The type hierarchy isn't creating the emphasis the brief needs" not "this doesn't feel right."

Lens is your visual researcher. When a designer needs references for "Japanese minimalism meets brutalist web design," Lens surfaces 5 perfect examples from across disciplines with context about why each one is relevant. A curator, not a Pinterest board.

Ink is your copywriter. Headlines, body copy, taglines, social posts. Not generic marketing copy. Writing that sounds like the specific brand it's writing for because it loads the structured voice files before writing a single word. Three versions of every headline, different approaches, not different words for the same idea.

Layer 2: Business Operations runs the studio as a business.

Pulse is your client intelligence. Knows every client's history, preferences, feedback patterns, and internal politics. Remembers that the CMO hates serif fonts, that the founder always pushes back on round one to feel involved, that the last project went sideways because nobody looped in legal early enough. Proactive briefing before every client meeting.

Donna is your financial intelligence. Project profitability, burn rates, invoice tracking, revenue forecasting. Leads with the key number, not the spreadsheet. "This project is 22% over budget with 3 weeks remaining. Here are two options." Warm, direct, practical. Never invents figures or certainty.

Forge is your project intelligence. Thinks three steps ahead. While the team is focused on this week, Forge already sees that next week's review collides with another project's deadline and the senior designer is double-booked. Flags risks early enough that they're solvable, not emergencies. Low-drama.

Layer 3: Growth handles how the studio shows up in the world.

Signal is your content strategist. Plans and drafts the studio's own content. Blog posts, Twitter threads, newsletters, case studies. Substance over volume. Original angles. Would rather post one thing a week that people screenshot than five posts that get polite likes.

Radar is your business development intelligence. Tracks which companies just raised a round and will need a rebrand. Which protocols are launching without a design team. Qualifies leads against the studio's sweet spot. Honest about fit. If a lead isn't right, says so before the team wastes time on a proposal.

Layer 4: Infrastructure maintains the systems underneath everything.

Archive is your knowledge manager. Past projects, design decisions, lessons learned. When someone needs to know how you handled a similar project two years ago, Archive knows. Not just file retrieval. Context-rich recall that includes the decisions, the constraints, and what the team learned.

Onyx is your brand system manager. Maintains the structured brand files for every client. Catches when a positioning statement says "users" in one file and "customers" in another. Tracks versions. Proactively audits for drift between files.

Gate is your operations admin. Meeting prep, scheduling logistics, follow-up tracking, vendor coordination. Quietly efficient. The team notices Gate's absence, not its presence.

How Information Flows

The power isn't in individual agents. It's in how they pass context to each other.

New project kicks off: Radar qualifies the lead. Pulse provides client context. Scout researches the landscape. Muse sets creative direction. Lens gathers references. Ink and the design team execute. Forge tracks the timeline. Donna monitors the budget.

Content production: Signal identifies the topic. Scout provides research. Ink drafts. Muse reviews. Signal publishes.

Brand system update: Client brand evolves. Muse approves creative direction. Onyx updates the structured files. Every creative agent automatically references the updated data.

Each agent makes the others smarter.

Humans Stay in Control

This matters more than anything else in the stack.

Agents prepare. Humans decide. Agents draft. Humans approve. Agents flag. Humans act.

Human decision points that agents never bypass: creative direction approval, client communication, strategic recommendations, budget and pricing decisions, scope changes, content publication, anything involving a commitment.

Agent autonomy zones: research and information gathering, first-draft generation, internal status updates, reference retrieval, data analysis, meeting preparation, quality checks.

The line is clear. Agents handle the volume. Humans handle the judgment.

How to Build This Without Losing Your Mind

You don't build all twelve on day one.

Month 1: Start with three. Ink, Muse, and Donna. Build their soul files. Create Claude Projects for each. Test them on real work. Iterate the soul files based on what works and what doesn't.

Month 2: Add Pulse and Forge. These are the connective tissue agents that make the first three smarter by feeding them client and project context they didn't have before.

Month 3: Add Archive and Onyx. These compound over time. Every project makes them more useful.

Month 4 onward: Add growth and specialty agents as the studio's capacity to manage them grows.

The shared soul/principles/guardrails architecture means each new agent plugs into the same foundation. You're extending a system, not starting from scratch.

After six months, your 5-person team operates like a 15-person team. Not because agents replaced anyone. Because agents handle the context-gathering, first-drafting, and pattern-tracking that used to eat 40% of every human's day. Your humans spend that time on the work that only humans can do: creative leaps, client relationships, and strategic judgment.

That's the stack. Not twelve chatbots. Twelve teammates with souls.