"I don't care about the code!"

I met with a local client yesterday, we're working on our first project together. While explaining why I recommended we move in a certain direction, he stopped me and said "I don't care about the code! I just want results". He went on to explain that he wasn't interested in hearing anything other than wether or not I could make the website work the way he wanted it to work. (and yes, of course I can) He didn't care what it would cost, he just wanted the work done ASAP.

I have found that a lot of clients share the same feelings on this matter. (It is however rare that they don't care about the cost.) I feel that I am doing a dis-service to my clients if I don't present them with the best options, and let them pick the one they are most comfortable with. However it seems that is not always the best approach. It really depends on the client I have found. Some like to be kept in the loop on everythings, others just want to be left alone and want me to make all the choices. They just want the website delivered as requested period, end of story.

I like working with both types of clients, it keeps me on my toes. Even though I feel more pressure when making all the choices with minimal client input. It's all good though, I'm happy to have the business and I'm thrilled to free to do whatever I want on the creative/technical side. (though I do require client buy-in at crital points, so that I avoid having to do a major rework of anything)

I love working with clients (I was born a people person). Every client has a diffrent perspective and diffrent style of working with a developer. I love the variey. Here's a info graphic that shows a few of the diffrent types of clients that freelancer come across during thier interactions with clients.

How To Identify and Deal With Different Types Of Clients - 15 Different Types of Clients

What I have found is that you have to treat each client diffrently than the last. Life would be easier at times for both the client and freelancer if there was a cookie cutter approach to each interaction.

The best thing I know to do is to draw on past experiences so that you can get head of problems before they even start. One thing to remember is that "No" isn't a bad word, and don't write a line of code until your contract has been signed.

Until Next Time...