Blog
Field guidesFeb 22, 20261 min read

Our six-week content engagement explained

Exactly what happens, week by week, when a client engages us for a content engine build. No surprises.

Our six-week content engagement explained

Our six-week content engagement explained

We get asked frequently what a content engagement with us actually looks like week by week. This is the answer.

Week one: audit and brief

We start with what you have. Every client has some content — a company blog, a LinkedIn page, an email list with a few thousand subscribers. We audit all of it: what's working, what isn't, what the gap is between the content you're publishing and the content you need.

By the end of week one, we have a content brief: a documented answer to who you're writing for, what they need to know before they'll buy from you, and what format and frequency the content programme will follow.

Week two: strategy and architecture

We design the content architecture: the categories, the content types, the publication rhythm. We create the content inventory — a list of the first twenty pieces of content, prioritised by impact.

We also set up the tools. We work with PostWave for CMS and distribution. If you have an existing system, we work within it.

Weeks three and four: the first content sprint

We produce the first four pieces of content. These establish the voice and format and serve as the template for everything that follows. We present them for approval, revise, and publish.

Week five: the handoff preparation

We write the voice guide — a three-page document your team can use to maintain the programme after we exit. We document the content calendar, the distribution workflow, and the metrics framework.

Week six: the handoff

A two-hour working session with whoever will own the programme internally. We walk through the system, answer questions, and agree on the check-in cadence for the following three months.

After the six weeks

We offer a three-month light-touch retainer: one monthly check-in, feedback on one piece of content per month, and availability by email for quick questions. Most clients take it. After three months, the team is running independently.

This model is deliberate. We're building something you own, not creating a dependency on us.

Share

Ask AI

Have a question about this post?

Ask the AI reader. It pulls quotes from this post (and the rest of the archive) and answers in a few sentences.

Related

Keep reading.

Loading…