I didn't disappear. I redesigned.

I've been quiet for about a month. Not because nothing was happening, but because I've been in the build.

A full content pipeline. A web app I launched and submitted to my first hackathon on the same day. The infrastructure that makes all of it possible without me living in it. Raising two young kids, ten acres, a full-time role, a graduate program, and every single thing on that list was made easier by AI and systems I built myself.

That's the proof of concept, and that's what I'm here to teach.

The content machine I was building

I input an idea. Claude writes the blog post and sends it to the blog. Then it converts the idea to a podcast script that sounds like how I talk, and generates show notes. The workflow fires in n8n. My AI voice clone records the podcast episode on ElevenLabs. HeyGen generates the talking-head video, and an agent completes it with automated b-roll and captions. Opus Clip pulls the short-form clips. Blotato distributes to every platform. Beehiiv gets the newsletter draft.

I never have to hit record. The AI does it.

One idea. More than twenty pieces of content. Less than an hour of total production time, compared with the five to six hours manual podcast production used to take.

My active time per week was two to three hours, and that was for the live tutorial and walkthrough videos I chose to record for YouTube. Not because the system required it.

What was working: Claude as the editorial brain. Every piece of content ran through a Claude Skill trained on my voice, my business model, and my rules.

The output sounds like me because I built the context, not because I got lucky with a prompt.

The pipeline wasn't fully automated end to end yet. Several steps were still in progress. I'm telling you about it because it's tempting to wait for perfect, but y'all deserve presence.

This is how you get the thoughts, the insights, the tools, and the worldview without me being the bottleneck. Consistency, scalability, sustainability.

Build the system once. Then let it run while you move on to the next idea.

The speaker outreach workflow

An automation is a workflow that does a specific job in your business without you being involved after it's built. It follows a predefined path. An agent takes it a step further by reasoning through multi-step decisions, doing tasks, and figuring out what needs to happen next without a fixed set of rules telling it what to do.

Most speakers spend hours a week hunting for stages. Finding the right contact, researching the event, writing a cold pitch from scratch, following up. I built a workflow that does most of that without me, and I was building an agent that took it even further.

Here's how the automation worked. A Google Sheet held my target events and organizer contact information. When I added a new row, n8n fired. Claude pulled the event details, cross-referenced my speaker bio and talking points, and wrote a personalized outreach email drafted to sound like I actually looked them up, because the workflow did.

The draft landed in Gmail ready for my review. I read it, tweaked if needed, and sent it.

The agent I was building did the hunting too. Instead of me adding rows to a sheet, it went out and found the events. It searched based on my speaker profile, my topics, my target audience, and the types of stages that made sense for where I was in my speaking career. It reasoned through which events were worth pursuing, found the right contact, and handed the result to the same outreach workflow.

The human checkpoint stayed intentional either way. I'm not sending automated cold emails to event organizers. But the research, discovery, positioning, and first draft are hours I'm not spending anymore.

If you book speaking engagements, consult, or do any kind of outbound that requires personalization at scale, this is worth thinking through.

Automate the research and the first draft. Keep the human in the send decision.

If this is your kind of conversation, join me for the next Seed & Society® newsletter.