I run a company with no employees. This is what it actually does.
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. I stay at the control points. Nothing sends, spends, deploys, or merges without me.
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 publish here is the record of the company I am running now: what the machine did, how it is gated, what worked, and what broke.
01The record
Evidence, including the bad runs
Anyone can say agents run their company. The evidence is the part worth reading, and it includes the runs that failed, marked so you can find them. A gate that stopped work is the most useful thing this company produces.
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 problem I had myself. The agents run all three.
- 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 stops a deploy 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 lands in your inbox, the runs that failed included.
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.
