FounderizerAn agent that builds the small thing
The feature you never get to. A commit, a deploy, and a note saying what changed.
The problem
Every product has a list of small things that are each worth half a day and together worth a month. They never get done, because half a day is exactly what a founder never has in one piece.
What the agent does
- Takes one item off the list and does it end to end: the commit, the checks, the deploy.
- Leaves a note saying what changed, which is the thing you read rather than the diff.
- Picks up the next one without being asked, if that is the duty you gave it.
- Works at the hours nobody is watching, which is when a small deploy is cheapest.
What you grant it
- The repository, through your own GitHub App, and whatever your deploy already needs.
- Your own Claude plan on that machine.
- A duty: the standing instruction that says this is work it keeps without being asked.
How a grant works, and why a narrow one costs you less than it looks, is its own page: deciding what an agent may reach.
Where it stops
It ships what the duty describes. Anything that needs a decision you did not delegate — a price, a name, a thing customers will see — comes to your phone first.
The honest limit
Small and well described is where this works. A feature nobody has thought through becomes a feature nobody thought through, built quickly. The thinking is still yours.
Questions
How does it know what to build?
From the duty you gave it, in your own words, and from the repository it can read. A duty is a standing instruction, not a single task, so it keeps the work rather than waiting to be asked.
Can I see what it did before customers do?
Every change is a commit in your own repository and every owner decision is a commit you can read and revert. What gates a release is whatever already gates it in your repository.
How many agents can I run?
One subscription covers one fleet — a hub, its machines and its agents — with fair use of five machines and ten agents.
The other jobs
Answering customer email
Your mail, in your words, with the ones it should not answer by itself passed to you.
Watching the money
A refund, a failed payment, a complaint: it checks what happened, acts inside the limit you set, and asks when it is outside it.
Fixing the bug
It reads the repository you gave it, pushes the fix, runs your own checks, and tells you what it ran.
Keeping watch
Work it keeps without being asked: it checks on its own schedule, and what it finds it sees through to the end.
What it costs, and what you carry before you pay. Anything you want to put to us plainly first: support@founderizer.com.