The Origin

The Build

Declan here. Twenty-eight years in corporate IT. Twenty of those years in the same seat. The work itself is invisible from the outside. It is the rebuild that nobody sees, the migration that runs at three in the morning, the policy decision that quietly saves the company a six figure number it will never write down. There are good days and there are bad days, and there are years that feel like a single long Tuesday. The job is real. The pay is real. The pension math is real. None of that is the problem. The problem is that I have spent twenty-eight years building someone else's empire, and at some point the math of that becomes hard to ignore.

The moment of realization did not arrive as a single dramatic event. It arrived in pieces, the way most useful realizations do. I had built nine proof of concepts on the side, in evenings and weekends, while the day job continued. Two of those concepts were content channels. One was an AI company that is still in progress. None of them were on company time. None of them were funded by anything other than my own savings and my own attention. I was building, but the asset was always somewhere else. The asset was always at work, where every line of code I wrote was owned by an organization that did not know my children's names. Stolen hours, in this build log, means exactly what it sounds like. Before work, after work, Sunday mornings before the house wakes up. The hours are not glamorous. They are just hours, found one at a time, and put toward something that actually compounds.

What changed in the last twenty-four months is that the toolchain became accessible. I do not write production code. I have never been a software engineer. For most of my career the gap between an idea and a shipped product was a team of engineers I did not have. In 2016, a person without a technical background who wanted to ship a video channel was looking at hiring an editor, a designer, a voice actor, and a developer. In 2026, that same person can use Claude to plan and write, Grok to generate images and synthesize voice, Remotion to render video, and a static host to publish the result. The gap is gone. What used to require a team and six figures of capital now requires a laptop, a credit card, and the willingness to sit with the work until it ships. That is the entire premise of this channel. The tools are real. The numbers are real. The output is real.

The build, in real numbers, looks like this. Before video one went live, eight hundred and ninety images were generated through Grok Imagine at seven cents per image. One hundred and twenty scripts were written across forty weeks of planned content, three episodes per week. The Remotion pipeline takes a finished script and produces a published MP4 in roughly forty-five minutes, including the AI voice generation, the timestamp alignment for word-level captions, the Ken Burns image transitions, and the brass-on-navy intro and close cards. The voice is Rex, generated by the Grok TTS API at four dollars and twenty cents per million characters. A single video costs about thirty-seven cents to produce in raw API spend. None of these numbers are hidden. None of them are estimates. They are line items that show up on a credit card statement.

The goal is ten thousand dollars per month in recurring income, before May 31 2027. That is not a round number chosen for a thumbnail. It is the number that replaces a corporate salary and the benefits that come with it, with enough margin to absorb the cost of buying our own healthcare and continuing to fund retirement accounts on the same trajectory. The date exists because someone in our household has been counting down to that exact day for reasons that belong to her, not to me, and I would rather meet her there than show up late. What liberation looks like, in practice, is the freedom to choose the next twenty years instead of having them chosen by the same desk that chose the last twenty. Every dollar earned, every dollar spent, every failure, every small win, will be documented here in real time. The receipts will not be retouched. If the math does not work, the math does not work, and you will see it the same week I do.

Here is what to expect from this channel and this log. Three videos per week during the launch arc, then four per week after that, on Monday, Tuesday, Thursday, and Friday at seven thirty PM Eastern. A blog post on this site the same day each video drops, expanding the script into a full record with the actual costs, the actual tools, and the actual outcomes. A monthly income report, even when the number is zero. A weekly progress update on whatever I am building. No hype. No vague inspiration. No fake numbers. If you are mid-fifties, mid-career, and tired of building something that does not belong to you, this is a build log written by someone in the same seat. Follow along. This is the build log.

The Tools

The Math

The Next Log