Contracts

[sharkey]

As im doing my first client work just now i was wondering what kind of things to include in the contracts i hope you's get what i mean. As i want to come over to the client as professional looking as possible.

[buntine]

You havent given us enough information. There are alot of variables involved when discussing this subject.

Please, give us some more precise and/or thorough details. ;)

Regards,
Andrew Buntine.

[sharkey]

I dont know how to really explain it but like for example when maintaining the site youve created do you sign a contract saying you will do it for "x" amount of time.

Sorry i cant explain it better.

[Sam]

I usually charge for maintainence based on who's fault it is. If I made a mistake in my original design that is causing the need for maintainence, I fix the problem for free. If the client broken something/needs something updated, I charge by the hour

[sharkey]

Hey kool that clears it up a bit for me thanks.

[crh3675]

Make sure to ALWAYS include informatin about Browers, Fonts and Colors. Especially about what browsers you do not code for (NS4.x) Also be sure to have an approval process so you don't get screwed by a client that likes to take their time. But most importantly, you need a clause that states "All changes that remain outside the scope of the contract remain billable at our standard hourly rate."

Many developers also forget to compensate for their "conceptual" time and B.S. time within a project. A good rule is to add 30% to your final "coding hours" cost to cover the "overhead" expenses of each project.

One more important item that we include is:

If Client at any time requests to deploy the website (also know as "going live") prior to the completion of the project, Client will pay the remaining balance due for the project within 30 days of deployment date. Developer will complete all work as contractually obligated when Client requests devloper to resume development. Client can request to go live at any time by following your approval process.