Who knows you might accidentally meet a contact that refers you to someone else who happens to own a huge company that will pay you lots of money to build websites.

I really do think it is smart to define special rates for different kinds of work. If there is some part of the work that is an extra headache to you, charge more. If it detours people from having you do it, you win. If you get paid enough that the headache is worth it, you win.

+ we started our own businesses so that we could follow our passion, if you’re not happy – don’t do it.

But she’s not a web designer. Working with her has been quite a learning process for me, because I naturally just want to please the client, and do it like they want. But what I didn’t realize at first is that she doesn’t really know what she wants in terms of functionality – and so much about the web is exactly that, the functionality. Also usability, accessibility, etc etc.

So I definitely second Liz’s advice to include a collaboration stage of the design/development so that the designer can express what he/she wants visually, and you two can discuss how to make that come to life.

I would also add that when developing someone else’s design, wireframes and mockups are absolutely essential. Not just that they need to simply be in existence, but that they need to be signed off on, approved, carved in stone. Otherwise, the developer ends up pixel-pushing to the designer’s heart’s content. And that is absolutely no fun for the developer.

/2 cents

As a general rule, I don’t code things that other people design, unless they are willing to pay a premium for it, and I specifically tell them why:

• print designers don’t have the experience to know what can/can’t be done on the web
• things take infinitely longer when web-based sizes/grids/dpi are not taken into account
• its boring coding work that you didn’t design

In the early days, i took everything I could get my hands on, because I had no idea if being a freelancer was going to pay the bills or not. I would say, if you need the money REALLY badly, do it. Otherwise, your time could better be spent on work that will actually contribute to your portfolio.

For the first few months of freelancing, I realize that I didn’t really have anything new to contribute to my portfolio, because everything was coding jobs! So I implemented new rates for technical-only projects, which were nearly double my usual rate. That way, if someone was hiring me to do code work only, they would pay double. If they allowed me to take on the create, the rate would remain as before. Incentive to get them to hire you for the whole job ;) And it actually worked. Now I don’t mind the odd code job because it pays quite a bit, which leaves me a cushion for the more creatively inspiring jobs.

Some of the best advice that I think is really really true:
You’ll always get more of the same work that you do. If you keep coding, you’re going to keep getting coding work. If you show logos/identities in your portfolio, you’re probably going to get more of that kind of work. Take on the kind of work that you want to do more of, and you’ll get known for that.

Good luck!