Hey guys I'm having a problem here, on giving out price quotes on larger online stores the customer always wants a set price, and I think I'm losing a lot of sales is there any one here that has a lot of management experience, or production experience on how this type of stuff is done? Like do typically web companies prototype stuff, or just always give a set price for a online store? I have caught my self in to having way more hours into something then what I should. Is there any books out there that can explain this stuff?
Make up a price list: * $500 Template * $50 each dynamic form * $500 user registration system * $1000 shopping cart, custom You should also adjust the pricing based on the job and how long you think it'll take you. Peace,
It is very much a case of breaking down the requirements into modules and then costing for each component. Generally there are synegies but by ignoring these it automatically includes a contingency fund (ie a registration system and shopping cart will both have a db and so there is only 1 block of time to create the db, db user, connectionstring etc)
I think AstarothSolutions has it right. If you're putting together a price quote, then work out the required modules and a price estimate for each part. If the client wants a detailed design document then they should pay for that. The detailed design document would provide enough detail to allow another programmer to build your program.