<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Your list looks like you pretty much got the bases covered. One
additional thing I have started doing, after a rather hard lesson,
is to specify the site the retainer is for. I had a couple of
clients think that because I was a retainer for their one site, that
they could start using my services for a lot of new sites they were
launching without any additional charges. <br>
<br>
Another good thing is limiting the contacts. Without that, you will
start finding your client having everyone in their organization
contacting you regarding problems, information or suggestions.
That's the reason a lot of larger shops go with the one
contact/contract model. Personally I'm not as strict on that, but
make sure they know you won't become a babysitter to every person
working for them. Even if it's a small company right now, you don't
want to wake up one morning and find out they have grown and you now
have a ton of people on you. That's something else I experienced
years ago when starting out and it was way to much stress to handle.<br>
<pre class="moz-signature" cols="72">Jamie Holly
<a class="moz-txt-link-freetext" href="http://www.intoxination.net">http://www.intoxination.net</a>
<a class="moz-txt-link-freetext" href="http://www.hollyit.net">http://www.hollyit.net</a></pre>
<br>
On 12/11/2010 2:06 PM, Angelina Fabbro wrote:
<blockquote
cite="mid:AANLkTikfsyC0rUWYuHggc1VWRVSyK2JDSDfF2wNsw_5J@mail.gmail.com"
type="cite">Happy Holidays everyone,
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>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. </div>
<div><br>
</div>
<div>Is there anything specific I should do or not do?</div>
<div><br>
</div>
<div>Thank you for you input, I enjoy lurking this list as you're
all invaluable in your advice.</div>
<div><br>
</div>
<div>Best regards,</div>
<div><br>
</div>
<div>- Angelina Fabbro</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
consulting mailing list
<a class="moz-txt-link-abbreviated" href="mailto:consulting@drupal.org">consulting@drupal.org</a>
<a class="moz-txt-link-freetext" href="http://lists.drupal.org/mailman/listinfo/consulting">http://lists.drupal.org/mailman/listinfo/consulting</a>
</pre>
</blockquote>
</body>
</html>