Matt Pritchett
Personal

What a Church or Ministry Really Needs From Its Website

If you lead a church or ministry, you probably didn't sign up to manage a website. You signed up to care for people. Then someone said you need an app, a new platform, a text system and a better homepage, and your to-do list got longer.

I want to say something plainly: you don't need fancier tools. You need your people to be able to do a few things easily. Everything else is optional.

I work with churches and ministries as well as businesses, nonprofits and teams. The problems look different on the surface, but they start in the same place: a real person trying to do something and getting stuck.

The four things your website and systems are for

When I look at a church website, I ask whether it helps people do these four things.

1. Connect

A first-time visitor is nervous. They want to know when you meet, where to park, what to wear, whether their kids will be looked after, and what it will feel like. If they can't find that quickly, some won't come at all.

Connecting also means the people already in your community can reach each other and reach you. Is there a clear way to ask for prayer, ask a question, or get in touch with a real human being? And does someone answer?

2. Give

Giving should be simple and obvious. Someone who wants to give shouldn't have to hunt for the page, create an account they don't want, or wonder where the money is going. Just as important, the person who counts and records gifts shouldn't have to re-type everything by hand on Monday morning.

3. Serve

Most churches and ministries run on volunteers, and volunteers get lost in sign-up sheets, group texts and email threads. A good system lets someone say "I'd like to help," see what's needed, and be placed without three people chasing them. It also keeps your leaders from burning out because everything runs through their phone.

4. Find answers

People come to your site with questions. When is the next event? How do I join a group? How do I get baptized? Who do I talk to about a funeral? If the answers are buried or out of date, your staff end up answering the same questions again and again.

What this means in practice

Notice that none of those four things is "have a modern design" or "use the newest platform." The tools are only a way to get there.

Here is how I'd test your current setup:

  • Ask someone who has never visited to find your service times and what to expect. Watch where they get stuck.
  • Try giving from your own phone. Count the steps.
  • Ask your volunteer coordinator what part of their week feels like busywork.
  • List the five questions your office gets most often, then check whether your site answers them.
  • Ask who can update the site today if the person who built it is unavailable.

That last one matters more than most people expect. A site that only one tired volunteer understands is a risk. Whatever you use, your team should be able to keep it current without a manual.

Be wary, but not afraid

Being wary of tech is healthy. Plenty of leaders have been burned by a system that cost too much, took too long, or was set up by someone who then disappeared. I'd rather you ask hard questions than sign something you don't understand.

Good questions to ask any person or company:

  • What problem will this solve for our people, in plain words?
  • Who on our team will run it day to day?
  • What happens if we want to move away from it later?
  • What will it cost this year, and the year after?

Sometimes the right answer is a ready-made platform. Sometimes it's something built around how your community actually works. Sometimes it's simply fixing what you already have. I would rather tell you honestly which one fits than sell you the biggest option.

Where I come from

I've been solving problems with software since 2007, working with universities, hospitals, household-name brands, nonprofits, churches and small businesses. I also build products of my own. If you'd like the background, you can read my story or learn a little more about me.

Matt Pritchett: I solve problems with software and systems, people first.

I take on a small number of outside projects each year, so I like to start by listening. Before I think about any software, I want to understand who is struggling, what they're trying to do, and what is getting in the way.

Start with the people

If your website and systems help people connect, give, serve and find answers, they're doing their job. If they don't, a better-looking tool won't fix it, but a clearer look at the problem usually will.

Got a problem? Let's start with the people.

← All writing