A community operating system for a volunteer-run Dawoodi Bohra organisation.

Toloba Chennai AEM is a long-standing volunteer-based organisation serving the Dawoodi Bohra community in Chennai. They run community services, organise events, and maintain the operational fabric that holds the local community together. The work depends on volunteers, on relationships, and on the trust of the families they serve.

Simply Five Studio is a long-term technology partner of Toloba Chennai AEM. The system we have built for them, and continue to evolve, handles the operational backbone of a community organisation that has grown well past the size where informal coordination is sufficient.

The situation

A community organisation of this kind serves several thousand families. Membership records, fee structures, event coordination, attendance tracking, and communication all run continuously. Volunteers do the operational work. The volunteers' time is the limiting resource.

The old way of running these workflows was a combination of spreadsheets, WhatsApp groups, and the institutional memory of a small number of people who held the operational picture in their heads. It worked, in the sense that the organisation continued to function. The cost was that growth, in members or in programmes, was constrained by how much operational complexity the small team could absorb.

The partnership with Simply Five Studio began with the recognition that the operational fabric needed to be encoded in a system the organisation owned and could rely on, so the volunteers' time could be spent on the actual community work rather than the coordination work.

What we built

A comprehensive web application that has evolved over years of active partnership, with new modules added as the organisation's needs have grown.

Member management

The full member database with household structure, contact information, relationship to the organisation, and historical participation. Search and filtering that makes it possible to identify the right people for any given outreach or programme. The member master is the structural foundation that everything else builds on.

Fee structures and billing

Membership fees, programme fees, event registration fees, and voluntary contributions all managed through a single billing surface. Invoices generate on the right schedule. Payment is tracked. Receipts are issued automatically. The financial visibility for the organisation's leadership runs continuously.

Event registrations and processing

Programmes and events of all kinds, from regular gatherings to special occasions. Registration flows. Attendee capacity management. Payment where required. On-site attendance capture. Post-event reporting. Each event runs as a structured workflow rather than a one-off coordination exercise.

WhatsApp integration

Communication with the community happens primarily over WhatsApp. The integration handles broadcast announcements, programme-specific messaging, and individual outreach. Each message is logged against the member record so the organisation has a clear view of who has been contacted about what.

Attendance during events

On the day of an event, attendance is captured directly in the system. The volunteers running the event scan or mark attendees as they arrive. The data feeds reporting that the leadership uses to understand engagement patterns and plan future programmes.

Reports and visibility

A reporting layer that gives the organisation's leadership the information they need to govern. Membership trends, financial health, programme participation, volunteer activity. The reports run continuously, which means leadership decisions can be made on current data rather than at the cadence of a manual monthly cycle.

How it works in practice

A member registers for an upcoming event through the system. The fee, if any, is collected. The member receives confirmation by email and WhatsApp. Their registration sits alongside their full record, which volunteers preparing for the event can reference to make sure the day-of-event experience is appropriate.

On event day, volunteers capture attendance. The data is immediately visible to leadership. The post-event report is available the same evening, which means the next event can be planned on real data rather than recollection.

Membership renewal cycles run automatically. Volunteer coordination for upcoming programmes uses the same database. The organisation's operational rhythm has settled into something predictable and sustainable, in a way that depended on the system existing.

What changed

The organisation can support a larger community without proportionally expanding the volunteer load. The administrative coordination that used to consume volunteer hours now runs in the system. The volunteers' attention is on the work the organisation exists to do.

Governance improved. Leadership has continuous visibility into the financial and operational health of the organisation. Trustees can answer questions confidently. The transparency that any community institution depends on for its ongoing trust is structurally supported by the system.

The relationship between the organisation and its members became more professional without becoming impersonal. Members get reliable communication. Receipts arrive without anyone needing to chase them. Event registrations work the first time. The small interactions that shape how a community organisation is perceived are uniformly handled well.

What's next

The system continues to evolve. New programmes bring new requirements. The technology partnership absorbs that work in a quarterly improvement rhythm. As long as the organisation continues to grow and adapt, the system grows and adapts alongside it. That is the value of running this as a partnership rather than as a one-off project.