A vendor demo is built to make the product look good. That is not a criticism — it is the vendor's job. It is your search committee's job to make sure the call also answers the questions that actually decide whether the tool survives contact with your volunteers six months from now.
The list below is nine questions, in four groups, written so a part-time secretary or a volunteer treasurer can bring them into any demo call for any product and walk out with real answers instead of a good feeling. Write the answers down. You will want to compare them across vendors later, and memory is not reliable after the third call of the week.
Start with money, because it is where vendors get vague
Pricing pages are often simpler than the actual invoice. Ask these three before anything else, and ask for numbers, not ranges.
What is the total monthly price, all in? Not the starting tier — the price for your church, with your number of people, your number of volunteers logging in, and any module you actually need. Some tools look inexpensive until the per-user add-ons and the reporting module and the text-messaging package are stacked on top.
What happens to the price as we grow? A congregation of 90 that grows to 150 should know now whether that growth triggers a new pricing tier. Per-member pricing in particular can turn a modest tool into an expensive one exactly when you are trying to welcome more people, which is a strange thing for church software to punish.
Can we cancel anytime, and what does that actually mean? Ask about contract length, notice period, and whether there is a fee for leaving early. A flat, predictable, cancel-anytime price is worth more to a small church budget than a slightly lower rate locked behind a year-long contract.
Ask what happens to your data if you leave
This is the question search committees skip most often, because nobody wants to think about leaving a tool before they have even bought it. Ask it anyway, on the call, before you sign anything.
Can we get our people and giving data out cleanly? A real answer names a format — a CSV export of the directory, giving history, and attendance — and says whether it is self-serve or requires a support ticket. A vendor that hesitates here, or says data export is a feature on a higher tier, is telling you something about how they think about your church's information.
Who owns the data while we are a customer? This should be an easy, immediate yes, but ask it plainly. You are looking for a straight answer, not a pause.
Ask about the people who will actually use it
The person on the demo call is rarely the person who will use the tool every week. The greeter coordinator, the Sunday school teacher, and the volunteer treasurer will. Ask on their behalf.
Can a volunteer do the one task they need in under a minute? Ask the salesperson to show you, live, how a greeter records that a guest came, or how a serving-team lead checks who is scheduled this Sunday. If it takes four menus and a login only staff would remember, it will not get used, no matter how complete the feature list is underneath it.
Does it support separate logins or permissions, and do we need that? Some tools give every volunteer who logs in the same view of everything; others let you restrict what a given login can see. Ask plainly which kind you are looking at, and decide honestly whether your church needs restricted roles or whether a single shared login is fine for a congregation your size. Neither answer is wrong, but you should know which one you are getting.
Ask what is read-only and what you can actually edit
Feature lists rarely distinguish between a screen you can act on and a report you can only look at. Both are useful, but they are not the same thing, and a vendor should be able to tell you which is which without prompting.
Which parts of the product are reports we read, and which are records we edit? Attendance history, for example, might be something you can only view charted against past weeks rather than a screen where you log a new session yourself. That can be a perfectly reasonable design if the number still comes from somewhere real — but you want to know it going in, not discover it in month two.
What does the product not do, and what will we still handle by hand or with another tool? Every tool at this price has edges. Some do not send email or text messages. Some do not process online giving — they record what came in, but the money still moves through a separate processor. Some have no child check-in kiosk. None of that is disqualifying on its own. What matters is that the vendor says it plainly instead of letting a glossy feature page imply otherwise.
Make the demo prove it, not just describe it
The strongest version of this call is not a slideshow. It is you, with your own list of weekly jobs — welcome a guest, take attendance, record a gift, schedule the serving team — asking to try each one yourself, live, on the call. Watch how long the salesperson hesitates before letting you drive.
This is exactly why SundayBridge runs a public demo of a fully populated sample church that anyone can walk through before talking to a person — it is read-only, so you are judging the shape of the tool rather than saving real data in it, but you can click through every screen at your own pace. If a vendor will not let you touch the product without booking a call first, that is itself an answer worth weighing.
If you are coming from paper or a spreadsheet rather than switching tools, our guide on moving off spreadsheets covers what actually changes in that move, and our longer piece on choosing church management software walks through the fuller evaluation these nine questions are drawn from.
Write the answers down before the next call
The most common mistake is trusting memory across a week of demo calls. By the third vendor, the price quotes blur, the promises about data export start to sound the same, and the tool that actually answered every question plainly gets no more credit than the one that talked fastest. Keep a simple sheet: one row per vendor, one column per question, and write down the actual words used, not your impression of them.
Once you have chosen and your data is ready to move, a clean starting record matters more than people expect. Our guide on cleaning up your church database is worth reading before you load anyone's information into whatever you pick, whether that is SundayBridge or something else.