I build systems. Lately, with AI.
I'm Doug Kilgore. I'm in my mid-fifties, I've been designing and building software for more than 30 years, and today I work as a software architect. AI is part of how I work every day.
I've always built things on the side. Alongside my career I've started ten businesses, six YouTube channels and seven websites. A few failed, a few worked, and a channel I started in 2014 has been watched for 8.4 million hours and still earns on autopilot. Running them taught me what owner-operators deal with every day: too much work, no tech team, and no time for tools that don't deliver.
Early in my career, hard problems meant longer hours, and I burned out more than once. What fixed it was better systems, better habits, and a meditation practice I started 27 years ago. AI changed the equation again. The work is fast now, but it's easy to spend that speed going in circles. My job, and what I teach, is the part AI can't do for you: being the architect.
Why AI made it click
I spent a couple of years of evenings and weekends going deep on AI before most people around me took it seriously. The pattern I see over and over is simple. People who give AI real context, ask it for a detailed plan, and scrutinize that plan before anything gets built get great results with very little rework. People who rush it fight the AI all day. The difference is never the tool. It's what goes in.
When a developer brings me something they couldn't solve with AI, it usually comes down to what they have or haven't given it. So I give it better input: screenshots, what the data actually points to, and which generic advice is a trap in this case. Most of those problems are solved in 20 or 30 minutes.
I see the same thing with family. My parents are in their 80s and run an online store. My mom knows her craft inside out but used to get stuck writing how-to posts. Now she gives AI a short paragraph with everything that matters, and it turns into a full, useful write-up. Her knowledge in, real work out. They pick it up quickly, and if they can, anyone can.
I've also built real AI systems for my own projects, including the pipelines behind 82 videos: they took my time per video from about 30 hours by hand to about 4, and the cost per video from $30 down to $5 to $8.
What I believe
- AI is one of the most useful tools a business can have, when it's used properly. It speeds up the work and takes repetitive jobs off your plate.
- Slop is a skill problem, not an AI problem. Garbage in, garbage out. If you take the first default answer, you get what everyone else gets.
- This is acceleration, not annihilation. In my experience AI isn't replacing people. It's speeding up the work, and faster work creates new needs: someone has to steer it and check the quality.
- You stay in charge. The AI never picks the direction. Your knowledge goes in first.
What you'll find here
A free kit to start with, and soon a YouTube channel with three kinds of videos: essays on where AI is going, real builds shown end to end with what they cost, and updates when something important changes. No benchmark-of-the-week videos and no doom.