Church Community Builder does not put a price on its website. You call, describe your congregation, and someone quotes you a number tied to your average weekend attendance and the modules you want turned on, usually inside an annual contract. That alone is worth sitting with before anything else: for a church of 150, the honest starting point is not a price comparison, it is a phone call you have not made yet.
This is not an argument that CCB is bad software. It was built for churches with departments — children's ministry staff, a business office, small-group coordinators, multiple campuses — and it does that job well. The question for a 150-person congregation is narrower and more useful: does your office look like the office CCB was built for, or does it look like one person at a kitchen table on a Tuesday night? The answer changes what the quote is actually worth to you.
The number nobody publishes, and why that matters
Quote-based pricing is common for software aimed at larger, staffed ministries, because the real cost depends on how many modules a specific church turns on — check-in, giving processing, staff scheduling, room reservations, and more all sit behind the same login, each one a lever on the final number. That makes CCB flexible for a church that needs six of those levers. It also makes it hard to compare against anything else until you have already had the sales conversation, described your ministry in detail, and waited for a proposal to land in your inbox.
A church of 150 people is exactly the size where that conversation can go either way. Some 150-person churches run a preschool, a food pantry, and three weekend services with a rotating volunteer crew — that is a real, multi-ministry operation, and a flexible platform priced for complexity may be the right tool. Other 150-person churches are one Sunday gathering, one small-group program, and a part-time secretary who also runs the sound board. The size is the same. The office is not, and CCB's pricing model assumes it can be shaped to either one, at a cost that reflects that shaping.
The second invoice: implementation
The monthly or annual fee is the number most churches ask about first, and it is rarely the whole cost. Onboarding a platform built around modules, permission levels, and configurable workflows means someone has to decide which modules apply, set up each one, migrate existing records into the new structure, and train whoever will use it. A staffed church often has a person whose job already includes exactly that kind of project. A volunteer-led office does not — the same treasurer who balances the books on a Saturday morning is now also the one learning a permissions model built for a business office.
None of that makes the software worse. It makes the sticker price an incomplete number. Before signing anything, it is worth asking the vendor directly: how many hours, realistically, will configuration and training take for a church our size, and who at our church needs to spend them? Write the answer down. It belongs in the same decision as the monthly cost, not in a separate conversation you have after the contract is already signed.
There is also a contract to read closely, not just a price to negotiate. An annual term means the decision is not really made in month one — it is made again, implicitly, at renewal, often with an automatic increase built in. Ask what happens if the church shrinks after a bad year, or if the volunteer who learned the permissions model moves away. A month-to-month tool lets a church change its mind cheaply. An annual contract asks you to be more certain up front, and that certainty is worth pricing in alongside the quote itself.
What a 150-person office actually does in a week
Strip away the sales language and most churches this size are doing the same handful of things every week: updating a handful of people or household records, following up on a guest or two from Sunday, recording the giving that came in, checking who is scheduled to serve, and glancing at attendance to see if it moved. That is a real list, and it is also a short one. A platform priced for staff scheduling across three campuses is answering a question most churches this size are not asking.
If your office has never opened a room-reservation calendar, never set a different login permission for a children's ministry coordinator versus the treasurer, and never needed check-in scanning at three simultaneous services, those are exactly the modules driving part of a CCB quote upward. That is not a criticism of the platform — someone, somewhere, is using every one of those modules for real. It is a question about whether that someone is you. Getting honest about the actual weekly admin rhythm your office keeps is a better starting point than a features list, because it tells you which modules you would pay for and never open.
Where CCB's depth genuinely earns its price
It would be dishonest to write this any other direction: some churches of 150 do need what CCB offers, and paying for it is the right call, not a mistake. A congregation running a licensed preschool needs staff scheduling and background-check tracking that go beyond a volunteer roster. A church with online giving as a real share of its income needs a processor built into the same system as the giving records, not a separate tool bolted on the side. A multi-site church needs one system that all three locations report into. In each of those cases, the depth is the point, and a flatter, cheaper tool would be the wrong answer dressed up as savings.
The mistake is assuming that because a church has reached 150 people, it has automatically reached that kind of complexity. Size and structure are related but not the same thing. A 150-person church with one pastor, one Sunday service, and a volunteer office can be simpler, administratively, than a 90-person church running two campuses and a licensed daycare. Ask which one describes your church before the attendance number does the deciding for you.
Running the two costs side by side
Suppose a CCB quote comes back at $200 a month for a church of 150, on an annual contract — that is $2,400 a year before any implementation hours are counted. Suppose those implementation hours run to twenty across a few weeks of configuration and training, split between a volunteer treasurer and the pastor. Twenty hours is half a work week that neither of them had free, spent before the software ever gets used for a real Sunday.
Now suppose a flatter tool costs $19 a month, month to month, with no contract and a public demo you can click through before deciding anything. That is $228 a year, and the setup is closer to an afternoon of entering people who already exist in a spreadsheet than a multi-week project. The gap between $2,400 and $228 is not automatically the right decision — if your church needs the modules the larger number buys, it is worth every bit of that difference. But if it does not, the difference is not small, and it compounds every year the contract renews.
A shorter path than another round of demos
Before booking another sales call with any vendor, CCB included, write down what your office actually did last week — not what a bigger, more complex church might do, what your office did. Match that list against each platform's real feature set, module by module, and let the mismatch tell you something. A church still moving off spreadsheets rarely needs multi-campus staff permissions on day one, no matter how big it hopes to get eventually. Buy for the office you run today, and treat the office you might run in five years as a separate decision for five years from now.
If that list turns out short — people, giving, serving, groups, follow-up, and a read of attendance — a flat-rate tool built for exactly that list, like SundayBridge, is worth sitting in the demo for an afternoon before a single sales call. If the list includes staff permissions, check-in kiosks, or online giving as a real weekly need, say so on the first CCB call and ask for the number in writing before you compare it to anything.
A longer look at how to weigh any two platforms against each other, not just CCB, is in choosing church management software, and church directory your team trusts is a useful gut check on whether your current record-keeping is the actual problem, before any new software gets blamed for it.