Creative

Plan content for every audience and every stage

Start from a business goal, give each audience its own branch, and plan what to publish at each stage and on which channel.

Start from a template

A content strategy template you can clone. Describe your launch in the root and plan each audience's content in its own branch.

Clone this template

How it works

Start with the goal the content has to serve, such as a product launch or more sign-ups. Each audience gets its own branch, and what you will publish for them sits underneath.

  1. State the goal. Ask for a content strategy for that goal. The model proposes audiences, content types and channels.

  2. Give each audience a branch. Under each audience, ask what they need to read at each stage: before they know they have the problem, while they compare options, and when they are ready to buy.

  3. Plan the channels. Under any piece, ask where else it can go. A research report might also run as a blog post, a webinar and a sales deck.

  4. Look for gaps. A stage with no content under it is a gap. Two branches that say the same thing are duplicate work.

Why a map instead of a strategy document

A long strategy document can miss an audience or a stage without anyone noticing. On a map, an empty branch is easy to spot. When priorities change, you can delete a branch without rewriting the rest.

Example

Say you run content at an edtech company before the back-to-school season. You have branches for teachers, school administrators and parents. Teachers want classroom setup and curriculum ideas, and administrators want budget cases and rollout timelines. Teacher testimonials come up under all three audiences, so you make them the main piece and cut a version for each.

Now try it yourself

Build a content strategy for a B2B cybersecurity company launching its first developer-focused product
The strategy sits at the intersection of two audiences: security decision-makers who sign contracts and developers who choose tools. Content must speak both languages — technical credibility for devs, risk-reduction narrative for buyers — without diluting either message.
How do we create content that serves both audiences without being generic?
Create two content tracks with shared assets. Technical track: open-source tutorials, API documentation walkthroughs, and benchmark comparisons (developers share these). Business track: breach cost calculators, compliance checklists, and ROI case studies (buyers forward these). Bridge content like 'How Our Engineering Team Evaluates Security Tools' serves both.

Ready to try content strategy?