Creation pipeline
A Page Brief moves through seven states from topic to published page, agents doing the heavy lifting while you steer each step.
The creation pipeline takes a Page Brief from a topic to a published page. It runs through seven states. Agents do the heavy lifting at each one, and you steer: you set the inputs, decide which feedback to apply, and approve what ships.
The unit of work is the Page Brief. Everything in this flow happens to a brief, and the brief carries its history from first outline to live URL. For the step-by-step version of this flow, follow from Opportunity to published page.
A brief can start three ways
How a brief begins shapes what it's tied to.
| Starting point | When you use it | What it's tied to |
|---|---|---|
| From an accepted opportunity | The common path, after you triage research | The opportunity's keyword, intent, and personas |
| From scratch | You already know the page you want | Whatever inputs you set by hand |
| From a live page | A page is decaying and needs a refresh | The existing URL, so you improve its history |
The third path matters more than it looks. A refresh brief stays attached to the live page's URL, so you build on the page's track record instead of starting a new one beside it. You improve a page, you don't duplicate it. GrowthOS routes overlapping opportunities here for you, and refresh a decaying page walks that path in practice. See opportunities for where most briefs come from.
The seven states
A brief moves forward one state at a time. Two states are terminal.
| State | What happens |
|---|---|
| Briefing | You set the inputs; an agent will generate a structured outline. |
| Writing | An agent drafts the full article; you edit in a rich-text editor. |
| Reviewing | Internal and external reviewers leave feedback as annotations. |
| Editing | You apply the feedback worth applying; an agent regenerates sections as needed. |
| Ready | You finalize the SEO metadata: title, meta description, slug. |
| Published | GrowthOS creates or updates the live page record. |
| Discarded | Terminal. GrowthOS archives the brief for history. |
A brief enters at Briefing from any of the three starting points above, then moves Briefing -> Writing -> Reviewing -> Editing -> Ready -> Published. Editing can loop back to Reviewing whenever a section needs another pass.
Five inputs shape the output
You decide most of what makes a page good before an agent writes a word. Five inputs do the heavy lifting.
| Input | What it sets |
|---|---|
| Title | The page's promise to the reader and the engine |
| Primary keyword | The query the page is built to win |
| Search intent | The durable want the page has to satisfy |
| Personas | Who the page is written for, in their language |
| Content Template | The page's form: funnel stage, outline, post-processing |
Four of these are obvious. The Content Template is the quiet one, and it's the highest-leverage lever in the brief.
A Content Template is a reusable blueprint that decides a page's shape. It sets the funnel stage, the outline structure, and the post-processing an agent runs after the draft. The same topic through a comparison template versus a case-study template produces two different pages: different sections, different evidence, different reader. Choosing the template is the decision that does the most to determine what comes out, which is why it's worth getting right at the briefing step rather than fixing later. Content Templates covers how to pick one, and taxonomy and scoring covers how a page's type and template steer the work that runs on it.
How review works
Review fits the way teams approve content, with people inside and outside the workspace.
- Internal reviewers annotate inside the editor, marking up the draft in place.
- External reviewers, like a client or an outside editor, open a public link with no account and annotate the same way.
- You decide, feedback by feedback, what gets applied. Nothing changes the draft until you act on it.
That last point keeps the operator in control. Reviewers raise issues; you choose which ones move the page. An agent will regenerate a section when you ask it to, but the call to apply feedback is always yours. Review and publish walks the review mechanics step by step. The split between agents and operators runs through the whole platform, not just review. See agents and operators for the full model.
Common questions
Who writes the article? An agent drafts it from the brief. You edit, direct, and approve. The first draft is a starting point, not the final word.
Can a reviewer without an account leave feedback? Yes. External reviewers open a public link and annotate the draft directly, no login required.
What happens at Published? GrowthOS creates the live page or updates an existing one, then the page enters your portfolio and starts accumulating performance signals.
Where to go next
Last updated at June 3, 2026
Opportunities
An opportunity turns one piece of keyword research into a decision you can triage: a query, the intent behind it, where it came from, and the page that would answer it.
Portfolio snapshots
The reports area turns your accumulated page and performance data into shareable, narrative snapshots you send by link, not a raw data export.