Is your question about scoping ultimately for pricing? A single HTML page could be really easy or take some time, depending on the PSD. I'd guess it could be a

Is your question about scoping ultimately for pricing? A single HTML page could be really easy or take some time, depending on the PSD. I'd guess it could be anywhere from 1 hours to 10 hours. If you're still learning I could see 30 if it's a particularly complex page, although that's a lot of time to spend on a single page. I advise against pricing per hour and instead quote a fixed price. There's lots of reasons why, just Google "why don't price hourly" and you'll see. I'd quote them a value and get a feel for how they react. For instance, you could suggest $1000. They might agree. They might say no, and counter-suggest $600. Or if they don't have a counter offer, you can always give them a discount. Again, just quote a price you're OK with, even if it takes you 30 hours, and then once you have it, you're incented to work efficiently (because you're not billing per hour, but per job). Your effective hourly rate on this job might end up at $250/hr, for all you know, if you work efficiently. Also, PSD to HTML is a pretty commoditized job. You're not really creating value, just being a code monkey. In fact it's not consulting, just contracting. So I don't really suggest you take those jobs on a regular basis, if you want to have pricing power. That kind of job is has plenty of competition from Eastern Europe, Asia, Africa, and other places where the cost of living is really low, and it's a race to the bottom.