It's time for the web development process to change again.

Years ago, the web development process started with designers making comps which developers had to make into sites. Now most agencies start with information architects (also called experience planners, usability engineers or anthropologists) building requirements and translating them into wireframes that designers and developers can then take to realize into functional sites. This is a better situation than it once was, but still not ideal. Now the designer, user and information architect have a voice, but developers are still left to an implementation role.

There are two reasons this is less than ideal. One is that developers are often on the cusp of innovation in functionality. Where designers focus on the appearance, and information architects insure sites are navigable and usable, developers look for ways to enhance functionality.

Perhaps more importantly, though, is the possibility to get insight into what already exists from developers. If functionality decisions are made exclusively by information architects you'll likely get exactly what you asked for. If you involve developers in the discussion you might get information about systems that are already available that closely address your requirements. Particularly when these options are open source you'll get the option to use a free system that is close to what you wanted out of the box at no cost. Then you'll be able to assess whether customization to go the final mile is worth it or not.

You may come to realize that you'd rather have something similar to what you originally asked for if it means big savings and quicker development time.