How I Run Five Brands on 12 Research Units a Month
30-in-30 sprint, day 14. Ask type: soft. Approved topic bank row 13 ("Longer"). Submit link: Search & Content Growth Engine. Stat source: Content Marketing Institute scaling survey (48% cite not enough repurposing), surfaced via EntrepreneursHQ content marketing statistics roundup.
How I Run Five Brands on 12 Research Units a Month
My content system ships 108 assets a month for my personal brand alone, and the research behind every one of them fits into 12 sittings. I also run AI and growth at NuVision Auto Glass, a $48M company, and my growth company NuroSparx serves US mid-market brands, so I watch marketing teams up close every week. Most of them produce a third of that volume with more people, and their writers still burn out.
The gap has nothing to do with talent. It comes from one structural mistake: teams research per platform instead of per topic.
The per-platform trap
Walk into most marketing departments and content splits by channel. One person owns LinkedIn. Another owns X. A third writes the blog. A fourth edits video. Each of them picks topics, reads sources, and writes from scratch inside their own lane.
Now trace a single topic through that setup. Say your company wants to talk about AI phone agents, the software that answers the calls your front desk misses. Your LinkedIn manager reads three articles and a vendor comparison, then writes a post. Two weeks later your blog writer researches the exact same subject from zero, because nothing connects the two of them. The video editor never touches the topic at all, because nobody handed over material. Your company just paid for the same learning three times and still skipped a channel.
Research is the expensive part of content. Reading sources, checking numbers, finding the angle: that work eats most of the effort behind any strong piece. The writing moves fast once the thinking exists. A per-platform structure pays the slow part again and again for one idea.
The industry already knows this. When the Content Marketing Institute surveyed content marketers about scaling production, 48% named the same obstacle: not enough repurposing. Teams keep creating new material instead of spreading the material they already paid to understand.
Founders feel this as a line item. The content budget grows every quarter, output stays flat, and the team asks for another hire. The hire never fixes it, because the structure creates the waste.
Research once, write from the brief
I fixed this with a rule my team can't break: we research any topic exactly once. The output of that one sitting is what I call a research unit. One topic, one session, one short written brief of 400 to 600 words. My team writes every asset on that topic from the brief and nothing else. Nobody opens a browser twice for the same subject.
The brief follows a fixed shape with six parts:
1. The claim. One sentence stating what the piece argues. For the AI phone agent topic: missed calls cost service businesses booked jobs, and software now answers them better than voicemail ever did.
2. The numbers. Every figure sits next to a source link that resolves. We cut any number without a source. We never soften it into "many" or "most". This single rule stops a team from publishing confident nonsense at volume, which is the biggest risk of producing 108 assets a month.
3. The receipt. The real artifact from our own work: which tool, which screen, what moved. At NuVision I pull the actual after-hours call log, because proof from your own operation beats any industry report you can quote.
4. What most people get wrong. The common misread on the topic. For phone agents: owners assume callers hang up on anything robotic, while the real loss happens before any voice picks up at all.
- The mechanism. Why the thing works, in 3 to 5 plain steps a smart outsider can follow.
6. The objection. The strongest argument against the claim, answered honestly. When nobody on the team can answer it, the topic goes back in the pool until someone can.
Writing the brief takes one focused sitting. That sitting replaces every separate research session your platform owners run today, and it forces the thinking into one document an editor can actually check.
Nine assets out of every brief
Here the fan-out starts. Fan-out means one brief branching into every format you publish. From each unit, my team produces 9 assets:
- 2 LinkedIn posts.
- 3 X posts: one long personal story, one short sharp take, one tactical breakdown.
- 1 X thread that walks the mechanism step by step.
- 1 long-form article, like the one you're reading.
- 2 short video scripts, 45 to 75 seconds each.
Run the math. 12 units a month times 9 assets each equals 108 pieces of content. Research happens 12 times. Publishing happens 108 times. That ratio is the whole economic argument for the system, and it is the number I show founders who believe volume requires a bigger team.
Each brief section already knows which assets it feeds. The receipt carries the LinkedIn posts and the long personal X post, because a real number from a real screen earns trust on those surfaces. The common misread becomes the short punchy post and the video hooks, because a contrarian line stops a scroll in the first second. The mechanism fills the thread and the article, because steps need room to breathe. The objection powers the tactical post, because an honest counterargument starts better replies than any hot take.
The drafting itself goes fast because the thinking already happened. My writers work from the brief with AI producing the first pass, then edit hard for voice. I broke down how we keep that output sounding human in .
Across the five brands I run this for, the mix shifts but the map holds. A consumer service brand swaps the X thread for a plainer Facebook post with an image attached. A company site takes a blog outline instead of a finished article, so the SEO team writes it inside their own keyword plan. The principle never moves: one brief in, every format out, zero second research sessions. You can see the shape of this work across the brands my growth company serves in our case studies.
Why the month beats the day
Most teams run content daily. Someone picks a topic in the morning, researches it under deadline, and publishes whatever the day allowed. Quality follows mood, and one busy week kills the calendar.
I build monthly. In the last four working days of each month, my team builds the entire next month: they write all 12 briefs, then draft and schedule all 108 assets before day one. The month itself becomes pure publishing plus daily engagement, and nobody makes a creative decision under deadline pressure.
Three things improve at once:
1. Decisions compress. I approve topics in one sitting instead of thirty small debates. Every idea goes into one running list, I mark yes or no with a reason, and the team builds only the approved rows. A new idea mid-month waits for the next batch instead of derailing this one. That single habit ended the Monday "what should we post" meeting at every brand I run.
2. Quality stops depending on the calendar. When a launch or a fire eats a week, the content ships anyway, because it already exists. The bad week hits my schedule, never the output. Before the batch system, one hard week at NuVision meant my personal accounts went dark for five days.
3. Measurement finally means something. A fixed batch lets me change exactly one variable per month, a posting time, a hook style, an asset mix, and read the result cleanly at month end. Change five things at once and the numbers teach you nothing.
Two spacing rules protect the batch. First, the same topic never appears on two platforms on the same day; the fan-out spreads across the week so a follower on two platforms sees fresh material on both. Second, my personal account posts a shared topic first and the company account follows a day later, because a founder account out-reaches a brand account on every platform I track. The brand rides the founder, never the reverse.
The batch build also hands hours back to the team, the same math I walked through in . Research time drops because it stops repeating. Meeting time drops because the decisions already happened. What remains is writing and editing, the two jobs your content people actually signed up for.
Hand this to your content team this week
You need the structure before you need my exact numbers. Give your marketing lead these five steps:
1. List next month's topics in one sitting. Pull them from sales calls, support tickets, and the questions buyers ask before they sign. Then approve or kill each one yourself in a single pass, with a one-line reason attached, so the list teaches your team your judgment instead of leaving them to guess it.
2. Write one brief per topic using the six parts above. Cap each at 600 words. When a writer can't fill in "what most people get wrong", the topic is too thin to build a unit on, and you just found that out for the price of a paragraph instead of nine dead assets.
3. Map your own fan-out. List every channel you actually publish on, then assign each brief section to a format the way I did above. Write the map down once and reuse it every month. A three-channel version of this map still beats a ten-channel plan nobody follows.
4. Build the month before it starts. Block the last four working days of this month, put the briefs in front of your writers, and draft everything. The first batch feels slow. The second one runs in half the time, because the map removes every "where do I start" moment.
5. Tag every asset back to its unit, then change one thing next month. When a post wins, the tag tells you which topic and which angle won, so the next batch gets smarter instead of luckier.
My team also keeps step-by-step playbooks on putting AI to work inside daily operations in our e-books library, a bonus read once the system runs.
The founders I talk to keep budgeting for more content when the fix is fewer research sessions feeding more formats. Twelve sittings. Nine assets each. One hundred eight pieces across the month, and the same map running five brands. Your team already has the writers. Give them the map.
If you'd rather have this engine built than build it in-house, NuroSparx sets up the whole system for brands, research briefs through publishing calendar, on our Search & Content Growth Engine page. Or book 30 minutes with me and bring your current content calendar; I'll point out where the duplicate research hides inside it. And if the AI drafting step is the part your team resists, read next.
