The Friday report
Friday’s numbers come from the systems that hold them, set beside last week and written up in the format you already use. The report waits in your inbox until a person reads it and sends it.
The numbers gather themselves. You read the report and send it.
Here’s a typical run, step by step: what automation handles, what the agent does, and the calls that stay with your team.
Step 1 of 5Pull the numbers
Automation
Takes orders shipped, on-time delivery, open tickets and cash collected from the systems that hold them, for the week so far.
Each number lives in one known place and is counted one way, so pulling it is the same query each week.
- Order system
- Support desk
- Report draft
~10 hours a month back
Where teams differWeeks run Monday to Sunday for many teams. Others close on Thursday night so the report can go Friday.
Step 2 of 5Look at what moved
Automation
Sets each number beside last week and your target. Open tickets are at 312, up from 211, which is past your 20% swing limit.
Your swing limit decides which figures get a closer look, before anyone reads a line.
The agent
Reads the 101 extra tickets and finds that 74 of them mention the billing page that changed on Tuesday.
The reason sits in what customers wrote, not in the count.
- Support desk
- Report draft
~7 hours a month back
Where teams differA 10% move is enough for some teams to take a look. Others only care about a miss against target.
Step 3 of 5Write it up
The agent
Writes the top three lines and a note for each section in the style of your recent reports, with a source under every figure.
Turning six sections into three plain sentences a leader will actually read is writing, not arithmetic.
- Past reports
- Report draft
~7 hours a month back
Step 4 of 5Read and send
Automation
Puts the draft in the ops manager’s inbox with the ticket jump at the top and the likely reason beside it.
The draft always goes to the same inbox, with its open questions at the top.
Your team
Confirms the billing page line or rewrites it, reads the rest, and sends the report to the leadership list.
The report goes out under a person’s name, so a person decides what it says.
- Report draft
~3 hours a month back
Where teams differSome teams have each section owner see their part first. Others leave the whole read to one person.
Step 5 of 5File it
Automation
Saves the sent report to the shared drive, notes the billing page for next week, and sets up week 40.
Filing the report and starting the next one are the same steps every week.
- Shared drive
~2 hours a month back
What changes
Each number comes straight from the system that holds it, with last week beside it. The ops manager reads the draft, answers one question and sends it.
- 4steps automated
- 2steps for the agent
- 1call kept with your team
Pick any step to see what happens there and why it sits in that lane.
What it could be worth
~29 hours a month back
$20,900 a year in time
For a 200-person company whose weekly report takes about nine hours to pull together, at $60 an hour. We work out yours from your own volumes before you sign.
Let’s build your agentOne proven agent, plugged into how you work.
Every team does this job a little differently, so we set these five with the people who do it today. We’ve done this in dozens of businesses, so we know where teams usually differ and ask about those first.
The agent
Same for every client- Follows the same proven steps
- A person on every exception
- Every decision logged
- Tested on your past work first
- Never sends the report on its own
-
Your systems
Where the work comes in, and where the result goes.
For this agentNumbers from your order, support and accounting systems, the report into your email or shared drive.
-
Your rules
The limits and exceptions it works to.
For this agentWhich numbers go in, your targets, and how big a swing needs a note.
-
Your team
Who signs off, and who covers when they’re away.
For this agentThe ops manager reads and sends it, and each section owner answers for their own number.
-
Your channels
Where your team hears from it.
For this agentEmail for the report, Slack or Teams for questions to section owners.
-
Your output
What it hands back, in the format you already use.
For this agentYour report in your own layout, with last week beside each number and its source underneath.
It builds one report on a schedule. Rolling every team’s numbers into a live view is the KPI roll-up agent, and fixing a number at its source stays with the team that owns it.
The agent, and everything that keeps it working.
- The agentRunning on your systems, under your rules.
- The review screenWhere the exceptions land for your ops manager and section owners.
- Your rulebookYour limits, exceptions and who signs off, in one place, often for the first time.
- A test reportYour past weekly reports, run through it and checked against the number.
- The runbookHow it works, what to check, and what to do if it stops.
- 30 days of tuningAfter it goes live, through a full month of your real weekly reports.
Hours your team spends pulling the weekly report together. We measure it before we start, and again at day 30.
Live in 3 to 6 weeks. About seven hours of your time.
We do the building. Your side: access, the last three months of reports your team sent, and a short weekly check-in.
Then 30 days of tuning, with a short check-in each week, about two hours of yours. At day 30 we show you the number and hand everything over.
It keeps running whether or not we stay.
It runs in your accounts
Your cloud, your systems, and an AI account in your name, billed by the provider at their rates.
Changes in the first 30 days are included
A new rule, a changed limit, someone new signing off. That’s what tuning is for.
After that, your call
Your team edits the rulebook, the care plan covers it, or a bigger change is quoted first.
About this agent.
What if a system is late with its numbers?
Can it write the commentary, not just the tables?
Does it have to be Friday?
Our process isn’t quite like this. Will it still work?
How do we agree the number?
What does it cost to run once it’s live?
Is there a weekly report you’d rather read than build?
Tell us how your team handles weekly reports today. We’ll show you this agent on examples like yours, and whether it fits the fixed price.
- 3 to 6 weeksto live, then 30 days of tuning
- $12,500fixed, per agent
- Yours to keepno license fees