<p></p>
<p>-- Alex UA</p>
<div class="gmail_quote">On Dec 11, 2010 4:49 PM, "Jamie" <<a href="mailto:intoxination@gmail.com">intoxination@gmail.com</a>> wrote:<br type="attribution">> Your list looks like you pretty much got the bases covered. One <br>
> additional thing I have started doing, after a rather hard lesson, is to <br>> specify the site the retainer is for. I had a couple of clients think <br>> that because I was a retainer for their one site, that they could start <br>
> using my services for a lot of new sites they were launching without any <br>> additional charges.<br>> <br>> Another good thing is limiting the contacts. Without that, you will <br>> start finding your client having everyone in their organization <br>
> contacting you regarding problems, information or suggestions. That's <br>> the reason a lot of larger shops go with the one contact/contract model. <br>> Personally I'm not as strict on that, but make sure they know you won't <br>
> become a babysitter to every person working for them. Even if it's a <br>> small company right now, you don't want to wake up one morning and find <br>> out they have grown and you now have a ton of people on you. That's <br>
> something else I experienced years ago when starting out and it was way <br>> to much stress to handle.<br>> <br>> Jamie Holly<br>> <a href="http://www.intoxination.net">http://www.intoxination.net</a><br>
> <a href="http://www.hollyit.net">http://www.hollyit.net</a><br>> <br>> <br>> On 12/11/2010 2:06 PM, Angelina Fabbro wrote:<br>>> Happy Holidays everyone,<br>>><br>>> I am about to be on retainer with a new client during a period where I <br>
>> assist in developing the specification for the project I will be <br>>> working on. It's a few weeks of research and design with regard to the <br>>> information architecture, interaction design and user experience. This <br>
>> will be the first time I am on retainer for these activities.<br>>><br>>> Usually my development contracts are simple; they lay out the <br>>> specification in detail, the quote I've given along with the design <br>
>> comps for which the spec and quote are approved, and the necessary <br>>> legal jargon should any discrepancy in expectations arise.<br>>><br>>> What sort of terms or clauses do you work under while on retainer? How <br>
>> does your contract differ from one tailored to development? My <br>>> intuition is simply to lay out what the expectations are - response <br>>> time for emails and phone calls, allocated time for meetings, what to <br>
>> expect as a finished product at the end of the period - wireframes, <br>>> for example.<br>>><br>>> Is there anything specific I should do or not do?<br>>><br>>> Thank you for you input, I enjoy lurking this list as you're all <br>
>> invaluable in your advice.<br>>><br>>> Best regards,<br>>><br>>> - Angelina Fabbro<br>>><br>>><br>>> _______________________________________________<br>>> consulting mailing list<br>
>> <a href="mailto:consulting@drupal.org">consulting@drupal.org</a><br>>> <a href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a><br></div>