Late in 2019 I became board chair of my home church. It was my first time in a role like that, and I took it seriously. I wanted to serve it well.
Then January 2020 arrived, and COVID-19 turned everything upside down. The World Health Organization declared a public health emergency, the lockdowns followed, and our once-thriving church emptied out to a skeleton crew running services online. For every church in America it had become do or die, and a great many folded. I was determined that ours would not just survive but learn to thrive.
We did. But it took adjustments, and one of them was a governance problem I never saw coming. To keep operating, the board needed to be able to vote online, and our bylaws didn’t allow it. The fix seemed simple. Find the bylaws, make the edit, put the new draft up for a vote.
First I had to find the bylaws. They were somewhere in Google Drive. There were several versions, and no one could say for certain that any copy online was the latest one in force. The authoritative answer didn’t live in the system at all. It lived in people’s memories. I had to ask a former board member, and in the end the board pieced the truth together out loud, leaning on whoever had been around long enough to remember. I needed clarity and speed. What I had was an archaeology project.
So the board voted online anyway, under “emergency powers.” Whether the bylaws themselves ever got formally updated, I can’t tell you. I’d have to go ask the institutional memory, which is, of course, exactly the problem. We did the right thing on a handshake, because the tools couldn’t help us do it properly.
That was one acute crisis. The daily friction was quieter and never let up. Someone would share a document with me, I’d follow the link, and Google would tell me I didn’t have permission to open it. But permission was the whole reason they had shared it. The system was refusing me the access the sender had just tried to give. I lost count of how many times that happened, blocked by a security model built for one person and their files, not for an organization and its work.
Through all of it I carried a low, constant sense of being disorganized and disjointed as a leader. Not for lack of effort. I simply had no clear path to the information I was responsible for.
Churches don’t have owners
Almost no one says this out loud: a church is not owned. It’s stewarded. There’s a board, a covenant, a shared and sober responsibility for money and people that aren’t yours and never were. The whole structure exists so that power is held in more than one pair of hands, and so that no single person, however beloved, however tired, however sure they’re right, can act alone on the things that can’t be undone.
Now look at the software that runs underneath all of it. Open almost any tool your church touches and you’ll find an owner. One account that can do anything: add people, remove people, move money, and, if it came to it, lock everyone else out. It’s a convenient default. It’s convenient for the vendor, who only has to reason about one all-powerful user. And it is a standing contradiction of the entire reason a board exists.
That contradiction is the original sin of organizational software. We built tools around a king and then handed them to communities that had deliberately, prayerfully decided not to have one.
What TrueBoard is
TrueBoard is church governance software that takes the board seriously as the thing it actually is.
Motions get raised and seconded. Votes are cast and counted and kept. Minutes write themselves from what actually happened, not from someone’s memory a week later. Documents live where the whole board can find them, in versions you can trust. And underneath it all is a model we built on purpose and won’t apologize for: every administrator is equal, and the decisions that can’t be taken back, like removing a fellow leader or closing the account, simply cannot be done by one person alone. The software waits for a second hand.
That’s the whole posture, in one sentence: no one acts alone on what can’t be undone.
I’ll write more later about how it’s built, because showing the seams is the point. But the important part today isn’t the mechanism. It’s that the mechanism agrees with your theology of leadership instead of fighting it.
Not another thing bolted on
There’s a shelf of good church-management software out there, and I’m not here to run any of it down. Most of it does a real job well: tracking members, scheduling volunteers, taking giving. Governance, when it shows up at all, is a tab. An afterthought stapled to a directory.
TrueBoard starts from the other end. Governance is the floor the whole building stands on. We didn’t add it; we started from it. We asked a narrower question than the all-in-one tools ask, and we tried to answer it completely: how does a board do its work with integrity, and how can the tool make integrity the path of least resistance?
That focus has a cost, and I’d rather you hear it from me. TrueBoard is young. We’re in live beta, which means you’ll occasionally find an edge we haven’t sanded yet. And the communal model puts friction in the very places most software has spent twenty years removing it. Sometimes you will want to do something and the system will make you wait for a colleague to say yes. That’s not a bug we’ll be fixing. That pause is the product. But it is a pause all the same, and you should know that going in.
Why this matters more than software usually does
I don’t want to oversell this. A better tool won’t make anyone holy. It won’t heal a board that’s already broken, or manufacture trust where none exists.
What it does instead is smaller, and it matters a great deal. It can keep an honest board honest with less effort. It can make a dishonest move harder and slower and visible. It can hold the trust a congregation places in a handful of stewards the way it was meant to be held: in common, in the open, by more than one.
Churches are where people bring their trust to be kept. When governance erodes, the wound isn’t really to a budget line. It’s to trust itself, which is the one thing a church can least afford to lose. Better tools won’t save us from that. But they can refuse to be the reason it happens.
What you’re really building
Here is the part I care about most, and it’s the reason TrueBoard exists at all.
Every church and nonprofit worth the name is a relay. The people leading it today are gifted and dynamic and, sooner or later, temporary. We retire. We move. One day each of us hands off whatever we were carrying, ready or not. The mission was never meant to depend on any one of us staying forever. It was meant to outlast us.
Most leaders I know want that, badly. We hope to be replaceable: to set the next generation up to succeed, to leave them a foundation instead of a tangle of passwords and half-remembered decisions. That hope is one of the most generous things about good leadership. It’s also the thing our tools betray, because when the dynamic leader finally leaves, far too much leaves with them. The context. The reasons. The record of who decided what and why, living in one head and one inbox that has just walked out the door.
A tool has limits worth naming. TrueBoard can’t train your successors. It can’t hand them wisdom, or character, or a sense of call. Those are human things, and they stay human. By itself it won’t advance your mission a single inch.
What it can do is keep the handoff from being a cliff. It holds the record whole, so the next board can read the story of a decision instead of guessing at it. It shares the keys from the beginning, so no one person’s departure ever locks the doors or leaves the lights off. The same design that means no one can act alone is the design that means no one can take the church down with them when they go.
That’s continuity. You won’t notice it on an ordinary Tuesday. You feel its absence on the hardest day, and you feel its presence as relief on the day everything changes. More than anything else it does, TrueBoard is built for the people who aren’t in the room yet: the ones who will inherit what you’ve stewarded, and carry it further than you got to.
Who built this
I should tell you where this came from. TrueBoard began in that bylaws hunt, and in a hundred smaller versions of it: a church doing its level best, slowed and tripped by software that was never built for the way a church actually works. At some point being frustrated stopped being enough, and I set out to build the alternative I had needed. That work is Aeris Labs, my studio. I built TrueBoard myself, to a standard I won’t compromise.
I come at software from an unusual angle. I was trained first to make physical things that don’t fail under load, then to make things worth looking at and listening to, and only then to write code. I build the way those disciplines taught me to: slowly, completely, with nothing left merely fine. I’ll show you that way of working in the posts to come, rather than just claim it.
Before you go
Whether or not TrueBoard is ever right for your church or nonprofit, I’d like you to leave with one thing. It’s a sentence you can say at your next board meeting, no software required:
Let’s make sure no one on this board can do anything irreversible alone.
Say it out loud sometime when the agenda is light. Watch what happens. The discomfort you might feel naming it is the gap the right tools are supposed to close.
If, when you’ve thought it over, you’d like to see what it feels like when the tool remembers for you, who decided what, and when, and with whose second, then TrueBoard is in live beta and the door is open. No rush. We built it to be here a long time.
Rob
Aeris Labs