Friday Numbers, Thirty Minutes
10 min read
The Monday block runs the business forward. The Friday session looks at what the week did, in dollars, and it exists because of an honest observation about owners: everyone agrees they should review their numbers weekly, and almost nobody does, because the review has no fixed shape. Thirty minutes, three questions, one skill. That is the shape.
The setup
The workhorse is the Finance Analyst Copilot from the toolbox, installed and pointed at the Brain like every other skill on your roster. Its setup interview wants your revenue lines, your fixed monthly costs, and your invoice terms; give it real figures, because a finance skill running on vague inputs produces confident vagueness back, which is worse than nothing.
Each Friday you bring it the week's raw material: money in, money out, invoices sent, invoices still open. Where that comes from depends on your bookkeeping; a copy-paste from your accounting software's week view is fine, and for a small operation, a typed six-line summary is fine too. The skill does not need beautiful data. It needs true data.
The three questions
The session is the same three questions every week, written into the runbook so Friday-afternoon brain does not have to compose them:
WORKFLOW: Friday Numbers
TRIGGER: Calendar. Friday, 15:00, 30 minutes.
1. [You] Paste the week: in, out, sent, open.
2. [Skill] Q1: Where is cash, and where will it be in
4 weeks if open invoices pay on their usual
schedule?
3. [Skill] Q2: Who owes us, how old is each debt, and
which two does the Chaser ladder hit Monday?
4. [Skill] Q3: What changed vs the last 4 weeks, and is
any change a trend or a blip?
5. [You] CHECKPOINT (5 min). Sanity-check any number
that drives a decision, against the source.
6. [You] One line in the week sheet: cash position,
biggest open invoice, one decision made.
DONE WHEN: The week-sheet line exists.Question 2 is where Friday feeds Monday: its output is the input for the pipeline sweep's invoice chasing, which means collections stop depending on the owner's memory of who owes what. Question 3 is where trends surface while they are still cheap: maintenance-plan signups drifting down for three straight weeks is a marketing conversation, and it gets had in week three instead of quarter's end.
The discipline of the checkpoint
Step 5 deserves respect. A finance skill will do arithmetic on whatever you paste, and if the paste dropped a line, the analysis is cleanly, plausibly wrong. The check is one habit: any number about to drive a decision, a hire, a purchase, a price change, gets traced back to the source document before the decision is made. Chapter 5 generalizes this into a full toolkit; on Fridays, this single trace-back covers most of the risk.
A second rule, standing and non-negotiable: the session analyzes; it does not transact. No payment gets scheduled, no transfer gets made "while we're in here." Decisions leave the session as notes in the week sheet, and money moves through your normal channels with your normal authorizations. Keeping analysis and execution separate is what makes it safe to eventually hand this session, too, to someone who is not you.
Month end
The first Friday of each month, extend the session to 45 minutes and add a fourth question: how did the month land against the last three? Revenue, costs, margin, and the one number your business watches most. This is not a books close, your accountant still does that; it is the owner's version, early and rough, which is exactly what the accountant's version, accurate and late, can never be.
Try it now
Install the Finance Analyst Copilot today, run its setup with real figures, and hold your first Friday session this week using the three questions verbatim, even if your "paste" is six typed lines. Put the recurring Friday block in your calendar next to Monday's. Your calendar now holds the system's whole heartbeat: plan and run on Monday, count and correct on Friday.