[CLUE-Talk] Contract Help (website development)

[Jeffery Cann]

Jed,

I have done a number of websites on a contract basis for the past 4 years.  
Here's my advice:

+ Use a contract that spells out the features, pages, and graphics included in 
the project.  You don't need to put in minutae, but at least list all of the 
site pages and a general idea of their content.  List other features, such as 
navigation, graphics, etc.

Don't forget to include what information you expect to receive from your 
client (see marketing notes below).

Also, cap the support limit.  Depending on the project, I will allow a certain 
time period for text changes or fixing bugs.  After the period, any other 
changes are charged per hour.  Don't forget support terms, as well.

I like to call the contract a proposal or statement of work so all parties are 
not as squeamish about signing.  But, I do make all parties sign, so it 
really is a contract (legally).  I have some examples which I'll forward to 
you directly.   Don't forget that the contract protects you and the business 
owner.  Most owners I have dealt with do not have a problem signing a 
document because they understand the point.  If someone does question it, 
then you can explain that the document simply states the terms of the 
business agreement to set the expectations for the project.  If they still 
don't want to sign it (which has never happened to me), I would wonder where 
their true intent lies.

+ Get the feature list down on paper, preferably in your contract.  This is 
important to prevent feature creep.  Feature creep will always happen, 
especially after the person who hires you sees the prototype and starts 
thinking about it.

+ Try to be flexible, but don't answer questions on short notice.  My standard 
response to a feature request is 'let me give it some thought and get back to 
you tomorrow'.  This sounds like a put off, but I have learned that before I 
set an expectation, I need to be sure I can meet it.  Sometimes this means 
research into how I will create the feature.

+ Hire out for graphics when / if you can.  Unless you are trained, your 
graphics with GIMP will look like mine:  quasi-professional and boring.  If 
the budget allows, contact local design / art schools for students willing to 
work for $20 an hour.

+ Don't forget a marketing plan.  How will you market the site?  Who is the 
audience?  How does the audience affect the design?  These are things that 
should come from the owner.  Often, the business owner will want something in 
return for the development costs.  Make sure you know his goals and put them 
in the proposal.  If you are not on the same page, bad things will happen.

+ In terms of rates.  I don't like to present an hourly rate for a project to 
the client.  Typically, I will determine how many hours I think it will take 
me and then multiple by my minimum hourly rate.  I charge different rates 
depending on the work.  Static web pages and SA work cost less than 
development.  I then present the costs for each component of the project.  I 
list some as required and others as optional.  This gives the client some 
flexiblity to change the bill by adding or removing features, rather than 
dropping your hourly rate.  There are times when a client won't pay me my 
minimum rate and when this happens, I don't do the job.  There's nothing 
worse than diluting your hourly rate because you'll begin to resent the 
client and your work will suffer.

HTH - Feel free to ask more questions based on my overview.

Jeff


On Sunday 08 December 2002 09:27 am, Jed S. Baer wrote:
> Hi Folks.
>
> I have the opportunity to submit an estimate for doing website
> development. I could use a little advice from folks who are doing this
> sort of stuff, regarding typical hourly rates, etc.
>
> The site is a mix of static/dynamic pages. The (currently) two dynamic
> areas are news items (posted by the owner), and a classified ad section.
> There might be voting-booth section too. There will likely be streaming
> audio/video, although that might be added later. Some areas of the site
> will require registration, and the registration will have to feed a
> confirmed opt-in mailing list(s). Other activities, such as choosing a
> hosting company, moving DNS, and setting up the mailing list(s) will be
> included.
>
> Since the only stuff like this I've done so far has been either handled
> very informally, or on a volunteer basis (and I haven't done a lot of it),
> any advice on how to spec/cost it out would be appreciated. Since the guy
> has already called me once at 9:30PM, I need some language in the bid for
> "after hours support". Any pointers to boilerplate statements of work etc.
> will be much appreciated.
>
> There's a graphics development component which might wind up being farmed
> out, depending upon how far I can get with it using The GIMP. One piece of
> that will be that I'll need to export the logo to a format suitable for
> providing to a T-Shirt printing company. If anyone ("Lose FAT Now!") has
> any tips on getting that done, that'd be great. Referals for professional
> graphic designers who specialize in marketing/logos would be helpful as
> well.
>
> Thanks for your help here, folks.
> jed

-- 
    planet earth (tm)
http://jefferycann.com/