[AccessD] Project Official Start

Just say no.  However if you can't ...

>if the client cannot approve it, he has to specify in writing exactly
>what is missing according to the specs

This is a big - big deal here.  Your having to go back to the specs and
rethink everything is a bummer - time waster - and a crock.

I usually ask for this each step of the way - as I stage my projects.
I define what's released and ready for them to test each step of
the way - they have 1 week to test and submit a list of problems.

I'm usually lenient on letting them add stuff until the final submission.
Then
their list becomes IT!!!! and I work through all the items.

Be sure to mark new and revised requirements as such and put on a change
order that is outside the cost and time deadline.

Document each step thoroughly and keep 3 1/2 copies at least.

Also make sure you're getting paid in stages.

After all this, they will still try to screw you.  Be afraid.  Be very
afraid.





----- Original Message ----- 
From: "Gustav Brock" <gustav at cactus.dk>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Wednesday, October 01, 2003 3:04 AM
Subject: Re: [AccessD] Project Official Start


> Hi Hadyn
>
> This "yes" is nothing more than a "Declaration of Intention" which on
> its own has some value though not being an agreement.
>
> I would not sign or negotiate anything before specs are settled as
> these are the foundation for any further discussion. Whether you or
> the client carries the cost for writing the specs doesn't matter.
>
> Then, don't accept 8%. Where does this figure come from? If you can't
> avoid it, go for 3% for each 14 days so you can reach a compromise at
> about 5% each 10 days (which, by the way, is just as arbitrary as 3%
> or 8% or 1 or 2 weeks). Further, only major missing items from the
> specs (do include a list of these in the final agreement) should
> release this penalty, not minor tweaks as correction of spelling
> errors in menu items and the like.
>
> Also, have a firm agreement on how long time the client can use for
> approving your app after you have installed a revised version. And, if
> the client cannot approve it, he has to specify in writing exactly
> what is missing according to the specs. If he delays this action, the
> same amount of days are added to your 11 weeks up to a maximum of,
> say, one week per approval after which your app will be regarded as
> approved whether the client has signed or not.
>
> /gustav
>
>
> > When do you say a project has started?  I have a client that has said
'Yes'
> > to a project, but has not signed off the spec, or the quote, and now
wants
> > to negotiate penalty clauses before they sign (if we don't deliver on
time
> > to the proposed end date (11 weeks from start of project) they reduce
total
> > payment by 8% for each full week we are late).  I have managed to get
them
> > to exclude Acts of God etc, and have suggested that if they are to blame
for
> > the delay we should be allowed to charge them for the extra time.
>
> > Any thoughts?
>
> > Kind regards
> > Hadyn
>
> _______________________________________________
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com