A church software subscription can look affordable until SMS credits are counted against the number of members you actually need to reach. Before approving an annual plan, calculate the full cost of contacting your congregation during ordinary weeks and urgent events.
At 7:40 p.m. in a committee room in Accra, Miriam reached line 17 of the budget spreadsheet. She was a composite church administrator, the kind who kept spare phone chargers in her handbag and remembered which ministry leader needed printed copies.
Line 17 read: “Additional SMS credits.”
The room went quiet.
The cost that appeared after the demonstration
The committee had already reviewed the subscription price, member records, event registration, and check-in tools. The advertised monthly fee fit their budget. With 500 members, the proposal looked ready for approval.
Then the treasurer asked a plain question: “Can this price send one message to everyone?”
Miriam checked the allowance. The included credits would not cover a single church-wide SMS to all 500 members. Routine reminders, conference changes, and transport updates would require additional credits.
That changed the calculation.
The committee had planned to approve the software that evening. Their next major conference was approaching, and coordinators needed time to prepare registrations and bus assignments. If the revised annual cost exceeded the approved technology budget, the purchase would return to the finance committee. That could push implementation beyond the conference.
Nobody signed.
The subscription price had been accurate. It had also been incomplete for the church’s intended use.
Calculate messages before comparing plans
Churches rarely send one message to each member and stop. A realistic event may require a registration confirmation, an advance reminder, a same-day notice, and an urgent update if a bus is delayed or a venue changes.
Start with the audience, then count likely sends.
For Miriam’s committee, the first calculation was simple:
- 500 recipients multiplied by one church-wide message equals 500 SMS credits, if the provider counts one standard message as one credit.
- Four messages to the same audience require 2,000 credits.
- Several events during the year can turn a small monthly allowance into a recurring overage.
Message length matters too. Some providers split longer texts into multiple SMS segments, so one message on the screen may consume more than one credit per recipient. Country, destination, and delivery channel can also affect the charge.
Ask the vendor to show how credits are counted, when they expire, and what happens when the allowance runs out. Does sending stop? Are extra credits purchased manually? Does the account move into overage billing? Can administrators set a spending limit?
Those answers belong in the budget before approval.
Match each message to the right channel
The cheapest plan may become expensive if every update goes through SMS. The better question is which messages genuinely need it.
A changed bus departure time may deserve SMS because members need to see it quickly. A general conference announcement might work through an in-app notification or email. WhatsApp may already be familiar, but scattered groups can create conflicting versions of the same update. What Happens When Every WhatsApp Group Holds a Different Version of an Event? shows why channel choice must include message control, not cost alone.
ChurchFlow is designed to route notices by urgency, with tools for event registration, bus coordination, and targeted updates. That approach can reduce unnecessary church-wide sends because a transport coordinator can contact the members registered for a specific bus. Multi-channel notification work is still in progress, so a church evaluating the product should confirm which channels are currently available and how each one is billed.
Build three budget scenarios:
- A normal month with routine reminders.
- A major event month with registration and transport messages.
- A disruption month with delays, cancellations, or urgent changes.
The disruption scenario matters most. A communications budget that works only when nothing changes will fail exactly when the church needs it.
Put the full annual cost on line 17
With three days left before the committee’s deadline, Miriam replaced the single subscription figure with a working annual estimate. It separated the platform fee, included SMS credits, expected additional credits, and a contingency for major events.
She also added one rule: no vendor comparison could use subscription price alone.
The revised figure remained within the amount the committee could approve, but with less room than the original proposal suggested. They reduced routine SMS use, reserved it for time-sensitive updates, and documented which notices could use other channels. The conference team could proceed without discovering the real communications cost during a bus delay.
At the next meeting, line 17 no longer held a vague allowance for “extras.” It showed who needed to receive messages, how often the church expected to contact them, and what those sends could add to the year.
Before your next approval meeting, ask for a sample invoice based on your member count and busiest event. Put that number beside the subscription fee. Then let the committee decide from the complete cost.
Comments
No comments yet.