I know the gap from club life
I am building Firetender as a Rotary member, not as someone looking at clubs from the outside. The work between meetings is familiar: finding the current member list, remembering what was agreed, checking who has paid and trying to give the next officer enough context to continue.
The problem is not a lack of effort
Rotary clubs are run by people who give their time because the work matters. The friction comes from records being spread across spreadsheets, email threads, documents and personal routines. A new officer should not have to reverse-engineer the club before they can help it move forward.
My reason for building this
I wanted one calm, practical place for the recurring record: members, dues periods, payment history, meetings, attendance, activities and follow-up. Firetender is deliberately smaller than a general-purpose association platform because a volunteer board needs clarity before it needs more configuration.
What I am trying to protect
The real test is the handover. Can the next treasurer understand the record, trust the history and pick up the work without reconstructing it from an inbox? Can the president see what needs attention without asking three people for three different versions? That is the standard I am building toward, one club at a time.