I think milestone contracts have been thoroughly discussed and paying for
anything that didn't work would have to be discussed at the time the
milestone is reached.  There are just too many contingencies when it comes
to client - customer relationships that require all contracts to be
contingency based.  "I would never pay for anything which didn't work" may
be fine for products but not for services.  I have had too many clients send
me production documents that failed even though we all agreed on what to
expect during the testing phase.  The document worked just fine during
testing, so am I to held accountable for the failures during production?
And what about changes and upgrades the customer makes over time, am I to be
held responsible for documents that fail because they were not likewise
updated?  How about the upgrades to the ERP software that may cause these
documents to fail because it longer supports the records you create?  Hence
the need for milestones.

 

The best advice I have read so far is to work with a department supervisor
on a daily or weekly basis to ensure that someone knows exactly what you are
doing and understands what issues you are having.  Until you actually start
working with a client, you can't possibly cover all the contingencies in a
contract.

 

Sincerely,

 

Jason McMahon

8079 Village Drive

Cincinnati, OH  45242-4315

 <mailto:[email protected]> [email protected]

http://gutausse.weebly.com/articles.html

 <http://gutausse.blogspot.com> http://gutausse.blogspot.com

 <http://www.linkedin.com/pub/jason-mcmahon/11/743/51b>
http://www.linkedin.com/pub/jason-mcmahon/11/743/51b

 

  _____  

From: [email protected] [mailto:[email protected]] On Behalf Of
Michael Mattias/LS
Sent: Friday, April 08, 2011 1:03 PM
To: EDI-L
Subject: Re: [EDI-L] <MISC> - To all Contractors out there

 

  

>But, currently, I'm still holding to my "Payment due 30 days after Invoice
>received" (I'd actually prefer Net15, but hey.)

You know, I was on "the other side of the desk" for a good number of years 
before I got into this line of work; that is, I WAS the client.

And as a user, I would never pay for anything which didn't work.. the date 
of invoice is meaningless.

I might pay "some" or even "most" of the invoice before I was sure... but 
until I was sure - either that it works or you will make it work 'real soon 
now' - that last payment is not going in the "outbound mailbox."

That experience is why now that I am on this side of the desk, I will always

work with clients and prospects to come up with "something" which gives both

parties a real incentive to "do it right and get it done on time." 
(Fundamentally I'm just one hell of a guy!).

Michael C. Mattias
Tal Systems Inc.
Racine WI
[email protected] <mailto:mmattias%40talsystems.com> 





[Non-text portions of this message have been removed]



------------------------------------

...
Please use the following Message Identifiers as your subject prefix: <SALES>, 
<JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC>

Job postings are welcome, but for job postings or requests for work: <JOBS> IS 
REQUIRED in the subject line as a prefix.Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/EDI-L/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/EDI-L/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

Reply via email to