Six months ago, publishing a blog post on my site required about four hours of focused work. Research, outline, draft, edit, format, create graphics, write the meta description, schedule social media posts, and queue the email notification. Each step was manual. Each step depended on me remembering to do it and having the energy to do it well.
Today, the same process takes about ninety minutes of my active time, and most of that is editing. The rest is handled by an automated pipeline that moves content from idea to published post with AI doing the heavy lifting at each stage.
This is how I built it, and how you can build something similar.
The Pipeline Architecture
Let me show you the full pipeline first, then break down each stage.
Stage 1: Ideation and scheduling — Topic selection, editorial calendar placement, keyword research
Stage 2: Research and briefing — Source gathering, competitor content analysis, outline creation
Stage 3: Drafting — First draft generation following the outline and voice guidelines
Stage 4: Editing — Human review and refinement, fact-checking, voice adjustment
Stage 5: Production — Image generation, formatting, meta data, internal linking
Stage 6: Publishing and distribution — CMS upload, social media posts, email notification
Stages 1-3 and 5-6 are largely automated. Stage 4 is intentionally human-intensive. This is the critical design principle: automate the mechanical work, keep the judgment work human.
The total pipeline from idea to published takes about twenty-four hours of elapsed time, with ninety minutes of my active involvement spread across two sessions (one for briefing and one for editing). The rest is AI processing and automation.
Stage 1: Ideation and Scheduling
I maintain an editorial calendar that plans content four weeks ahead. This calendar is not generated by AI. It reflects my strategic decisions about what topics to cover, what keywords to target, and how topics connect to each other and to my business goals.
What AI does help with: keyword research and topic validation. I describe a topic to Claude and ask: “What questions are people actually asking about this topic? What related topics would make good companion pieces? What angle would be most useful for founders in the DACH market?” The AI suggests angles and validates that the topic has search demand.
I also use AI to identify internal linking opportunities. “Given my existing published articles on [list], which of my planned topics would create the strongest internal link connections?” This produces a content strategy where articles reinforce each other rather than existing in isolation.
The editorial calendar lives in a simple spreadsheet with columns for: publish date, topic, target keyword, outline status, draft status, edit status, and published status. Nothing fancy. The pipeline automation reads from this spreadsheet to know what to work on next.
For founders building their first content strategy, the editorial calendar is the foundation. Without it, AI-produced content is random and disconnected. With it, every piece serves a purpose.
Stage 2: Research and Briefing
When a topic is scheduled for production, the research stage triggers automatically.
Step 1: Competitor content scan. An AI agent searches for existing content on the topic, summarizes the top ten articles, and identifies what they cover well and what they miss. This ensures my content adds something rather than repeating what already exists.
Step 2: Source compilation. If the topic relates to my existing expertise (most do), the agent pulls relevant context from my knowledge base: past writing, client experiences, Startup Burgenland data, or Vulpine Creations examples. For topics requiring external data, it compiles relevant statistics and references.
Step 3: Outline generation. Based on the research, the agent produces a structured outline with: hook opening, four to six H2 sections, key points for each section, planned examples, and closing takeaways. It also suggests internal links to existing articles.
Step 4: My review (10 minutes). I review the outline, adjust the structure if needed, add personal examples the AI could not know about, and approve for drafting. This is the first human touchpoint.
The research stage produces what I call a “content brief” that contains everything the drafting agent needs: outline, source material, voice guidelines, internal link targets, and my specific notes.
Stage 3: Drafting
The drafting agent receives the content brief and produces a first draft. This is the stage where training AI on your brand voice matters most.
My drafting agent has permanent context structured in XML blocks so each piece of context has a clear purpose:
<system_context>
<voice_profile>[Five pages of guidelines, sentence patterns, and banned words]</voice_profile>
<style_guide>[Formatting rules, header conventions, link conventions]</style_guide>
<audience>[Who reads this blog, what they know, what they need]</audience>
</system_context>
<few_shot_examples>
<example type="opening">
Last November I raised Vulpine's base package from EUR 2,400 to EUR 3,800.
Three clients left. Seven new ones signed within six weeks.
</example>
<example type="technical_explanation">
The Kleinunternehmerregelung keeps you VAT-exempt under EUR 55,000 annual
revenue. No Umsatzsteuer, simpler bookkeeping, less paperwork.
</example>
<example type="personal_anecdote">
I was a grown man. A consultant. I dealt in strategy frameworks and
competitive analysis. The idea that I'd be sitting in a hotel room trying
to do card tricks would have made my colleagues laugh.
</example>
</few_shot_examples>Three to five few-shot examples are the single most reliable way to steer output format, tone, and structure. More reliable than pages of abstract instructions. Why? Because the AI pattern-matches against concrete samples. It extracts rhythms, vocabulary choices, and structural habits that explicit rules cannot fully capture. I include diverse examples — openings, technical explanations, personal stories, closing takeaways — so the AI has a reference for every section type.
With this context, the agent produces drafts that are recognizably in my voice. Not perfect, but close enough that editing is refinement rather than rewriting.
The drafting process is section-by-section. The agent writes each H2 section individually rather than generating the entire post at once. This produces better results because each section gets focused attention, and the agent can reference earlier sections for coherence.
Output: a complete first draft of 2,000 to 2,500 words, formatted in markdown, with internal links placed, and [VERIFY] flags on any factual claims that need checking.
Stage 4: Editing (The Human Stage)
This is where I spend most of my active time, and it is non-negotiable. The editing stage has three components:
Voice refinement (30 minutes). I read the entire draft and adjust anything that does not sound like me. AI drafts tend toward a slightly formal, slightly generic register. I inject personality, adjust the rhythm, add humor where appropriate, and remove any phrases that feel artificial.
Specific things I watch for: overuse of transitional phrases (“moreover,” “furthermore,” “in addition”), overly balanced statements where I should take a clear position, and generic examples where a specific personal example would be stronger.
Fact verification (15 minutes). Before I manually check, I run a quality control prompt with structured evaluation:
<evaluation_criteria>
<criterion name="factual_accuracy">Are all claims verifiable? Flag specific
statistics, named studies, and company data with sources.</criterion>
<criterion name="voice_match">Does this sound like Felix or like a polite
text-generation committee?</criterion>
<criterion name="actionability">Can the reader implement this today?</criterion>
</evaluation_criteria>Every [VERIFY] flag gets checked. Statistics get sourced. Claims get validated. References get confirmed. Catching what AI gets wrong at this stage prevents publishing errors that damage credibility.
In my experience, about ten percent of AI-drafted factual claims have issues ranging from outdated information to outright fabrication. This is not a knock on AI. It is the reason human editing is part of the pipeline.
Structural adjustment (15 minutes). Does the article deliver on the headline’s promise? Is the opening compelling? Does each section earn its place? Is the closing actionable? Sometimes sections need reordering, expanding, or cutting. The AI draft is a strong starting point, but it is not the final architecture.
Total editing time: sixty to seventy-five minutes. This is the most valuable time I spend on content because it is where my specific expertise, experience, and judgment differentiate my content from AI-generated generic content.
Stage 5: Production
After editing, the automated production stage handles everything needed to turn a markdown document into a ready-to-publish blog post.
Image generation. An AI agent generates a header image based on the article topic and my image style guidelines. I have a prompt library for consistent visual style. The agent generates three options; the automation selects the one that best matches the style parameters.
Metadata generation. The agent produces: SEO meta description (under 160 characters), Open Graph description, and social sharing text for three platforms.
Formatting. The markdown is processed into the final format for my CMS (Astro-based static site). Internal links are verified (no broken links). Header hierarchy is checked. Reading time is calculated.
Social media drafts. The agent generates platform-specific posts for LinkedIn, Twitter/X, and any other active channels. Each post is adapted to the platform’s format and audience expectations.
This entire stage runs automatically and takes about five minutes of AI processing time. The only human check is a quick review of the generated image and meta description, which takes about two minutes.
Stage 6: Publishing and Distribution
The final stage is fully automated and triggered when I mark a post as “approved” in the editorial calendar.
CMS publishing. The formatted post with metadata and images is deployed to the site. For my Astro-based site, this means committing to the repository and triggering a build.
Social media scheduling. The platform-specific posts are scheduled across the week following publication. Not all at once; staggered to maximize visibility.
Email notification. If the post is part of the weekly newsletter, it is automatically included in the next newsletter draft. If it warrants a standalone email, an email draft is generated for my review.
Analytics tracking. Baseline metrics are noted so I can compare performance to targets after one week and one month.
The publishing stage requires zero active time from me once I hit “approve.” This is the payoff of building the pipeline properly: the last mile of content distribution, which is tedious and easy to forget, happens automatically.
Building This Yourself: The Practical Path
You do not need to build this all at once. Here is the order I recommend:
Month 1: Manual pipeline with AI drafting. Use AI for the drafting stage only. Everything else (research, editing, formatting, publishing) stays manual. This proves the concept and builds your prompting skills.
Month 2: Add research and production. Automate the research brief generation and the post-editing production steps. You are now only manually doing ideation, editing, and publishing.
Month 3: Add distribution. Automate the social media and email distribution. You are now manually doing ideation and editing only, which is where your time should be spent.
Month 4: Refine. Optimize each stage based on three months of data. Which research briefs need the most adjustment? Where does the drafting agent consistently fall short? What production steps need human review? Refine based on real experience.
At each stage, the AI workflow patterns are the same: define the input, write the instructions, specify the output format, provide examples, and include quality checks.
The Results
Before the pipeline: two to three blog posts per month, each taking four hours. Total: eight to twelve hours per month of content production.
After the pipeline: four to five blog posts per month, each taking ninety minutes. Total: six to seven and a half hours per month of content production.
More content, less time. But the bigger win is consistency. Before the pipeline, I would skip weeks when other work was busy. The pipeline keeps content flowing because the automated stages run regardless of my schedule. I only need to be present for the editing sessions, which are easier to schedule than full writing sessions.
The quality has also improved. When I was writing everything from scratch, my energy and attention varied from post to post. Now, the AI draft provides a consistent baseline, and my editing energy goes to making each post genuinely good rather than just getting words on the page.
Takeaways
-
Design the pipeline around one human touchpoint: editing. Automate everything before and after the editing stage. Your time and judgment should concentrate on making AI-drafted content excellent, not on mechanical production work.
-
Build incrementally. Start with AI drafting only. Add research automation, then production automation, then distribution. Each phase adds one layer of automation.
-
Invest heavily in your voice profile and drafting context. The quality of the AI draft determines how much editing you need. Five pages of voice guidelines and example articles pay for themselves immediately.
-
Keep the editorial calendar human-driven. Strategic decisions about what to write, when, and why should not be automated. They should reflect your business goals and audience needs.
-
Measure before and after. Track posts per month, time per post, and content consistency. These metrics prove the pipeline’s value and identify stages that need improvement.
