Case study · our own company
A company run by AI agents, directed by one engineer.
Broke to Built's daily work is done by AI agents: building tools, watching the sites, checking billing and writing code. Anthony Snider sets the goals and signs off on new paid offers, price changes and anything that takes a payment. This page shows how that works.
- Apify accounts other than ours that ran one of our tools, last 30 days
- 301 across all 184 tools on our account, public and unlisted
- Public sites answering our daily check
- 7 of 7 checked Oct 22, 2026, 3:30 AM ET
- Tools for sale on the Apify Store
- 141
What the agents do
Each agent owns one job.
One job per agent, written down, with a daily check that flags any agent that has gone quiet.
- Build and sell tools
141 cloud tools for sale
Agents build and test small single-job tools, listed on the Apify Store and priced per result. In the last 30 days, 301 Apify accounts other than ours ran at least one of the 184 tools on our account (public and unlisted), read from our monitoring on Oct 22, 2:07 PM ET.
- Watch the company
A check that runs every day, with no one at the desk
A scheduled agent counts our cloud services, confirms each has its timers, opens our main public sites, checks billing and writes a report. On Oct 22, 2026: 15 of 15 core services deployed, 7 of 7 sites answering, billing in good standing.
- Write the code
Changes arrive as reviewable pull requests
Our cloud agents make changes on a branch and open a pull request. Anthony reads it and merges it, or doesn't. This website's redesign was built that way.
- Run the infrastructure
34 cloud services that don't need a laptop
The services run on Cloudflare Workers and the tools on Apify, so they keep working when nobody's computer is on.
How Anthony directs them
Agents do the work. A person owns the decisions.
These are the standing rules the agents work under. They're the same guard rails we'd put on a system we build for you.
-
He sets the goals
Priorities come from him. Agents propose, he picks.
-
Money waits for his yes
New paid offers, price changes and taking payments all need his approval first.
-
Nothing ships unreviewed
Cloud agents' code lands only when he merges it, and one designated agent does the deploys.
-
There's a kill switch
Publishing new tools is switched off unless he turns it on. Today it is off, and the daily check says so.
What this means for you
We build the same thing for clients.
If your team loses hours to the same task every week, this is the kind of system we design: agents with one job each, checks that catch a silent failure, and a person signing off where it matters.
Honest about limits
The numbers on this page are a dated snapshot from our own monitoring, not a live feed. When something fails, the check reports it.
Readable by machines
Our services are listed as plain JSON at /api/services.json and for AI assistants at /llms.txt.
Built in the open
Experiments, including the ones that didn't work, are in the lab.
Want a system like this for your work?
Tell us the job. We'll tell you plainly whether we can help.