Your team, thoughtfully built.

How to Run a Weekly Business Review With AI

By Staffmor Staff

Practical guides from the team building Staffmor.

To run a weekly business review with AI, give it the same numbers for the same period every week and ask for three things: what was measured, what is still unexplained, and three next actions. A weekly review connects this week's evidence to next week's decisions. Its job is to keep you from deciding on a number you haven't looked at closely.

The example is a made-up workshop business. These are not Staffmor customer figures.

Give it a week you can check

Eight bookings and two cancellations, so six places are reserved.
Three customer questions about equipment.
Your time this week: one page revision and one check with the instructor.

Say what each number means. Are bookings counted before or after cancellations? If the review celebrates eight while the room expects six, the review is wrong before it starts.

The request

The request: "Review the week from the bookings, support questions and last week's action list below. Show the facts, how they compare with last week, what is still unexplained and three proposed next actions. Keep total bookings separate from current reservations. Do not guess why people canceled, and do not send instructions to anyone."

What comes back

Measured: eight bookings, two cancellations, six reserved.
Observed: three equipment questions, all asking what to bring.
Unknown: why the two people canceled.
Proposed: make the equipment section clearer, confirm the instructor, check next week's capacity.

The mistake to watch for

A number is not its own explanation. Two cancellations will come back as "customers find the price too high" if you let it, because a review that explains everything reads better than one that says "unknown." Nobody told you why they canceled. If you want to know, ask the two of them.

The equipment questions are different. Three people asked the same thing and the notes say what they asked. That one you can act on.

Carry forward only what you accept

Pick the actions you are taking, give each an owner and a date, and drop the rest. Next week, start by checking whether those happened. Don't rewrite last week's plan to match what you now know. A review that is always right in hindsight teaches you nothing.

Run it in your Staffmor office

Open the office on the computer running it with its Start Staffmor launcher. If you already have a paired web office, open it here. Paste this request and the source material into the conversation. Use your approved Codex connection, or ask your open Claude Code session to "Check Staffmor for work." A saved request is not a completed result. Review the answer or file when it comes back and reply with corrections. Ask a second pass to check the arithmetic and whether each proposed action follows from a fact.

Staffmor works from the numbers you give it. It does not connect to your analytics, and the decisions stay with you. New to Staffmor? Set up your office with Codex or Claude Code and an empty folder. Use your own supported AI account and approve the download, office activation and local folder/network access during setup. Claude Code pickup is manual; keep that local session open.