What this is

The publishing engine gets built once and then run weekly. Pillars, formats, calendar, prompt library and a review loop designed so your time goes into thinking rather than production.

What it looks like in practice

  • Four to six content territories with a defensible claim to each
  • Ninety day calendar anchored to the current week
  • Format library covering long form, short form and visual
  • A review loop that keeps drafts in your voice

What you get

Deliverables, stated up front.

Included in scope

  • Content pillar document
  • Ninety day rolling calendar
  • Prompt and idea library
  • Weekly draft, review and publish workflow

Where it sits

Part of Founder Authority Programme.

The 5C Framework across a twelve month arc.

See the whole practice

Frequently asked

Create, in plain terms.

How often should a founder publish?

Three times a week is where compounding starts and the workload stays sustainable. Daily is achievable and usually degrades quality. Once a week rarely builds enough surface area to be remembered.

Who writes the posts?

We draft, you review. The argument has to be yours or it will not survive the first serious conversation it creates. If a draft does not sound like you said it, it does not publish.

What if I disagree with a draft?

Then it gets rewritten. Founders who wave drafts through without reading them produce content nobody can defend, which is worse than publishing nothing.

In more depth

Building an engine, not a habit.

See the whole practice

Why founders stop publishing

Almost always because every post starts from a blank page. Motivation is not a system. We remove the blank page with pillars, a rolling calendar anchored to the current week, and a prompt library that turns one fifteen-minute conversation into a week of drafts.

Your voice, captured properly

The first three weeks are spent recording how you actually argue: the phrases you reach for in sales calls, the things you are tired of hearing in your category, the examples you always return to. Everything after that is written against that record, not against a house style.

Two hours a week, spent on judgement

Your input is one working session and one review pass. Production is ours. If a founder is spending six hours a week on content, the system has been designed badly.

A buffer, so travel does not break the run

We keep two weeks of approved drafts ahead. The single most common cause of a founder programme collapsing is a busy fortnight, and a buffer removes it.

Also in Founder Authority Programme

Related services.

ClarifyCommandConvertCompound

Start here

Start with a conversation, not a proposal.

Send a brief → How we work