Claude Code for Business Automation: Automate Work, No Code

In this lesson you learn how bigger jobs are put together, and how to pick the simplest way that works.

First, the five workflow patterns for multi-step work:

• Straight line. Steps one after another.

• Branch. Different items get different handling.

• Parallel. Parts of the job that don’t depend on each other.

• Hand-off. One part of the job goes to a helper.

• Review loop. A second pass checks the work before you see it.

Then the frame: a set of files Claude builds in your folder (your rules, the flow, a run log, checks and a report) so every run follows the same rules, even in a new session.

Finally, the ready-made prompt. The prompt is what you write. The frame is what Claude builds from it. It has three parts: your request (Part A), a ready-made block that builds the frame (Part B) and optional blocks you add only when the job needs them (Part C).

In this lesson you open the automation-builder skill and see how it’s built, then watch it build a real automation from an empty folder.

The demo is a job search:

• Claude checks 26 company job boards.

• It sorts 2,862 postings into apply, clarify and skip.

• It drafts a tailored resume and cover letter for each good fit.

You also see how you stay in control. Claude asks only what it can’t work out itself, stops twice for your OK (on the plan and after a small trial run), and is told to check its work before it reports done. In the demo, 20 out of 20 checks pass, and the 18 postings it couldn’t decide go into the report for you to approve.

Job hunting is just the demo. The same method works for your own repeat work.

In this lesson you build three more automations you can copy for your own work: one small, two big.

First, how to choose. A small job where a slip doesn’t matter only needs a short prompt, saved as a command (the way you did in Lesson 3). A big job with many steps, money or messages going out needs the full kit.

The three jobs:

• A daily AI news brief. Claude collects the latest stories from sources you pick and sends four of them to your Telegram every morning. It remembers what it already sent, so you don’t get repeats.

• Client proposals from Gmail. For each client brief in your inbox, Claude reads the attached PDFs and builds a slide deck, a pricing sheet with formulas and a draft reply email. It sends nothing. Prices come only from your own price list.

• A lead finder. You give it an industry and a city. Claude pulls local businesses from Google Maps, filters out the ones that don’t fit and gives you a checked list. You approve the uncertain ones, and you see the cost before each run.

For each job you see the problem, the short request you write, the run and the result. Then you see which few lines to change to make it your own.

You also learn which jobs to put on a schedule and which to run by hand.

In this lesson you learn how to live with your automations week after week: run them again, review the results, change them and know their limits.

• Keep them in one place. One main folder, one folder per automation. The folder name, the command name and the task name all match, so you always know which is which. The Scheduled page shows them all.

• Run again in a new session. A chat is a one-time tool. Open a new session in the automation’s folder, type its command, and it picks up with the same rules.

• Schedule only what repeats. Jobs that run the same way every time get a Daily or Weekly schedule. Everything else stays manual: press Run now.

• Fix wrong results. Tell the automation to change the rule, and it updates its own rules file. Wrong across the board? Change the rule. Wrong once? Redo that one item.

• Review from the report. Approve or reject the items that need you, and tell the automation what to do next.

• Reuse and move. Copy an automation for a similar job. To move to another computer, copy the folder, sign in again, add your keys and set the schedule again. Share a clean copy without your keys.

• Know the limits. It runs only while your computer is on and the Claude app is open. A missed run catches up once. A new email or file won’t start it. Jobs that need your browser stay manual.

Your last exercise: pick one weekly job of your own, build it, run it twice and schedule it if it repeats.