We have a 14-chapter enterprise whitepaper at ThinkingAI, a full handbook on running growth with analytics agents. Product marketing wrote it, and I re-scoped how it goes out. Most teams park the whole PDF behind one form, point some traffic at the landing page, and wait. I chose to slice it, with an exec sponsor signing off: I take each chapter apart into public pieces that rank and get shared, while the chapter's actual playbook stays behind the download. The download becomes a qualified lead. Here is how it runs, including the part where a live trial caught the pipeline making things up.
One chapter becomes four things
Every chapter turns into a public blog, a LinkedIn post that points to it, a newsletter feature, and the gated playbook. Each output has one job. The blog has to rank, and LinkedIn and the newsletter send readers to it. Then the blog pitches the full playbook, which sits behind a form. Someone who reads the free version and still wants the complete workflow, the templates, and the benchmarks is a real prospect, and after the form we know who they are.
The flow only works in that order. On LinkedIn the link goes in the comments and always points to the blog and never straight to the download, so the pitch happens on a page we control and the platform sees a native post.
The free-vs-gated boundary is the control
Get this line wrong and the whole engine breaks. Too thin and the blog reads as an ad and never ranks. Too generous and it answers everything, and the download has no reason to exist. So the split is fixed, and it is the same for all 14 slices.
In the public blog I lead with a keyword-first H1 and a 50-word answer, quantify what doing nothing costs, name 3 to 4 root causes, and walk the approach at concept level (named steps, what the agent monitors and drafts, where the human approves). I close with one anonymized outcome, metric given as a range, and an FAQ with schema markup plus internal links to sibling chapters.
Behind the download I put the full workflow with the queries, schemas, and thresholds, the complete event taxonomy, the templates and dashboards, the benchmarks and diagrams, and the other 13 use cases. We publish the concept and keep the execution behind the form. A red-line pass checks every draft against that line, and it has caught a breach once.
Waves sequenced by search demand, with a KPI gate
I set the publishing order by search demand. Kimi (one of the pipeline's models) ranked all 14 chapters by buyer fit, then I validated every head keyword against Ahrefs (US). The rule: lead with winnable, high-intent clusters, and treat the high-volume, hard-to-win terms as slower authority plays.
Wave 1, weeks 1 to 3, is quick wins plus real volume: high-value user re-engagement reframed as churn prevention, the top pain for subscription apps, creative lifecycle management (rising queries, high commercial intent), data development and governance (big, moderately winnable, builds enterprise trust), LTV lifecycle operations (an exec KPI and evergreen, though a hard SERP), and sales campaign attribution (broad demand, an authority play). Wave 2, weeks 4 to 7, goes vertical: ad monetization, game economy health, short-form drama retention, complaint investigation, release instrumentation. Wave 3 holds the four chapters with jargon-heavy or thin standalone demand for cluster support later.
Wave 2 waits until I read Wave 1: rankings, traffic, download conversion. The gate is directional and the rule is short: if no chapter has reached page two by week four, I rewrite the boundary before committing the next five chapters.
The cadence: two chapters, four pieces, blog first
Two chapters a week means four pieces of content. The blog always publishes first, for two reasons: LinkedIn needs a live destination, and search engines start indexing before the social push. The week runs Tuesday blog A, Wednesday blog B, Thursday LinkedIn A pointing at blog A, Friday LinkedIn B pointing at blog B, and Monday the next pair enters production. Each newsletter issue features that week's strongest piece.
Nine stages, two human gates, no self-grading
Models do almost all of the 9-stage production line. Stage 0 slices the chapter and sets the scope. DeepSeek drafts the outline (angle, audience, gating boundary). Claude reviews it. Ahrefs keyword research locks the main keyword before a single body sentence exists. The draft runs 1,400 to 1,800 words in the house voice. A red-line review scores it and anything under 8/10 goes back. Claude does the final edit plus meta: title, slug, summary, SEO, FAQ schema. Then the first human gate: I approve the blog, the first artifact that reaches me. After that the pipeline generates the LinkedIn post and newsletter feature, written for a cold first-time reader, and I approve those at the second gate. The last stage packages everything and puts it on the calendar.
The writer, the reviewer and the second reviewer are always different models. Nothing grades its own work. I approve twice per chapter.
What the Chapter 10 live trial caught
Chapter 10 ran the full pipeline as a live trial, and that run is why I trust the gates. The red-line review caught three things before any of them reached a reader: a gating breach, where the draft gave away material that belongs behind the form; an em dash, which the house style bans; and a fabricated stat, a number that appears nowhere in the source chapter. The third one is the reason the review stage exists at all. The judgment that was wrong on that run was mine: I had drawn the first gating line too generously, and I moved it afterward.
Keyword research proved itself on the same chapter. The draft H1 targeted “win back lapsed subscribers”, which Ahrefs put at ≈0 searches. I retargeted it to “churn prevention”: 600 monthly searches at keyword difficulty 5. Same chapter, same substance, and the new H1 turned an invisible page into a winnable one.
Where it stands
The whole line has run once. The pipeline drafted, red-lined and finalized Chapter 10's blog, then produced its LinkedIn card, caption and newsletter feature. All that is left is my go: lock the revision loop, start Wave 1. Once that lands, the line produces two chapters a week, with two approvals per chapter and nothing else on my desk. The baseline is honest about where it starts: blog traffic near zero because the blog is new, and a newsletter list of 1,000-plus. I will know by the end of Wave 1 whether the split holds: five chapters live, and the download conversion on them decides whether Wave 2 ships.