Technical
The Content Pipeline, Eleven Months Later: What the Machine Looks Like Now
I have published 335 articles in 335 days. That is not willpower. It is a pipeline. Eleven months of refinement turned a blog into a system that runs with less effort than the first month.
Morning, 15 Minutes
I wake, pour coffee, and write the excerpt and outline for todays article. That is it. The outline contains title, target keyword, three section headers, and a closing line. The excerpt is the first two sentences of the article.
This is the only creative work of the day. Everything else is execution.
Mid-morning, 30 Minutes
Between client calls I draft the article from the outline. I use Claude Code as a writing partner but the voice is mine. The model is an editor, not a ghostwriter. If an article sounds like it, I rewrite it.
Pipeline Automation
A Python script reads my drafts, validates frontmatter, checks for forbidden patterns (em dashes never survive), and posts to the peaklight.ai API. The same script schedules the next days newsletter digest.
drafts/2026-03-30.md -> validate -> POST /posts -> schedule digestMonthly Batch
The first of each month I run a batch script that creates the next months articles as drafts with publish dates pre-set. This is the artifact I am writing right now for March 2026.
The batch script has paid for itself every month. Manual entry for 30 articles is a full day. Batch entry is 10 minutes.
The Discipline That Stuck
Write the outline the night before when the topic is fresh. Write the article the morning after when the body is ready to flow. Never publish without a real reader being the imagined audience. Never skip a day. Never apologize for a short article. Never miss the deadline.
The Discipline That Broke
Tracking every word count. Tracking every SEO score. Tracking every social share. These were busywork. I dropped them. Engagement improved.
The Payoff
Consulting leads that arrive already pre-qualified because they read the articles. Repeat clients who cite a specific post. A growing newsletter that produces predictable signal. A portfolio that compounds.
Reading
Ali Abdaals content systems writing and Tiago Fortes Second Brain taught me the pipeline mindset. The daily writing habit is older than the tools. The systemization is what AI made possible at this scale.
RELATED READING
The Consulting Shift I Am Making In Year Two
After a year of writing and building, my consulting practice is changing shape. Shorter engagements. Sharper outcomes.
ReadThe Frontend Shift: Shipping Less JavaScript In Year Two
A year ago I reached for Next.js for everything. This year I often reach for nothing.
ReadThe Serverless Lesson I Would Write On A Sticky Note
After a year of shipping serverless projects, one rule explains most of the wins and all of the losses.
Read