When I served in an elders quorum presidency, and later as a branch president and in a bishopric, there was always so much to keep track of. Who still needed an interview. Which calling was waiting to be sustained. What we said we'd follow up on in ward council. Most of it lived in group texts, a spreadsheet someone forgot to share, or my own memory, and a lot of it got lost after the meeting.
That's why I built Wardzen. I wanted a place where a bishopric, a presidency or a stake can look at the same picture, see the next step, and spend less time chasing paperwork. That frees them to focus on what the gospel teaches us to do: to love and care for the Lord's people.
Built for the long run
Callings change. Bishops are released, new clerks are called, presidencies get reorganized. When that happens, the work shouldn't walk out the door with the person who was doing it. In Wardzen, access follows the calling, so the next leaders pick up right where the last ones left off.
But that only matters if Wardzen is still around. I don't want a ward to build its habits around a tool and then have to start over because it went away. My goal is to keep Wardzen maintained and improving for the long run, and that's where the cost comes in.
Why there are paid plans
I'm one person running this. Hosting, email, backups, security and the time to keep improving things all cost money, and I'd rather be upfront about that than pretend it's free to run.
So Wardzen has a free plan and paid plans. The free plan has the core tools most units need: callings, ordinations, missionaries and more. Ward Plus and Stake Plus add the tools that save the most time week to week, and the ones a stake needs to work with its wards. The units that get the most out of Wardzen help keep it going for everyone else.
I'd rather grow slowly and stick around than grow fast and disappear. You can see the plans on the pricing page.
One thing paying doesn't change: your unit's records stay with your unit, and leaders enter only what they choose.
If you have questions, or ideas for what Wardzen should help with next, write to me at support@wardzen.com.
Ben