Command the Machines
0 / 5
7
BAND II · MONEY
Week 7 of 12 · GSTAAD · 1,050 m

Make Month-End a Non-Event

Month-end stops being an event this week.

Your numbers have been talking about you behind your back — to your accountant, quarterly, in a language you pay to have translated. This week they answer to you: any question against your own accounts, reviews that show only what's wrong, the cash crunch named six weeks early, a collector with no capacity for embarrassment — and on Friday, the most satisfying test in the course: you try to sneak one past the machine, and it catches you.

Not your desk? This week's moves work on any desk: ask your own numbers anything · review only the exceptions · see the crunch six weeks out.

Today · one task

Drop this quarter's export next to Week 2's documents and ask: which line moved most last quarter — and why? Then ask two more questions you'd have saved for the accountant. Save it as THE NUMBERS PRESS.

Your management accounts have been sitting on the shelf since week two — that was never an accident. Today you ask them anything, in plain English, and get the answer with the number attached.

You'll have: THE NUMBERS PRESS saved — and three real answers from your own accounts, without a call to your accountant.

  1. Freshen the shelf if it's easy. Your accounting system exports the latest management accounts in two clicks — drop the export into the Project next to the set from week two. If not easy, the shelf copy carries today fine.
  2. Ask the first question, and make it this one: "Which line moved most last quarter — and why?" Watch it answer with the number, the line and where it read it.
  3. Ask two more you'd normally save for the accountant — margin on your main offer, the cost line that's been creeping, what you actually spent on {the thing you suspect}. Save the press as THE NUMBERS PRESS.

You are my numbers press. Answer my questions from the management accounts and financial documents on my shelf — nothing else, never from general knowledge. Every answer carries: the number, the line it comes from, and the document and period you read it in. If the accounts don't hold the answer, say exactly what's missing and which export would fix it. Plain English throughout — I want the answer a sharp FD would give me across the desk, not a lecture. First question: which line moved most last quarter, and why?

COPY

Rescue — Only annual statements on the shelf? Use them — the habit is the lesson. Then send your accountant one line tonight: "Please send monthly management accounts as a spreadsheet export from now on." Two clicks their side, a new organ your side.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

You answered "which line moved most last quarter, and why" — without calling your accountant.

Want more — A live connection to your accounting system is the upgrade, where IT allows it — the press gets fresher, the habit stays the same. And keep the exports coming monthly: Wednesday's cash view and next week's Morning Page both drink from this well.

The numbers answer to you now. Tomorrow you stop reviewing everything — and start reviewing only what's wrong.

Today · one task

Export two lists that should agree — like your bank statement and your books. Paste both in and review only the mismatches, each with its reason attached. Save it as THE EXCEPTION PRESS.

Most of what you review each month was already right before you looked at it. Today the matched items learn to pass in silence — and only the genuine exceptions reach your desk.

You'll have: THE EXCEPTION PRESS saved — this month's reconciliation done in minutes, with every item you actually saw being a real exception.

  1. Pick two lists that are supposed to agree — the bank export against the invoice list, the supplier statement against your ledger, orders against deliveries. Export both; two clicks each.
  2. Paste them into the press below. It matches everything that matches — in silence — and hands you only the mismatches, each with the reason it surfaced.
  3. Review the exceptions only. Minutes, not the afternoon. Anything on the list you can't explain in one look goes to the person who can — with the press's reason line attached. Save as THE EXCEPTION PRESS.

Here are two lists that should agree: {name them}. Match them. Everything that matches passes in silence — do not show me matched items, do not summarise them, no victory laps. Surface ONLY the exceptions: items on one side and not the other, amounts that differ, dates that don't line up, anything appearing twice. For each exception: one line on what it is and WHY it surfaced. End with one number — how many items matched silently — so I know the silence was earned.

COPY

Rescue — It flagged half the list? Your two exports cover different periods. Match the date ranges and run again — most "exceptions" are just calendars disagreeing.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

This month's review took minutes — and every item you saw was a genuine exception.

Want more — Every pair of lists in your business that should agree gets this treatment now — stock counts, payroll against contracts, card statements against claims. The press doesn't care what it's matching; the silence is the product.

Exception-only is the new review. Tomorrow the same honesty looks forward — six weeks forward.

Today · one task

Type in today's bank balance, then give the prompt your receivables, payables and committed spend. Read the six-week view — and say the tightest week, and what causes it, out loud.

Cash crunches don't arrive — they approach, visibly, for weeks, while nobody assembles the picture. Today you assemble it: six weeks forward, your tightest week named, while there's still time to do something about it.

You'll have: THE CASH VIEW PRESS saved — a rolling six-week cash view built from your own receivables, payables and committed spend, with every assumption shown.

  1. Give it the raw picture: today's balance (one number, typed), what's owed to you and when it's due, what you owe and when, and the committed spend — payroll dates, rent, the standing orders. Exports where you have them, plain description where you don't.
  2. Read the six weeks it builds — week by week, in and out and running balance, with the assumptions listed at the bottom where you can argue with them.
  3. Name the tightest week out loud, and its driver. Then make one move while it's cheap: pull an invoice forward, chase the big one, shift the spend. Save as THE CASH VIEW PRESS.

Build my six-week cash view from what I give you: today's balance, receivables with due dates, payables with due dates, committed spend. Lay it out week by week: money in, money out, running balance. Then: (1) name the tightest week and what drives it; (2) list every assumption you made — what you assumed pays on time, what you estimated — plainly, at the bottom, where I can argue with them. This is a projection from my own numbers with the assumptions shown, not a prophecy — if an input is missing, ask me rather than invent it.

COPY

Rescue — Don't know the exact numbers? Rough ones, labelled rough, still draw the shape — and the shape is the win. Being a week out on the right crunch beats being precise about nothing.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

You can state your tightest week in the next six — and what drives it.

Want more — Refresh it every Monday with the fresh export, and by next week it feeds your Morning Page — the crunch that used to ambush month-end becomes a line you read over coffee.

The crunch has a name and a date now. Tomorrow you appoint the one employee who's never embarrassed to ask for money.

Today · one task

Paste the prompt above into a scheduled task set for Monday 07:30, and run it once now. Approve the batch of chasers in under five minutes — then send them yourself, today.

Somebody owes you money right now, and the reason they haven't been chased is that chasing is awkward. Meet the one employee with no capacity for embarrassment — and perfect manners.

You'll have: THE COLLECTOR on The Roll — every invoice more than a week overdue with a courteous, escalating chaser drafted and queued. You approve the batch. You send.

  1. Open a scheduled task and paste the order below. It reads your invoices and your sent mail, finds everything seven-plus days overdue, and drafts each chaser as a continuation of the real thread — first nudge gentle, later nudges firmer, all of them courteous.
  2. Run it once, live, now. Watch the first batch build. Read the drafts — approving the batch should take under five minutes. Send the approved ones yourself, today. That's the win, in front of you.
  3. Schedule it weekly, name it — THE COLLECTOR — and sign The Roll: what it does, what it may touch. Drafts and queues only — it never sends. Write the denial next to its name.
The Send Law · money edition

Money-adjacent words leave this building by human hand — always. The Collector drafts; you send. And its tone is locked to firm-courteous, because collections is where brands die: one snippy chaser costs more than the invoice. The machine supplies the persistence. You supply the name at the bottom — and the judgement about when persistence should become a phone call.

Every Monday at 07:30, read my invoice list and my sent mail. Find every invoice more than 7 days overdue. For each, draft a chaser that continues the REAL thread in MY VOICE — tone locked to firm-courteous, always: first chase is a warm nudge, second is a clear reminder with the amount and date, third asks plainly for a payment date and offers a call. Never threaten, never guilt-trip, never mention "final notice" — if a debt reaches chase four, flag it to me for a phone call instead of drafting. Queue everything for my approval; you never send anything, ever.

COPY

Rescue — It chased an invoice that's actually in dispute? Tell it once — "exclude {client}; that one's with me" — and it remembers. Note the exclusion on The Roll, next to its name.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

Every overdue invoice had its draft, you approved the batch in under five minutes — and you sent them.

Want more — Notice the pattern: this is week three's Deal Chaser aimed at invoices — same engine, same law, different silence. The machines are starting to rhyme. That's not coincidence; that's Week 12 approaching.

Name it, note its powers, sign The Roll — worker number three, and the politest persistent employee you'll ever have. Tomorrow you set a trap for the machine — and hope it catches you.

Today · one task

Plant one fake transaction in today's export. Run the sweep on the doctored list — then check the report caught your plant.

Every business has transactions nobody looks at twice — that's where duplicates hide, where odd amounts slip through, where the new payee nobody remembers approving lives. Today the machine sweeps them all. And you test it by cheating.

You'll have: THE AUDIT PRESS saved — a full sweep of your transactions with anomalies reported — and proof it works, because it caught the fake you planted.

  1. Plant the anomaly first. Take today's transaction export and seed one deliberate fake — a duplicated invoice, an amount with a digit swapped, a supplier that doesn't exist. Don't mark it. This is the test.
  2. Run the press below on the doctored list. It sweeps for duplicates, odd amounts, new payees, round-number oddities and out-of-pattern entries — read-and-report only.
  3. Check the report for your plant. Caught? That's trust, earned the hard way — you tried to sneak one past it and failed. Save as THE AUDIT PRESS; run it on the real list whenever you like, nightly when you're ready.

Sweep this transaction list for anomalies: duplicates (same payee, same or near-same amount, close dates), amounts that break the payee's pattern, payees appearing for the first time, suspiciously round numbers where the history isn't round, and anything out of rhythm with the rest. Report each anomaly with one line on why it surfaced. You read and report only — you change nothing, flag conservatively, and if the list is clean, say "clean" and stop. No drama, no padding: an honest sweep, however short.

COPY

Rescue — It missed your plant? Your fake was too good — or the sweep needs the history. Paste last month's list alongside today's and run again; anomalies are pattern-breaks, and patterns need a past.

You just built a machine. Give it a name.

Say what it does and what it's allowed to touch, then tap the button. It joins the count at the top of your screen — that count is your workforce, and it grows every week.
Did you get this done?

Your planted anomaly — caught.

Want more — The nightly schedule is the natural home when you're ready: every transaction swept while you sleep, the morning report waiting. Powers never change: read-and-report, forever. Week 10 audits the auditor.

Week seven is in. The numbers answer to you, reviews show only what's wrong, the crunch is named six weeks early, the politest collector in the business is on The Roll — and the machine passed the one test that matters: you tried to fool it, and it caught you. Next week it answers bigger questions than money.

Week 7

Month-end is a non-event now.

Five for five. Your accounts answer plain-English questions with numbers attached, matched items pass in silence, the tightest week of the next six has a name and a driver, worker number three chases money with perfect manners — and when you planted a fake anomaly to test the sweep, it caught you. That last one is what trust looks like with machines: earned, adversarially.

0 of 5 done

The week's quiz · seven questionsNO PASS MARK · IT TEACHES
Continue → Week 8