Everything that's included, in plain terms

The first build

When you get in touch, we start with a conversation — not a form to fill in on your own, but an actual chat about your church. What are your service times? What's coming up? Who's the site for — regular congregation, or people who've never set foot inside before? That conversation is what the site gets built around, rather than a generic template with your name swapped in.

A standard build includes:

• A proper home page, written from what you've told me — not filler text with your church's name pasted over the top
• A contact page with a working enquiry form and a thank-you page once someone's sent a message
• Service times and regular pattern of worship, kept prominent and easy to find
• A what's-on or events section for anything coming up
• A safeguarding page, if your church needs one — with your policy and contact details clearly laid out
• Privacy policy and cookie policy pages, so the site is properly compliant from day one
• Whatever else genuinely matters to your church — a history page, a "how to find us" page with directions, a giving page. We agree the full list together before I start building, so nothing's guessed at

For a group of parishes sharing one site, this looks a little different — see the Groups & Benefices page for how that's structured.

What's deliberately left out

I don't build online shops, ecommerce, or take payments directly through the site. If your church already uses a giving platform — the Parish Giving Scheme, or something similar — I'll add a clear link through to it, but the payment itself happens on their platform, not mine. I also don't add member-management systems or livestreaming players; if you already use a service for either, I'll link out to it rather than try to rebuild it.

This isn't a gap in what I can do — it's a deliberate choice. Sites that try to do everything tend to do most of it badly. A church website's real job is simple: let people find out what you're about, when things happen, and how to get in touch. Everything here is built around doing that properly.

Hosting

Once your site is built, it's hosted as part of the same £50 a month — there's no separate hosting bill, no renewal notice to worry about, no technical account to manage yourself. If you need a domain name registering, that's handled as part of getting started too.

Unlimited updates

This is where a church website usually goes wrong elsewhere: it gets built once, looks great for a month, and then quietly goes stale because nobody has the time or the technical confidence to keep it updated. That's the whole reason this service works the way it does — every update after launch is done by me, personally, at no extra cost and with no cap on how many you send.

That's a big enough part of the service that it has its own page — see Keeping Your Site Current for exactly how sending an update works, what to send, and roughly how long it takes to go live.