The first production
implementation.

William DeCourcy spent his days leading lead generation and performance marketing at AmeriLife. In his off hours, he was building Professor Leads: a growth media brand with a weekly cadence across YouTube, TikTok, LinkedIn, X, Beehiiv, and a long-form blog.

The problem was obvious. A weekly multi-platform content machine needs someone operating it full time. William did not have that person. He had a laptop, a studio workstation, and a conviction that AI agents should be able to run most of the workflow. So he built it — on WExIQ's methodology, using himself as the first reference implementation.

Each week runs the same protocol. The pipeline produces 25 distinct pieces of content across six platforms: 5 YouTube Shorts, 5 TikTok clips, 10 LinkedIn posts, 2 X posts, 1 long-form blog post, and 2 newsletters (Beehiiv and the LinkedIn Playbook Preview).

Monday and Tuesday, an AI agent scans a Slack crosslink channel for a partner article and drafts five short-video scripts with Voice DNA checks. Wednesday is filming day — one batch of five clips on a dedicated Windows workstation with studio lighting. By Thursday, a Python pipeline trims silence and normalizes audio to broadcast standard, Opus Clip handles cross-platform scheduling, and an AI agent drafts platform-specific captions into the scheduler. Thursday through Saturday, the blog and both newsletters are drafted, quality-gated against Voice DNA and Brand Standards, and published. Friday afternoon, a health-check job pulls from nine data sources, runs nine reasoning passes for insights and recommendations, renders a PDF infographic, and emails the report via Resend.

No calendar invites. No standups. Just the pipeline running.

The pipeline definition lives in one JSON file. The production workflow reads it. The public /resources/content-pipeline page also reads it. When the pipeline changes, the public documentation updates on deploy. No drift.

Same principle on the analytics side: the weekly /healthcheck page renders from the same JSON archive the email report uses. The operator sees what the system sees, and so does anyone watching the brand.

This is a reference implementation on the founder's own brand, not a third-party client engagement. The YTD audience above reflects the first 113 days of a new media property — early-stage, pre-scale. The interesting signal is the operating system, not the reach.

What this case proves is straightforward: an agentic content pipeline can be built and running in under three weeks, cost-competitive with a single full-time hire, and observable enough that a founder can look at one URL on Friday afternoon and know exactly what happened this week. That is the product.