Skip to main content
Story, System, and Send are three chapters written in sequence, and Scale is the layer running underneath all three from the day the partnership begins.
The sequence is not arbitrary. A publishing engine pointed at an unclear message produces a great deal of visible work that says nothing in particular. A message with no engine behind it stays in a document. And both of them, unmeasured, become merely a matter of opinion. So we settle what is true first, then build the thing that operationalizes it, and then put it into the world, while measuring throughout.

​
The chapters

Chapter 1—Story

The message. Your conviction surfaced and shaped into effective marketing. Artifact: the Storybook.

Chapter 2—System

The technical infrastructure. Website, integrations, and analytics. Artifact: a live website.

Chapter 3—Send

The publishing. Podcast, content, email, and social, on schedule, over years. Artifact: a podcast.

Scale

The measurement layer. Performance data and a monthly audit that says plainly what worked and what didn’t.

​
The bookends

The two pieces of a partnership that usually go unnamed have names here. The Prologue is discovery, the Thesis, the proposal, and kickoff—the work of starting well. The Epilogue is offboarding done as an honored departure rather than an awkward silence, with a final review, a verdict on the thesis, a clean handoff of every asset, and an open door. Naming them matters because unnamed work tends to be unowned work. A kickoff nobody scheduled and a handoff nobody documented are the two most common ways a good partnership ends badly.

​
Timing, roughly

Most of Chapter 1 lands in the first thirty to sixty days, with the message revisited quarterly or annually thereafter. Chapter 2 typically lands in months two through five, depending on the size of the build. Chapter 3 begins once Chapter 1 has produced enough raw material to publish from, usually around month three or four, and then compounds for as long as the partnership lasts. These are typical shapes, not promises. Your sequence is set in your proposal and adjusted in the monthly audit as reality intervenes, which it does.

​
What ends a chapter

Each chapter has exactly one artifact, the single deliverable that says the chapter is finished. Story ends with a Storybook. System ends with a website that is live, indexed, and wired for performance. Send ends with a podcast that has published on a stable cadence. We are strict about this because “done” is the hardest word in agency work. An artifact gives it a definition you can hold in your hand.

​
Why Scale is not a chapter

Measurement is not a phase you graduate into. The infrastructure gets built once, inside System, but the measuring itself starts as soon as the website is live, so the baseline for judging the work is your actual starting position rather than a number reconstructed later from memory. Every month you receive an audit. It is written as an editor’s letter rather than a dashboard export—what the last period produced, what it did not, and what the next period is betting on. It is deliberately honest about the things that are not working, because a report that is always green is a report nobody can use.