Our Content Calendar Runs on Our Own Tool: Here's the Setup

By Aran P Ploshansky

The full operating setup behind HYR Studio content calendar — recording cadence, batch pipeline, calendar rules, and the 20-minute weekly ritual that keeps it running.

We've written before about [*why* we dogfood HYR Studio](/blog/how-we-use-hyr-studio-to-market-hyr-studio). This post is the *how* — the actual operating setup behind our content calendar, in enough detail that you could copy it.

## The cadence: two recordings a month

Everything starts with source material. Ours is deliberately low-production: two recordings per month, 15–25 minutes each. One is usually a product or customer story; the other is a point-of-view piece (like this one — it started as a voice memo about our own calendar).

The rule: **no recording, no content.** If we haven't captured a real idea in real voice, we don't manufacture posts to fill the gap. Silence beats filler.

## The pipeline: recording → batch → calendar

Each recording goes through HYR Studio and comes out as a batch: typically 2 [carousels](/blog/the-anti-generic-guide-to-ai-carousels), 4–6 [quote cards](/blog/what-90-days-of-customer-batches-taught-us-about-quote-cards), 1 thread, 1 [newsletter section](/blog/from-transcript-to-newsletter-in-15-minutes), and 1 [blog post](/blog/the-creators-seo-play-turning-episodes-into-blog-posts). Two recordings therefore produce roughly 20–25 assets — a full month of publishing inventory.

Then the curation pass: we cut about a third. The kill criteria are simple — if an asset could have come from any content tool's demo account, it dies. If it sounds like us on a good day, it ships.

## The calendar rules (not decisions)

The surviving assets map onto the month by rule:

- **Mondays:** anchor asset — carousel or the blog post announcement - **Wednesdays & Fridays:** quote cards (the rhythm layer) - **Thursdays:** thread, on the weeks we have one - **Every other Friday:** newsletter, closing the loop on that fortnight's theme - **Floating:** announcements ship the day the feature does; news reactions ship within 48 hours or not at all

Because these are rules rather than decisions, scheduling a month takes one sitting. Nobody on the team asks "what should we post Tuesday?" — [the calendar answers before the question exists](/blog/building-a-branded-content-system-not-just-one-off-posts).

## The weekly ritual: twenty minutes

Monday morning, twenty minutes: review the week's scheduled assets, check they still make sense against anything that changed (a launch moved, a customer story got better), swap at most one slot. That's the entire ongoing overhead. The heavy lift happens twice a month at recording time — which is exactly where a founder's content hours *should* go.

## What breaks, honestly

Two failure modes show up. First: a thin recording produces a thin batch, and no downstream cleverness fixes it — the fix is always a better conversation, not better extraction. Second: announcement weeks crowd the calendar, and the temptation is to publish everything. We've learned to bump evergreen assets forward instead; the batch doesn't expire.

## Why we're showing the wiring

Partly because "we use our own tool" is only credible with receipts. But mostly because this setup is the product's actual thesis in operation: the creative work happens twice a month, in voice, at full attention — and the system turns it into a month of branded, [unmistakably-ours](/blog/why-we-built-hyr-around-voice-preservation) publishing. If the founder of a repurposing company needed more than twenty minutes a week to run his calendar, you should ask hard questions about the product.

**Turn your next episode into a content batch →** [hyrstudio.com](https://hyrstudio.com)