The right ChurchWork plan is the lowest tier whose published member, SMS, and storage limits cover your next event with room to spare. Before paying, separate those limits from features that are currently available: registration, QR and GPS check-in, groups, bus coordination, and admin reporting are ready to evaluate, while real online payment processing and AI Analytics should not influence your choice today.
At 4:17 on Friday afternoon, Daniel had three browser tabs open in a church office in Accra. Registration was due to open after Sunday service, the volunteer coordinator needed access before Saturday’s rehearsal, and a handwritten estimate of expected attendees sat beside his cooling tea.
Daniel is an illustrative composite, but the decision is familiar. Choose too small a plan and registration could run into a limit at the worst moment. Choose the highest tier because it carries the longest feature list, and the church could pay for capabilities it cannot yet use.
By 5 p.m., his committee expected a recommendation.
Start with capacity, not the longest feature list
ChurchWork publishes three plan levels: Free, Standard at $49, and Premium at $99. The practical comparison begins with the limits shown for each plan, especially members, SMS usage, and storage.
Write down four numbers before choosing:
- How many member records must be active?
- How many people could register for the event?
- How many SMS messages might the church send during registration and on event day?
- How much space will event banners, member photos, and other uploads require?
Use the current figures displayed on the pricing page when making the decision, since plan limits can change. Then leave a reasonable margin. A church expecting its records or message volume to sit close to a plan ceiling has already outgrown that tier for this event.
This avoids a common pricing mistake: comparing monthly prices without comparing the activity those prices must support. The same discipline applies when reviewing other quotes, as explored in Church Software Pricing: What Three Quotes Taught Ama About First-Year Cost.
For Daniel, the key number was not the size of the Sunday congregation. It was the number of records, registrations, and urgent messages the team needed the platform to handle during a concentrated registration period.
Compare what the team can use now
ChurchWork’s currently available operational capabilities give a church several concrete ways to prepare for registration:
- Administrators can create and publish conferences with dates, venues, schedules, speakers, deadlines, and capacity settings.
- Members can register for conferences and receive registration codes and QR codes.
- Check-in teams can scan QR codes, look up attendees, prevent duplicate check-ins, and monitor attendance.
- Churches can enable GPS-validated self-check-in within a configured venue radius.
- Transport coordinators can create bus routes, manage capacity, assign riders, and issue boarding passes.
- Administrators can organize members into groups and subgroups.
- Church teams can manage multiple branches, roles, and permissions from one system.
These capabilities address the Friday problem directly. Daniel could judge whether the registration desk, transport team, and branch administrators would have the tools required when the doors opened.
ChurchWork has already supported approximately 8,752 registrations for IMPACT 2025. That is useful operational evidence, but each church should still test its own workflow, permissions, data, and connectivity before opening registration to members.
If your immediate concern is replacing WhatsApp replies with dependable attendance records, Church Event Registration: How Kojo Turned WhatsApp Replies Into Reliable Attendance offers a practical companion to this plan decision.
Exclude unavailable capabilities from the buying case
Two published capabilities require particular care.
Online Giving should not be treated as ready for live donations because its card capture currently uses a mock payment method. A church that needs to process real contributions should keep its existing payment route in place and evaluate ChurchWork for registration, events, groups, transport, and member administration instead.
AI Analytics should also be excluded from the Premium justification. The label appears in the pricing structure, but there is no usable AI Analytics feature behind it today.
This distinction protects the committee from buying on aspiration. Standard or Premium may still be the right choice because of their published capacity limits, volunteer tools, branding options, or other available functions. The decision should stand without counting Giving or AI Analytics as working benefits.
Daniel crossed both items off his Friday checklist. The comparison became shorter, and the room became quieter. He no longer had to defend every phrase on the pricing page. He only had to match current needs to current capabilities.
Choose the smallest safe plan, then rehearse
Free is the sensible starting point when its published limits cover the church’s immediate records, messages, and storage needs. It can also provide a lower-risk environment for learning the workflow before a larger rollout.
Standard at $49 fits when the church needs capacity or available administration features beyond Free. Premium at $99 should earn its place through limits and capabilities the team can use now, rather than the unavailable AI Analytics claim.
Whichever tier fits, run one rehearsal before registration opens. Create a test event, register a few volunteers, scan each QR code, check permissions, test a duplicate check-in, and walk through the bus process if transport is involved. Confirm who will make changes when a pickup time, room, or attendee record is wrong.
On Saturday morning, Daniel’s volunteers stood around one phone and one laptop. One person registered, another scanned the QR code, and a third watched the attendance count change. The committee had chosen a plan that covered the event they were about to run, with a clear reason for every dollar.
Comments
No comments yet.