10 Questions to Ask in a ChMS Demo (and What Vendors Hope You Won't)

Demos are performances. The right questions turn a polished walkthrough into a stress test that protects your church. Below are ten questions that reveal where products are mature, where they rely on workarounds, and where your team should dig deeper.

Before you ask them, send a one-page scenario list so the rep cannot claim surprise. Assign a notetaker who is allowed to interrupt politely when the screen skips a step. Record the session if policy allows, and promise your team you will debrief within twenty-four hours so impressions stay honest.

1. Show me how permissions work for pastoral notes versus directory fields

You want to see granular roles, not a vague promise of "secure." Ask who can export notes, whether notes appear in unexpected places, and how access is audited. Mature systems separate sensitive pastoral content from public-facing profile data.

Follow-ups: Can a pastor delegate temporary access for sabbatical coverage? If a staff member leaves, how quickly can credentials be revoked? Is there an audit log entry when someone views a sensitive note? If the answer is vague, mark it as a governance risk, not a small detail.

2. Walk me through merging two duplicate households after a wedding

Duplicates are inevitable. Watch whether merge is reversible, how giving history attaches, and whether group enrollments transfer cleanly. If the vendor hesitates, your future admins will live in spreadsheet purgatory.

Ask what happens to recurring gifts, pledged campaigns, and historical attendance when profiles combine. Ask whether any identifiers remain that could confuse external integrations. The merge story is where pretty directories go to die, so push past happy-path examples.

3. How does a refund move from online giving to accounting export?

Ask for the actual screens. You are testing whether finance receives a coherent audit trail. If the answer is "we handle that outside the system," count the hours your treasurer will spend each month.

Clarify partial refunds, donor-covered fees, and end-of-year reporting. Ask how reversals appear in batch exports and whether there is a clear link between the public-facing transaction and the ledger line. Invite your treasurer to speak during this segment; their silence often means future frustration.

4. Demonstrate unsubscribe and consent for email and text on a live contact

Compliance and trust matter. You need clear opt-in, opt-out, and per-channel preferences. If messaging is an afterthought, you risk frustrated members and sloppy data.

Ask how pastoral or transactional messages differ from promotional ones, how a person can change preferences without a staff intermediary, and how bounced or failed sends are surfaced. Trust is built when members control their channels without drama.

5. What happens when a volunteer has accounts in two churches on your platform?

Real life is messy: blended families, joint ministries, and community partnerships. Understanding data separation prevents accidental cross-church visibility.

Push on notifications, shared identity providers, and support access. You want confidence that a login at Church A never exposes roster data from Church B. If the vendor minimizes this scenario, take note if your community is highly interconnected.

6. Export my people and giving data right now into CSV I can open

Portability is stewardship. If exports are delayed, limited, or require a ticket, treat that as a strategic risk. You are not planning to leave on day one, but you must be able to.

Ask whether exports include stable unique identifiers, how large datasets are handled, and whether sensitive fields are appropriately scoped. Open the file before the call ends. If columns confuse you, imagine how your admin will feel at midnight.

7. Show attendance trends for a group without exposing individual pastoral flags

Leaders need insight without gossip infrastructure. The demo should show thoughtful aggregation and role-aware dashboards.

Ask how trends handle visitors versus members, how absentee follow-up is assigned, and whether small groups can see individual histories in ways that create social pressure. Good analytics serve care; brittle analytics create anxiety.

8. How do custom fields scale without breaking reports?

Every church collects unique information. Ask how many custom fields are practical, how they validate data entry, and whether reporting stays fast. Beware endless custom fields that become junk drawers.

Discuss field types, required versus optional enforcement, and how imports map columns. Ask for a report that filters on a custom field live. If the system stutters with modest data, plan for pain at year-end.

9. What is your realistic timeline for our migration, and what breaks first?

Push past marketing timelines. Ask what typically delays launches, how historical gifts are handled, and what your team must supply. Honest vendors name friction points.

Request a sample project plan with owners on both sides. Clarify what happens if your data is dirtier than expected. The goal is not pessimism; it is alignment. Churches that underestimate migration effort rarely underestimate stress.

10. Who owns support after go-live, and what does escalation look like?

Clarify channels, hours, and whether you get a named contact. Sunday morning emergencies need a path that does not begin with "submit a forum post."

Ask for realistic response expectations for severity levels and how bugs are communicated back to engineering. If your church serves multiple time zones or campuses, confirm how coordination works when issues span roles.

How to run the room without being adversarial

Frame questions around care for your people and clarity for your staff. Pause after each answer and ask your volunteer observer, "Could you do that task next week without me?" If the answer is no, note the training gap as part of the decision.

Silence after a question is data. Let it breathe.

Red flags to watch in any demo

• Everything is "on the roadmap" without a timeframe.
• Complex tasks require unofficial Zapier chains as the primary plan.
• Permissions are described with hand-waving instead of screens.
• Exports or APIs are treated as premium mysteries.
• Your questions are redirected to a generic marketing PDF.

Green flags that build confidence

• The rep admits a gap and shows a documented workaround.
• They encourage sandbox time without a salesperson hovering.
• They reference churches similar in size and polity without naming them inappropriately.
• Security and privacy answers include specifics, not slogans.

After the demo: a 24-hour debrief habit

Same night, capture three sentences: what thrilled us, what worried us, and what we still do not understand. Compare notes across roles before memory smooths the edges. Schedule follow-up emails that reference timestamps in the recording so vendors cannot dodge.

Score answers with a simple rubric

For each question, grade the response: demonstrated live, demonstrated with caveat, promised later, or unclear. Weight the first two categories heavily. "Promised later" belongs on a risk register with an owner and a date, not on the highlight reel.

If two vendors tie on features, let support quality, data portability, and volunteer usability break the tie. Those factors decide whether you thrive after the honeymoon.

Second demos: deeper, narrower, slower

Bring the same scenarios back for a second pass once you understand the basics. Slow the rep down on the hardest 20 percent of your ministry. If they resist slowing down, you learned something valuable about post-sale patience too.

Bring a quiet critic and a friendly optimist

Pair personalities intentionally. The optimist catches vision; the critic catches gaps. Debrief separately, then merge notes. If both agree something is excellent, it probably is. If they disagree, schedule a focused follow-up rather than voting by volume.

Vocabulary check: privacy, consent, and security

Ask vendors to define terms they use freely. What counts as encryption in transit and at rest for your context? How are administrator actions logged? What is the difference between a role, a permission, and a share link? Clarity here prevents accidental oversharing later.

Include kids ministry and safety leaders in one focused segment

Schedule fifteen minutes with your check-in coordinator present. Ask about labels, guardian rules, allergies, and how substitutes gain temporary access. Watch how emergency contact changes propagate. If this segment feels bolted on, your families will feel that on Sundays.

Compare apples to apples across vendors

Use the same script in every demo. If one vendor races ahead while another lingers on basics, slow everyone to your list. Fair comparison protects your integrity and reduces post-demo arguments rooted in uneven experiences.

End each demo with two written requests: answers to any open questions and links to help articles that prove claims you heard verbally. Written follow-up separates memory from marketing.

If a question stumps the rep, resist filling the silence for them. Note the timestamp, assign an owner to verify later, and move on. Unanswered questions are not failures; they are homework.

Strong demos survive good questions. Use this list as a spine, adapt it to your polity and campuses, and you will choose software with eyes open rather than hopes inflated.