MURAGE™
How it worksFeaturesSolutionsUse casesComparePricingLearn
DownloadDownload
MURAGE™

An AI Chief of Staff and a team that does the work. Open source, from Ferrox Labs.

Product

  • Features
  • How it works
  • Engines and apps
  • Privacy and security
  • Pricing
  • Murage Cloud
  • Download
  • Changelog
  • FAQ

Solutions

  • Solopreneurs
  • Founders and startups
  • Agencies
  • Ecommerce
  • Small business
  • Creators and educators
  • Developers
  • SaaS
  • Nonprofits
  • Consultants and freelancers
  • Customer success teams
  • Legal and professional services
  • Small teams
  • Sales teams
  • Operations managers
  • OpenClaw and Hermes
  • Industries
  • Use cases
  • Build your team

Compare

  • vs Claude Code
  • vs Codex (ChatGPT Work)
  • vs Claude (Cowork)
  • vs Paperclip
  • vs OpenClaw
  • vs Hermes Agent
  • vs Manus
  • vs Genspark
  • vs n8n
  • vs Zapier
  • vs Grok Bot
  • vs Meta Muse
  • vs Claude Duet
  • vs OpenAI Dots
  • vs Cue by Manus
  • vs Instinct
  • vs Viktor
  • vs Lindy
  • vs Tasklet

Resources

  • Learn
  • Docs
  • Team library
  • Team gallery
  • Skill library
  • AI Chief of Staff
  • How we test
  • Limits
  • Switching to Murage
  • Open source
  • Blog
  • Community on Discord
  • Release notes

Company

  • About
  • Why trust Murage
  • Press
  • Partners
  • Enterprise
  • Contact
  • Privacy
  • Terms
  • Cookies

© 2026 Ferrox Labs, LLC. Murage is open source under AGPL-3.0. Murage™ is a trademark of Ferrox Labs, LLC.

Blog

By Sean Donahoe·Oct 28, 2026·2 min read

Get paid faster: a weekly invoice chase that runs itself

How to set up a Murage team that sorts your overdue invoices, drafts a reminder for each one in the right tone, and keeps a chase log. You press send.

Cover image for Get paid faster: a weekly invoice chase that runs itself

"Just following up on invoice 1043" is the worst email in business. Not the hardest to write. The worst. It goes to someone you like, about money they owe you, and every week you don't send it the next version gets harder, because now you also have to explain why you waited.

So it doesn't get sent.

Most late payment looks like that. The work was done, nobody is unhappy, and the invoice sits in someone's accounts department because nobody chased it. A small team in Murage can do the chasing. It sorts your overdue invoices, drafts one reminder for each in a tone that matches how late it is, and keeps a log of who was chased and when. Nothing goes out until you approve it.

You need Murage with an AI engine behind it (Fuigo, your existing Claude or ChatGPT plan, or an API key) and your aged receivables report, which every accounting tool can export; if your accounting app is already connected, the bot reads it straight from there instead. If you want the reminders waiting as email drafts, Gmail or Outlook connects through Flux Router or your own connected-apps key.

The tone ladder, and what comes back

Drop the export into a Murage project, so the file, your notes and the chase history live in one place. Then tell your Chief of Staff how firm to be, and when:

Here is our aged receivables export. Draft a reminder for every
invoice over 30 days. Friendly at 30 days, firm at 60, final notice
at 90. Repeat reminders get one step firmer. Send nothing.

Those words are kept as a rule, so next month's run uses the same 30, 60 and 90 day steps without you saying so again. If there is a line you want in every final notice (bank details, a phone number, the name of the person to call), add it now rather than editing it into each draft later.

Your Chief of Staff picks the specialists. On this job that is usually Numbers, who sorts by age, amount and payment history, Ops, who tracks who has been reminded and when, and Copy, who writes the reminders and keeps them short.

What comes back is a summary and a stack of drafts. Say sixteen invoices past 30 days: nine first reminders, five second, two final notices, each carrying the invoice number and the amount.

Then you read. The client who has paid you on time since 2016 and is 61 days late for the first time does not get the firm template; soften it, or just ring them. Tighten the one that is too apologetic. Approve the rest.

Murage keeps the chase log, so next week it already knows that last week's nine first reminders are now due a second, firmer one, and it won't send a friendly note to someone who had a firm one seven days ago.

Monday at 9

Ask for the chase to run every Monday at 9. Your Chief of Staff proposes a routine, and nothing is scheduled until you press Confirm. The routine runs while your computer is on and Murage is open. If the laptop was asleep at 9, a run up to 12 hours late still happens when Murage comes back, so a 9am Monday routine on a laptop you open at 10 is fine.

Two things it never does

It never sends without you. New bots start on Ask, so every reminder is a draft until you approve it, and anything that touches payments waits for you as well (the stop line explains how that works).

And it never marks an invoice as paid. "The bot knows which reminders went out, why can't it tick the invoice off" is a fair question. We kept it out because the bot doesn't know what landed in your bank account. Your accounting tool stays the source of truth, you update it, and the next export shows the change. The team can't know that a client paid by bank transfer yesterday and the export hasn't caught up; you can, and a reminder for an invoice that was paid yesterday is the one email worse than no reminder at all.

When to skip it

Two overdue invoices a year, write them yourself. This pays off when invoices go out every week and the chase keeps sliding to next Monday. And take any real dispute out of the batch and pick up the phone, because firmer wording won't settle an argument about the work.

The invoice chasing use case shows the whole job and the Get Paid team in the library is a ready-made place to start. Download Murage, export the overdue list, and get this week's reminders drafted before lunch. You still press send on each one. Murage won't do that part for you.

Sean Donahoe, founder of Ferrox Labs, which makes Murage.

Checked against Murage 1.0.8.

Keep reading

Oct 25, 2026

Back from the holidays without reading every email

After time away, the goal is not to read everything. It is to know what needs you first. How to ask a Murage team for a catch-up brief, with draft replies waiting and nothing sent.

Oct 25, 2026

Get your paperwork ready for your accountant

A year of receipts and invoices does not have to become one frantic weekend. How to have a Murage team sort the folder, list what is missing and draft a one-page summary for your accountant.

Oct 25, 2026

Tidy your downloads folder with AI, and see the plan first

A new-year folder tidy where nothing moves until you approve the plan. How to sort, rename and flag duplicates in Murage, and keep the folder tidy with a weekly routine.

Try the thing you just read about.

Give your first job to Murage.

Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.

Download Murage

No account needed · Runs on the AI plan you already pay for