Kit

Invoicing & Getting Paid

What you are owed, how late it is, and the chase already written — rebuilt from a year of your own sent mail. Nothing is ever sent for you.

Cashflow dies in the gap between "sent" and "paid", and most of that gap is already in your sent mail. The first sweep reads back through a year of it — the invoices you issued and the remittances that came back — and builds the book: every invoice with its number, who it went to, what it was for, when it was due, and whether the money has landed. From then on the board shows what you are owed, how much of it is late and by how long, what has been paid lately, and which invoices are ready for a chase. Drop a remittance or a bank statement into your vault and the matching rows are marked paid — one at a time, asking when two could fit, never a sweep through your ledger. On Thursdays Brook picks the invoices that have gone too long and Sorrel writes each chase into your drafts, in your own voice, and stops there. Nothing is ever sent for you, and nothing here tells you what a client is worth putting up with.

Try it free

2 agents, 1 routine, 1 dashboard, 1 record, 2 skills, 1 workflow. Installing offers the first sweep on the same screen — connect, run it, and everything can be retimed or paused after.

Getting PaidExample data
Outstandingacross 4 invoices
$14,000

$8,800 of it past its due date

May
Jun
Jul
Aug
Sep
Ready to chaseInvoice book
INV-1042 — Aisha66 days past due$4,800
INV-1044 — Tomaspart paid · 40 days past due$1,400
INV-1046 — Marcopart paid · 24 days past due$2,600
INV-1048 — Danadue in twelve days$5,200
Owed, by how lateas at Monday’s sweep

0–30 days

$2,600

31–60 days

$1,400

61+ days

$4,800

The crew

Brook

Keeps the book of what you are owed, notices what has gone too long, and never chases anyone for you.

Steady and unhurried; keeps running whatever the weather, and never raises its voice.

Sorrel

Writes the chases into your drafts, in your voice. Never sends.

Courteous, plain and unflustered; asks once, clearly, and never leans.

What else it installs

Invoice bookrecord

One row per invoice — the number, who it went to, what it was for, when it was due, and whether the money has landed.

Invoice captureskill

"Sent Aisha INV-1042 for the phase-one work, 4,800, thirty days" — one sentence, and the book knows.

Invoice chase draftsskill

Writes the chase into your drafts, in your voice. Never sends.

Getting Paiddashboard

What you are owed, how late it is, what has landed lately, and who is ready for a chase.

Invoice sweeproutine

Mondays — files what you invoiced, marks what has been paid, and says what has gone past its date.

Runs mondays · 8am

Invoice chaseworkflow

Each Thursday it picks the invoices that have gone too long and drafts a chase for each.

Runs thursdays · 9am

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

  • Invoice sweep runs mondays · 8am and keeps the Getting Paid dashboard fresh. Mondays — files what you invoiced, marks what has been paid, and says what has gone past its date.
  • Invoice chase runs thursdays · 9am, in 2 stages: Brook reads and picks (handing over needs chasing), then Sorrel drafts the chases (handing over drafted).
  • What is captured lands in the Invoice book record, which lives at Data/Invoice Book in your vault — yours to open, search, and edit like any other file.
  • The Getting Paid dashboard reads from the record and shows, at a glance: outstanding · overdue · paid in the last 90 days · invoices on the book · owed, by how late · on the book, by status · raised, month by month · ready to chase · the book · every invoice — tap one to open that client · how this board works.

The wiring, in one breath: Brook holds Invoice capture · Sorrel holds Invoice chase drafts · Invoice capture writes to Invoice book · Invoice sweep writes to Invoice book · Invoice book shown by Getting Paid · Getting Paid kept fresh by Invoice sweep · Invoice sweep run by Brook · Invoice book feeds Invoice chase · Brook hands over to Sorrel.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

  • Open Getting Paid on a Monday, after the Invoice sweep has run. Outstanding and Overdue are the two numbers; Owed by how late tells you whether this is one stubborn invoice or a drift across the book.
  • Say an invoice the moment it goes out — "sent Aisha INV-1042 for the phase-one work, 4,800, thirty days" — and Invoice capture files it exactly where the sweep would have, due date and all.
  • When a remittance or a bank statement lands, paste it into the chat or drop it into your vault. Invoice capture matches it against the open rows and marks only what fits, asking when two invoices could take the same payment — that is what keeps Outstanding honest without a spreadsheet.
  • Read Ready to chase on Thursday, after the Invoice chase pass, then open your drafts: the wording is already pitched to how late each one is. Change what you want, send the ones you mean to, and leave the rest.
  • Ask Brook the questions a ledger would make you compute — "what has Contoso still got out", "what did I invoice last quarter", "what got paid this month" — and the answers come from your own book.
  • Tell Brook the standing rules once: your terms, when a chase should first go out and how often after, the client you never chase. Every sweep and every chase pass works by them — and when a row is wrong, say so; that correction is what keeps the board true.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, records and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

  • Your terms — thirty days, forty-five for the bigger clients — said once and used for every row filed after.
  • When a chase should first go out and how often after, and the clients who are never chased at all.
  • The mailbox your invoices go out from, so the sweep looks in one place instead of everywhere it can reach.
  • When the Monday sweep and the Thursday chase pass run — or turning either off and keeping the book by hand.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

  1. Adding the Kit ends at the first sweep’s own screen, where the email grant is asked for — that is the whole pitch, so the ask sits in front. Start it and Brook reads back through a year of your sent mail for the invoices you issued — number, client, amount, date due — and through what came back for the remittances that settled them, and builds the book from it. It reads; it never sends anything, never replies, and never chases a client. It is a real run and uses credits like any other.
  2. When that first sweep finishes, Brook leaves one short note in your 1Presence inbox saying what it filed — how many invoices, for how many clients — and invites a few minutes on the three things only you know: which mailbox your invoices go out from, which of these are actually yours to collect, and what your terms are. That is also where you say what has already been paid.
  3. Skip the sweep and the book still works by hand: tell Brook the invoices you have out — the number, who it went to, what it was for, the amount and when it was due — and the board fills from that. Nothing in that conversation touches your mail, and the Invoice sweep waits on your Routines screen until you choose to run it.
  4. After that the sweep runs on Monday mornings: it files what is new, marks paid only what a remittance matches beyond doubt, redraws the board, and raises a card only when something has gone past its date or a payment could not be placed. On Thursday mornings the chase pass runs — Brook picks the invoices that have gone too long, skipping anything you have already been in touch about in the last fortnight, and Sorrel writes each chase into your drafts. Nothing is ever sent.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits

Put the Invoicing & Getting Paid kit to work.

Install it, run it once against something that already happened, and see whether what comes back sounds like you.

Try it free

Everything it installs can be retimed, paused, or removed.