Your client workspace. Out of the chat window.

A chat app hides your work inside a thread. Run Claude inside a free code editor and keep your whole client book as files you can see, open, and keep, with every edit approved before it saves.

Stop working inside a conversation. Start working in files.

In a chat app, everything lives in one long thread and last week's work is buried up the scroll. A free code editor puts every file down the left, opens any document in the middle, and lets Claude work beside them while you watch and approve every change.

In a chat app your work lives in a conversation. Here it lives in files you can see, open, and keep.

Set up once. Two prompts a month after that.

01

Install the editor and the extension

A free code editor plus the Claude extension. No API key, no coding required to use it as a file-based workspace.

02

Build the tracker

A clean table, one row per client property, built from a plain-text list you paste in.

03

Log the month

Paste income and expenses and let Claude add them to a running log and flag any shortfalls against the tracker.

04

Draft the client or partner report

Claude reads the tracker and the log and drafts a one-page update as a new file in the same folder, pulling only from what's there.

The monthly log prompt

Update my income log for [month]. Here is what came in and went out: [figures]. Add this as a new section, then compare against the tracker and tell me which properties are short or missing, and by how much.

What it still gets wrong.

i.

Every edit shows as a diff you approve

Nothing is changed silently. You stay in control of every file.

ii.

It's not automatic coding knowledge

Almost none of the work here is code. The editor is simply a better workspace than a chat thread for files that persist.

Next Playbook