Draft late invoice reminder emails every Monday for your approval
Have Claude Cowork set up a Monday-night agent that drafts late-invoice reminder emails for you to review and send, as the author describes.
What the agent did
Source-reported example · as described by Michel Abood (San Diego), works in a wine-import business (per his own reply on the post); the posts do not name the company; Rundown profile 'michel' links to linkedin.com/in/michelabood; company size not stated
The author, Michel Abood, who works in wine import in San Diego, posted on The Rundown's Workflow Hub that his industry has tight margins and a rudimentary back end, so sending late-invoice reminders was repetitive manual labor.
He says he had Claude Cowork walk him through creating an agent that logs in every Monday night, checks the company's late accounts receivable, and compares the customer names against a Google Sheet list he created.
It uses an email template he provided, adds the contact name from the Sheet, and includes each late invoice's identifying number, amount and due date. The agent puts the emails in his Drafts folder and emails him a report showing which customers were included, how much each one owes, and the totals.
He reviews the drafts, confirms they look good, and sends them himself. His LinkedIn post of 2026-10-12 describes the same workflow (Gmail drafts, final say his).
Both posts attach a screenshot of a report email to himself, dated 10/11/2026 and labeled a test run: subject "TEST Invoice reminders 10/11/2026: 7 draft(s) ready", the line "TEST RUN. Drafts were created for review; the weekly schedule is not affected.", and "7 draft(s) ready in Gmail Drafts," followed by a past-due amount the author blacked out.
Neither post quotes a prompt or shows an example of the customer reminder drafts.
He says this "has saved me about an hour every Monday night of tedious, repetitive manual labor" (his own estimate). His LinkedIn post describes "a task that takes me the better part of an hour every week: chasing late invoices."
The report-email screenshot attached to both posts is a test run dated 10/11/2026 that says "7 draft(s) ready in Gmail Drafts"; the 7 drafts are from that test run, not a typical weekly count.
Limitations
Short posts with no prompt and no example of the customer reminder emails, and no measured before-and-after. The time saved is the author's own estimate.
Both posts attach a screenshot of a test-run report email dated 10/11/2026 ("7 draft(s) ready"; a past-due amount is blacked out); it is labeled a test run and says the weekly schedule is not affected, so 7 is not a reported typical weekly volume.
The posts do not name the receivables system or say how the agent logs in, how long the weekly job has run, or whether the reminders got invoices paid.
He says he reviews and sends every reminder himself; he also says everything he builds has "a human in the loop until I am 100% sure there won't be some embarrassing or problematic error" (his reply on the post).
The Rundown post's text says the emails go to a Drafts folder and does not name the email service; the attached screenshot and his LinkedIn post say Gmail. The posts do not name his company. The model is not stated.
Try it in your business
What you'll need
Claude Cowork; access to your list of overdue invoices (the post does not say how); a Google Sheet of customer names and contact names; your own reminder email template; access to your mailbox so drafts can be saved; your own review before anything is sent.
The agent reads the company's late-receivables list, a Google Sheet and an email template and leaves drafts in the author's mailbox, so it works across several of his tools. The post does not say how those connections are made. The label is our reading, not something the author states.
Starting prompt
The author didn't publish their prompt (read both posts, the author's reply and the attached screenshot; the steps are listed but no prompt is quoted), so this is our adaptation.
How ours differs from the original setup: Same execution agent (Claude Cowork). The author published no prompt, so this is our starting prompt built from his step list.
It asks for the report in the conversation instead of the email the author's agent sends him, adds a list of overdue customers missing from the Sheet and unreadable items, and says to change nothing in the invoice system. The system, sheet and template are blanks for you to fill in.
Every Monday evening, open [my receivables or invoice system] and list invoices that are past due. Match each customer against my Google Sheet [name] (customer name, contact name). For each match, draft a late-invoice reminder from my template [paste template], using the contact name and each overdue invoice's number, amount and due date. Save the drafts in my Drafts folder. Do not send any email. Then give me a short report: customers included, amount owed per customer and the total, plus any overdue customer who is not in my Sheet and anything you could not read. Do not change or mark anything in the invoice system; I review and send the drafts myself.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Categorize bank transactions, number vouchers, match payments to invoices and draft year-end accounts
Have Claude Cowork do the bookkeeping from a bank statement and spreadsheet, match payments to invoices and draft year-end accounts, as the author describes in a LinkedIn post that he says Claude wrote.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork with access to your bookkeeping spreadsheet (and a backup copy), your bank statement export and your sales invoices; last year's accounts prepared by your accountant, for the format; a rules file kept alongside the spreadsheet; your own answers to its questions; your accountant's review.
You are helping me with bookkeeping in Cowork. Files: bank statement [file], bookkeeping spreadsheet [file], sales invoices [folder], last year's accounts from my accountant [file]. Step 1: make a backup copy of the spreadsheet before changing anything and tell me where it is. Step 2: read the spreadsheet and describe my categories, how voucher numbers run and which kinds of transaction never get a number; wait for me to confirm. Step 3: fill in only blank rows where the category and voucher number are clear from the history; for anything new or ambiguous, list a question for me instead of guessing, and never overwrite a filled row. Step 4: check your work against the backup: row counts, and gaps or duplicates in the numbering; report what you find. Step 5: match each client payment to a sales invoice and list any invoices still outstanding and any matches you are unsure about. Step 6: save the rules we agreed, and my answers, to [rules file] and show me what was added. Then, only after I have reviewed all this, draft this year's accounts in the same layout as last year's, section by section, from the categorised data, and flag anything that needs my accountant's judgement (for example depreciation, tax and opening balances) instead of filling it in. Do not send anything to my accountant or anyone else.
Screen potential clients against your ideal-client criteria and log the scores in a spreadsheet
Have Claude Cowork screen potential clients against your ideal-client criteria and log each score with a link to its proof in a spreadsheet, the agent the author describes.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Cowork; your written ideal-client criteria and any disqualifying rules; access to the sites it searches (the post does not say how); a spreadsheet for the results; your own decision on who to contact.
Screen potential clients for [my business]. My ideal client is: [criteria]. Skip any company that [disqualifying rule, for example already has its own IT staff]; check that before you score. Find companies through [job postings, LinkedIn, Upwork or other places I name] that look like [type of company or role]. For each company, read its website and LinkedIn page, then score it from [low] to [high] against my criteria. For every score, record a link to the evidence behind it. If you cannot check something, give the company no score and write down what is missing and why. If two sources disagree, record both with their links; if either source fails my criteria, disqualify the company; if you cannot tell which source is accurate, give the company no score and flag it for my review. Put everything in a spreadsheet called [name]. Do not contact any company or send anything; I decide who to reach out to.
Stage bookkeeping entries from receipts and bank rows for owner approval
Have Claude Code or Codex work through a bookkeeping backlog: read receipts and invoices, propose accounts and VAT, match bank rows, and stage draft entries that wait for your approval before anything is posted.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code or Codex with your own Anthropic or OpenAI subscription; a bookkeeping platform the agent can reach through a CLI or MCP server with a stage-then-approve queue (he used Igdrasil); your receipts, invoices and bank feed in that platform; a practice company for testing; your rules for voucher series, recurring accounts and what should wait; your own approval of every posting and anything sent to the tax authority
You're helping me with the books for my company [name] in [bookkeeping tool], which you can reach through its CLI/MCP. Work in drafts only. First, list what is unmatched in the bank right now and group the rows. For each group, read the linked receipts or invoices and propose the account, VAT code and business purpose, and flag anything unclear, new suppliers, mixed VAT or unpaid supplier invoices for me instead of guessing. Use voucher series [series] and these rules: [account rules, what should wait]. Create draft entries and stage them for my approval, then check the draft set for duplicates and show me a list of what you staged. Do not post, approve, correct or delete anything, file or send anything to the tax authority, export to other systems, create test entries, or change any code. After I approve a batch and it's posted, read the ledger back and give me a reconciliation, not a summary.

