Website Technical Specification
Document - Why Every Web Designer Should Use One |
|
|
|
|
| Today I had the lovely pleasure
of experiencing something that drives me absolutely up the
wall. Trying to get usernames and passwords from a new client.
If ever you've been in this position before as a freelance
web developer, you'll know exactly what I'm talking about.
You've just picked up a new client, who has asked you, or
literally begged you, to help them clean up someone elses
mess. By someone else, I mean another designer or web developer
who has let them down. This, believe it or not, is quite common,
and something I'm certainly very wary of.
Remember, if ever you sit down with a client and they spend
the entire meeting, whinging about their previous web developer,
chances are the blame can be shifted 50/50. It's rarely always
the fault of the developer. It's usually a case of poor communication
between both parties. But anyway, I'm getting off topic, this
isn't what I wanted to cover in this article.
What I did want to cover, more importantly is one contract
that is grossly under utilized by many web developers world
wide. And that document is, what I refer to as a "website
technical specification document". Take a look at the
video below, and remember, this document template is available
in my web design business startup kit which can be purchased
HERE
Best of luck to you.
John
Share This Article With Friends
If you are a freelance
web developer or designer and you are looking to start your
own business, or improve on your existing business, then click
HERE.
|
| |
