5 Ways To Scare Your Web Dev Clients Away
Posted on 22. Oct, 2009 by Web Design in Web Development
This post has been kindly guest written. Sue Varty is a freelance technical and corporate writer who specializes in e-book creation, user guides, training manuals, web copy and last-minute proposal preparation. Sue has worked for IBM, Compuware and Franklin Templeton Investments. Contact her at www.wordtree.ca and ask about her web designer and web developer partnership program.
1. Speak “tech” all the time.
Some folks may find it impressive that you know the ins and out of UNIX and how your last open source coding project attracted media attention, but the majority do not. Especially when acronyms start spewing forth with articulated speed. Keep in mind that executives are employed to keep you employed and need to understand your ideas to communicate them to stakeholders and customers. One way to minimize “tech” talk is to include the following words into each technical statement: We are using [technology/programming language] to enhance [a specific part] of our business. YOU know why you chose a specific technology or solution – it might not be obvious to others. Make it obvious – relate it to the bottom line and people will start respecting your statements instead of avoiding you in the lunch room.
2. Pitch unrealistic media.
Change is all around you – but often last in the IT department. If your client has thousands of dollars invested in a specific technology, rocking the boat is a dangerous proposition. Pick your battles wisely and create a one-page new media proposal; setting up some expectations up front for future web development is always a good thing. Imagine the site or development project three months from the time you are engaged and spell out the media or technology you will need. This will keep surprises to a minimum. One-page proposals are short and specific to get your concerns across.
3. Don’t provide case studies.
Why do people go with your services? What unique coding/customized solutions did you provide? Lay it on the table in a case study format with powerful testimonials. Create a case study (online/or hard copy) and a matching referral “sheet”. Only send out the referral sheet with names and contact information if they need more information. Make sure that you put a case study request into the current proposal so you can build another one later.
4. Price yourself out of their reach.
Find out their web development budget ahead of time. Do they have the funds for what you typically charge? Asking is daunting – especially with a new client who may have started something and it’s going all wrong. Don’t tell them you can fix it. Tell them you can fix it for X amount of dollars. Be as up-front as possible and they will be more comfortable later on in the process. Be prepared to walk away or offer a gap analysis for a fixed fee.
5. Design something they can’t maintain.
You made it through the project with your sanity intact. Now it’s time to cut the cord. Do you have the resources to help your client maintain the site? Ensure that these post-project resources are built into your contract from the beginning. Larger firms can usually provide support and maintenance but if you’re a “lone ranger” you want to avoid those late night calls for help. Set yourself up for success with an exit plan before you begin the project.
5.5 Twitter Bonus Twips:
From @taffer
~ If your page doesn’t pass validation (validator.w3.org) you’re doing it wrong. Even if the client says “IE6 only”.
~ Designing With Web Standards (www.zeldman.com) is my favorite web dev book; 3rd edition coming, apparently.
16 Responses to “5 Ways To Scare Your Web Dev Clients Away”
Leave a Reply
Loading ...
Milan Davidovic
22. Oct, 2009
Good points made in this one, Sue. For a <140 char version, could we say something like…
Web dev clients fear
- what they don't understand (or believe).
- what they can't afford.
Solona Armstrong
22. Oct, 2009
I agree. That’s what I was scrolling down to type. Not addressing clients’ internet fears. If they’re not comfortable making payments online, they will likely not be comfortable accepting them either, for example.
Behrouz
22. Oct, 2009
oooh!!!
Speak “tech” all the time…………………………………..
thank for the post
Chris Morata
22. Oct, 2009
Nice post. I would definitely have to agree with the “speaking tech too much” point. I’ve fallen into that trap a couple times and have almost lost a couple clients.
Andy
22. Oct, 2009
Love the website!
James
22. Oct, 2009
Tell them you are called Derek but now you wish to revert back to Delia, so would they mind possibly waiting a few days for a quote while you sort it out.
Andy
22. Oct, 2009
Quality, that would scare me right off.
Genevieve
22. Oct, 2009
All good points. I find that in the case of #4, sometimes scaring them away is a good thing. Clients who aren’t up to paying your prices or want you to come down in price significantly, can often be headache clients if you end up taking them on (don’t do it!).
Rory
24. Oct, 2009
i agree, dont sell your self short (or poor)
Phil
26. Oct, 2009
That is very good advice Genevieve. These kinds of customers also tend to want to be able to make unlimited changes without paying, or you finalise a design, build the site and then they don’t like it!
Valerie
22. Oct, 2009
5 excellent points. Many thanks for the post.
designfollow
22. Oct, 2009
thanks for this tips.
Marty Sullens
22. Oct, 2009
Great tips, every designer should really follow these..
Trust me I’ve been there..
Thad
23. Oct, 2009
I don’t agree with last Twitter statement:
“If your page doesn’t pass validation (validator.w3.org) you’re doing it wrong. Even if the client says “IE6 only”.”
Validation is important but if you have a good reason for breaking a rule, you should do it.
designium
23. Oct, 2009
ROFL nice tips
ehhehe
irma
14. Jul, 2010
Great insights. I talk in code sometimes to my detriment. A helpful reminder.