Working with an AI assistant.
Connecting one to the systems you already run, and handing it the work that repeats. Written from one desk: what is connected, which work moved across, where it goes wrong, and what stayed human. No predictions, no tool announcements, no prompt collections.
7 pages, and counting
Guides
How the arrangement is set up: what gets connected, and the written rules that keep decisions from being reopened every session.
- Connecting an assistant to the tools you already runA connection gives an assistant standing access to a system your company already pays for, so a question that spanned seven browser tabs is answered in one pass.
- The project instruction fileThe document that tells the assistant what has been decided and why, so last month’s decisions survive this month’s session.
Patterns
One recurring job handed over, written down so you can run it on your own stack. Each says where it goes wrong.
- The month the tool brokeA time-tracking tool stopped working. Instead of migrating to another vendor, the history was exported and tracking was rebuilt into a system already owned.
- From a meeting to a task list, without notesMeetings become transcripts, and transcripts become draft tasks on the right client board. The draft is the point; nothing goes live unread.
- Letting the assistant plan the weekThe assistant reads the whole queue and proposes the week: what comes first, and which tasks to group so a day can be spent inside one client’s work.
- The work that happens while you’re awayRoutines run on a schedule in the cloud without a machine being open, and longer jobs keep going after the desk is empty.
Reference
What this desk runs on today. It carries everything that dates fastest, so the other pages do not have to.