An agent that answers the customer
Your mail, in your words, with the ones it should not answer by itself passed to you.
The problem
Support is the work that cannot wait and cannot be batched. A founder answers at midnight because the alternative is a customer who waits until morning, and the answering is rarely the hard part — it is being there.
What the agent does
- Reads the inbox you gave it and drafts in the voice it was shown, not in the voice of a chat assistant.
- Sends the answers that are inside the limit you set, and leaves a record of each one.
- Hands you the ones that are outside it, on your phone, with what it would have said.
- Keeps going at the hours you are asleep, because it runs on a server and not on your laptop.
What you grant it
- The mailbox. It reads and sends as the account you grant it, and nowhere else.
- The limit: what it may answer by itself, and what it must bring to you.
- Your own Claude plan, signed in on that machine from the Mac app. We never hold a provider credential.
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
Anything you did not grant it reaches your phone as a question. A refund it cannot decide, a complaint it should not answer, a customer asking for something new: it drafts, it does not send, and it waits.
The honest limit
It is as good as the voice you showed it and the limit you drew. An agent given a vague limit will ask you about too much; one given a wide limit will answer something you would not have. Start narrow.
Questions
Does my customer email go to Founderizer?
No. The agent runs on your server and reads your mailbox from there. Nothing of a fleet reaches this site except an email address, a payment and an entitlement.
Which mailbox can it use?
The one you grant it, through a login held in the vault on your own machine. We never see that login and we cannot use it.
Will it answer something I would not have?
Only inside the limit you set. Outside it, it asks. Every answer it sent and every decision you made is a commit you can read and revert.
The other jobs
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.
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.