You've decided to try an AI content pipeline. The pricing page asks how many posts you want a month, not how many seats or how many words. If you've never budgeted this way, the number feels arbitrary. Ten posts, fifty posts, a hundred. Pick one.
This post is a way to pick one on purpose. It anchors on the post as the unit of cost, works through what different goals actually consume, and closes with three worked examples at small, mid, and larger budgets.
Why the unit is the post
Most tools in this category price by seat or by word. Seats reward big teams, which punishes solo operators. Words reward padding, which punishes anyone who writes tight. Neither maps to the thing you actually publish.
The post is the unit you plan around anyway. Your editorial calendar is a list of posts. Your cornerstone plan is a count of posts. When you meet with a client or your boss and talk about output, you say we're shipping four posts a week, not we generated 12,000 words. A post budget lines the pricing up with how you already think.
There's a second benefit that matters for first-time buyers: it's predictable. A run that eats more research than expected does not cost you more. A revision cycle where the editor agent goes back and forth with you a few times does not cost you more. You are buying a finished, approved post, not an API meter.
What a cornerstone push actually consumes
A cornerstone piece is the deep, definitional post you want to rank for a hard head term. On its own it is a single post in your budget. Cornerstones rarely travel alone though.
The pattern that works is one cornerstone plus a supporting cluster. The cornerstone anchors the topic. The cluster posts pick off adjacent search intent, link back to the cornerstone, and give search engines a reason to trust that you cover the topic in depth.
A minimum viable cluster is around five to eight supporting posts. A serious one is twelve to twenty. So the honest math for a single cornerstone push looks like:
- One cornerstone
- Five to twenty supporting posts
That means a cornerstone push consumes six to twenty-one posts from your monthly budget. If your budget is ten posts a month, you can run one push and take a breath. If your budget is thirty, you can run one properly and start on the next.
What a cluster costs to build out
A cluster by itself, without a fresh cornerstone above it, is a different animal. You are picking off related queries around a topic you've already covered, or a topic where you don't need a definitive anchor piece yet.
Clusters are lighter than cornerstones because the research overhead is smaller. The research agent has already mapped the terrain the first time. On the second pass, it's looking for gaps and adjacent search intent, not the whole territory. In post-budget terms, a cluster is whatever number of posts you commit to it: five, ten, thirty. The unit is the same.
The useful thing to notice is that clusters are how a monthly cadence actually fills up. Cornerstones are punctuation. Clusters are the sentence.
Where a small budget still pays off
If your budget is small, say a handful of posts a month, the temptation is to write it off as too little. That is not right. A small budget forces choices that a big budget lets you skip.
With a handful of posts a month, you can:
- Ship one cornerstone every quarter and spend the rest of the month on its cluster
- Refresh a few existing posts each month, which often moves rankings faster than new posts do
- Cover one narrow topic well instead of covering ten topics badly
The reason this works is the pipeline structure. A supervised agent loop with human approval means the posts you do ship are ones you actually stand behind. Small budgets amplify quality-per-post because there's less room to hide a weak one.
The cadence and depth tradeoff
Every post budget forces a tradeoff you should make deliberately, not by accident.
Cadence means posts per week. It signals freshness, feeds the newsletter, keeps the site alive. Cadence buys you consistency.
Depth means fewer posts, longer research, more revision cycles with the editor agent, tighter alignment with your writing rules and brand voice rules. Depth buys you the pieces that actually rank.
A common mistake is to buy the biggest post budget you can afford and split it evenly across a calendar. Even splits produce even results, which usually means unremarkable. A better move is to weight your budget: roughly two thirds to depth pieces you plan carefully, one third to lighter posts that keep cadence up.
The post budget doesn't dictate the split. You do. But it sets the ceiling on how far you can push either lever.
Three worked examples
Here are three ways to size a monthly budget against a real goal. Adjust the numbers to your own situation. The logic transfers.
Example one: solo founder-marketer, small budget
You run marketing at a two-person SaaS. The blog exists but hasn't shipped in six months. You want to prove it can move a needle without hiring.
Budget shape: A handful of posts a month, at the low end of the range.
How to spend it:
- One cornerstone per quarter, so roughly one post every third month goes to the anchor
- Two supporting cluster posts a month
- One refresh of an existing post each month, run through the same pipeline
Why this works: You're not trying to publish daily. You're trying to build one credible topic hub per quarter, then a second, then a third. In a year that is four hubs, each with a cornerstone and eight or so supporting posts. That is a serious blog.
Example two: small in-house team, mid budget
You have a content lead and one writer. You're the content lead. You want to move from two posts a week to four without adding a second writer.
Budget shape: A few dozen posts a month, in the middle of the range.
How to spend it:
- One cornerstone push a month, meaning the cornerstone plus five to eight cluster posts
- Six to eight standalone cluster posts against topics you've already established
- Two to four refreshes, prioritized by which URLs are sitting on page two of search results
Why this works: The team already knows the brand voice. The pipeline enforces it on every draft, which frees your writer to focus on the two or three pieces a month that need a human's full attention. Approval checkpoints are where the writer's judgment lives, not the first draft.
Example three: agency, larger budget
You run content for four clients. Each has its own brand voice rules, writing rules, and topic map. You need per-brand output that doesn't blur.
Budget shape: Near the top of the range, split across client workspaces.
How to spend it:
- Per client: one cornerstone a month, five to eight cluster posts, one to two refreshes
- Across clients: keep brand voice configs isolated per workspace so a slip on one account cannot bleed into another
- Reserve five to ten posts a month for tests: new topic angles, new formats, or accounts you're onboarding
Why this works: The unit economics fall out cleanly. A post costs the same whether it's for client A or client D, which makes client billing straightforward. Per-brand voice rules keep the output distinct. The live agent log means when a client asks why the writer took a particular angle, you have a real answer, not a shrug.
A note on getting the number wrong
You will get the number wrong the first month. Every first-time buyer does. The signal that you set it too low is that you cannot finish a single cornerstone push. The signal that you set it too high is that posts are stacking up in the approval queue because you haven't reviewed them.
Either way, the fix is the same: adjust next month. The post budget is a monthly commitment, not a cell you locked in a spreadsheet.
Pick a number that maps to one honest goal, spend it deliberately, and let the next month teach you what to change.