Counting the Cost of a Church Website
Hello again from Church Plant Media! In our Web Stuff Wednesdays Introduction we asked you, the readers of Challies Dot Com, to comment on that post with your church website questions. Carl asked the following:
If I understand correctly, there are two kinds of web sites: sites you build and host yourself and sites that are built and hosted by a company (which is what I think Church Plant Media does). Can you talk about the advantages and disadvantages of each kind? Why would it be best to use a solution like yours?
Carl: In one sense, you are correct. All church websites must be designed, coded, configured, and then hosted someplace on a server. If your church has a pastor or members who are tech-savvy, then you may be able to do all of the website building and hosting in-house. Or you may choose to outsource some or all of the website development depending on your level of expertise. But just like any in-house building project, you usually “get what you pay for” from whomever is involved.
To help you understand the advantages and disadvantages, let’s “build” on this analogy. If your church building has a leaky roof, in order to get it fixed you could go all old-school and start the project by smelting and crafting your own hammer and saw. Then you could cut down your own lumber and tar your own roofing tiles from scratch. Then you could climb up to the roof yourself and rebuild that leaking section up to code on your own. In this scenario if you do not have the skills of a blacksmith, lumberjack, carpenter, and roofer, then you’ll probably need to buy the tools and materials or hire the manpower to get the job done right. Or you might have a volunteer in the church who will work for free and you hope he can fix a roof as well as he says he can. But only time will tell if the roof starts to leak again.