How it works
What the system does with a request, and how an engagement sets it up and looks after it afterwards.
A working session, replayed
A replay of real working sessions from 24 and 30 September 2026, rebuilt from their Telegram history and logs, with names changed. The first is the busiest stretch in our records, not a typical day. It is the set-up we run our own work on, which has more in it than a client install. Chancelry installs the same design on yours.
Transcript
A replay of real working sessions, 24 and 30 September. Names changed. Will asks what else it can work on. A domain's email set-up is checked. Two records go live, with a check. It won't type Will's password. Five more jobs start. None need Will. An Instagram check is fixed. A presentation is brought into line. Privacy and terms pages are fixed. A sign-up form hole is found. Will says go. Both are live, checked. A backtester passes its honesty test. It corrects its own overstatement. Safety gates fixed, 87 cases tested. 58 commits across 8 repositories, in 79 minutes. 30 September: a force push is tried. The safety gate refuses it. No approval overrides it. What it learns is kept in plain files. This one is its rule about dashes. Chancelry installs an AI operator on your own machine, and supports it afterwards.
The price isn’t on this site. Ask and we’ll email you the figure and the full terms. You don’t need a call first.
Start with one job
Name one job you’d take off your desk. We agree in writing what “working” means, and we aim to have it running within a week of agreeing it, in your own email and systems.
You name the job. Reply to our email or use the consultation form. We’ll reply by email to say whether it fits.
We agree it in writing. A one-page scope: the job, the accounts it touches, and what “working” looks like.
Aiming for a week. We aim to have it running within a week of agreeing the scope, set up on your own accounts over a screen share you start.
Handover. A 45-minute screen share, then one round of changes within 14 days.
If it earns its keep, it grows. The same set-up can take on more of the firm, up to the full operator described below.
Examples of a single job. Not client results.
- Candidates who’ve gone quiet. A list each morning of candidates who haven’t replied in the time you set, with a chaser drafted for each. You decide in the scope whether it sends or waits for you.
- Business development research. A weekly list of firms that match what you look for, with why each one made the list and where the details came from.
- Replies you’d otherwise miss. When a candidate or client replies, you get a message on your phone saying who it was, and any follow-up to them stops.
What you’ll need
- The accounts the job runs on, in your own name and paid for by you.
- A paid Claude plan whose terms allow your business use, if the job uses Claude.
- If a computer is involved: administrator access, and a backup you’ve checked can be restored.
- One person who can approve the scope and sign off at handover.
- Nothing technical to learn. You start a screen share and we do the set-up.
The route of a request
You send a request from Telegram.
The orchestrator passes each piece of work to the specialist suited to it.
Several specialists can work at once.
Every shell command and file edit passes the safety gate before it runs.
The orchestrator reports back, and what was decided goes into a written memory you can search.
An operator you run from your phone
The system is built on Claude Code. A lead orchestrator reads your messages on Telegram, passes each piece of work to the specialist agent suited to it, and reports back. Several specialists can work at once.
It can run commands, edit files, push commits and send messages. It keeps a written memory of decisions and context, searchable across sessions, so a new session picks up what the last one settled.
It isn’t hosted anywhere. It runs on your machine, under your own Claude plan.
We run the same design on our own work.
The name comes from the chancellery, the office that held a ruler’s seal and acted with their authority.
How an engagement runs
Consultation. We learn how your business runs and whether this suits it. Either side can stop here.
Scope. We agree what the operator will handle, which machine it lives on, which accounts it can touch, and what it must never do.
Installation. On your machine. The safety gate goes in before the operator is given anything real.
Configuration. Specialists, routing, memory and rules, written for your business.
Handover. You run it from Telegram while we watch it work.
Support. While the monthly support runs, when something we set up breaks we restore it or give you a workaround, and we add a check for that fault.
What you have at the end
When the engagement ends, each of these is in place.
- An orchestrator installed on your machine and running on your own Claude plan.
- Specialist agents set up for the work your business does, with the routing written down where you can read it.
- A Telegram channel that only the accounts you approve can reach.
- A memory in plain files, started with how you work.
- A safety gate in place before the operator is given real work.
- A technical reference and a handoff note for each project it works on.
- Support afterwards, from the person who configured it.
Questions
Open a question to read its answer.
Is this software I subscribe to?
No. It’s a service. We install the system, configure it for your business and support it afterwards. The software runs on your machine, under a Claude plan you pay Anthropic for directly.
What do I need before we start?
For one job: the accounts it runs on, in your name, a paid Claude plan whose terms allow your business use if the job uses Claude, and one person to sign it off. For the full operator: a Mac or Windows PC that can stay on, a paid Claude plan whose terms allow your business use, a Telegram account, and enough comfort with a terminal to follow what’s being set up.
What happens if my machine is off?
It stops. It runs on your machine, so a computer that’s shut down or asleep can’t answer, and it won’t bring itself back unattended. We can build you an outside check that messages you when it goes quiet. Expect that alert within hours, not minutes.
Start with a conversation
Tell us how your business runs and what you’d hand over first. If Chancelry suits it, we’ll say so. If it doesn’t, we’ll say that too.