Most of the time the project took too long and we ended up with $1/hour.
I know just how that goes! (only, I'm making about 40 cents an hour on this project right now, and expect to be down to 30 before finishing this up...

;-)) (Don't you love those quick $200 an hour script requests? :-D)
What you should do is either charge hourly based on going rates in your area and your amount of expertise (because a beginner will take a lot longer than someone experienced, and that would through off your prices...) The other way is to guess how long it will take you to complete the project and then charge a set price based on that...Beware, however....make sure you know the entire project and everything involved when bidding using that last way...Like I said...I won a big php/mysql/eccommerce project for $1,500 that I thought would take me about 20 days.....That was in the beginning of March!!!!!! :-S....My client's putting up with me, only because he knows (and I do too, now!) that this is worth well over $15,000...But it's costing me big time....I had to pay someone else $1,200 just for a piece of it, because it was well over my head...The reason it's taking me so long is because I "assumed" I knew what I was bidding on

...It wasn't really my fault...everyone else assumed the same--it was a safe assumption, however, it was still my fault because I didn't check into it as carefully as I should have...
Just be carefull, know what he can pay, know how long it will take you and how much you need to make to break even, and how much leverage you have over the other bidders....
Rick
-----------------------------------------------------------
RISTMO Designs
Arab Church
Reference Guides