Outreach Rebuild
We build websites for churches on a monthly plan, so you know where we stand, and this guide will still play it straight. Plenty of churches should DIY. The goal here is to figure out, honestly, whether yours is one of them.
The real choice is not about software
Modern DIY builders are good. Templates are attractive, editors are friendly, and hosting is bundled. If the question were only "can we produce a decent-looking site?", DIY would win on price and this article would be two sentences. The real question hiding underneath is different: whose job is this, for the next three years? A church website is not a project; it is a small ongoing responsibility, like the church lawn. Everything below is really about who mows.
The honest case for DIY
- Lowest cash cost. Commonly $10 to $40 a month for the builder plus a domain. For a church plant counting every peso or dollar, that matters.
- Full control and instant edits. No waiting on anyone; the person with the login fixes the typo tonight.
- A genuine ministry fit. Some churches truly have that member: skilled, willing, and in a stable season of life. When the gift exists in the body, using it honors the giver.
The honest case against DIY (it is not quality)
The DIY sites that fail rarely fail at launch; they fail in month nine. The volunteer changes jobs, has a baby, moves, burns out, or simply stops being asked. Nobody inherits the login. The site freezes with last year's Easter on the homepage, and every guest who visits reads the staleness as a message the church never meant to send. We wrote a whole piece on this pattern, because it is the most common thing our audits find: the real reason church websites go out of date. It is not laziness. It is that upkeep was assigned to a season of one person's life, and seasons end.
The honest case for done-for-you
- Continuity is the product. The site's owner is an institution with an inbox, not a season of someone's life. Updates keep happening when volunteers' lives change.
- The church does only the part it is uniquely able to do: supply truth. Times, events, photos, stories. Everything technical is somebody else's job, permanently.
- Predictable cost. One flat fee covering build, hosting, security, and updates, instead of a quiet pile of renewals, plugins, and favors.
The honest case against it
- It costs real money forever, commonly $50 to $250 a month across the industry, and a church budget is sacred trust. If the fee crowds out ministry, the math is wrong.
- Edits go through a person. Good providers publish their turnaround (ours is on the pricing section, with plan caps in plain numbers); bad ones become a bottleneck. Ask before signing.
- Providers vary wildly. Ownership questions matter enormously: who holds the domain, the content, the giving account if you part ways? The only right answer is the church. Walk away from any other answer, including from us.
A decision framework that stays honest
Answer these four, in writing, with your leadership:
- 1. Do we have the person? Not "could someone learn it" but a named, willing, skilled member in a stable season, who wants this as ministry.
- 2. Do we have the successor? If that person stepped back next year, who inherits it? If the room goes quiet, you have your answer about DIY's real cost.
- 3. What is the true budget? Count volunteer hours honestly next to the monthly fee. The full numbers on every option are in our cost breakdown.
- 4. What happens on an ordinary Tuesday? A service time changes. Walk through, step by step, how it gets onto the site under each option, and how long it takes. The Tuesday test predicts the next three years better than any demo.
Still torn? Send us your current site and we will record a free audit telling you honestly which path fits, including when the answer is "your volunteer is doing great, keep going." It has happened, and we said so.
