Our convictions
These aren't features; they're the beliefs that shaped every decision behind Unfold. Software that handles a church's teaching should be answerable for more than whether it works — for how it treats the preached word, and the people who receive it. Here's what we hold ourselves to.
Member-facing output must trace back to your church's own teaching. When the knowledge base has nothing relevant to say, Unfold doesn't fill the silence — it says so, and points the member back to their pastor. A machine should never improvise theology, and ours is built so it can't.
A healthy church is neither a broadcast network nor an org chart. Formation moves through people — disciple-makers, mentors, ordinary relationships. So Unfold sends nothing: no email blasts, no notifications, no scheduled pushes. Content becomes shareable, and someone hands a link to a specific person through the channel their relationship already uses.
The act of handing it over is itself a small formation practice — it makes the giver ask, "who is this for, who am I walking with?" Automating that away would work against the whole point.
Get people what they need in a couple of steps, then get out of the way. For most of what Unfold makes, once you have it you no longer need the software. No engagement loops, no nagging, no mistaking attention for ministry. Good tools are quiet.
Church apps mostly sit unopened. So Unfold is a plain website that works well on a phone — no install, nothing to set up for the volunteers who do the carrying. The pull toward "just build an app" is constant; resisting it is a discipline we hold on purpose.
We build tools in service of the mission of the church. We strive to honour established biblical patterns, using technology to empower "one another" ministry.