FounderizerAn agent that keeps watch
Work it keeps without being asked: it checks on its own schedule, and what it finds it sees through to the end.
The problem
The things that break quietly are the expensive ones. A founder finds out when a customer writes in, which is days after the moment it would have been cheap to fix.
What the agent does
- Holds a duty rather than a task: it decides when to look, and it looks when you are not there.
- Follows what it finds to the end, instead of filing an alert for you to triage.
- Reaches your phone when the next step is yours, with what it already knows.
- Says nothing when everything is right, which is what makes the message worth reading.
What you grant it
- Read access to whatever it is watching, from the vault on your own machine.
- Your own Claude plan on that machine.
- The duty itself, and the limit of what it may do about what it finds.
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
A duty does not widen itself. What it may do about what it finds is what you granted; the rest is a question on your phone.
The honest limit
An agent that watches costs model use every time it looks, on your own plan, because it is your account it is signed in to. A duty that checks every minute is a duty that spends every minute. Choose the schedule, then watch what it spends.
Questions
Why does this need a server and not my Mac?
A laptop is shut at the hours a watch is worth having. A small Linux server is enough — a €5 VPS is where most people start.
What reaches my phone?
What needs you. The iPhone app and the notifications to it are part of what the subscription pays for, and they stop if you stop paying, while your hub and its agents do not.
Will it exhaust my Claude plan?
It can. Claude’s plans are sold for a person working, and an agent that runs while you sleep reaches the limit on your account. Start with one agent and one duty and watch what it spends.
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.
Shipping the small thing
The feature you never get to. A commit, a deploy, and a note saying what changed.
What it costs, and what you carry before you pay. Anything you want to put to us plainly first: support@founderizer.com.