Why this matters
A church website works best when someone keeps it current every month, so it makes sense to pay for it the same way: a flat monthly fee for upkeep, instead of a large one-time redesign now and then. A redesign pays for launch day. A first-time guest needs the service time, the sermon series and the pastor's name to be right on the Saturday night they look you up, long after launch.
The assumption worth questioning is that a website is a one-time project, like a new roof: save up, pay once, move on. A website keeps changing after launch. Service times shift, a new series starts, a staff member moves on. When nobody's job includes those edits, they wait, and the site slowly stops matching your Sunday. That is nobody's fault: the project ended, and the work kept going. A monthly fee puts that work on someone's calendar.
At a glance
- A flat monthly fee fits a part-time church team better than a one-time redesign, because it pays for the upkeep a first-time guest depends on as well as the launch.
- In our 2026 State of Small Church Websites study, an audit of 2,000 church websites, 72.8% of small church websites (n=1,734) showed an update within a year, about three in four. Keeping a site current month to month is the ongoing part, and it needs an owner.
- A monthly fee is worth paying only when it includes real work: edits, updates, and a person to ask. If it covers hosting alone, your platform bill already does that.
- If a volunteer already keeps your site current every month, you don't need a monthly service fee.
The thesis
In my view, a church should pay for its website monthly, as a service, rather than buy it once as a project. What a first-time guest needs is a site that is right this week: today's service time, the current series, the pastor's name and face. That takes small, regular edits, and a monthly fee is the honest way to pay for regular work.
The study shows two different bars. A yearly update is common: 72.8% of small church websites (n=1,734) showed one. Being current is a separate question. Across all judged sites in the same study (n=1,930), 41.2% showed current content, meaning an update within about three months. Current is what a guest sees on Saturday night, and it comes from steady edits rather than a big launch.
It also fits how a small church budgets. A large one-time invoice can mean a vote and a season of saving. A steady monthly amount sits in the regular budget, where a treasurer can plan for it.
What changes if you believe this
You stop asking "when can we afford a redesign?" and start asking "whose job is it to keep this current?" The second question decides what a first-time guest sees. Say a family new to town checks your homepage on Saturday night. If the time and address are right, they can plan their morning.
You also compare three years instead of one invoice: the redesign, the upkeep hours after it, and the next redesign, beside a flat monthly fee for the same three years. Then check what work each one includes.
And you treat the platform bill as the starting point of the cost. In our 2026 study, the median visible platform spend for small church websites (n=1,734) was $16 a month, as of the July 2026 crawl. That is the platform's published starting price, the software alone. The edits a guest depends on are a separate cost, paid in volunteer hours or in a monthly fee.
The strongest counterpoint
A one-time build can be the better choice. If a capable volunteer updates your site every month, a monthly service fee pays for work that is already getting done. A monthly fee that covers hosting alone buys little beyond what your platform plan already provides, so a careful treasurer is right to ask what the money does each month. There is also a fair question about who is making this case: Church Digital sells a flat monthly website plan, so read this knowing which side we're on.
I still hold the thesis because a standing job is sturdier than one person's free time. Volunteers move, change roles and get busy, and none of that is their fault. A monthly arrangement keeps the edits going when that happens. If your volunteer has it covered, keep your platform plan and skip the service fee. That is a good outcome, and you don't need us or anyone else for it.
Common mistakes
- Paying a monthly fee that includes no work. If the invoice covers hosting and nothing else, you may be paying again for what your platform plan already provides. Ask the questions in the table below before you sign.
- Adding a fee on top of a volunteer who already keeps the site current. That pays twice for the same work.
- Deciding the budget before the site. If your site works on a phone and the person who updates it can still log in, it may need steady upkeep rather than a rebuild.
Five questions to ask before you pay any monthly website fee:
| Ask the vendor | Why it matters |
|---|---|
| Who makes edits when service times change, and how fast? | The time on your homepage is the one they plan their morning around. |
| Are sermon and series updates included? | A current series shows the church is active this month. |
| Is the security certificate (HTTPS) renewed for us? | If it lapses, browsers show a warning page instead of your site. |
| Is there a limit on edits each month? | A limit you reach every month means the edits wait. |
| Can we leave with a copy of our site and our content? | You keep what you paid for if you ever switch. |
Practical takeaway
This week, open your homepage on your phone and check three things against this Sunday: the service time, the current sermon series, and the pastor's name. If all three match, your upkeep is working, whoever does it. If one is off, write down your platform fee, your domain renewal and the hours someone spends on the site each month, then decide who should own the monthly edits. Here is a short note you can forward to your treasurer or board:
> Before our next budget talk: our website needs someone to update service times, sermons and events every month. Can we list what we pay now (platform, domain, volunteer hours) and decide who owns that work? A monthly fee only makes sense if it pays for those edits.
Frequently asked questions
Is a monthly church website fee cheaper than a one-time redesign?
It can be over three years, when the monthly fee includes the upkeep that keeps you from needing a second rebuild. A redesign can look like the cheaper choice because you pay once. Compare the full three years instead: the build, the hours spent on upkeep after it, and the next build. Put the monthly total beside that, and check what work each one includes.
What does a church website normally cost per month?
The software alone is modest. In our 2026 State of Small Church Websites study, an audit of 2,000 church websites, the median visible platform spend for small church websites (n=1,734) was $16 a month, software only, as of the July 2026 crawl. A monthly fee that includes edits and upkeep pays for someone's time as well as the software, so expect it to cost more than the platform alone.
When is a flat monthly fee the wrong choice for a church?
When a volunteer already keeps your site current every month and the design still works for a first-time guest on a phone. Then a monthly service fee pays for work that is already getting done. Keep your platform plan, thank your volunteer, and pay for monthly help only if that upkeep stops happening.
Where this connects in our work
- What a church website actually costs in 2026, which breaks the costs down by type of site.
- When to scrap and start over on a church website, if you're not sure your site needs a rebuild at all.
- How to audit your own church homepage, a longer version of the phone check in this post.
Next step
If you'd like a second opinion on whether your homepage needs a rebuild or only steady upkeep, ask for a free homepage review. It is a video of about 4 minutes, sent within 2 business days.