Most owners learn how last week went on Thursday, in fragments: a QuickBooks screen after dinner, a scheduling app in the truck, a bank balance that doesn't match the feeling in the shop. The data existed the whole time, sitting in three systems that never talk to each other. What never existed was the spare morning to pull it together.
Five numbers, and you pick them
Every piece of software you use ships with a dashboard, and every one of those dashboards was designed around what that product happens to measure. The scheduling app celebrates jobs. The phone system celebrates calls. The accounting file knows the truth and makes you dig for it. None of them was designed around what you, personally, would check first thing if checking were free.
A digest inverts that. Before anything gets built, you name the numbers you actually steer by. For a service contractor that is usually some version of: jobs booked versus completed, dollars invoiced, receivables past 30 days, calls missed and recovered, average ticket. For a retail counter it might be sales against the same week last year, labor as a share of sales, and the week's top mover. The list is yours, it is short on purpose, and when a number stops earning its place you swap it for one that does. Vendor dashboards measure what the vendor sells. This measures what you watch.
What Monday's message can look like
Here is the shape of it — the figures below are an illustration, not anyone's real week:
Week of Aug 3–9.
Booked 31, completed 27. Four carried over — three waiting on parts.
Invoiced $18,400. Past 30 days: $6,120 across five invoices; oldest is 47 days.
Missed calls: 14 texted back, 9 replied, 5 booked.
Average ticket $412, in line with the last six weeks.
Flag: Tuesday calls up sharply after the storm on the 4th. Wednesday's board is full; Thursday has room.
Six lines. Under a minute to read, at the counter or in the truck, with nothing to log into and nothing to interpret.
Where the numbers come from
Late Sunday night, a scheduled job queries each system through its own interface: the field-service or CRM software for jobs and estimates, the accounting file for invoices and the receivables aging, the phone platform for call counts and text-back outcomes. The results are assembled into one message and sent to you at the time you chose.
The honest complication is that these systems disagree with each other. A job marked complete in the scheduler is not necessarily invoiced in the books, and the gap between the two is not a defect in the report — it is a finding. "27 completed, 24 invoiced" means three finished jobs have not been billed, and that line has a way of fixing itself once it shows up every Monday with your coffee. A digest built well surfaces the mismatches between systems instead of smoothing them over.
A flag in plain English, not a chart
Each number is compared against its own history — the trailing several weeks, and where seasonality matters, the same week last year. When something moves outside its normal range, the digest says so in a sentence: "Tuesday calls up sharply after the storm." When the likely cause is visible in the data — a storm date, a holiday, a price change you logged — the sentence names it. When the cause is not visible, the sentence says that instead, which is your cue to ask around the shop.
The order of operations matters. Arithmetic decides whether a flag exists — thresholds against history, not impressions. The language only states what the arithmetic found. The failure mode of most "AI reporting" is prose that sounds insightful about numbers that are ordinary, and the way to prevent it is to let the words carry no authority of their own.
Delivered where you already look
The digest arrives as a text or an email — 6:30 Monday morning is a common choice. Not a dashboard, and that is deliberate. A dashboard assumes a habit of visiting it, and the graveyard of small-business software is full of beautiful screens with four logins in the last quarter. A message requires no habit. It interrupts you once a week, briefly, and it is done.
When a line raises a question, you reply to the message, and the question goes to a person who can pull the detail behind it.
What a digest cannot tell you
It is only as truthful as the systems underneath it. If jobs are not closed out or invoices sit unentered until Friday, the digest reports that fiction with full confidence, and a confident wrong number is worse than no number at all. The first few weeks usually expose bookkeeping habits before they expose business trends — which is uncomfortable and useful in equal measure.
It reports; it does not diagnose. It can tell you receivables grew by $4,000 this week. It cannot tell you the general contractor on your biggest job is stalling. The sentence points at where to dig; the digging is still yours.
And one week is weather. Small operations have noisy weeks, and a weekly report will tempt you to re-plan every Monday. A single soft week means very little; four in a row is a trend. The discipline of not reacting is part of using the tool well.
It also does not replace your bookkeeper or your monthly close. It is a Monday habit, not an accounting system.
Where to start
Write down the five numbers you would check every Monday morning if checking cost you nothing. If five don't come to mind, start with three — and make one of them receivables past 30 days, because that is the number that gets away quietly while everything else feels fine.