The Back Office

What the machine is actually running

Not demos. Each of these is a live attempt at revenue, and the interesting part is that one setup runs all of them at once.

• A calculator site chasing two revenue lines My NEC calculator site is the one electricians use on the job. Affiliate placements are one play, display ad revenue is the other, and both of them turn on organic traffic I have to earn rather than buy.
• An ebook pipeline Markdown in, EPUB and print PDF and cover out, ready for the store. The pipeline is the product here, because every book after the first one costs a fraction of what the first one did.
• A newsletter and a blog that write their own first draft A scheduled agent reads the week of real work and drafts both. I approve or I do not. Nothing publishes without a person.
• A video pipeline Raw footage in, cut clips and captions out, queued to Instagram and TikTok. The distribution problem for everything above.

The through line is organic. No ad spend, a hard ceiling of a hundred dollars a month on tools, and a full time job in the way. That constraint is why the system looks the way it does, and it is the same constraint most people reading this are under.

What is inside

• The pipelines The release playbooks in full, and more of them as they get written. One ships a tool with no human in the loop. Another publishes under my own name and keeps a person in it without letting them become the bottleneck. They are the actual files, not a diagram of them.
• The standards The bar every page and every deploy has to clear here, and the script that fails the build when it does not. A rule with nothing enforcing it is a rule nobody follows, including me.
• The system Where an instruction has to live to get read at all, how the skills hand off to each other, and what the databases underneath hold. This is the part you cannot get from a repository, and the part that took the longest to get right.
• The incident log Dated write-ups, and more of them every week, because they are a byproduct of working rather than a content calendar. Each one is what broke, what it cost, why it happened, and the check that catches it now.
• A room, a call, and a vote Chat split by topic, one live call a month, and one member-voted build a month. If a calendar month ends with no call, you get that month's $79 back. That is a term, not a promise.

It has to run in your environment, not mine

The thing that makes a setup like this useless to everybody else is that it is welded to one machine. So everything in here is written to move: the installer that merges my hook block into your config instead of overwriting it, the schemas for the databases the agents read and write, the config that wires which hook fires on which event in what order, and the reasoning for every shape so you can change one without breaking the next.

If you want to run this against your own side hustle instead of mine, that is the intended use, and it is what the whole thing is organized around.

The parts stay free

Every hook and every skill I run is free, MIT and public, with no held-back version. If that is all you want, take the whole repository and go, and nobody here is annoyed by that. My courses are free too, starting with the beginners course. What costs money is the assembled machine and the reasoning behind its shape, which is the part a repository cannot hand you.

What it is not

Not a course. Not one-to-one coaching, and not in person. Not a place where I post a lesson a week and call it a membership. Not a promise that any of these side hustles works, because I am finding that out in public and writing down the parts that do not.

$79 a month

Cancel whenever you like. Come see the inside of The Back Office, and read the membership terms before you join.