I run a company with no employees. The only job left is mine.
I'm Charles Green. I have a SaaS holding company with no employees, where AI agents run the daily operations under written doctrine. They pull the funnel numbers, hunt gaps in the products, open pull requests, draft outreach, and write the board report. The control points are mine for now: sending, spending, deploying, merging. Everything up to those is theirs, and each control point is theirs to earn too, one proven surface at a time. The job I am building toward is setting the goals and watching the monitors, and that line moving is the most interesting part of my week.
Before this I spent years as a CISO and engineer, and 25 years operating across 11 companies in the United States, Thailand and Japan. What I write here is how this one runs: how the work gets handed over, how a gate is built, what each week taught me. If you are working out how much of your own company could run this way, that is the question I am answering in public.
01The record
The runs, on the record
A row goes on the page for every run the machine makes: what it did, which gate it went through, and what changed afterwards. A gate that stops a run gets a row of its own, because a stopped run is the gate doing the job it was built for, and that is usually where the next improvement starts.
The rows are the short version. How they are built is on the machine page, and that is the part worth taking.
Source: gate readouts and run logs, one file per receipt
02The products3 of them
Three products, at three different stages
Each one started as a job I was doing badly by hand, which is still the only kind of idea I trust. The agents run all three now.
- Email WatchThree DNS records decide whether someone can send mail as you. The reports that say whether they are working arrive as machine-readable XML, which is no use to the person who owns the domain. Email Watch reads them and answers in a sentence.
- Vendor WatchVendor risk lives in a spreadsheet that was accurate the day it was filled in. Vendor Watch turns a vendor domain into an assessment that keeps rechecking itself, and shows its evidence for every line.
- Security Questionnaire AutopilotA buyer sends a security questionnaire and the deal stops until somebody answers questions they have already answered four times this year. The answers exist. They are scattered across old spreadsheets, a policy folder and a trust page nobody maintains.
Live: open to the publicBuilding: runs, not open yetExploring: not built, and it may never be
03Latest issues
Written while it was still happening
A gate fires, or a routine turns up something I would have walked past, and the issue about it goes out while I am still working out what it means. At least one a week, more when the week produces more.
- When Your AI Agent Becomes a Skeleton KeyConnect an agent to your CRM, your email and your database and it inherits everything those tools can do. The permission layer nobody built.
- AI Agents Aren't Coming. They're Already Taking Market ShareWhat changed in the stack, what it costs now, and what the gap looks like from the other side of it.
- Four Months Building: Why a Serial Entrepreneur Is Betting on Profitable SaaSThe search that did not land, and the arithmetic that made building the better option.
The newsletter
Get the issues by email
The full issue in your inbox: what the machine did this week, what changed because of it, and enough of how it works to try it in your own company.
Double opt-in. One click to leave, in every message. You get the newsletter and the occasional note on what I'm building. I hate spam too: your address is never sold, and nobody else markets to it.
