Often it can be difficult working with older folks, older generations, small businesses, friends, or family as they might have a skewed perception of how web technology works in comparison to print media etc. You might be working with someone who is used to Microsoft Publisher, Quark, Micrsoft Frontpage, etc and cannot grasp web concepts such as CSS, XHTML, tableless designs, dynamic web programming etc and any possible limitations or differences in design and functionality. .... compared to what they're used to, because of this they might be terribly fussy and particular.

If you have a fussy client like this who sighs at your every suggestion, draft, or mockup design whether it be static pages, a custom script or a common CMS then it is time to seriously talk to them about it.

Working with friends, family.. or fussy clients can be very difficult. It's time to be honest with them!

You should explain exactly what your concerns are,,, such as differences between print and web, requirements of web standards/compliance, usability, dynamic navigation, functionality to make the site interactive and how it all works in a way they understand and why it creates differences that they do not prefer or understand. You should explain and demonstrate how the differences are only that, differences and not unproductive or useless but rather that they are necessarily and required. Even limitations or consequences of doing something the right way and in a productive way should be explained to cover why the limitation exists and why but what is gained by it or what it allows for.

"A dynamic web standards compliant website that will be successful and serve it's purpose is put together very differently then what you might be used to, you will have a fixed width layout for this purpose......... you will have a line break here for this purpose............ you will have a visual verification code of your contact page for this reason........ you cannot use Microsoft Frontpage anymore to edit your website for this reason....... " etc. Let your client know that there are a lot of requirements and you will not/cannot necessarily make a layout/functionality as perfect match of their draft or desires and why. There will be deviations, and unfortunately they will have to make room for that and allow you to ensure the site is built right.

If they cannot accept this and think the task is simple or specific requirements can be met, then you may want to let them know that you cannot do the project and let them struggle with someone else.... if they want exactly what they want even with all the consequences (that they probably do not understand) then so be it. Surely no one else will do as good of a job as you.... even reading articles like this one and consideration for their projects and trying to get feedback on how to handle situations like and how to handle it is a fine example of how you have the clients best interests on your plate, but if they can't appreciate your services and have confidence in letting you do your job, and you cannot gain their confidence, DON'T DO IT!

Settle the details first, proceed only once agreed on what the final product will look like and it's functionality, otherwise, potentially you will pay a significant price with the hassle of ongoing support with a client that really cannot be helped. If they are fixed in their ways, let someone else cater to them. The only exception would be of course, if the price of the project justifies the aggravation.... but remember it is your services and reputation on the line and if you cannot satisfy this client, chances are they won't be proclaiming themselves as ignorant, instead they will tell everyone they know how incompetent that you are.

Always set expectations before starting a project, provide website design drafts and demonstrations of website functionality to ensure you are on the same page and mutually agree to the direction and goals of the project and what the final product will be,,,, do this in steps and your financial arrangements should also be based on steps. A basic roadmap would be to perform work and bill for the work in cycles such as 1. Planning 2. Drafts/demos 3. Final Product , this allows you to end the project at any of those stages if it is not working out.

If you need a good starting point for implementing good business practices for web design related activities, I highly recommend the Sitepoint Web Design Business Kit. http://www.sitepoint.com/books/freelance1/