How Much Should a Church Website Cost?

Church budget meetings have a particular silence in them, and it usually arrives right after somebody asks what the website is going to cost. Nobody wants to look uninformed, the numbers people have heard range from free to twenty thousand dollars, and the quotes in front of them don’t line up in any way that allows comparison.

So let’s take the awkwardness out of it.

There are two costs, and quotes usually name one

The first is the build: designing it, writing it, putting your content in, connecting whatever you use for giving and sermons, and launching it.

The second is keeping it alive: the domain, hosting, security certificate, software updates, backups, and a person who responds when the giving page stops working on a Saturday night.

Almost every unpleasant surprise in this category comes from a quote that priced the first and stayed quiet about the second. A church pays for a build, assumes that’s it, and discovers eighteen months later that nothing has been updated since launch and nobody was ever assigned to do it.

When you get a quote, the useful question isn’t “how much.” It’s “what happens in month four.”

Why the published ranges are so wide

Search for church website pricing and you’ll find numbers from a few hundred dollars to well past ten thousand. One Little Web’s cost study, which is a web agency’s own research and should be read with that in mind, puts small-business builds anywhere from a few hundred with a freelancer up to five figures with an agency.

That spread isn’t companies disagreeing. It’s the word “website” covering completely different amounts of work.

At the low end, someone applies a template, drops in your logo, and hands it back. At the high end, someone interviews your staff, writes your copy, shoots real photos of your building and your people, migrates fifteen years of sermon archives, connects your giving platform, and trains your office manager to update it.

Both are websites. One is a weekend and one is a project.

This is also why comparing two quotes by their totals tells you almost nothing. Put them side by side and compare the scope line by line. Who writes the words? Who takes the photos? Who moves the old content? What happens after launch, and for how long?

What each line item is actually for

Domain name. Your address on the internet, rented annually. Modest cost. The important part isn’t the price, it’s whose name it’s registered in.

Hosting. The computer your site lives on. Cheap shared hosting and managed hosting can differ by a factor of ten, and the difference is mostly speed, security, and whether a human being will help you at 9pm.

SSL certificate. The padlock in the address bar. Free on most modern hosting now. If someone is billing you separately for one, ask why.

Design and build. The one-time work. This is the number most quotes lead with.

Content. Writing, photos, and moving your existing material over. Frequently the biggest hidden cost, because it’s the part churches assume they’ll handle themselves and then don’t. A launch delayed six months waiting on staff bios is a real and common cost.

Updates and security. Not optional, and bigger than most people assume. Patchstack, a security company that publishes an annual report on the WordPress ecosystem, counted 11,334 new vulnerabilities disclosed across WordPress plugins and themes in 2025. Somebody has to keep up with that, forever. If it isn’t in your quote, it’s on you.

Backups. Cheap insurance. Verify they exist and that someone has actually tested restoring one.

Support. What you’re really buying with a monthly plan. Ask what the response time is and who answers.

The question that actually determines your budget

Not “how big is our church.” It’s: who on your team is going to own this in three years?

If you have a staff member or a genuinely committed volunteer who will keep the site current, learn the tools, and still be here in three years, a one-time build makes sense and you’ll spend less.

If you don’t, and most churches under a few hundred people don’t, then you’re choosing between an ongoing plan and a site that slowly goes stale until someone proposes rebuilding it. The rebuild almost always costs more than the maintenance would have.

That’s the honest tradeoff, and it doesn’t have one right answer. It has a right answer for your church.

What we’d tell you to ask any vendor, including us

1. What’s included after launch, and for how long? Get it in writing, with a response time.
2. Who owns the domain and the hosting account? It should be your church, on your church’s email address. If a vendor registers your domain in their own name, that’s worth resolving before you sign anything.
3. What happens if we leave? A straight answer here tells you most of what you need to know about a company.
4. Who writes the content? The most common reason a website launch slips is that nobody agreed on this.
5. Is the price a build fee, a plan, or both? Some quotes are a one-time fee. Some are monthly. A few are a one-time fee that quietly becomes monthly.

If a vendor gets uncomfortable at question two or three, that discomfort is the answer.

We publish our own plan pricing on our church website hosting and support page rather than making you ask, which is the standard we’d hold anyone else to as well. Whether or not you talk to us, take the five questions above into the conversation. They’re the difference between a budget line you can defend and one you’ll be re-explaining next year.