Brief
Weekly operations summary
From the sales sheet, the stock file and the WhatsApp thread. Monday, 06:30.
- Tools
- 4
- Approvals
- 1
- Output
- 3 files
I build the layer between the model and the business: the channels it answers on, the tools it may touch, the rules it cannot break, and a record of every action it takes.
Typed into the chat, then typed again into the sheet.
A price change that only one person in the company knows how to answer.
Rebuilt every Monday morning from the same four files.
A list that lives in a photo on somebody's phone, and is wrong by Thursday.
Everything above stops when that person takes leave.
None of it is a model problem. It is a missing layer between the model and the company, and that layer is buildable.
Live surface · sample data · not a customer system
Brief
From the sales sheet, the stock file and the WhatsApp thread. Monday, 06:30.
Read the brief
Three files and one thread, opened in their native formats.
Reconcile
Match the totals. Two numbers disagree, and both are kept.
Draft
The summary in the format the ops group already reads.
Check against the rules
Nothing published that is not costed. Nothing invented to fill a gap.
Ask you
The run does not guess which of the two numbers is right. It stops here and waits.
Run paused. Nothing leaves the building.
Send and log
Summary to the ops group, entry in the audit log, both reversible.
Each line is written when the step completes. The approval line is written when you press it.
Nothing has run yet.
Nothing here is a model. It is the ordinary engineering around one.
WhatsApp Business, email, Telegram. The customer writes where they already write, and the business answers with one identity.
one number, one inbox, one voice
The facts your team repeats: prices, terms, names, how a complaint is handled. Written down once, so nobody re-explains them.
read from files you own
The systems it may touch, each with a written scope: read this sheet, draft this document, never send without approval.
permission written next to the tool
Work that runs on a clock instead of a memory: the Monday summary, the daily price refresh, the month-end pack.
runs without anyone pressing send
What it may never do, who it must ask, and what has to be true before money or a customer is involved.
stops on purpose, by design
Every action, every approval, every change, readable by the person who carries the risk. Not a chat history.
who did what, and who said yes
Runs on a machine you control, with your keys and your backup. Self-hosted by default, so it survives the consultant.
your hardware, your data
An assistant with no channel is a demo. With no log, it is a liability.
Small, boring, and measured. The interesting part is what the business keeps at the end.
One workflow, chosen because it eats the most repeatable hours. Not the whole company, and not a proof of concept nobody uses.
It runs beside the person who owns the work, in the channel they already use, with a human check on anything that leaves the building.
We read the log together and cut whatever did not earn its place. Fast, blunt, and cheaper than defending it.
The runbook, the keys, the access list, and the names of the two people who can stop it. You are not dependent on me to keep it running.
Your server. Your keys. Your data.
Self-hosted by default, so the system stays in your building after I leave, and so a shutdown of somebody's API is a Tuesday problem rather than the end of your operations.
Next step
Opens WhatsApp with your note already written. Nothing is sent until you press send there, and this site stores nothing you type.