← Back to examples
Agentic example

Invoices paid, without you chasing anyone.

Agentic examples · Markus

A conversation is free.
£199 buys the Working Diagnosis - the plan for your version of this.
Building and running it starts from £399/month.

Somebody pays an invoice. You find out three days later, when you happen to check the bank - and by then you've already sent a chaser email you didn't need to.

An agent can watch for something happening, work out what it means, and get the boring three-step follow-up ready for you - without you having to remember to do any of it.

Nothing here moves money, and nothing sends itself. That's not a limitation I'm apologising for - it's the whole point. Read on for why.

Phase 1 - the agent watches and matches

Step 1

Read-only bank access

View only. It cannot move money, and never can.

Step 2

Match to invoices

A new payment matched against your open invoices.

Step 3

Draft, don't act

A CRM update and a thank-you email, drafted only.

1. Read-only bank access. Open Banking lets an agent see your business account transactions - view only. It cannot move money, and it isn't given the ability to.

2. Match to invoices. A new payment lands. The agent matches the amount and reference against your open invoices and flags the ones it's confident about.

3. Draft, don't act. For each match, it drafts two things: an update marking the invoice paid in your CRM, and a short thank-you email to the customer confirming receipt.

Phase 2 - you're still the one who decides

Step 4

You check the queue

Matched payment, proposed CRM update, proposed email.

Step 5

One approval, both actions

Approve, and the CRM updates and the email sends.

Step 6

Unclear waits for you

A part-payment or mismatch - never guessed.

4. You check the queue. Drafts sit in one place - matched payment, proposed CRM update, proposed email - for you to glance at, not hunt for.

5. One approval, both actions. Approve, and the CRM updates and the email sends. Reject or edit, and nothing happens until you say so.

6. Anything unclear waits for you. A part-payment, a mismatched reference, an amount that doesn't quite fit - the agent doesn't guess. It leaves it for a human to look at properly.

Why nothing runs on its own

I could build this to auto-send the moment it finds a match. I won't, and I wouldn't recommend anyone build it that way. Money and customer-facing messages are exactly the two things worth a second of a human's time before they go out - the cost of checking is tiny, and the cost of an agent getting one wrong in public isn't.

Agents draft, agents prepare. A human decides. That's not a compliance line - it's how I'd want my own accounts handled, and it's the only way I build anything like this.

Worth saying plainly: this is shown as a simple version. The same pattern can be built simple or pushed a lot further - more sources it watches, more it can draft, more it checks before handing back to you - depending on what your business actually needs.

Wondering if this needs new software first? Usually not - here's how that actually works.

What the £199 buys, and what it doesn't

The Working Diagnosis buys the plan for your version of this - which invoices, which CRM, which bank, and where the approval step actually sits in your day. Not the build itself. The report is yours to keep either way. If we go further, the £199 is credited off the first invoice.

If chasing payments is eating more time than it should, send a note. I reply myself, usually within a working day. We'll work out whether this is worth doing for your business. Happy to talk after 6pm or at a weekend if that works better around the job - within reason, I'll fit round you.

Send a note - I reply within a day
← Back to examples