When people are considering a web project, one of the most important factors is how much money they are going to need to spend in order to make it happen.
Yet at least initially, it's a difficult question to answer. It's not that it's a bad question. It's a really good question actually; it's just not well-defined enough.
Let me explain by asking you a question: How much does it cost to build a building? Unless you're in the construction industry, you probably have no idea. But even if you are, you still can't give me a straight answer. Why? Because you don't know enough about the building I am asking you to building.
The exact same logic applies to the web. In keep with the building analogy, are we talking about a house? A mall? A skyscraper? Do we need elevators? A special HVAC system? Custom architecture? Buildings have an unlimited range of styles, features, and sizes, so do websites.
So, how much does a website cost? I don't know. How much content do you have? Do you need a blog? News? An event calendar? E-Commerce? User login capabilities? Do you need to integrate with third-party services? Other custom features? In some cases, the features an organization needs on their website won't affect the base price very much. In other cases, it drastically affects the price.
I'll be honest: I'd love to tell you how much a website costs, because that means you might hire me to build one for you. But until we have a conversation about exactly what kind of site you have in mind, I run the risk of giving you a quote that's way off base by giving you a number.
But of course, if you really want a price, don't hesitate to contact me. I promise I'll be able to come up with one. ;)