Weekly numbers report
Half of Monday back, about 3 hours a week. Last week's numbers land on one page in your inbox before anyone has to ask for them.
3hours a week back, typically
In your inbox, Monday 6am
Weekly numbers
Week 43: jobs up, cash a bit behind
- Jobs completed48 (last week 41)
- Invoiced$61,200 (last week $54,900)
- Collected$47,300 (last week $52,100)
- Callbacks2 (last week 5)
- Overdue jobs3, all flagged to Jess
How it runs
What we build, step by step.
This is the usual shape. Yours gets built around how your team actually does the job.
- 01
Jobs and hours pulled from the job system
Jobs completed, jobs booked, callbacks, hours on site and anything still open past its due date.
- 02
Money pulled from the books
Invoiced, collected and outstanding for the week, matched to the same period as the jobs.
- 03
One sheet updated, week on week
The same layout every week, with this week next to last week and the same week last year where you have it.
- 04
A short note on what changed
Three or four plain sentences on what moved and the likely reason, with a link to the job or invoice behind each one.
- 05
Sent before Monday starts
The report lands in the owner's and managers' inboxes early Monday. Any number that couldn't be pulled is marked, not guessed.
Shown with software we see a lot. If your team uses something else, we build it into that instead.
Built for your business
Same job, different business. We build yours.
Two firms in the same trade rarely run a job the same way. Different software, different steps, different people signing off. We build it for your business, around how your team actually does the job.
Your steps
Built around the order your team already works in, odd exceptions included.
Your software
Runs inside the tools you already pay for, set up the way you use them.
Your rules
Your wording, your limits, your sign-offs. Nothing generic goes out in your name.
You sign off
Your team keeps the final say.
For the first month a manager checks each report against the source systems before it goes round. After that it sends on its own, and any number far outside its usual range is flagged for a person to confirm.
What it's worth
What those hours add up to.
3 hours a week, over 46 working weeks, is 138 hours a year. At $50 an hour, that’s
$6,900
back in the business, every year.
Typical, not promised.
Before and after
The job, before and after.
How it runs today
Every Monday someone logs into the job system, the accounting software and a couple of spreadsheets, copies the figures into last week's template and fixes whatever broke. It takes half a morning, it gets skipped in busy weeks, and the owner reads it on Tuesday.
What we build
- Jobs and hours pulled from the job system
- Money pulled from the books
- One sheet updated, week on week
- A short note on what changed
- Sent before Monday starts
A month in
Three hours of copying and pasting gone every week. The Monday meeting starts with the numbers already read, so it's about what to do, not what happened.
Keep it to the numbers you act on
The temptation is to put everything in. A report with forty numbers gets skimmed. We start with the six to ten figures you make decisions from (usually jobs done, revenue, cash collected, callbacks and late work) and add more only when someone asks for them twice.
The short written note matters as much as the table. A number going down is only useful if you can see why, so each change links back to the jobs or invoices behind it.
FAQ
What if a number is wrong in our system?
Then the weekly report shows the wrong number too, but it usually looks odd next to last week. Unusual swings are flagged so a person checks the source before the report goes out.
Can different people get different reports?
Yes. The owner can get the one-page summary while the operations manager gets the detail underneath, both built from the same figures.
More for operations
See them all →Next step
Bring this one to a free live build.
Thirty minutes on weekly numbers report. We build its elf with you, live, and you keep it.