Can you imagine walking onto a car lot and asking the salesman "how much for a car?" The salesman would naturally ask, "well what type of car, what is it that you want? You tell him "just give me a ballpark?" So the salesman says our used cars start as low as $500 and our high end cars for as much as $100,000. Now you are not going to walk away with a clear idea of how much you're going to spend until you tell the salesman what type of car you want, approximately how much you're wanting to spend and if you're looking for a beater, an SUV, a luxury car or what.
When it comes to developing a web application or complex website, a 30 minute conversation about what you're trying to accomplish is not going to be enough information to get a quote. If you insist on a price ie "We're meeting tommorrow and need to know how much this will be, just a ballpark", your account manager is going to have to ballpark extremely high to include the unknowns. Your constituents might faint!
The point that I'm trying to make is that the more programming feature "unknowns" there are when you try and get a price, the more that project is ultimately going to cost AND you're going to end up paying for project analysis anyway.
Lets take a look at a better scenario. Lets go ahead and hire the development firm to help us determine the project needs and then deliver both a blueprint of what the site will have and include, and a price quote for doing the work. Much like building a house, isn't it?
The project manager and development team can help management address all the site needs in the most efficient and effective way. Keep in mind, they do this everyday and can point out what is absolutely necessary, what can be added later, what might be an expensive add-on that's not absolutely needed or what can be substituted that's more efficient. By the time you have a quote in your hands, everything has been fleshed out, you have your blueprint and you are paying according to a detailed outline. In other words, you'll be paying for exactly what you're getting.
A side benefit too, wouldn't you rather scrap the dev team (if you didn't have confidence in them) part way through analysis rather than part way through development. Yikes! I guarantee you, you will know once you're working on analysis if this team has what it takes to do your project. If you do get through analysis with this group, by golly you will have found your dev team and if you get the go ahead on the detailed site outline and costs you'll be confident, part of the project cost is already paid and you will be well on your way!