Planning Center is sold as a suite: People, Services, Check-Ins, Registrations, Giving, Groups, each a separate product with its own price, all sharing one login and one underlying database. A lot of churches buy in expecting to use most of it, and then a year later discover that the only tab anyone actually opens is People — the directory, the households, the notes on who called after surgery. Everything else sits there, paid for, unopened.
If that describes your office, this is not an argument that Planning Center is bad software. It is well built, and churches running a full production on Sunday morning with check-in stations and a service plan get real use out of the rest of the suite. This guide is for the smaller and more common case: a church that wanted a directory, ended up with a platform, and wants to know what a tool built only for the directory would look like instead.
What the People module is actually doing for you
Strip away the rest of the suite and People is, at its core, a contact database with households, custom fields, tags, and a workflow builder for tracking who needs a follow-up call. That is a real and useful thing. It is also a smaller job than the price tag suggests once you are paying for a platform that assumes you will eventually turn on Check-Ins or Services.
The workflow builder in particular is powerful in a way that can outgrow a small office. It is built for a staff person who configures automation rules, assigns steps to specific team members, and reviews a pipeline daily. A volunteer secretary working four hours a week does not need a workflow engine. She needs to know that the visitor from three Sundays ago has not been called yet, and by whom.
How a People-only pattern actually shows up
It rarely announces itself. A church signs up for the suite during a busy season — maybe a new building meant setting up Check-Ins, or a music director wanted Services for a few months. Then the building project ends, or the music director leaves, and the modules that were built around that season quietly go unused. Nobody makes a decision to stop; the tabs are just not clicked anymore. Six months later, the only thing anyone in the office opens is the directory, and the invoice has not changed to reflect that.
The way to catch this is not to ask what the software can do — it is to ask what got opened. Pull up login activity, or simply ask the volunteer or part-time staff member who runs the database day to day: which tab did you open this week, and the week before that? If the honest answer is People, three weeks running, you are already a People-only church, whatever the subscription still says.
Where the suite pricing catches people off guard
Planning Center prices each product by the number of active people in your database, and those thresholds are shared across products even when you have only turned one on. A church of a hundred and eighty people that only uses People can find itself paying a rate calibrated for a database that size across every product tier they have added, whether or not the module gets opened. It is not a hidden fee, exactly — it is published pricing — but it is easy to sign up for the suite during a season when check-in or service planning felt urgent, and then keep paying for it long after that season passed.
The fix is not complicated: pull up your actual bill and compare it to what a flat-rate, directory-only tool would cost for the same church, not to the sticker price of the People module in isolation. For a lot of smaller congregations that comparison is not close.
What a directory-first tool gives up
Be honest about the trade before making it. Moving from the full Planning Center suite to a tool built only around people, giving, and follow-up typically means:
- No service planning. If your worship team currently builds set lists and schedules musicians inside Planning Center Services, that piece does not travel with a directory-only tool. You would need to keep that module or replace it elsewhere.
- No check-in kiosk. A children’s ministry running name tags and a printed label system through Check-Ins will not find an equivalent kiosk in a smaller tool.
- No online giving processing. A directory-first tool can record and report on contributions, but the actual transaction — the card charge itself — happens somewhere else, or does not happen electronically at all.
- No form-based event registration with payment. Signing people up for a retreat with a paid ticket and a waitlist is a Registrations-module job, not a directory job.
None of that is a surprise if you know it walking in. It only becomes a problem for a church that assumed a smaller tool was simply a cheaper version of the same suite, rather than a narrower tool built around a shorter list of jobs.
What you get back for that trade
The case for going narrower is not a longer feature list — it is the opposite. Fewer settings screens, fewer products to configure, and a login that opens straight to the thing your office actually needs on a Tuesday morning: the directory, who is serving this month, what has come in for giving, and who from Sunday still needs a call. SundayBridge is built that way — one profile per person with groups, serving, giving, care, and an engagement timeline together, plus a follow-up board that ages a guest’s next step until someone with a name and a date actually takes it. There is no service planner and no check-in kiosk to skip past, because the tool was never trying to be the whole suite.
That shift matters most in the first few weeks after moving off a spreadsheet or off a bigger platform: the office needs a directory it trusts and a giving record before it needs a service plan or a check-in kiosk. Solving the smaller problem well tends to matter more, early on, than adding the bigger platform’s full feature list back in.
A shorter list to compare tools against
Rather than comparing Planning Center’s full brochure to a competitor’s, write down what your office genuinely opened in the last month. For most People-only churches that list is short: keep the directory current, know who serves where, record what came in on Sunday, and follow up with the guest who left a card. Once that list is on paper, choosing church management software becomes a comparison against that shorter list, not against every tab in a suite you never fully opened.
It is worth checking that list against a normal week, too. Walking through what a typical week of church admin actually requires, start to finish, tends to surface whether service planning and check-in are genuinely missing pieces or just modules you turned on once and never opened again.
The follow-up question a directory-only view cannot answer alone
One thing worth checking before you switch: does the smaller tool tie a guest’s visit to an actual next step, or does it stop at the contact record? A directory that tells you a visitor exists is only half the job. What a small office actually needs is somewhere that follow-up ages visibly — a name attached to the guest, a date by which someone said they would call, and a way to see at a glance that nobody has yet. That is a different feature than a workflow builder aimed at a paid staff person managing a pipeline; it is closer to a short list that gets checked every Sunday afternoon. Reading how a guest actually becomes a member over time is worth doing before you assume any directory-only tool covers that step by default.
Migrating the directory itself
Planning Center will let you export your People directory as a CSV, and that part is usually painless. What is not always painless is getting that file into the new tool. Some directory-first products have no CSV import at all, which means a church of a hundred and fifty people is entered by hand, one household at a time, rather than uploaded in an afternoon. That is not a hidden flaw so much as a fact worth asking about directly before you commit — and worth budgeting real hours for either way, since even a smooth import still needs someone to check that households, birthdays, and notes landed correctly.
Whichever tool you land on, a clean household structure going in saves rework later. How households and individuals are modeled is worth understanding before the first record gets typed in, since fixing a flattened family structure after the fact is far more tedious than setting it up correctly the first time.
Closing thought
Planning Center is not the wrong choice for a church running a full production and a children’s check-in line every Sunday. It is the wrong shape for a church that bought the suite hoping to grow into it and never did. If your office has quietly narrowed down to one tab for the last year, that is not a knock on the software — it is information about what your church actually needs, and it is worth taking seriously before the next renewal comes due.