How to Hire a Church Website Designer: Questions, Contracts, and Red Flags

Somebody on your board said it at the last meeting: "We really need to do something about the website." Everybody agreed. And then, somehow, it became your job.

Now you're looking at portfolios. They all look nice. Every company says it understands churches. You've never hired a web designer before, and this is the congregation's money.

To hire a church website designer well, decide what the site has to do, send every candidate the same one-page brief, and compare their written answers on price, timeline, who updates the site, and who owns it. The portfolio matters. It just isn't where this decision gets made.

If you're looking for names, our comparison of church website design companies covers the field. This post is about how to run the hiring process, whoever ends up on your shortlist.

Do you actually need to hire a church website designer?

You need a designer when your current site can't do what your church needs and nobody on your team can reasonably fix it. Plenty of churches don't need one yet. There's nothing wrong with a template that fits.

Be honest about which of these sounds like you:

• Hire someone when the site is hurting you, you've got no one with the time, or you need things a template can't do.
• Keep and fix it when the site is decent and the real problem is that nobody's kept it current. That's optimization, not a redesign.
• Do it yourself when you've got simple needs and a volunteer who'll stick with it. Start with how to build a church website and our church website builder comparison.

Not sure? Read the signs in when a church outgrows its website builder before you spend anything.

What should you decide before you contact a designer?

Decide three things first: who the site is for, who'll update it after launch, and what you can spend. If you skip this, the designer's assumptions will fill the gap.

Write them on one page. This is your brief, and it doesn't need to be polished.

• Who it's for. First-time visitors, your members, or both? If both, which comes first?
• What must work. Service times, sermons, events, giving, groups, your church management system.
• Who keeps it current. A staff member, a volunteer, or someone you pay?
• Your budget. A real range, including the monthly cost after launch.
• Your deadline. And the actual reason for it, if there is one.
• Who decides. The person who signs and the people who get a say.

That last one matters more than it looks. Website projects stall when a committee meets the design for the first time at the end.

How much does a church website designer cost?

A freelancer typically runs $1,500 to $7,500, and a custom build with a larger team runs $5,000 to $25,000 or more, plus ongoing hosting and support. Our breakdown of what a church website costs walks through every path, and the five-year math shows why the monthly line matters as much as the launch price.

Tell candidates your range up front. You're not giving away your negotiating position. You're saving everyone three weeks.

What questions should you ask a church website designer?

Ask the questions that produce a written answer you can compare. Send the same list to everyone, by email.

About the money

• What's the total price, and exactly what does it include?
• What will we pay every month after launch, and what does that cover?
• What counts as a change that costs extra?

About the work

• How long from signed contract to live site, and what do you need from us to hit that date?
• Who will actually do the work, and who's our contact?
• Who writes the words? This one quietly derails more projects than design does.
• Can we talk to a church you built for two or more years ago?

About finding you on Google

• If we're replacing a site, how do you protect our existing search rankings?
• Will you set up Search Console, analytics, and redirects before launch?
• How do you handle our Google Business Profile?

Be careful with anyone who guarantees first-page rankings. No honest designer can promise what Google decides.

About after launch

• Show us how a volunteer changes the service times. Can we watch it, live?
• What happens if you go out of business, or we part ways?

What should a church website contract include?

A good contract says what you're getting, when, for how much, and what you keep if it ends. We're not lawyers, so have someone in your congregation with that background read it. Look for these in plain language:

• Ownership. Your church owns the domain, the content, and, ideally, the design and code. Get it in writing.
• Domain registration. Registered in your church's name, with your church holding the login.
• Giving. The processor account is in your church's name, not the vendor's.
• Scope. How many pages, how many revision rounds, and who supplies photos and copy.
• Payment schedule. Tied to milestones, not just dates.
• Exit terms. Notice period, what you can export, and how the handoff works.
• Term length. Any commitment period, and what happens at renewal.

Ownership is the one churches regret skipping. We wrote the longer version in does your church own its website, and it's worth fifteen minutes before you sign.

What are the red flags when hiring a church website designer?

The biggest red flag is an answer you can't get in writing. Here are a few others worth noticing:

• A price that only exists after a demo, and changes after it
• A monthly fee nobody can fully explain
• The domain registered in the vendor's name
• Every small text change routes through a support ticket
• A portfolio that's all screenshots, with no live sites you can visit on your phone
• "We understand churches," with no questions about yours

That last one tells you plenty. A good designer should be curious about your church. Who's in your neighborhood? Who's walking through the door? What do people ask on their first Sunday?

How do you compare church website designers?

Put the written answers side by side in a simple table and score what actually matters to your church. Then visit each candidate's live church sites on your phone and try to find the service times and the giving page. Time yourself.

Want a standard to compare against? These church website examples show what clear looks like.

Then call the references. Ask them one question: "What do you wish you'd known before you signed?" People will tell you.

Where we fit

You should know we're one of the options, so read this section accordingly. We do custom church website design and development. Our public pricing starts at $1,995 for a full migration and $3,495 for a custom design, plus $195 a month for Studio, the platform that keeps the site current. The church owns the domain, code, and content.

We're also not the right fit for every church, and a small congregation with a willing volunteer may be better served by a good template. If you'd like a real look at what you have before deciding anything, our $295 church website audit is credited toward any package within 90 days if you hire us. If you want to ask us the questions above, book 15 minutes.

Your One Step

Don't start with a portfolio.

Start with the page. Write your one-page brief this week, even if it's rough, and show it to two people who'll have an opinion later.

That single page will make every conversation that follows clearer, cheaper, and shorter. Your church's website is worth getting right, and you're more equipped to hire well than you think.