The Monday Review: Is Your Consulting Business Actually Alive?
Most consultancies don't die in one bad month. They stop moving in small ways nobody writes down: a pipeline with no reply in two weeks, a project that has quietly become charity work, an invoice that keeps not being mentioned. Each one is survivable. Unnoticed together, they are what a dead business looks like months before anyone calls it dead.
The Monday Review is a twenty-minute check built to catch those four things while they are still small. Same time every Monday, before the week starts. You need only what you already have: last week's calendar, your active project list, your unpaid invoices, and whatever actually got finished.
Four questions, in this order.
Question one: did anything in the pipeline move this week?
Not "how many leads do I have." A list of names is not a pipeline, it is a contact sheet. The question is whether anything changed state in the last seven days: a reply arrived, a call got booked, a proposal went out, a follow-up was answered.
Count those state changes. That count is the metric.
Zero is not automatically a crisis; one quiet week happens to everyone. Zero for three weeks while you are heads-down on delivery is how a business runs out of work two months after it looked busiest.
The action: take the three oldest conversations that went quiet and send one specific follow-up to each. Specific means it references the last concrete thing they said, not "just checking in."
"You mentioned the board wants the pricing work before Q1 planning. Is that still the timing, or has it moved?"
One question, easy to answer, no apology. Those three messages are usually the highest-yield minutes of your week.
Question two: is any project quietly losing money?
For every active project, compare hours logged against hours assumed. On fixed-fee work the test is blunt: if the hours spent at your normal rate now exceed the fee, you are subsidizing that client.
You rarely need to wait for the finish line. Compare the percent of hours used against the percent of work done. Seventy percent of the hours at forty percent of the deliverable is an early warning, and it is far cheaper to raise now than at delivery, when the conversation becomes about the bill instead of the work.
The action: for any project in the red or heading there, pick one of two honest paths this week — have the scope conversation, or decide on purpose to absorb it. What you cannot do is leave it undecided. Undecided is how a project turns into a grudge.
One overrun is weather. The same overrun on three consecutive projects is pricing or scoping, and the weekly review is where you notice the pattern while it is still cheap to fix.
Question three: who owes you money, and for how long?
List every unpaid invoice with its age: current, past 15 days, past 30, past 60. Two numbers matter — the total overdue, and the age of the oldest one.
If that oldest number keeps climbing month after month, you do not have an admin problem. You have a client-health problem wearing an admin problem's clothes.
The action: one specific email per overdue invoice, sent Monday, oldest first. Not a statement, not a reminder system — one line with a date and a question:
"Invoice 1042 was due on the 30th. Can you confirm it is in this week's payment run?"
Friendly, dated, no apology, no "just following up." You are not asking for a favour; you are confirming a scheduled event.
Question four: did the business move forward, or just stay busy?
Busy and forward are different things. Busy is the week you answered everything and shipped nothing new. Forward leaves evidence: a deliverable accepted, a decision unblocked, or one part of the business itself made better — a proposal template that now takes an hour instead of three, a service page written, a step you will never have to work out again.
The action: write one line in the same note each week — this week the business moved forward by ___. If the line stays empty, that is not a reason to skip it. The empty line is the finding.
Where a model helps, and where it does not
The mechanical half of this review is summarizable in a couple of minutes from notes you paste in: turn last week's calendar and sent mail into a list of pipeline state changes, list projects by hours against scope, list invoices by age. A capable chat model also does it without the flinch that makes people round their own numbers in the flattering direction.
It cannot set the priority order below, and it cannot make the call you are avoiding. Drafting is the easy half; the review only works if a person decides.
When two or more answers are bad
Do not build a recovery plan. Work in this order, because cash fails fastest and quietest:
- Money owed (question three). Payment for work already delivered is the cheapest revenue available this week.
- Pipeline movement (question one). Tomorrow's cash, and the last thing you can still influence before a dry month arrives.
- Project margin (question two). Today's leak — fixable with one conversation.
- Forward motion (question four). The compounding work. Important, and the only item here that can wait a week without getting worse.
One action per bad answer, this week. The review is a habit, not a rescue.
Keep the record
The individual Monday is not the point; the series is. After a month you have four weeks of the same four answers, and a trend is much harder to argue with than a memory. Two of the questions — pipeline movement and margin drift — only become visible over time, which is exactly why a monthly review tends to find them after they have already cost you something.
Four questions, twenty minutes, written down. A consulting business that is alive is not one having a good week; it is one where these four things keep moving.
This note describes a routine, not a result. No revenue outcomes, client engagements or success rates are claimed. Bracketed placeholders are slots to fill from your own records.
Related notes
- Four Numbers Every Freelance Tracker Should Calculate — the monthly version of the same checks, computed instead of answered.
- Scope Doesn't Creep. It Gets Invited. — the mechanism behind most of the margin problems question two surfaces.
- The Decision Log, Not the Notes — the record that makes question four answerable with evidence instead of a feeling.