Illustrative example, not a real client: a gated community where the treasurer spent nights chasing payments can organize collections with three changes, without touching its bylaws.
An illustrative, anonymized example: not a real client and with no figures. It shows the path of a mid-size gated community with a volunteer treasurer, a five-person committee and monthly dues.
The starting point
Reminders went out when the treasurer remembered, each one written from scratch. Residents asked about their balance in the chat and nobody knew for sure what had been paid. Accounts were presented at the meeting and caused arguments.
Change 1: balances and payments on WhatsApp
Each resident checks their balance and sends proof of payment on WhatsApp; Dot receives it and the treasurer confirms. Reminders go out on a fixed, friendly schedule. See Dues and collections.
Change 2: accounts in view
Income and expenses visible to whoever pays, with receipts. Questions stopped landing on the treasurer. See Clear accounts.
Change 3: notices with confirmation
Meeting and due-date notices go out on WhatsApp and the committee sees who opened them. See Notices.
What it teaches
No rule or fee had to change: measuring, reminding predictably and showing the money was enough. The treasurer got the nights back, and decisions stayed with the committee.