Replace 'How'd We Do This Week?' With a Report That Sends Itself

Every Monday morning, in thousands of small businesses, the same conversation happens.

"How'd we do last week?"

And then twenty minutes of people trying to remember. Someone pulls up a screen. Someone says "I think we did about nine jobs?" Someone else corrects them. Nobody's sure how many leads came in. The owner leaves the meeting knowing roughly what they knew going in, and the whole thing gets repeated in seven days.

That is not a management meeting. That is a data-gathering exercise with a table and coffee, and it should be a text message that arrives at 7am whether anyone shows up or not.

Why the meeting exists

It exists because the information isn't anywhere. If the numbers lived somewhere anyone could see, nobody would need to sit in a room reconstructing them from memory.

So the meeting is a symptom. Kill the symptom and you haven't fixed anything — people will still not know how they did. Fix the underlying problem, which is that your business does not currently produce a record of itself, and the meeting stops being necessary on its own.

The good news: the record is mostly there already. It's scattered across your phone system, your invoicing tool, your calendar, and your inbox. It just never gets assembled.

What goes in the weekly report

Keep it short enough to read on a phone while the coffee brews. Five to eight lines. Each one with a comparison, because a number without a comparison is not information.

Leads. How many came in, from where, versus last week and versus the four-week average.

Response time. Average minutes to first contact, and the percentage handled within an hour.

Quotes. Sent, and their total value.

Jobs. Booked, and completed.

Revenue. Booked, and collected. Two different numbers, both of them true, both of them worth seeing.

Outstanding. Quotes waiting on an answer. Completed jobs not yet invoiced. Invoices past due.

Next week. What's on the calendar. This is the one that turns a report into a decision, because it's the only forward-looking line in the whole thing.

Then, at the bottom, anything that crossed a line you set. "3 leads went uncontacted for more than 4 hours." "Two invoices are more than 30 days past due." "Zero leads on Thursday."

That's the report. If it's longer than a phone screen, it's too long, and the parts past the fold are decoration.

The comparison is the whole thing

"We got 23 leads" is trivia.

"We got 23 leads, down from 31, and down from a 4-week average of 29" is a reason to go look at something.

Every single line needs the comparison. This is not a design preference. It's the difference between a report you glance at and a report that makes you act. Human beings are bad at absolute numbers and very good at noticing that something moved. Build for the thing people are good at.

Use an arrow. Up, down, flat. That's the entire visual design budget you need.

How to build it without a project

You do not need a data warehouse. Here's the escalation ladder — start at the bottom rung and only climb when the current rung annoys you.

Rung one: someone fills it in. A template. One person, twenty minutes every Friday afternoon, fills in the same seven lines and sends them. That's it. It's manual and it's fine, and it is enormously better than the Monday meeting because at least the numbers exist and they're consistent week to week.

Do this first even if you plan to automate. It forces you to define each number precisely — and you'll discover, when someone has to fill in "average response time," that you have no way to compute it. That discovery is the real value of rung one.

Rung two: half automated. Most of your tools will already email you a summary. Your phone system can send call stats. Your invoicing tool can send an accounts-receivable summary. Turn those on and have them land Monday morning. The report is now three emails instead of one, which is worse than one but way better than none.

Rung three: assembled. A small script pulls the numbers from wherever they live, does the arithmetic and the comparisons, and sends one message. This is the real version. It's not a big build. It's a scheduled job that reads a few APIs and formats some text.

Once it exists, it runs forever and costs nothing, and the Monday meeting is optional.

Send it to the phone, not the inbox

The delivery channel decides whether this works.

If it goes to email, it competes with 140 other emails and loses. If it goes to a dashboard behind a login, it loses harder — you have to remember to go look, and on a Monday you will not remember.

Text it. Or put it in whatever chat tool your team actually watches. The report should arrive uninvited, in a place you're already looking, and require zero clicks to read.

I've watched carefully-built dashboards go unopened for months while a plain-text Monday summary got read every week for years. The difference was never the quality of the data.

Then use it

A report that nobody acts on is just a more efficient way to feel informed.

So attach the report to a habit. Fifteen minutes on Monday, alone or with one other person, and exactly three questions:

What moved, and why? Not every line. The one or two that moved most.
What's stuck? The outstanding section — the quotes waiting, the jobs uninvoiced, the leads not called. Assign each one a name and a deadline, right there.
What one thing do we change this week? One. Not a list.

That's a fifteen-minute meeting that produces decisions, instead of a forty-minute meeting that produces a shared understanding of last week.

The compounding part

Here's why this matters more than it seems.

A weekly report creates a record. After six months, you have twenty-six weeks of the same numbers, measured the same way. Now you can see things that are invisible week to week:

The slow drift in response time that's been happening since you hired the new guy
The seasonality you always felt but never confirmed
The channel that's been quietly degrading for two months
The fact that your quote-to-close rate dropped the week you raised prices, and recovered three weeks later

None of that is visible in any single week. All of it is obvious in a table of twenty-six. And you cannot go back and generate that table retroactively — the data has to have been captured, consistently, the whole time.

Which means the best day to start the weekly report was a year ago, and the second best day is Friday.

Do this Friday

Write the seven lines. Fill them in by hand. Send them to yourself Monday at 7am.

Do that for four weeks. You'll immediately know which numbers you can't get, which ones you don't care about, and which one you find yourself staring at. Then automate exactly that, and delete the rest.

The meeting goes away on its own once nobody needs it.

If you want the assembled version — one message, every Monday, no login, no meeting — that's the kind of system I build. Drop me a line and tell me what you'd want on the first line.