The case at a glance
- Approved by
- Panaversity ·
12 min read
The case in ten sentences
- Lakeshore Supply asks Nisha's firm for a month-end pack for its bank: a cover, a memo and three slides.
- By hand the pack takes 17 hours, and most of that is matching about 3,400 bank lines and copying figures.
- The firm already has every part it needs in Claude, and has never used them together.
- In one afternoon it joins them: a project for the rules, a skill for the method, a connected drive and a folder for the files, a borrowed desk for the matching, four artifacts for the result, and a scheduled task for the time.
- On Tuesday one request does the job in 25 minutes. People check it, Nisha approves $198,300.00 by name and figure, and the pack goes out as PDFs.
- When the first run forgets something, the firm fixes the instructions, not the slide.
- On Wednesday the morning check finds that the bank took back $3,450.00: a check that was not paid. Reconciled cash is $194,850.00, which is $150.00 under the bank's minimum.
- The firm runs the job again, so every piece changes together. Sana approves the new figure and tells Dana a day before Dana's bank meeting.
- The setup read, computed, built and repeated. People checked, approved, decided and told the client.
- On Friday the client's owner asks for twenty packs a month, sent straight to the bank, for less. Nisha must decide how far the setup may run alone, and what the work is worth.
Which part for which need
| The need | The part | Why this part |
|---|---|---|
| Rules for one client, the same in every chat | A project | Its instructions are read in every chat in the project |
| A method for one kind of work, for any client | A skill | Claude uses it when a job matches |
| Files you work on at your desk | A folder, through the desktop app | Claude reads them where they are, but only while the app is open |
| Files a job must read without you | A connected app, such as a shared drive | A job in the cloud can reach it |
| Heavy work: thousands of lines | The borrowed desk in the cloud | Claude runs a program there. The desk is cleared afterward. |
| The result, kept and updated | Artifacts | They last, and a run can update them by their links |
| Work at a set time | A scheduled task. Here, the worker's routine: the morning check. | It runs when nobody is there |
| Check, approve, tell | A person | No part carries the responsibility |
Four rules from the case
- Join the parts. Each part is useful alone. The time is saved where one part hands work to the next.
- Fix the setup, not the result. A fix by hand lasts one month and reaches one piece. A fix in the instructions lasts, and the next run reaches every piece.
- Put files where the job can reach them. A folder on your computer is for work at your desk. A connected drive is for work that runs without you.
- Keep the name with a person. The setup makes checking faster. It does not make it optional.
Words to remember
| Word | Meaning |
|---|---|
| Setup | The parts joined for one job: project, skill, files, schedule and artifacts |
| Project | A place that keeps files and instructions for one piece of work |
| Skill | Saved instructions that teach Claude one kind of job |
| Borrowed desk | The temporary computer in the cloud where Claude runs a program. It is cleared afterward. |
| Scheduled task | A job that runs at a set time, with nobody watching |
| Run note | A few lines Claude saves after each run: what it read, the figure, the pieces it updated |
| Month-end pack | The pieces a client needs at the end of a month: here, a cover, a memo and slides |
| Bank line | One payment in or out, as the bank records it |
| Matching | Pairing each bank line with the same payment in the ledger |
| The bank's minimum | The cash Lakeshore promised its bank to keep at month-end: $195,000.00 |
| Shared drive | An online folder the whole team uses, such as Google Drive |
| Connected app | An app, such as a shared drive, that Claude has been allowed to open |
| Deposit | Money paid into a bank account |
| Closing balance | The money in an account at the end of the last day |
| The worker | The firm's AI Worker: Claude, running inside Slack |
| The morning check | The worker's routine that looks at the bank's lines each morning |
| Ledger, or books | A company's own record of the money it paid in and paid out |
| Check | A paper order to a bank to pay money, also spelled cheque |
| Returned check | A check that the payer's bank refused to pay. The money is taken back. |
| Reconciled cash | The bank's balance, plus deposits the bank has not shown yet, minus checks the bank has not paid yet |
| Timing item | Money on its way, such as a check the bank has not paid yet. It sorts itself out. |
| Artifact | A piece of finished work in Claude that you can keep, change and share |
| AI Worker | An AI system you hand a whole job to, inside limits you set |
| Routine | Claude in Slack's name for a scheduled task. Here, the morning check. |
| Approval | A named person's written yes, which names the pack and its figure |
| Unrecorded item | Something the bank shows and the company's books do not show yet |
The work this prepares you for
Nisha's week is the work of a Forward Deployed Engineer (FDE): someone who solves a company's business problems with AI Workers. Friday's decision explains why the cases prepare you for it.
How this case connects to the others
You can read this case alone. If you have read the other three, this is how they fit.

- Case 1 asked whether the work is good. Here, that is Hamza's four tests.
- Case 2 asked whose name is on the work. Here, the pack goes from the firm's own mailbox.
- Case 3 asked whose word the worker takes: whose instructions it follows. Here, a named person approves each pack and its figure. That happened twice: on Tuesday and on Wednesday.
- It is the first case that uses the artifacts from Build Something, and the first that joins every part of this section in one job. Exhibit 1 lists them.
- Owner
- Panaversity