A firm of three

Six months later

Nisha no longer worked alone. Six months after the bridge for Mark Ellis, her firm had three clients who paid every month, two staff, and a small office above a bookshop in Karachi.

She had not hired because she wanted to manage people. She hired because the work came in faster than one person could check it. Her AI Worker could prepare a file overnight. It could not sit in a client call. And it could not be the second check she now wanted on everything that left the firm.

The people

Hamza had joined four months ago, in his first job after his accounting exams. He was careful and fast. He hated to keep a client waiting.

Sana had fifteen years in audit. She worked Monday to Thursday and reviewed work before it left. She was the one who asked, about any number, "How do we know?"

Nisha owned the firm and signed every engagement letter. When she was a company of one, she had also sent every file herself.

The client and the weekly job

Lakeshore Supply (a fictional name) sold kitchen and cleaning supplies to restaurants around Cleveland, Ohio. It had come to Nisha through Mark, who knew its owner.

Lakeshore's controller, Dana Ruiz, ran a finance team of two. Lakeshore borrowed from its bank on a credit line, and the bank wanted a one-page cash report every Friday. Dana paid Nisha's firm $1,500 a month for one thing: a weekly cash reconciliation.

A cash reconciliation compares two records of the same money.

• The bank's record. What the bank says came in and went out.
• The ledger. Lakeshore's own books, where its staff record each receipt and payment.

The two almost never match on a given day. Most differences are timing items. Lakeshore writes a check on Tuesday, and the supplier does not cash it until the next week. A customer's check is deposited on Thursday and clears on Friday. These fix themselves.

Some differences are not timing. The bank charges a fee that nobody recorded. A clerk types 1,540 for 1,450. A payment goes out twice. These do not fix themselves. Someone has to find them.

So the job was to explain every difference, say which kind it was, and give Dana one figure she could trust: the reconciled cash balance. The file was due every Friday at 9 a.m. in Cleveland. That month, 9 a.m. in Cleveland was 6 p.m. in Karachi. Dana put the figure into the bank's report the same morning.

Why the project could not come along

In Case 2, Nisha had built her AI Worker as a project: one coordinator, a few threads, a Library for every version, and a nightly run. It had served her well. It could not serve a firm.

The project belonged to her account, and Anthropic's documentation was plain about it. A project belongs to one user, and it cannot be shared with another user. Projects were also not offered on team plans yet.¹ And a Slack channel could not be pointed at a project.

So Hamza and Sana could not hand the worker a job, or see what it had done, unless Nisha did it for them. She thought about giving them her password. Then every action would appear as her, and nobody could say who had asked for what.

She had two choices.

She chose the second. The firm moved to a Team plan, and the worker moved into the place where the three of them already talked all day: Slack.

Next, A worker with its own name.

Sources for the product facts in this story are given in full in the exhibits.