Back to the catalogDoc · Content & hooks

A content calendar for voice AI operators (3 posts a week)

A fixed-slot weekly calendar that kills the blank-page decision — opinion Monday, proof Wednesday, teach Friday — with a month of angles, a batching workflow, and the CTA baked into every slot.

Most operators don't have a content problem. They have a decision problem — every posting day starts with "what do I make?", the blank page wins, and the account goes quiet for three weeks. A calendar kills that decision. You show up, the slot already tells you the angle, and you just fill it. Here's a calendar built for someone running an agency, not a media company — three posts a week, sustainable, with the CTA baked in.

The rule before the calendar

Consistency beats volume, and it isn't close. Three posts a week every week for three months will out-earn seven posts a week for two weeks and then silence. Pick a cadence you can hit on your worst week, because your worst week is the one that decides whether the engine compounds or dies. Three is the number most solo operators can actually sustain while delivering for clients.

The weekly template (3 slots, fixed angles)

Assign each posting day a permanent job so you're never choosing an angle cold:

  • Monday — Opinion / contrarian. The highest-performing format. Disagree with the loud advice in the niche. "Stop selling AI receptionists." This is your reach post; it's meant to travel.
  • Wednesday — Proof. A demo clip, a client win with a real number, or a transcript teardown. This is your trust post; it converts the people Monday reached.
  • Friday — Teach / answer. Turn one sales objection or one build question into a short how. This is your authority post; it makes you the obvious person to hire.

Rotate within the slots so you're not the "cost math" person every Monday, but keep the slot's job fixed. The structure is what removes the decision.

Mapping angles to a whole month

Four Mondays, four Wednesdays, four Fridays — twelve posts. A clean month looks like:

  • Mondays: contrarian take → pricing hot take → niche hot take → "most agencies die because ___".
  • Wednesdays: live demo → client-win number → transcript teardown → before/after screenshot.
  • Fridays: answer the hallucination objection → the discovery-call structure → "we already have a receptionist" reframe → the escalation-layer explainer.

Every one of those maps to a doc or tool you already have in this kit, which means the body is already written — you're just recording the hook and the proof.

Batch, don't drip

The trap is treating each post as a fresh project. Instead:

  • Pick one recording day. Film three to six pieces in one sitting while you're already in the headspace.
  • Write the week's three hooks first, before you record anything. If a hook doesn't have a number or a story behind it, cut it now, not on camera.
  • Schedule, don't post live. Manual daily posting is where consistency goes to die. Queue the week and forget it.

Batching turns content from a daily tax into a two-hour weekly block.

The CTA is part of the calendar, not an afterthought

Every post ends with one comment-keyword CTA — "comment MATH and I'll send the one-pager." Decide the keyword when you plan the post, not after. Each slot has a natural resource: Monday's opinion pairs with a doc, Wednesday's demo pairs with a checklist, Friday's teach pairs with the tool that does the thing. The keyword → auto-DM → free resource → captured lead loop is the entire point; a post without it is a hobby.

What to track (keep it to two numbers)

Don't drown in analytics. Watch two things weekly:

  • Saves and comments, not views. A post that gets saved is a post that earned trust; views are vanity.
  • Keyword comments → captured leads. This is the only number that pays rent. If reach is up but keyword comments are flat, your CTA is weak, not your reach.

The one-line version

Fix three weekly slots — opinion Monday, proof Wednesday, teach Friday — batch a month in one sitting, map each post to a resource you already have, and bake one comment-keyword CTA into every single one. The calendar removes the daily decision, and removing the decision is what keeps the engine running long enough to compound. When the planning-and-publishing busywork is the part that keeps slipping, that scrape-script-caption-publish-capture loop is exactly what I built Hermes to run so operators stop going quiet.

buildwithhermes.com · No code

Build voice agents with zero code.

Stand up a production agent without wiring Vapi, a CRM, and a billing tool together by hand. Configure, launch, and move on to selling.

See the platform