Run Your Small Business from a WhatsApp Group: 7 Workflows

For millions of small teams, the office is a WhatsApp group. The barber shop with three chairs, the cafe with five staff across two shifts, the two-van repair crew — they do not run on project management software. They run on a group chat, because it is already installed, everyone actually reads it, and it costs nothing. That is not a failure of professionalism; it is a sensible choice. The failure happens when the group has no structure, and the day's takings drown somewhere between a meme and a voice note. Here are seven workflows real small teams run inside WhatsApp, plus the ground rules and message formats that keep the group usable at month three, not just week one.

Ground Rules That Keep a Work Group Usable

• Two groups, not one: a work group for numbers and operations, a social group for everything else. Mixing them kills both.
• Fixed formats for recurring messages. When every sale looks the same, anyone can scan the whole day in ten seconds.
• Numbers get their own message. Never bury an amount inside a paragraph — it has to be findable by scrolling.
• Photos always get one line of text. A bare receipt photo means nothing three weeks later.
• Pin the rules and the message formats to the top of the group, and have every new hire read them on day one.
• Reply to the message you mean. Answering a morning question with a bare yes at 6 pm creates confusion; the reply function exists for exactly this.

Workflows 1-3: Sales Log, Expenses, and the Evening Cash Count

Workflow 1 is the sales log. Every sale — or, in high-volume shops, every closing total — goes into the group in a fixed format: amount, payment method, what it was. Sale 32 card haircut takes four seconds to type and creates a permanent, timestamped record the whole team can see. Workflow 2 is expenses. Whoever pays for something posts a photo of the receipt with one line: exp 85 cash — coffee beans, weekly order. The photo preserves the proof, the line makes it findable, and nobody has to remember at month-end who paid the window cleaner. Workflow 3 is the evening cash count. At close, one message: counted cash, card terminal total, any app payments, and the difference against what the day's sales messages predict. A three-person cafe team doing this honestly will catch a till discrepancy the same evening it happens — not three weeks later when nobody remembers anything. Together these three take under five minutes a day and produce something most small shops never have: a complete daily money record.

Workflows 4 and 5: Shift Handovers and Stock Alerts

Workflow 4 is the shift handover. The outgoing shift posts the same four lines every time: how much is in the till, what is running low, what went wrong, and what the next shift needs to know. For example: till 150 / milk low, enough for tomorrow morning / card terminal froze once, restarted fine / Mrs Ortega collects her order at 5. The incoming shift starts informed instead of guessing, and the classic nobody-told-me disputes end, because everything is written down with a timestamp. Workflow 5 is the last-box rule for stock. Whoever opens the last box, bag, or bottle of anything posts it immediately: LAST: espresso beans. No counting, no stock software — just a reflex. Once a week, someone scrolls the group for LAST messages and builds the supplier order from them. It is crude, and it works far better than the alternative, which is discovering at 8 am on Saturday that nobody flagged the milk.

Workflows 6 and 7: Task Lists and Supplier Chats

Workflow 6 is the morning task message. One person posts three to five tasks with names attached: today — Ana terrace setup, Luis inventory count, Marco bank deposit. Each person replies to that message with done as they finish, so completion threads neatly under the assignment. It is not a project board, and for a team of five it does not need to be. Workflow 7 is supplier chats. Keep each supplier in a separate one-to-one chat, negotiate and order there, then forward the final order summary into the team group. The team sees what is arriving and when; the price discussion stays private. This one habit prevents the classic mess where three different people order from the same supplier in the same week.

Message Formats and Templates That Save Time

• Sale: amount, method, item — sale 45 cash beard trim.
• Expense: exp 120 card — new clippers, receipt photo attached.
• Day close: close — cash 380, card 510, bizum 45, total 935.
• Handover: till 150 / milk low / terminal froze once, fine now / pickup at 5.
• Stock alert: LAST — espresso beans, add to Monday order.
• Tasks: today — Ana terrace, Luis inventory, Marco bank run. Reply done to this message.

When a Group Chat Stops Being Enough

The group has limits, and they show up on a schedule. Around month two, someone spends ten minutes scrolling to find last Tuesday's closing total. Around month three, the owner starts retyping the group's numbers into a spreadsheet every Sunday night, and that retyping quietly becomes the most hated hour of the week. Around month six, a number typed in the chat does not match the till, and there is no easy way to add everything up and check. None of this means abandoning the group — the habit of logging everything in one shared place is exactly right, and your team already has it. It means the group needs help with the part chat was never built for: adding up, categorising, and exporting. Whether that help is a disciplined spreadsheet, a simple bookkeeping app, or a tool that reads the group itself, the seven workflows above stay the same. The typing your team already does is the system; everything else is just where the totals live.