This guide is for the church where the words "content management system" make the whole deacon board look at their shoes. Maybe your last website died with a lapsed domain. Maybe you never had one. Either way, you know the church needs to be findable, and you know nobody on the roll wants a new part-time job maintaining it.
Good news: you do not need a tech person. You need to know what a church website actually has to do, what the options honestly cost, and what to ask before you sign anything.
What a church website actually needs
Visitors look for five things, in roughly this order: when you meet, where you are, what to expect (kids, dress, how long), who you are (a few real faces and your beliefs in your own words), and a way to reach you. That is the whole job. Everything else, sermons online, event pages, photo galleries, is lovely but optional.
Notice what is NOT on the list: animations, a members-only area, an app. A forty-person church does not need what a four-thousand-person church buys. You need the five things, kept true, every week of the year.
The "kept true" part is the trap. A website that says the wrong worship time is worse than no website, because a wrong time sends a visitor to a locked door. Whatever option you pick, the deciding question is not "how pretty is launch day," it is "who fixes it in October."
The options, honestly
A volunteer or somebody's nephew. Free, sometimes wonderful, usually temporary. The site is only as alive as that one person's season of life. When they move, graduate, or burn out, the login leaves with them. If you go this road, insist the church owns the domain and the passwords, on paper, in the office.
Do-it-yourself builders (the drag-and-drop kind). Twenty to fifty dollars a month, and honest work IF someone at the church enjoys fiddling with them. For the church this guide is for, the builder becomes a guilt machine: it can do everything and nobody touches it after March.
Agencies. Two to ten thousand dollars up front for a beautiful launch, and then you are back to the October question. Some churches love this road. Most small ones cannot justify it.
Managed services (someone else runs it for you). This is the newest lane and, we would argue, the right one for a church with no tech person. The range is wide: some charge $50 to $300 a month and take days to make a change. Ours, Parson, is $19 to $49 a month: you email the website in plain words, "VBS is July 20 to 24, supper included," and it updates itself in about a minute, with an undo if you mistype. Either way, the principle is what matters: pay for the KEEPING, not the launch.
Five questions to ask anyone, including us
1. Who owns the domain, and can we take a full copy of our site if we leave? (The only safe answer: you, and yes, free.) 2. What happens when we need a change in October, and how long does it take? 3. What does it cost per month, all-in, and is there a contract? 4. What does it look like on a phone with weak signal? (That is where your visitors are.) 5. If we have no photos, will it still look like a real church website?
Any vendor who squirms on ownership, or whose answer to October is "you will do it yourself in our dashboard," is telling you who they built the product for. It is not you, and that is fine. Somebody finally builds for you.
If you want to see what the email-run version looks like, our twenty example sites are live at parson.church, and every one of them is a working website you can poke at from the phone in your hand.