How an Agent Operator runs a quarter.
Most growth teams run on backlogs. A list of tasks, sorted by who shouted last. The Agent Operator runs on Rocks. Three of them. Nine Pebbles underneath. SOPs that make the work repeatable when the agents do it.
This page is how the system works.
Backlogs are how teams disguise production as strategy. Tasks get sorted by who asked last. Output goes up. Decisions stay shallow. Nothing compounds.
Rocks are different. A Rock is a bet the team is making with the quarter. Not a project. Not a sprint. A claim about what changes if the quarter goes well.
Three Rocks is the limit. Anything more is a backlog with a different name. Anything less and you're not actually running a function.
The work underneath each Rock is three Pebbles. The work underneath each Pebble is an SOP. That's the whole shape.
The grid above is empty. Every operator running this framework fills it in differently. The Founder Brand quarter looks one way. A category-claim quarter for an AI-native company looks another way. The shape is the same.
A Rock answers one question: what claim are we trying to earn the right to make by the end of the quarter?
Not “ship more content.” Not “increase pipeline.” Not “improve conversion.” Those are tasks dressed as goals.
Three Rocks show up in every quarter I run, regardless of the company. The category changes. The founder changes. The industry changes. The Rocks don't.
Rock 01. Own the [category]. The creative work that earns the right to claim the category. Includes the moves designed to land as viral moments.
Rock 02. Activate the [founder] as a media engine. LinkedIn articles, posts, and video. YouTube. The founder's voice becomes the channel.
Rock 03. Build the [industry] community. LinkedIn surface for the persona. Podcast and newsletter to feed it. IRL dinners in Tier 2 cities to close the relationships that close.
You can read those out loud at the start of the quarter and explain them to a board member without showing a slide. That's the test. If it needs a slide, it isn't a Rock. It's a project.
Three Rocks per quarter. Picked at the start. Defended for 90 days.
A Rock without Pebbles is a poster. Pebbles are the specific things that get shipped, on specific dates, that add up to the Rock being earned.
A Pebble looks like: category benchmark live at a named URL on a named date. Or: six branded events in the quarter, each producing eleven finished assets. Or: IRL dinner series in three Tier 2 cities, fourteen people per dinner.
Pebbles have dates. Pebbles have counts. Pebbles either shipped or didn't. No partial credit.
Three Pebbles per Rock. Nine Pebbles per quarter. Each one binary.
A Pebble without an SOP is a one-time event. An SOP is what makes the Pebble repeatable, because the agents are the ones running it.
An SOP names the inputs (what the agents need), the steps (what they do), the handoffs (where humans review), and the outputs (what ships). Every Pebble that runs more than once gets one.
The SOP is also the moat. A competitor can copy a Rock. A competitor can copy a Pebble. They can't copy the operating system underneath, because that's the part that took the year to build.
Every SOP runs on three layers.
The instructions the agents follow. The voice. The constraints. The format. Specific enough that two agents running the same prompt produce work indistinguishable from each other.
The context the agents need. The voice profile. The brand kit. The customer interviews. The competitive map. Updated weekly. The agents don't make things up because they have the source material in front of them.
The orchestration. Which agent runs first. Where the handoffs happen. Where the human reviews. Where the work sits while it waits. Which channel it ships to. The plumbing.
Most operators stop at the prompt. The agents fail without all three.
A quarter run on Three Rocks produces four things:
The thing the brand earns the right to say it owns. Backed by shipped work, not slides.
Every asset, dataset, customer outcome, and benchmark that came out of the quarter. Stored, indexed, and cited by the AI answer engines. AEO is a byproduct of the Rocks running, not a separate strategy.
In-market signal converted into meetings. The GTM engineering layer routes engagement, intent, and warm replies into the calendar. The founder is the channel. The Agent Operator runs the routing.
The SOPs that the next quarter starts from. Each quarter the operating system gets tighter, because the work that was manual the quarter before is automated the quarter after. The team gets smaller over time. The output gets bigger. That's the trade.
In April 2026 the CEO of Box published a job description for a new role he thinks every team will need. The agent deployer and manager. Other operators are calling it the Agentic Operator.
I'm Andrew McGuire. I've been doing the work since before it had a name.
The platform underneath is forked OpenClaw, rebuilt for this. Five agents in production. One operator. Every workflow gets announced in Shipped first.
The methodology runs the same way regardless of the company. The Rocks change. The Pebbles change. The shape doesn't.
The system applied to founder content and pipeline. The first worked example.
See the Founder Brand quarter →More worked examples publish in Shipped, every Friday.
Every Friday in Shipped. The app I built that week, the lesson it taught me, and one prompt you can steal. New SOPs published there first.
Subscribe to Shipped. →