Values that keep church work human and trustworthy.
C.A.R.E is the shorthand we use for the promises behind the product: remember the calling, steward trust, build dependable systems, and listen closely to the people doing the work.
Our values
C.A.R.E is small enough to remember. Deep enough to govern the work.
These are not office-wall words for us. They shape what we build, what we decline, how we support customers, and how we talk about the responsibility of serving church teams.
01
Calling
We build for the people doing the quiet work behind Sunday: the admin reconciling details, the volunteer welcoming families, and the pastor trying to stay present with people instead of paperwork.
How it shows up
We choose clarity over novelty, keep workflows close to real ministry language, and ask whether a feature gives church teams more room to serve.
Product decisions start with the ministry job, not the software category.
We keep operational work visible enough to coordinate, then quiet enough to get out of the way.
We avoid features that turn care, discipleship, or stewardship into vanity metrics.
02
Accountability
We design for careful stewardship of people, finances, access, and time because church teams carry real trust from real communities.
How it shows up
We make ownership, permissions, approvals, records, and audit trails easier to understand so leaders can answer what happened and why.
Permission changes should be easy to explain later.
Financial workflows should support review, reconciliation, and responsible handoff.
Privacy-sensitive records should be protected by default and shared with intention.
03
Reliability
We create dependable systems that hold steady during Sunday check-in, giving review, trip planning, media publishing, and the ordinary weekday work between them.
How it shows up
We value boring infrastructure, predictable interfaces, and recovery paths over fragile cleverness.
Critical workflows need loading, empty, error, and success states.
Data should have one dependable source of truth across campuses and teams.
Teams should be able to keep moving when one task, file, form, or integration needs attention.
04
Empathy
We listen closely to pastors, staff, volunteers, finance teams, media teams, and operations leaders because the right workflow is usually hidden in their weekly rhythms.
How it shows up
We write product copy plainly, design for repeated use, and treat support conversations as product research.
Interfaces should be understandable by a trained volunteer and efficient for a full-time operator.
Migration, setup, and support should feel calm and respectful of small teams.
We would rather simplify a workflow than make a customer memorize our model.
Values in practice
How values become product decisions
The best values leave fingerprints. Here are the product instincts they create inside Cendance.
Trust beats cleverness
If a feature affects people, permissions, giving, finance, or public sharing, it needs clear ownership, review paths, and language a team can explain later.
One calm source of truth
We prefer connected records over copied spreadsheets, because duplicated data slowly becomes duplicated pastoral work.
Built for Monday too
Sunday matters, but so do the quiet Monday tasks: follow-up, reports, notes, approvals, reconciliation, and preparing for the next service.
The kind of company we are building
We want Cendance to feel like a steady hand.
For church teams, that means clear tools, respectful support, careful data stewardship, and software that makes ministry operations calmer instead of louder.