You Don’t Write Code and You Want Claude Code to Handle the Weekly Admin. Start With These Eight Jobs.

Why most Claude Code demos don’t look like your week

Most demos show someone building an app in ten minutes. Your week looks different. It is a price list, an inbox, three quotes and a report you keep meaning to write on Monday.

The chat window can draft any of those. Then it stops at the door, because it cannot open your files. Claude Code can. It reads the folder you start it in, changes files when you allow it and runs commands on your computer. That reach is the whole point, and it is also why the safety steps below matter.

The other snag is that your business probably does not live in a folder at all. Your books sit in accounting software, your quotes come out of a job app, your site lives on a website builder. Claude Code cannot log in to those by itself. So every example here starts with a folder you build.

Step 1: Build one working folder of copies

Export copies from the tools you already use and put them in one folder. Claude works on the copies. You put the checked result back yourself, by importing, pasting or retyping it.

• Spreadsheets: File, then Download or Export. CSV gives one tab as plain rows.
• Accounting software: open a report such as unpaid invoices and look for Export near Print.
• Job and booking apps: list screens often export clients, quotes or jobs. If not, download single PDFs.
• Website builders: export posts if you can. If not, paste each page into a text file named after it.

Name each file by what it is and when you exported it, like price-sheet-2026-10.csv. Excel and Word files are not on the official list of formats it reads, so test one first. Ask it to describe the first five rows without changing anything. If the answer is wrong, export a CSV or a PDF instead.

Step 2: Make it ask before it changes anything

Switch to Manual mode before your first real job. In Manual, Claude reads freely but stops and shows you each edit or command, and you answer yes or no.

This matters more than it did a year ago. The tool used to ask by default. It no longer does.

Auto mode became the default starting mode in terminal and VS Code sessions on all plans by the end of September 2026 (Claude Code documentation, read October 2026).

Auto mode has a background checker, and the documentation says plainly that it reduces prompts without making anything safe. Press Shift+Tab and watch the status line until it reads manual mode on. For any job that reaches past a handful of files, use plan mode first: Claude looks at everything, writes a plan, and changes nothing until you approve it.

Step 3: Pick your first job from this table

Each row is a job the book walks through or uses as a small-business example. The safety column is the part people skip. Read it before the first column.

A good first job has three traits. The files already sit on your computer, or you can export them there. You can judge the result at a glance. And if it goes wrong, you lose nothing you can’t restore. Bad first jobs involve money leaving your account, emails to customers or deleting anything.

Step 4: Turn the weekly report into a command

The weekly report becomes a skill you trigger by typing /weekly-report. You write it once, in plain English, and it runs the same way every Monday.

The skill names its sources: a sales/ folder with this week’s export, an inbox/ folder with customer messages saved as text, and your task list. It writes four sections. Numbers this week, each with the file it came from. What customers asked about most. Tasks done and overdue. Three things to decide.

Two rules carry the weight. It never estimates a number; if a figure is not in a file, it writes “not found.” And it never sends the report anywhere, it only saves it.

The quote check works the same way. Your markup, flat lines and legal text sit in a separate rules file, so you can change a price rule without touching the steps. It recalculates every line and returns a table, then one sentence: ready to send, or not ready.

Step 5: Schedule one job that only reads

The morning briefing is the best first scheduled job, because its worst case is a bad report, not a broken folder. Here is a short version of the prompt from the book. Change the questions to fit your business.

You are my morning briefing. Read only. Change no file.

From the files in this folder, tell me:
1. Open jobs: which moved in the last 7 days, which did not.
2. Inbox: anything new in the inbox folder, including ALARM notes.
3. Today: ONE big task, and at most two small things
   I can finish in under 15 minutes.
4. Drift: if I started something new this week while an
   older job is still open, say so in one sentence.

Rules: under one page. If a folder you expect is missing,
say so at the top and do not guess. If unsure, write
'not sure' and why.

The line about missing folders is there for a reason. A job that cannot find its inbox will happily report “inbox clear” every day.

Where it runs depends on what can stay switched on. As of the book’s October 2026 check:

• Routines run in Anthropic’s cloud, so the laptop can be closed. They are a research preview.
• Desktop scheduled tasks need the desktop app running and the computer awake.
• /loop repeats inside an open session and expires after 7 days. Treat it as “watch this while I’m here.”
• Your computer’s own scheduler running claude -p works, but it is a pattern users built, not a documented feature.

Routines can run at most once an hour, and scheduled runs are capped at 100 per hour per account (Claude Code documentation, read October 2026).

Nobody is there to click yes overnight. So the book’s wrapper runs with --permission-mode dontAsk and --permission-prompts none: reading is allowed, and anything that would need approval is refused instead of waiting. The flag with “dangerously” in its name stays off your laptop.

Step 6: Add a check that tells you when a job went quiet

Scheduled jobs rarely fail loudly. They stop, and silence looks exactly like “nothing to report.” The fix is a tiny script with no AI in it that watches the jobs.

It asks three things of each job. Is the task there and switched on? Was its last result 0, the code for success? How old is the newest report file? If anything looks off, it drops an alarm note into your inbox folder, and the next morning briefing puts it in front of you.

One of the author’s own briefing jobs crashed without a word for 44 days in 2026, because its inbox folder was missing.

Another time every routine stopped for 7 days while the scheduler still said “Ready.” The laptop was on battery at 7:30, and missed runs were never caught up. When the watcher first ran, it found 3 real failures.

Step 7: Keep keys and client data out of every job

Passwords, API keys, bank details and customer records never go in a prompt, a notes file or a template. Claude Code saves every session as plain text on your computer, kept for 30 days by default.

• Give the name, not the value. Tell Claude which environment variable holds a key and ask it never to print or write it.
• Use blanks for clients. “Draft a reminder to a client whose return is missing a form” needs no name and no amount. Write [CLIENT] and [AMOUNT], then fill them in yourself.
• Keep client folders elsewhere. Store them outside the folders Claude works in, and add deny rules so it cannot read or edit them.
• Check your training setting. What Anthropic does with your sessions depends on your plan and one privacy setting. Read the current data-usage page and choose what your clients would want.

If what you really want is a customer-facing tool rather than admin help, that is a different project. Read how to get an app built without coding if you want to build an app instead.

Fair doubts