Case 4: Nisha's Month-End

A job that took two days now takes about two hours of people's time. The firm did not buy a new tool. It joined the ones it already had.

Panaversity case study · November 2026

The case in one minute

A small accounting firm must prepare a report for a client at the end of every month. Done by hand, it takes a junior accountant two days: download the bank's lines, match them against the client's books, then type the result into a sheet, a memo and slides.

The firm's owner, Nisha, already uses Claude. She has always used its features one at a time. For this job she joins them into one setup:

• a project, a place for one piece of work, holds the client's rules;
• a skill, a saved way of doing one kind of job, holds the firm's method;
• Claude reads the files where they are. Some are in the firm's shared drive, an online folder the whole team uses, such as Google Drive. Claude has been allowed to open it, so it is a connected app. Others are in a folder on a computer;
• Claude does the matching as a small program, on a temporary computer in the cloud;
• Claude builds the sheet, the memo, the slides and the cover as artifacts, pieces of work it keeps and updates, from one result;
• a scheduled task, a job that runs at a set time, looks at the bank again each morning. In this story it is called the morning check. The firm's AI Worker in Slack (an AI that does whole jobs, inside the firm's team chat) runs it.

On Tuesday the report goes to the client, Dana. On Wednesday the morning check finds that the bank's figures have changed, before any person notices. The firm runs the job again, and a reviewer approves the new figure. Dana hears about it a day before her meeting with her bank.

What this case teaches. Each feature of Claude and ChatGPT is useful alone. Joined together, they become a workplace for a job that comes back every month. The setup reads, computes, builds and repeats. People check, approve and decide. In one line: build the setup once, and it does the job again. Your judgment is still yours.

Is this not just Google Docs with AI? No. Writing was never the slow part of this job. What the setup did compares the two fairly.

What you will be able to do

After this case you can:

1. choose the right part for each need: a project for rules, a skill for a method, a folder or a connected app for files, the cloud for heavy work, an artifact for the result, a scheduled task for the time;
2. join those parts into one setup for a job that repeats;
3. say what the setup does and what a person must still do: check the result, approve it by name, and tell the client;
4. change the setup, not the result, when something goes wrong, so that every piece stays the same.

What you will do

• Read the story, in six short parts. It takes about 40 minutes.
• Do the lab, in 75 to 110 minutes. You build a smaller version of the setup with sample files: a project, a skill, one run that makes three pieces, and a late bank line. On a paid plan you can add a sheet, a folder and a real scheduled task. The core path works on a free plan.
• Decide. At the end the client's owner wants the same work for four companies, a month-end pack and four weekly packs each, some sent straight to the bank, for less money. The case does not say what Nisha should answer.

What you need. The Claude desktop app with a free account. A paid plan adds three optional steps: a sheet, a folder on your computer and a real scheduled task. Two to three hours in all. You can do everything alone.

You do not need the earlier cases

This is the fourth case about the same firm, but you can read it alone. Here is everything you need.

• The firm. A small accounting firm in Karachi. It pays for Claude's Team plan. Nisha owns it. Sana is the senior reviewer. She has fifteen years of experience checking companies' accounts, and works Monday to Thursday. Hamza is the junior accountant.
• The client. Lakeshore Supply, a company in Cleveland, Ohio, that sells goods to shops. Dana Ruiz is in charge of its accounts. Walter Brennan owns it. Tom Becker works at its bank.
• The worker. An AI Worker is an AI system you hand a whole job to, inside limits you set. The firm has one in Slack, its team chat. It is Claude, running inside Slack. This case calls it the worker.
• The worker's weekly job. Every week the worker downloads Lakeshore's bank lines, saves them to the firm's shared drive, and prepares a one-page cash file: a draft on Wednesday and the final file on Friday.
• The morning check. In this story the worker gets one more job, at a set time each morning. This case calls it the morning check. It is a scheduled task. Claude in Slack calls a scheduled task a routine.
• The firm's habit. Before anything goes to a client, Nisha or Sana approves it, and the approval names the file and its figure. Files go to the client from the firm's shared email address, which starts with reports@.
• The time. Karachi is 9 hours ahead of Cleveland. When it is 6 p.m. in Karachi, it is 9 a.m. in Cleveland.

Words you will meet. You do not need to know accounting. These ten words are enough.

• Bank line: one payment in or out, as the bank records it. A month has thousands of them.
• Matching: pairing each bank line with the same payment in the company's own record. What is left over needs a look.
• Deposit: money paid into a bank account.
• Closing balance: the money in an account at the end of the last day.
• Ledger: a company's own record of the money it paid in and paid out. Accountants also call it the company's books.
• Check: a paper order to a bank to pay money, also spelled cheque. A check is cashed when the bank pays it.
• Reconciled cash: the cash a company really has at month-end. You start from the bank's balance. You add money paid in that the bank has not shown yet. You take away checks that the bank has not paid yet. Here: $201,480.00 + $6,120.00 − $9,300.00 = $198,300.00. If the books are right, the ledger shows the same figure.
• Timing item: money on its way, such as a check the bank has not paid yet. It sorts itself out in a few days.
• Unrecorded item: something the bank shows and the company's books do not show yet. Someone must record it.
• Artifact: a piece of finished work in Claude that you can keep, change and share, such as a doc, a deck of slides or a sheet. Build Something teaches these.

One more word is this case's own: the setup is the parts joined together for one job. The case at a glance has all the words in one table.

The story takes place in 2027, a little after this book was written.

How this case is organized

The story comes first. Read the six parts in order.

1. Two days of copying: the client asks for a monthly report, and Nisha counts what it would cost by hand.
2. One place for Lakeshore: the firm builds the setup in one afternoon.
3. The run: one request does the job, people check it, and the report goes out.
4. Wednesday morning: the morning check finds a change, and the firm runs the job again.
5. What the setup did: Nisha lists what the setup did, what people did, and where it can still go wrong.
6. Friday's decision: the client's owner asks for more, for less.

If you do the lab, you can do it at any point after part 3. The lab says when to stop reading.

After the story come The case at a glance, a summary, and the questions for discussion. The exhibits hold the details: the project's instructions, the skill, the request and the tables. Check yourself has flashcards and a quiz. The final assessment covers this whole part of the book, so it needs the earlier sections too.

Instructors will find a teaching note and a practical run sheet.

About this case. It is a fictional teaching case, and it is not accounting advice. The people, the companies, every figure and every time are made up. What each part of Claude can do was checked against Anthropic's help pages in November 2026. Nobody has yet tried this exact setup from start to finish, so the times are examples, not measurements. Until that test is done, treat the case as a teaching draft, not a tested recipe. A few tables are marked illustrative for this reason.¹ The lab is yours to run. The exhibits say more.

If you have read Cases 1 to 3, The case at a glance shows how this one connects to them.