On Thu, Feb 21, 2008 at 6:35 PM, MB Software Solutions < [EMAIL PROTECTED]> wrote:
> Stephen Russell wrote: > > > >>> > >>> > >> For me, I spec out roughly in text (and perhaps a few non-functioning, > >> static mockup screenshots) along with the cost estimate. They say > 'yea' > >> or 'nea.' > >> > >> > > ------------------------------------------------------------------ > > > > I made that mistake once. > > > > I thought that some $ in a slow time was better then no money. > > > > Wrong answer! In my case at least. > > > > > Where's the flaw in the approach I described? Doesn't outlay tons of > work for nothing. ???? > -------------------------------------------------------------------- How can you present a cost estimate when you really have no real scope as to what they want? I mean I have been presented with a report in Excel and they wanted an application to feed in the data to create it. Do you really know more then 20% of their business? Did you do FabMate this way, and if so how many upgrades had to be done because your knowledge of the industry was lacking? How do you state in your proposal what the measurable problems that currently exist and when your app is delivered how to measure that you have fixed that? -- Stephen Russell Sr. Production Systems Programmer Mimeo.com Memphis TN 901.246-0159 --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
