I install an open-source ICM agent into the tools you already pay for — email, Slack, repos, calendar, recorder, your vault — so everything lands in one place with a memory of your goals. Then I keep it running, every night, on the harness you already have.
I built the system. You bring the data. The system reads from a fixed set of places; your side of the deal is to own accounts in them. Each one is a secret you can rotate.
Anything else — your CRM, your booking tool, your ticketing system — you bring in by export or webhook into the inbox. The system pulls; it never writes into your other tools. That's what keeps it the same system for everyone, and the same system next year.
Install is booked with 50% down; the balance is due at go-live, and the monthly starts the day it's running. Cancel any month — the folders keep working without me, because they're yours.
We map your surfaces, I tell you which tier you actually are (sometimes it's "just use the free agent"), and you get a written install plan either way.
The $200 is credited in full against the install if you book within 30 days.
Pay $200 and pick a timeDeposit books your install week. The interview comes first — your projection page and entities — then wiring, then go-live. Balance at go-live.
Book the install · pay $600You're not paying for the agent. You're paying for the interview that produces your projection page, the wiring of each surface, and the fact that someone checks it every morning. Plenty of people should just take the repo — the fit call will tell you if you're one of them.
Nothing, until you click. Every outbound action — email, message, commit to a protected branch — sits behind a gate. The gate is a file; you can read it and tighten it.
In a git repo you own, on your machine or your VPS. I hold the config and the secrets you gave me, and you can rotate them any time. Nothing is copied to a platform.
Claude Code, Codex, or Gemini CLI — whichever you already subscribe to. The install writes a CLAUDE.md / AGENTS.md and the role folders; there's no runtime of mine in the loop.
No, by design. Those are other people's operations layers; wiring into them is a build I'd then be maintaining against their API forever, and the moment anyone wants write-back it stops being the same system for everyone. Export or webhook their data into the inbox and it's in — that's the "you bring the data" half of the deal.
Yes. That's the design. Every role declares what it loads, writes, and never touches. If you stop paying, the nightly pulls and the brief keep running from your own cron; you just lose the monthly check-in and the person watching it.