|
PureBytes Links
Trading Reference Links
|
Dear Colin,
Leslie's suggestion is a good start, and as a retired lawyer, I would like to
suggest a little more as a bare minimum --- namely, that what you write include
your expectations (what, when, how, who, where, etc.), as detailed as you can
make them, together with what will happen if and when your expectations are not
realized (ie, your remedies upon default). No, I don't think you really need 20
pages, and yes, I do think you need more than 2 sentences. In my book, you need
an agreement that spells out the pluses AND and provides for all the minuses,
with as much detail and clarity as you can provide, cause sure as shootin', fate
will often give you something in between, and then you need something to fall
back on to see what was going on in the minds of the parties when they thought
they were both talking about the same thing.
Sincerely,
Richard
Leslie Walko wrote:
> Colin:
>
> Just write a simple statement to that effect.
> Since the statement only reaffirms industry practice and legal
> precedent, it does not have to be elaborate.
>
> If you really really want to fuss, there is a software consultants
> association, virtually all consulting agencies belong to it that has a
> 20 page blah blah document.
> But, you do not need all that.
> Two sentences will do AND write your payment check upon receipt of
> unprotected code.
>
> Leslie, an ex-consultant.
>
> cwest wrote:
> >
> > Does anyone have an Agreement they'd care to share under which I can engage
> > someone to develop software to which I have title to the source.
> >
> > Thanks in advance
> > Colin West
>
> --
> Regards,
> Leslie Walko
> 610-688-2442
> --
> "Life is a tragedy for those who feel, a comedy for those who think"
> Horace Walpole, 4th earl of Orford, in a letter dated about 1770
|