Per Page Pricing
After a needs and requirements meeting I typically go with per-page-pricing when preparing a proposal as most of my clients are small to medium sized businesses and only some have need for a database or e-commerce site which can be a little more “involved”.
I used to calculate the number of hours I thought would go into a project. As an example, I might have included 3 hours of research, 3 or 4 hours assessing the competition, 5 hours designing the main interface, 4 hours coding, a couple hours for manipulating images, formatting the text, testing and so on and so on. However when I compared those hours multiplied by my charge out rate compared to a standard pricing scheme, I was really close almost every time. So I started going with a standard fee for the first page and then charge a per-page cost for the next 10 and if more pages are required, I’d then reduce the per page cost for the following 10 etc.
Of course with this type of pricing there are limits to the number of images allowed on each page as well as the amount of text per page as it could easily get out of hand. If someone wants 20 images on a page, the 15 extra images I work with are charged as an extra using a standard per image charge. The same can be said for excessive text that needs to be formatted on a given page.
This is a rather simplistic explanation and a little more goes into it than what I’ve indicated, but basically I have found it really works – for me anyhow. As a check, I do log the number of hours I put into each project, on specific development levels and compare it to the amount invoiced and of course can adjust my charge out rate per page if I was falling short of my targets.
Sorry – it wasn’t supposed to be this long winded.
|