Durable Church
Menu

Work with us

We help your church stop depending on any one person.

Hands-on work on the people, decisions, and systems your ministry depends on. We build it with your team, then hand it over, and we plan our exit from the first conversation.

What we work on

Built with your people. Then handed over.

People

Leaders who can carry real responsibility in every ministry and department, and succession planned before someone leaves.

Decisions

Who can say yes, and to what, so the work doesn’t all wait on the pastor.

Systems

The website, member database, communications, and guest follow-up, set up so more than one person can run them.

Transitions

A pastor or secretary leaving, or a church newly on its own after leaving a denomination.

Sound familiar?

Where churches usually call us.

  • A pastor or long-time secretary is leaving, and the know-how is leaving with them.
  • One volunteer holds the keys to something everyone depends on.
  • Every decision waits on the pastor.
  • You’ve left a denomination and now own everything the conference used to provide.
  • Something important runs, but nobody else could run it.
  • A whole department runs on one staff member’s knowledge.
  • Decisions stall somewhere between the staff and the board.
  • Staff turnover resets the same work every few years.

Who we serve

From pastor-and-volunteer churches to multi-staff congregations.

Pastor and volunteers

The pastor or one faithful volunteer holds almost everything. We start small: a study your people can run, or one area built and handed over.

A small staff

A few people carry what the whole church depends on. We begin with a listening visit and a plan in phases your leaders can approve.

Multi-staff churches

Departments run on one staff member’s knowledge, and decisions stall between staff and board. We work department by department alongside your executive leadership, and train an owner inside each area.

Evangelical, mainline, and newly independent congregations. Plans are written so your elders, council, session, vestry, or board can approve them one phase at a time.

A first engagement

Two ways to start. You choose.

A listening visit and a written plan

We learn how your church actually works, name what depends on whom, and give your leaders a written plan in phases they can approve one at a time.

One area, start to finish

Pick one thing that depends too heavily on one person, like the website, the staff system, or how decisions get made. We build it with your people and hand it over.

Either way, you can stop after any phase and keep everything built so far.

How it goes

Four phases. The last one is us leaving.

  1. 01

    Listen

    Learn how your church actually ministers, not how a software vendor thinks church should work. Together we name what depends on whom, and what would stop if they were gone.

  2. 02

    Build alongside

    We build with your staff and volunteers, not for them. The work comes in phases, and each phase stands on its own. You can stop after any one and keep everything built so far.

  3. 03

    Transfer

    Everything moves into your church’s name and hands. Your people make a real change, live, while we’re still close enough to help, before we call anything handed over.

  4. 04

    Release

    We step away. Help stays available if you want it. It is never required. And if our leaving would break something, the work isn’t done yet.

When we’re done

What your church holds when we leave.

  • People on your team who have already done the work themselves, not just watched it.
  • At least two people ready to carry each critical responsibility.
  • Clear lines on who can decide what, written down and already in use.
  • Every account and system registered to the church, not to us.
  • A plan for when someone leaves, a password is lost, or a bad day comes.
  • Plain-language guides, with honest notes on what is verified, what is assumed, and what is still unknown.

What we won’t do

  • Become the person your church can’t do without.
  • Make decisions that belong to your leaders.
  • Hold your logins or keep the keys “for convenience.”
  • Sell you anything you can’t walk away from.
  • Measure success by how much you still need us.

What it has looked like

Four patterns from real churches.

A staff system people can rely on

Staff questions and conflicts all ran through the same few people. We put a staff system in place: a handbook, job descriptions, onboarding, and policy sign-offs, along with a clear path for resolving conflict and restoring relationships.

A home for every decision

Decisions piled up on the same few desks. We gave the church a shared way to place them, so each decision has a home, an owner, and a clear point where it moves up. Staff now settle routine decisions themselves and bring the rest forward with a recommendation.

A church website, handed over for good

The church moved from ongoing support to ownership. Hosting, domain, and accounts moved into its name, with two administrators on each. Staff received a handbook and companion guides, then made a supervised live change themselves before the handoff was called complete.

A digital ministry roadmap in stand-alone phases

Website, church management system, and communications, sequenced so the church could stop after any phase and keep what it had. Decisions were captured in staff workbooks, so the choices stayed with the people living with them.

Shared without names, out of respect for the congregations.

The durability test

The work is complete when your church would keep running if we, or anyone else, became unavailable tomorrow.