Claude Cowork builds weekly overdue-invoice drafts

Michel has a limited back-office system and regularly spends Monday evenings preparing overdue-invoice reminders. Claude Cowork helps him create an agent workflow that logs into the system, checks late accounts receivable and compares customer names with a Google Sheet he supplies.

The workflow uses his email template and adds the contact name, invoice identifier, amount and due date. It places finished messages in the Drafts folder rather than sending them to customers. A separate report reaches Michel with the customers included, each balance and the total, giving him a second view of what the draft batch covers.

He reviews the messages, confirms the contents and presses Send himself. The account reports about an hour saved each Monday, without an independently measured time study or evidence of debt recovered.

Claude Cowork is specifically credited with constructing the agent workflow. The post does not identify its running harness, so this entry does not claim Cowork itself performs every scheduled login. The useful operational detail is separating reminder preparation from customer delivery and including both invoice-level identifiers and an aggregate report. Name matching still needs review: the source does not describe a demonstrated fallback for ambiguous names, missing contact rows or disputed invoices. Those limits matter before adapting the process to a different accounts system.

Prompt
Suggested prompt (written by Agents In Use, not the author's)

Source: Blog · Michel