u/styleforge-io

Question for the buyers here, and it's not an AI question, just a structure one.

When you build a campaign, how many distinct avatar personas are you actually designing for, and how many creatives does each one get?

My background is the creative side, 40 years of it. The way I've always worked, the avatar comes first. Back in the day every ad had a picture of the person it was aimed at taped to the wall next to it. And my rule became one concept per avatar rather than five variants of one concept, because Meta's delivery seems to collapse lookalike creatives into basically one entity. Five same-concept variants buys you one auction ticket, not five.

But I watch teams run 30 creatives against what is really one buyer in their heads. And other teams run 3 broad ads and call Advantage+ a strategy. Both swear by it.

So I'm curious what this room actually does:

- How many personas do you genuinely build for in one campaign?

- How many creatives per persona before you admit you're just making variants?

- And when fatigue hits, what do you refresh first, the creative, the hook, or the person you're aiming it at?

Feels like every buyer has a ratio in their head and nobody ever says it out loud. What's your playbook here?

The 2026 AgencyAnalytics benchmark surveyed about 500 agencies and AI search visibility came out as the number one new service clients are asking for, ahead of paid ads and short form video. Matches what I'm hearing directly.

So I'm curious how shops here are actually handling it, because from what I can tell everyone is inventing their own version of this service right now.

- How are you delivering it?

- And what's it billing at?

I've seen research showing one time audits running between 1,500 to 5,000 and ongoing programs at 3K a month and up.

Curious whether that matches anyone's reality or whether those numbers are aspirational.

Is anyone here already selling this as a defined service and if so what are you packaging with it? llms.txt optimization, other services to improve it?

Question for the buyers here, and it's not an AI question, just a structure one.

When you build a campaign, how many distinct avatar personas are you actually designing for, and how many creatives does each one get?

My background is the creative side, 40 years of it. The way I've always worked, the avatar comes first. Back in the day every ad had a picture of the person it was aimed at taped to the wall next to it. And my rule became one concept per avatar rather than five variants of one concept, because Meta's delivery seems to collapse lookalike creatives into basically one entity. Five same-concept variants buys you one auction ticket, not five.

But I watch teams run 30 creatives against what is really one buyer in their heads. And other teams run 3 broad ads and call Advantage+ a strategy. Both swear by it.

So I'm curious what this room actually does:

- How many personas do you genuinely build for in one campaign?

- How many creatives per persona before you admit you're just making variants?

- And when fatigue hits, what do you refresh first, the creative, the hook, or the person you're aiming it at?

Feels like every buyer has a ratio in their head and nobody ever says it out loud. What's your playbook here?

I've owned and run a few agencies over the years, and I'm genuinely curious how newer agencies are leveraging AI right now, because 2026 is a different world than the one I built mine in.

And I don't mean simple stuff like using ChatGPT to write copy or speed up research. That stuff shaves minutes off tasks that were never really the problem. I mean the deeper layer: what lets you take on more clients, turn work around faster, or deliver something you couldn't before?

My own lens on it, for what it's worth: I look at everything through chop and hops.

Chop is how fragmented a task is, all the little manual steps inside it.

Hops are the jumps between platforms to get one thing done. Export here, reformat there, paste it into the next tool, chase the asset, upload again. The stuff that quietly eats most of a solo operator's week.

One thing that opened my eyes was running a timesheet on myself for a week, not for billing, just for truth about where the hours go. I started to challenge my process and steps to force a change in how I got stuff done faster and with better outcomes.

So I'm curious where others are landing:

What tools or setups are genuinely delivering outcomes for you, not just saving a few minutes?

What have you tried that disappointed you?

And has anyone cracked the one-person-operating-like-a-team-of-five thing, or is that still mostly talk?

For context on my bias, I've spent 40 years on the creative side and the last two building AI agency tools in this space. But I'm asking because I want to hear what's real out there, not to sell anything.

I build a creative platform for ad agencies and brand teams. It makes ads, product videos, brand assets, that kind of thing, and it's driven by Claude Code, Cowork and Claude.ai over the browser all over MCP. There are over 200 tools.

Everyone hits the same wall somewhere around twenty tools, where the agent stops routing well and starts guessing. Two obvious fixes didn't work for me.

Fewer tools didn't work, because the work genuinely needs that many verbs. Making an ad and publishing an ad and scoring it with music are different things.

Better tool descriptions didn't work either, and that one surprised me. Every description is prefill. You pay for all of them on every turn, including the turns where that tool was never getting called. So writing more of them makes the problem quietly worse.

What worked was giving up on the idea that the agent should figure out the route.

Think about what you're actually asking it to do. A user says "make me a product video for the new jacket." The agent now has to decide: pull the product from the store, or ask which one? Generate the shots or use the existing photos? Score it before or after the cut? Publish, or stage for approval? None of that is in any single tool's description, because it isn't about any single tool. It's about creating an OUTCOME that uses multiple tools.

My solution was to create what I call Playbooks. I have over 150 of them now, one per outcome an agency actually asks for. And these literally drive complex multi-step decisions, routes, processes, and the checks-and-balances any predictable outcome needs.

Each one names real tools and the order, and marks where a human has to say yes and where money gets spent. The user fills in a couple of blanks and the agent runs it.

Two rules keep these from rotting, and they're the bit I'd actually steal if I were reading this.

Don't re-teach. A playbook names tools and the order and nothing else. It never restates what a parameter does or how the craft works. That stuff lives in the tool description, which gets served fresh every time you connect. The first version I wrote duplicated the rules into the playbooks and it fell apart in about three weeks, because the tools changed and the playbooks didn't. Now there's one home for each fact.

Steer, don't script. Steps say things like "reuse an existing project before making a new one" rather than dictating exact calls. The agent still gets to think. You want a spine, not a script, and you find out which one you wrote the first time reality doesn't match the happy path.

The part that makes this MCP rather than documentation: the playbooks are served by the server. There are tools to search them and fetch one by name. So nobody pastes a recipe in. The agent asks what the play is for this outcome, gets it back, and runs it. That's the routing layer, and it's why the tool count stopped mattering.

The test that convinced me it was real: fresh agents, no memory, no docs, never talked to me, given only a user's plain sentence and the connection. Over a hundred runs against the live platform. They do it right on first contact.

Disclosure, this is my own platform so obvious bias. But none of this is specific to it. If you're deep into tool count and losing the agent to route-finding or getting inconsistent outcomes, that's where I'd look.