[Catalyst]

An example:

A client hires you to add some Google Maps integration to their website. You've never used the GMap API so you have to learn it as you go. The job ends up taking 5 hours total, but you figure you could have done it in 2 if you already knew Google Maps.

So would you charge for 5 hours, or for 2 hours, or something in the middle?

If you were never going to use Google Maps again on a project would that make a difference?

[TJSingleton]

I think this is going to depend on the situation. For instance if you were hired as a Google map's specialist, I would not charge for the learning. If you were hired for something else and Google maps was no specified, I would charge a reasonable amount of time for the learning. Possibly I would charge a reduced rate for that development time. For instance, if my hourly rate was $1.00/hr, I might only charge $0.75 for the time where I am less skilled.

[marcamos]

In the scenario you describe, I think I would meet them half-way, charging only for 3.5 hours.

[James Mitchell]

I'm not so sure I'd do a combination of TJ and Marc's suggestions. Say a reduced rate and more hours. It also might all come down to what you *sold* them initially as well.

[jameson]

I guess it depends on the situation, but normally I don't charge anything for learning.. especially if it's something I feel like I should already know. For example, I start building a contact form, decide it's about time I start putting in some more Ajaxy form validation, and end up spending four hours researching it and figuring out how to do it. To me, I did that for myself more than for the client, so I wouldn't charge them.

On the other hand, if the client gives me a crazy request, way outside of the original scope of the project, I'll definitely charge for the time it takes me to do it, learning or not.

[Rob Kaper]

Allowance for "learning time" (or simply research) should be included in your standard rates, unless the research comprises a disproportionate amount of time for the given project and is very specific to that project.

For just a simple map, five hours seems like a lot, so your client could suspect you don't have a lot of expertise with Google Maps. Then again, if you can sell them those five hours, you should. There's nothing wrong with that.

[Bullzeye Design]

I dont typically tell the client my number of "hours" spent on the project... rather I break it down into line items...

research of google maps $50.00
integration of maps into website $70.00
testing $20.00, etc. etc.

But I suppose in my head I do tally the amount of hours and charge according to that. Usually it's just a standard price I set up front, taking into account I may get snagged up with a problem or something else slows me down. Some projects I'm extremely profitable, others I just about break even.

[Locksmithcharlottenc]

If you were hired for something else and Google maps was no specified, I would charge a reasonable amount of time for the learning.

[iPhoneUnlock]

If you were hired for something else and Google maps was no specified, I would charge a reasonable amount of time for the learning. Possibly I would charge a reduced rate for that development time.