Quote:
|
Originally Posted by orfeo
I find per page charging very-very wrong. Issues of complexity arise all the time. It's not the same to build a site that has one standard layout through out 20 pages and another one with different designs per section or other customizations.
|
I understand what you are saying, however to say the per-page pricing is very-very wrong is wrong. It may not work for you but at least for me, it can simplify the process of estimating and may work for others.
I can appreciate the complexity and additional labour when not using the exact design layout throughout the entire site. This can easily be built into the cost. So if there are design mods on inside pages, this can be accounted for as an "extra".
Whether someone build an estimate around an hourly rate and end up at a cost of say $3000 for a basic site or you do a per-page estimate and end up roughly at the same price, I don't see that it really matters.
It's clear when a client wants 10 pages, but also is somewhat interested in a flash intro or banner, the this can be added in as an "extra" or "suggested service" alowing the client to choose. The same goes for any database work - it is added in as an extra.
I find that after taking note of the client's needs and requirements it's can also allow them to control their budget, scaling back or adding pages if necessary.
I've done both hourly and per page estimating but find per page much easier and can almost be done on the spot at a client meeting if the site needs are simple. Of course per-page pricing doesn't work when including a database,flash design, or even a "gallery" where a designer works with 100 imagesor more. These are priced separately.
I also include language in our contract which allows us to re-evaluation of an estimate should the needs or requirements change.