Early on, building FaithDash, the easier decision would have been to leave SMS alone entirely. Bulk SMS platforms already exist in Uganda — several of them, including ones that explicitly market to churches, schools, and SACCOs. Building a member database, attendance tracking, and event management, and then telling churches "for texting, just use one of those," would have been less work, and arguably less risk. Plenty of software makes that call and it's a reasonable one.
What kept coming back, in conversation after conversation with people actually running church communications, was the same shape of story this whole series has been telling for fifty posts now. An admin with a spreadsheet three people had edited differently. A visitor card sitting in a basket because nobody had time to type it into a second system. A funeral announcement that needed to reach four hundred phones in fifteen minutes, with the "real" contact list somewhere on a laptop that wasn't in the room. None of those problems were about SMS being hard to send. Every generic portal in this market sends SMS just fine — EgoSMS, SMSOne, Trust SMS Uganda, RedSMS, Oracom, FamITech, and the BulkSMS Uganda gateway FaithDash itself sends through, all of them reliably deliver a message to a phone. The problem was always upstream of sending: knowing, accurately and currently, who to send it to, and remembering to send it at all.
The decision that actually mattered
So the choice wasn't really "build SMS or don't." It was narrower than that: should the recipient list live inside the same system as the church's actual member records, or should it live in a separate portal that has to be fed, by hand, from a spreadsheet exported out of the first system, forever. Once framed that way, it stopped being a hard decision. A portal that doesn't know who's a visitor versus a member, who attended last Sunday, or who joined the choir this month isn't a smaller version of what a church needs — it's a different kind of tool solving a narrower problem, built to serve banks and retailers and political campaigns as readily as congregations, with a UI and workflow that reflects that breadth rather than a church's specific shape.
That's why FaithDash's Messages page sends to segments that already mean something inside the system — All members, Visitors only, Members only, Leaders only, any custom tag — instead of asking anyone to upload a CSV. It's why Automation exists at all: visitor follow-ups, event reminders, and event attendee follow-ups, configured once through a form and left running, because a generic portal has no concept of "visitor" or "event" to trigger anything from in the first place. None of that required beating anyone on price. It required building the workflow around data the church already has, instead of asking the church to re-donate that data to a second, disconnected tool every time it changed.
What we deliberately didn't try to do
We didn't try to build a cheaper SMS gateway. FaithDash sends through BulkSMS Uganda, the same class of telco-connected infrastructure that independent bulk SMS platforms in this market also run on, and the price — UGX 35 per SMS part — reflects that underlying rate honestly, not a discount and not a markup dressed up as one. We also didn't try to build a general-purpose bulk SMS API for arbitrary uploaded contact lists; that's a real, useful thing, and Africa's Talking already does it well for developers who want to build their own integrations. FaithDash is built around a church's own member and event data specifically, which means it's a worse fit than a generic portal for, say, a political campaign or a retailer's promotional blast — and we're fine with that trade, because it's not who this was built for.
What "grew organically" actually looked like
The live cost counter in the composer, the background job with its progress readout, the low-balance warning sitting next to a one-click top-up, the searchable message history — none of these arrived at once as a grand plan. Each came from a specific, recognizable frustration: someone sending blind without knowing the cost, someone standing over a page babysitting a send, a treasurer topping up mobile money at 11pm because nobody saw the warning in time, an admin unable to answer "did we actually send that" without asking around. The feature list is really just a list of small disappointments other tools left unaddressed, one at a time.
Where that leaves things
We're not going to tell you FaithDash is the only reasonable way to text a congregation in Uganda — plenty of churches run perfectly well on a WhatsApp group and a shared spreadsheet, and plenty more will do fine on one of the portals named across this series. What we'd ask, if you've read this far, isn't to switch tools. It's to notice, next Sunday, where your church's real member list actually lives, and whether the thing sending your texts knows the same truth about your congregation that you do. If it doesn't, that gap — not the price per SMS — is usually where the real cost has been hiding all along.