It’s Monday morning, and someone on your staff has been asked a simple question: how many of the people who started coming this spring are in a group now? To answer it they open the groups tool, then check-in, then giving, then a spreadsheet to line the three up. By lunch they have a number they mostly trust.
Ask where your people’s information lives and the answer is usually “everywhere.” The groups tool has a list. The check-in system has a list. Giving has a list, the email tool has a list, event registration has a list, and the app has a list of its own. Each was set up to do its job, and each keeps the people it needs for that job.
None of those lists is wrong. The trouble is that they’re all partly right, about the same people, in different places.
What one place for everyone means
It means one entry per person that every part of your platform writes to. It holds their profile and household, the groups they’re in, and every time they checked in, gave, registered, served or opened a message. It holds notes from the people who care for them, visible only to those who should see them.
When everything lands in one place, nobody has to line up facts from six systems. You can read one person’s history, in order.
Here’s what that looks like for one example person at a church. She’s made up; the shape is what matters.
Maya Okafor
An example person, not a real member
- Day 1Found youWatched a service online, then came in personSource · livestream link
- Day 3JoinedFilled in the welcome card in your appSource · connect card
- Week 2Came backChecked the kids in at the second serviceCheck-in · kids’ ministry
- Month 1Found a groupJoined a Tuesday small group, and kept coming backAttendance · 4 of 4 weeks
- Month 3GaveA first gift, then a monthly oneGiving · recurring
- Year 1ServesNow leads the welcome teamRole · team leader
In a church running separate tools, each of those lines exists somewhere, but nothing connects them. Nobody can see that the person who watched online in the first week now leads the welcome team, or how long that took, or what happened in between.
What changes when everyone is in one place
Questions become reports
The questions leaders actually ask are almost always about two things at once: attendance and giving, groups and serving, events and renewals. When those live in different tools, every answer is an export and a spreadsheet. When they live together, it’s a report someone can open on Monday. Every organization asks different questions, so the reports that answer yours are part of the build.
| Organization | What lands in one place | A question it answers |
|---|---|---|
| Church | Every visit, check-in, gift and group | Who stopped attending and stopped giving in the same month? |
| Nonprofit | Every signature, shift, donation and event | Which volunteers have never been asked to give, and which donors have never been asked to volunteer? |
| Association | Every renewal, event, course and committee | Which members come to events but haven’t renewed? |
| University | Every event, introduction, mentoring match and gift | Which alumni show up to events and mentor, but have never been asked for a gift? |
| Creator | Every sign-up, lesson, live session and payment | Which course or cohort leads members to upgrade? |
The journey becomes visible
Because every step lands in order, you can see the path people take from the edge of your community toward the center: where they came from, what brought them closer, and where they stalled. Across everyone, those paths show you which first steps lead to people who stay. There’s a practical guide to mapping yours in how to map your member journey. We describe this on our features page as knowing where everyone is.
You can act on it
All that history is only useful if it tells someone what to do. When it’s together, the platform can bring the right people to the right person each week:
- First-time guests with no follow-up yet. Send a welcome.
- Attending a month, not in a group yet. Suggest a group.
- Regulars who have missed three Sundays running. Ask their leader.
- Monthly gifts that have stopped. Reach out.
- Serving every week for six months. Invite to lead.
Each of those depends on data from at least two tools. None of them is possible from a single list in a single product.
People see what they should, and nothing else
Keeping everyone in one place doesn’t mean everyone sees everything. Roles decide who sees what: a group leader sees their group, a campus sees its people, and pastoral notes stay with the people who care for them. That’s easier to get right with one set of permissions than with six tools, each with its own idea of who is allowed to see a person.
What it takes to get there
You don’t get there by connecting the tools you have. It has to be designed, and in our process that starts in the Discover phase, where we map the tools you run today, what each one holds about your people, and the path members take from first contact to leadership.
Then come the decisions that are hard to change later: what each person’s entry holds, how households and relationships are modeled, and who can see what. Getting those right at the start is cheaper than rebuilding them in year three; we wrote about one of those decisions in Build Notes #001.
Then migration. The same person appears in several tools, spelled differently, with different email addresses. Matching them is careful work, and some history from older systems won’t map cleanly. We plan for that from the start, and we run the old tools alongside the new platform until your team is confident nothing has been lost.
Why it has to be yours
Everyone’s whole story, kept in one place, is the most valuable thing your platform holds. It’s the history of every relationship your community has built. Keep it inside someone else’s product and you’ve made it easier to hold hostage. The vendor sets the price of keeping it, the terms of taking it with you, and the roadmap for what it can do.
That’s why we build it as a platform you own. It lives in your database, in a cloud account you control, and you can export it whenever you like. The code that reads and writes it is yours too, so if you ever change who works on it, your people’s history stays exactly where it is. Our ownership terms set out what that means in detail.
When you don’t need this yet
If you have fewer than about 1,000 members, run your community on one or two tools, and nobody spends their week matching lists, you don’t have this problem yet. A single SaaS tool with a good export is the right choice, and you should keep it.
If you recognized your organization in the separate lists, the questions nobody can answer and the Monday spent reconciling, it’s worth a conversation. Bring the list of tools you use, and we’ll go through what bringing them together would look like for you.