Ted Roche wrote:
> On 6/29/07, MB Software Solutions <vfpmcp AT mbsoftwaresolutions .DOT com> wrote:
>
>
>> I look at it this way: how long am I going to be tied up with this job
>> if I get it, given the scope that has been defined? Let's say it's 2
>> months....then I decide "Ok, it I want to bill $xxxxx this year, that
>> means I should bid 2/12 of $xxxxx for the job. Perhaps a bit more to
>> pad it for a little scope creep (that I would allow as a courtesy...but
>> not to be taken advantage of). Does this logic have any merit or is it
>> crazy too?
>>
>
> A little of both. I have had little jobs that turned into 2 and 3-year
> engagements with clients. And big jobs that turned out to be things
> that could be cranked out pretty quickly. For me, there's the entire
> issue of who is assuming risk on the job, and how that risk is shared.
> Rather than make my best estimate, add in a profit margin, and give
> the client a fixed bid, I prefer to offer a time-and-materials
> contract so I can deliver the client the system he or she needs and
> they can make the spending decisions on what they are willing to pay
> for.
>
> But that is another long religious discussion.
>
>
That's why I never work anymore without a clearly defined contract
spelling out exactly what will be delivered...so that there's no "gray
area" where they say "you owe me this yet" when I really don't.
--
Michael J. Babcock, MCP
MB Software Solutions, LLC
http://mbsoftwaresolutions.com
http://fabmate.com
"Work smarter, not harder, with MBSS custom software solutions!"
©2007 MB Software Solutions |
