Brand-voice content pipelines at cadence.
Named brand-voice writer Skills we run for a handful of clients. Each one produces research-grade, Generative Engine Optimization (GEO) optimized content in the client's voice at a cadence traditional agencies cannot match.
- Stack
- Claude · Claude Skills · Airtable · Firecrawl · DataForSEO · Perplexity API
- Time
- ~2 weeks to build a brand Skill · ongoing to operate
- Cost
- ~$0.30–$1.20 per article in API fees
- Shipped
- Running against live client brands today
Context: brand voice is the hard problem, not volume.
Volume is not the hard part of AI content. Volume in an actual brand voice, with research behind every claim, and with Generative Engine Optimization (GEO) chunking baked in. That is the hard part. Most AI content pipelines we audit for clients fall apart at the voice layer. The output reads generic inside a week.
The fix is a brand-specific writer Skill. One per brand. The Skill encodes the voice, the house style, and the chunking rules, and it reruns against new topics without drift. Our pipeline produces articles that get cited by Perplexity and ChatGPT because they are chunked, schema-rich, and written in a voice the brand's editor actually recognizes.
The approach: seven stages, one required human.
Architecture walkthrough, top to bottom.
The 10-point quality control rubric.
Every article gets scored by the editor against this rubric before it publishes. Anything scoring below 8 of 10 goes back for revision.
- Does the first sentence of each H2 directly answer the implied question?
- Are there at least 3 citable chunks (300–500 words, self-contained, no pronoun dependencies on surrounding sections)?
- Is there a numbered list or table for at least one key concept?
- Does the FAQ section have 3–5 genuine questions, not filler?
- Is the brand voice consistent with the voice guide? (Specific tone rules, not vibes.)
- Are claims backed by named sources, not vague "studies show"?
- Is the schema payload valid and aligned to the article's actual structure?
- Is the meta description 150–162 characters and genuinely descriptive?
- Are internal links included to the three nearest pillar pages?
- Would you personally share this on LinkedIn without being embarrassed?
What we shipped.
- Brand-specific writer Skills for a handful of clients. Each one encodes that brand's voice, house style, and chunking rules
- The general-purpose
winston-geo-articleSkill we use for new brands before we invest in a brand-specific writer - Zapier or Make workflows plus the Airtable template they read from and write to
- The editor rubric plus a training doc for onboarding new editors
Lessons.
- Skip the human editor = skip the quality. No amount of prompt engineering fixes this. We tested. Pipelines without the editor step produce work the team will not sign their name to.
- Pipeline velocity is rate-limited by editor throughput, not API throughput. The APIs can run faster than the editors can review. If you want more volume, you hire more editors. Not more compute.
- Naming individual agents matters. When the outline is wrong, you want to debug "outliner" not "the pipeline." Named agents make it obvious which stage failed and cut debugging time by more than half.
- Brand voice is downstream of a voice guide. Pipelines without an explicit, written voice guide regress toward generic LLM voice within three or four articles. The voice guide is load-bearing infrastructure.