Monday — one message a week
One message, every Monday, in the same shape: what came in, what went out, what is waiting on you and for how long, and what went wrong last week.
It never rounds a bad week up. The numbers are whatever the numbers were, and a report you cannot trust in a bad week is not worth reading in a good one.
Monday to Friday,
in specifics rather than verbs.
Invented and generic on purpose — there are no clients yet, so nothing below describes a real business. What it does describe accurately is what the role would do and where it would stop.
The message is there before you start. Same order every week, so your eye knows where to go.
What came in: enquiries, bookings, orders. Counted, and compared with the four weeks before it rather than with a target.
What went out: offers sent, invoices raised, what was paid.
What is waiting on you, oldest first, with the number of days attached. This is the block most people read first after a month.
What went wrong: what a role stopped on, what it could not read, what it had to ask about.
If a number moves sharply it says so in a sentence, without a theory about why.
What you actually do,
and how long each part takes.
"Easy onboarding" is not a claim anybody believes. This is the list, with a duration on every line, and the longest line is the fortnight where it does nothing.
Nothing you have not already given the other roles. This one reads their work.
Say which day and which hour. Monday morning is the default and Friday afternoon is the other sensible answer.
One week of watching, so the first one you receive is not also the first one it has written.
It arrives weekly. Reply to it in a sentence to change what is in it.
Three ways this role fails,
and what happens then.
It will be wrong. The design assumption is not that it will not be — it is that when it is, the item stops, says so and waits, and that you find out from the system rather than from a customer.
A number looks wrong.
Every figure is traceable to the items behind it, so the answer is a list rather than an argument. A report you cannot drill into is a report nobody believes twice.
A role was broken all week.
That is in the fourth block, first. A weekly report whose job is to look calm is worse than no report.
There is nothing to say.
It says that, briefly, rather than padding. The point of the same shape every week is that a quiet week takes ten seconds to read.
It never rounds a bad week up. The numbers are whatever the numbers were.
What this role does not touch.
A role that claims to take everything is a role nobody with a real business believes. Naming what stays with you is what makes the rest of the page worth reading.
Three questions
this one gets and the others do not.
Can I have it as a dashboard instead?
That is a build, not a role, and it is usually the wrong first step. A dashboard is a place you have to remember to go; a message on Monday morning is one you have already read by accident. Start with the message.
Does it work without the other roles?
Partly. It can only count what something is recording, so on its own it reports what your existing systems expose. It is the cheapest role and it is worth the most alongside two or three others.
Can my accountant get it too?
Yes, and several people can each get their own version with different blocks. It costs the same.
Watches the inbox so you can stop refreshing it.
Turns an enquiry into a priced offer, ready to send.
Issues them, chases the quiet ones, matches the payments.
Reads what arrives as a PDF and files it where it belongs.
Bookings, reminders, cancellations, and who did not turn up.