How content actually compounds for a small team — and why most agencies still describe it as a calendar

A week ago we walked through what a self-improving content engine looks like as a recursive loop — the sensor / policy / tool / quality gate / learning frame from Tom Blomfield's YC batch talk on self-improving companies. The day after, we showed what installing that loop looks like as files in a folder. Two pieces on the loop that makes content get smarter every week.

This piece is about the other axis. Not the loop — the surface the loop is publishing on. A small team can have the cleanest recursive learning loop in marketing and still ship into nothing, because content isn't only a loop. It's also an operating model with named layers, and most small teams staff one of those layers full-time and treat the other four as optional.

The framework for the surface comes from a 2021 essay called Decentralized Content Marketing, written by Alex Birkett (co-founder of Omniscient Digital, a B2B SaaS content agency that punches well above its 50-person weight). He named five layers a content function actually has to run: Strategy, Enablement, Execution, Feedback, and Repurposing. The two frames stack — Blomfield's loop is how the work gets smarter; Birkett's surface is what the work has to staff. This post is about the surface.

The pattern Birkett named — and why it still holds in 2026

Look at how most content marketing agencies describe what they sell, and a pattern shows up fast.

Click through six or seven content-marketing agency sites and the same phrases keep coming up. Some sell "units per month." Some describe "batches of posts at predetermined dates." One walks you through "a 4-step process that produces over 250 blog posts every month." A few larger shops name more functions on the way to the deliverable — strategy, creation, operations — but the path still stops at "ideation through publication." A smaller group names a distribution layer on top of production and calls the whole thing a content engine.

What none of them name in their public language is feedback as a layer. Or repurposing. Or — taken together — an operating model with named layers and a closing edge between them. The framing reads as a calendar of deliverables, billed by cadence. Volume and schedule are the spine.

That framing isn't wrong. It's incomplete. A small team running content as a calendar produces a steady stream of work that doesn't compound. Each piece is a deliverable that gets shipped and then ages. The team's leverage is bounded by how many pieces they can ship per month — and how many pieces per month is a function of headcount. That's exactly the bind the team was trying to escape when they hired an agency or a head of content in the first place.

The frame his essay names is different. Content as a distributed system — strategy upstream, execution downstream, with feedback and repurposing running across the whole thing. The five layers aren't a checklist; they're the functions the work has to pass through if a single piece is going to do more than show up on the calendar.

How we'd rebuild this for a small AI-native team

His diagnosis was right. A content function has those five layers whether the team names them or not, and the layers that don't get named don't get staffed. What's changed since 2021 is the cost of running the layers under AI-native delivery. Five years ago, staffing all five required a content team. In 2026, a small team — three people or fewer — can run all five, but only if the layers are explicit, and only if the team knows which layer is doing the work on any given week.

Strategy. Where the function is pointed. The audience. The named theses the work is in service of. The channels in scope. A small team that skips this layer doesn't notice for the first quarter, because anything publishes against any reasonable strategy. The miss shows up at month four — a quarter's worth of posts shipped, and the reader can't name a single thesis back to you. Under AI-native delivery this layer lives as a short rules file the AI loads on every task: what the brand stands for, what's off-limits, who the work is for. One or two pages. Half an hour to update once a quarter.

Enablement. Everything the team needs to ship good work without re-deciding the same thing every time. The idea backlog. The templates. The named rules — "don't invent numbers," "cap named sources at three," "no contrarian framing against allies." Without this layer the same arguments happen every Monday: what's a good headline, what counts as a source, how long is too long. The senior person on the team becomes a bottleneck on every piece. Under AI-native delivery this layer is a folder of small instructions files the AI assistant pulls in by name — one for the headline check, one for the source check, one for the audit pass. The folder grows by a file or two every week as the team learns what to lock in.

Execution. The actual published work. Blog posts. Founder posts on social. Podcast appearances. Newsletter sends. The visible surface — and the only layer most teams staff full-time, on the assumption that the other four will happen by adjacency. They don't. A team that hires a head of content, gives them no strategy file, no enablement folder, and no feedback loop is staffing one layer out of five and calling it a function.

Feedback. The signals that come back. Replies from the people the work is actually aimed at. Sales-call transcripts that quote a specific piece. Inbound DMs from named accounts. Citations from AI-search engines. A team that doesn't name this layer defaults to raw reach as the success metric — likes, impressions, follower count — and never finds out which pieces actually moved someone toward a conversation. Under AI-native delivery, a daily 5-line "what came back" digest closes the loop in under a minute a day: the AI watches the inboxes, the replies, and the citation feeds; the lead on the engagement reads the digest; the patterns surface within a few weeks.

Repurposing. One piece becomes many. A long-form post becomes a LinkedIn thread, a 60-second clip, a newsletter section, a slide in a panel deck, a section of the next sales pitch. The cheapest leverage on the whole surface — and the layer that gets staffed last on almost every team we've seen, including ours.

That last one is where this post turns honest about us.

Where our own surface is weakest

On the four upstream layers, we operate the way the framework recommends. Strategy is locked in a short rules file every piece reads on the way in. The enablement folder gets a new instructions file most weeks — this week's addition is one for "describe both sides of a binary you're tempted to declare," and earlier in the month we added one for the headline check. Execution is a daily ship: a post on this blog, a paired distillation under one founder's byline on LinkedIn. Feedback runs every Friday in a learning pass we don't skip — the AI surfaces what came back during the week, one of us reads it, and at least one rule in the enablement folder gets edited as a result.

Repurposing is where we under-staff. Every blog post here ships with a single LinkedIn distillation under the author's byline, and nothing else. The same piece could be a thread on X, a short video clip pulled from the closing argument, a one-pager for a prospect already in conversation, a slide for the next panel deck — any of which would land for a different reader at no additional research cost. None of them happen this week, because the next blog post is louder in the calendar than the repurposing of the last one. The calendar wins, even on a team that knows better.

That's the trap. A team can name the layers, know which layer compounds, and still default to the calendar — because the calendar produces a visible deliverable today. Repurposing compounds quietly. Skip it for a week and nothing visibly breaks. Skip it for a quarter and you wake up to a backlog of published pieces and a single outbound thread on each, when the same pieces could have been the spine of a buyer's first three conversations with you.

The closing edge

If the loop is what makes content get smarter and the surface is what content has to pass through to land, the closing edge between them is small. A reader's reply in the inbox on Tuesday becomes a note in the enablement folder by Friday's learning pass; the next piece's brief reads that note and writes prose that wouldn't have existed without it. Each week's work writes into next week's rules. That's what compounds means on a content function.

It's also why a small team can outpace a larger agency that ships more volume. The larger agency is delivering against a calendar, billed by cadence. The small team is shipping into an operating model that gets a little sharper every Friday. A buyer can tell the difference inside two months — the small team's third post answers a question the buyer surfaced in their first reply; the agency's twelfth deliverable answers nothing in particular, because nothing was listening.

The smarter loop helps. The named surface is what the loop is publishing on. Both have to be there.

If you only have one, the loop is the wrong half to skip. Start with the surface. Name the five layers. Staff Repurposing on the way in, not on the way out.