Every ward runs on the same improvised stack: a group chat for decisions, a spreadsheet for who has spoken, a shared doc for the agenda, and someone's memory for everything else. It works, barely, because the people running it care enough to make it work.
None of it was built for the calling. The group chat loses assignments the moment the conversation moves on. The spreadsheet lives on one person's account and leaves with them. The agenda doc starts from a blank page every week.
The cost isn't the tools. It's the meeting time spent reconstructing what everyone already decided.
What we're building instead
Beespo is one shared workspace for the operational side of the calling — programs, agendas, activities, assignments, and the follow-up that connects them. Plans build up in spare minutes during the week. Decisions leave with owners. Unfinished work carries forward on its own.
We build for every organization in the ward, not just the bishopric. A Relief Society presidency planning an activity and a clerk preparing Sunday's program get the same care.
This blog is where we'll write about that work — what we ship, what we learn, and what leading well looks like when the tools finally cooperate.