[consulting] Contract terms for retained services

[Bill Fitzgerald]

In addition to the advice you have already been given, make it very 
clear that they are paying for services at an hourly rate, and that you 
are putting hours towards a deliverable.

Depending on the internal communications within the client's team, the 
same set of wireframes could require vastly different amounts of time to 
produce.

Cheers,

Bill

On 12/11/10 11:06 AM, Angelina Fabbro wrote:
> Happy Holidays everyone,
>
> I am about to be on retainer with a new client during a period where I 
> assist in developing the specification for the project I will be 
> working on. It's a few weeks of research and design with regard to the 
> information architecture, interaction design and user experience. This 
> will be the first time I am on retainer for these activities.
>
> Usually my development contracts are simple; they lay out the 
> specification in detail, the quote I've given along with the design 
> comps for which the spec and quote are approved, and the necessary 
> legal jargon should any discrepancy in expectations arise.
>
> What sort of terms or clauses do you work under while on retainer? How 
> does your contract differ from one tailored to development? My 
> intuition is simply to lay out what the expectations are - response 
> time for emails and phone calls, allocated time for meetings, what to 
> expect as a finished product at the end of the period - wireframes, 
> for example.
>
> Is there anything specific I should do or not do?
>
> Thank you for you input, I enjoy lurking this list as you're all 
> invaluable in your advice.
>
> Best regards,
>
> - Angelina Fabbro
>
>
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20101212/1d0edc6e/attachment.html