The system

One recording in. A week of work out.

The homepage version of this is five steps. This is what happens inside them: six stages, starting with who you are trying to reach and ending at published posts that sound like you, including what each one produces and where a person is still required.

The six stages

What happens between the recording and the post.

01Angles worth making
Your buyer studied before anything is written
What your buyer reads, watches and shares, studied first. The angles come out of that, so the work is aimed.
Before a line is drafted, the people you are trying to reach get read: what they already follow, the language they use for their own problem, and which of your positions actually lands with them. For one client that meant studying what the buyer wears, posts and shares before a single reel was cut. For another it meant separating three audiences, funders, families and the community, because the same footage has to say a different true thing to each. This is the step that decides what gets made. The rest of the pipeline decides how well it gets made.
02A written spec
Your language captured as a working specification
One session in. A file out: your cadence, your words, and the ones that are never yours.
Everything you have published gets read, and one session captures the positions that were never written down. The output is a file: cadence, the vocabulary that belongs to you, the vocabulary that never does, and worked examples of right and wrong. Specific enough that two different people produce recognisably the same brand from it, and specific enough that a check can run against it.
03A draft
Generation, with the specification as the input
Drafting runs against that file. The file is what makes the output recognisable, not the model.
This is the step people mean when they say AI, and on its own it is the cheap half of the job. A model given a topic and a tone adjective produces the average of everything it has read. A model given a detailed specification produces something recognisable.
04A candidate
The check, before a draft becomes a candidate
A draft with a blocked term never reaches the queue. A gate, not a warning.
Every draft is checked against your blocked-term list before a person ever sees it. A draft containing a blocked term does not reach the approval queue. Compliance is built in at that point rather than left to somebody remembering.
05Every format
Programmatic production
One source event becomes every format. The tenth piece costs what the first one did.
One source event becomes every format the channels need: landscape for the site, vertical for Reels and Shorts, square for Instagram, plus the written pieces. Rendered from templates, so the tenth piece costs what the first one did and nobody opens an editor.
06A published post
Approval, then publishing, then a written report
Finished work waits for your yes. Then it publishes, and a report says what shipped.
Finished work waits in a queue for a person. Approved work publishes on the cadence in the scope, to your accounts. A written report says what shipped and what the numbers did, on a fixed rhythm, whether or not the numbers were good.

Stage three, in practice

What a guardrail looks like when the words genuinely matter.

Insightful Recovery Solutions is a peer recovery practice. In that field the wrong noun is not a tone problem. It is a credibility problem with the exact people the work exists to serve, and it is the kind of mistake that gets screenshotted.

So the list is not advisory. These terms are checked at the pipeline, and a draft containing one does not become a post.

Blocked, cannot publish

addict
clean
abuse
substance abuser
junkie

Required instead

person in recovery
sustained recovery
recovery support
person-first language

The list is his, in his repository. When his field’s language shifts, he changes the file and everything downstream changes with it. The full account is on the Insightful Recovery Solutions case study.

The brand specification

The thing that gets handed over.

The Build phase hands over one repository. It holds the brand specification, the blocked-term lists the pipeline checks against, the render templates, and the publishing config, all versioned in git. It is the thing the client keeps.

It is the reason this is not a rental. The specification, the term lists, the render templates, and the publishing config are files in a repository under your account, from the first commit onward. If the engagement ends you keep operating, and if you hire someone they inherit a written document.

Build and Run

What the engagement covers.

Two phases. The first installs the pipeline and hands over the repository it lives in. The second operates it.

Build, one time: Your language captured as a specification, the blocked and required term lists, the render templates, your channels wired in, and a first run of work produced against all of it. The repository is handed over in the first week.
Run, monthly: The pipeline operated on a named cadence. Every draft is checked against your term lists before it reaches you, finished work waits for your approval, and a written report says what shipped and what the numbers did.

Fit

Where this does not work.

Nobody will be on camera: The specification is built from your material and the pipeline runs on what you bring it. A company that wants content made with nobody from the business in it is better served by a studio, and the answer on the call will say so.
Approval needs a committee: One person has to be able to say yes. If every post routes through a group, the approval gate becomes the constraint this was meant to remove.

The obvious question

If the operator is unavailable.

The work does not live in one person’s head. It lives in four things, and all four are in your name from the first week.

The specification: A written file in a repository under your account, from the first commit onward
The term lists: The blocked and required language, versioned in the same repository
The templates: The render config that produces every format, so the outputs can be rebuilt
The accounts: Every channel, login and analytics property in your name, never ours

What stops is the cadence. Nothing above it stops, and anyone you bring in starts from a written document instead of an interview. You can check all four on the first day of the engagement.

Content Infrastructure

Four connected layers. Your perspective becomes pipeline.

Not ghostwriting. Not another AI tool. A creative system that captures your thinking, enforces your voice, produces multi-format content, and distributes it. All from 30 minutes of your time per week.

Your Brand

Hover each area to learn more

Video, social, carousels, brand docs. All produced from your voice system. All published on schedule. Built in 30 days. Voice carried at scale.

Before / After

Before and after content infrastructure.

Before

×Founder approves every post, video, and campaign
×Content takes 4–7 days from brief to publish
×No documented brand rules. Every asset is a one-off
×Team can’t execute without founder in the room
×Tools don’t talk to each other. Manual everything

After

System enforces brand rules. Founder reviews monthly, not daily
Content cycle reduced from 6 days to under 4 hours
Brand voice codified as guardrails. Consistent across every channel
Team executes from templates and workflows without asking
Intake, agents, render, delivery. Running end to end

Where a person is still required

The parts that are judgement.

Every position and every claim: What is true about your company, and what you are willing to say publicly, is not a thing a pipeline can determine.
The specification itself: Written from your material, signed off by you before anything is produced against it.
Approval before publish: A standing gate with no path around it. You can widen it for formats that have been right consistently. You cannot accidentally remove it.
Anything a mistake would be costly to make: Regulated claims, anything about a named person, and anything you would have to walk back. Those route to a person by default.

See where your content stands first.

The scan scores your published pages across five dimensions and shows your biggest finding in full. No email required to read the result.

See what it produced

Or reach out directly

Tell us about your brand.

Name, email, and one line. We'll get back to you within 24 hours.

What happens between the recording and the post.

01Angles worth making

Your buyer studied before anything is written

What your buyer reads, watches and shares, studied first. The angles come out of that, so the work is aimed.

Before a line is drafted, the people you are trying to reach get read: what they already follow, the language they use for their own problem, and which of your positions actually lands with them. For one client that meant studying what the buyer wears, posts and shares before a single reel was cut. For another it meant separating three audiences, funders, families and the community, because the same footage has to say a different true thing to each. This is the step that decides what gets made. The rest of the pipeline decides how well it gets made.

02A written spec

Your language captured as a working specification

One session in. A file out: your cadence, your words, and the ones that are never yours.

Everything you have published gets read, and one session captures the positions that were never written down. The output is a file: cadence, the vocabulary that belongs to you, the vocabulary that never does, and worked examples of right and wrong. Specific enough that two different people produce recognisably the same brand from it, and specific enough that a check can run against it.

03A draft

Generation, with the specification as the input

Drafting runs against that file. The file is what makes the output recognisable, not the model.

This is the step people mean when they say AI, and on its own it is the cheap half of the job. A model given a topic and a tone adjective produces the average of everything it has read. A model given a detailed specification produces something recognisable.

04A candidate

The check, before a draft becomes a candidate

A draft with a blocked term never reaches the queue. A gate, not a warning.

Every draft is checked against your blocked-term list before a person ever sees it. A draft containing a blocked term does not reach the approval queue. Compliance is built in at that point rather than left to somebody remembering.

05Every format

Programmatic production

One source event becomes every format. The tenth piece costs what the first one did.

One source event becomes every format the channels need: landscape for the site, vertical for Reels and Shorts, square for Instagram, plus the written pieces. Rendered from templates, so the tenth piece costs what the first one did and nobody opens an editor.

06A published post

Approval, then publishing, then a written report

Finished work waits for your yes. Then it publishes, and a report says what shipped.

Finished work waits in a queue for a person. Approved work publishes on the cadence in the scope, to your accounts. A written report says what shipped and what the numbers did, on a fixed rhythm, whether or not the numbers were good.

What a guardrail looks like when the words genuinely matter.

So the list is not advisory. These terms are checked at the pipeline, and a draft containing one does not become a post.

Blocked, cannot publish

addict
clean
abuse
substance abuser
junkie

Required instead

person in recovery
sustained recovery
recovery support
person-first language

The thing that gets handed over.

What the engagement covers.

Two phases. The first installs the pipeline and hands over the repository it lives in. The second operates it.

Build, one time

Your language captured as a specification, the blocked and required term lists, the render templates, your channels wired in, and a first run of work produced against all of it. The repository is handed over in the first week.

Run, monthly

The pipeline operated on a named cadence. Every draft is checked against your term lists before it reaches you, finished work waits for your approval, and a written report says what shipped and what the numbers did.

Where this does not work.

Nobody will be on camera

The specification is built from your material and the pipeline runs on what you bring it. A company that wants content made with nobody from the business in it is better served by a studio, and the answer on the call will say so.

Approval needs a committee

One person has to be able to say yes. If every post routes through a group, the approval gate becomes the constraint this was meant to remove.

If the operator is unavailable.

The work does not live in one person’s head. It lives in four things, and all four are in your name from the first week.

The specification

A written file in a repository under your account, from the first commit onward

The term lists

The blocked and required language, versioned in the same repository

The templates

The render config that produces every format, so the outputs can be rebuilt

The accounts

Every channel, login and analytics property in your name, never ours

What stops is the cadence. Nothing above it stops, and anyone you bring in starts from a written document instead of an interview. You can check all four on the first day of the engagement.

The parts that are judgement.

Every position and every claim

What is true about your company, and what you are willing to say publicly, is not a thing a pipeline can determine.

The specification itself

Written from your material, signed off by you before anything is produced against it.

Approval before publish

A standing gate with no path around it. You can widen it for formats that have been right consistently. You cannot accidentally remove it.

Anything a mistake would be costly to make

Regulated claims, anything about a named person, and anything you would have to walk back. Those route to a person by default.