How to Make the Case for a New Church Website to Your Leadership

You already know your church needs a new website. Maybe it was built in 2014 and looks like it. Maybe it's slow, hard to update, or no longer sounds like your church. Maybe you've patched it for years and keep hitting the same walls.

‍

Knowing what you need is the easy part. Getting your lead pastor, elder board or finance committee to pay for it is harder.

‍

This post is for the communications director, executive pastor or admin who has to make that case. Here's how we'd approach it.

Understand why leadership hesitates

To most church leaders, a website project looks like a design expense. You see it as the first thing a new family experiences before they ever visit. Closing that gap is most of the work.

‍

You'll probably hear some version of these:

• "Our current site works fine."
• "We have other budget priorities this year."
• "Can't we just update what we have?"
• "How do we know it's worth it?"

‍

They're fair questions. Plan your answers before the meeting so you're not reacting in the moment.

Lead with impact, not design

"Our site looks outdated" rarely moves a board. "People are deciding not to visit because of what they find on our website" gets attention.

‍

Connect the website to things leadership already cares about: guest experience, outreach, getting new people connected, and helping members find groups and places to serve. About 80% of people visit a church's website before they ever attend in person. And when Stanford researchers studied how people judge a website's credibility, design was the most-mentioned factor, coming up in 46% of people's comments. If your site is confusing, out of date or hard to use on a phone, some of those people won't come.

‍

A better website changes that. Here's what Scott Harris at Brooklake Church told us shortly after their new site launched:

‍

"Not only does our new website look amazing, but it is also both robust in content and simple to navigate. It's only two months old and it's already drastically improved how people take next steps with us."

‍

That's the kind of outcome leadership cares about. Frame your ask around it.

Show the cost of doing nothing

Leaders see the invoice. They rarely see what the current site is costing. Make that visible.

‍

If you have Google Analytics, pull a few numbers before the meeting:

• Monthly visitors, and how many reach your Plan a Visit or New Here page
• How much of your traffic is on phones
• Your most visited pages (are service times and location among them?)
• How many Plan a Visit or connect forms came through the site last year

‍

Then add what your team already knows: how long it takes staff to post an event, how often information is out of date, and whether anyone besides one volunteer knows how to update the site. Staff time is a real cost, and boards understand it.

‍

No analytics? Pull up the site on your phone during the meeting and try to find service times, parking and kids info. That demo often does more than any number.

Compare it to things your church already funds

Your leadership approves lobby updates, new signage, outreach events and staff hires because they understand what those do. Put the website in that category. It does the same job as a welcoming lobby for the 80% of people who check you out online before they walk in, and it keeps working every day of the week.

‍

You don't have to argue that the website matters more than other priorities. Just show it belongs alongside them.

Bring a range, not a single number

Walking in with one number invites a yes or no. A range with context invites a conversation about what you actually need.

‍

Explain what moves the price: the number of pages, custom design versus a template, integrations with tools like Planning Center or Rock RMS, multiple campuses, and whether you need help with copy and photography. Then list what's included, like design, development, mobile layouts, CMS setup for sermons and events, SEO setup, training and launch support. Line items make the number feel earned rather than arbitrary.

‍

For reference, our Essentials package starts at $7,500 and our Custom package starts at $15,000. You can see what each one includes on our pricing page.

‍

Cover ongoing costs too. With Webflow you pay for the build once, plus a monthly hosting plan. There are no plugins to update or security patches to pay someone for. If you're paying a monthly platform subscription now, add it up over five years and compare.

Make the timeline and process concrete

Uncertainty makes leaders hesitate. Show them exactly what they're approving and when it ends.

‍

Our projects move through discovery, sitemap and wireframes, design, development and launch, and most take 3–4 months from kickoff. Give leadership a start month and a launch month. If a date matters, like Easter or a fall kickoff, say so and work backward from it. You can walk them through our full process.

Consider a smaller first step

If the full budget is a hard ask this year, ask for discovery first. A paid discovery phase covers goals, strategy and a sitemap, and it gives leadership a clear scope and price before they commit to the whole build. At Sunday Best, the discovery fee is credited toward the project if you move forward.

Put it on one page

If your leadership decides from a written proposal, keep it to one page:

1. The problem: what the current site isn't doing, with one or two numbers or examples
2. What changes: what a new site would do for guests, members and staff
3. The investment: the range, what's included, ongoing costs and timeline
4. The ask: the specific amount you need approved

‍

Use plain language and skip the jargon. The goal is to give them enough confidence to say yes, not to bury them in data.

‍

Want help building the case? Get a quote and we'll give you a clear scope, price and timeline you can take straight to your leadership.