Exactly, Hal. I did my last project using FB3 with your MVC adoption. We were doing the prototype for quite a long time and spend many, many ideas to it - but so did the client. My partner always said: "Now it was enough prototyping - we will have to start coding or the client wants to have more and more features". In fact I have been aware of that situation, but in the end the client wanted to PAY MORE for his application, because he saw his prototype growing - he really got a feeling about the scope of the project.
Paul -----Original Message----- From: hal helms [mailto:[EMAIL PROTECTED]] Sent: Dienstag, 16. April 2002 19:10 To: [EMAIL PROTECTED] Subject: RE: Conversations follow on ... Jeff, I often do the prototype on a fixed budget. I'm not trying to make money off of prototypes and having the client pay for them ensures they have some skin in the game, so to speak. You might think, "Gee, what if the client takes forever on the prototype?" I thought so, anyway, at first, but found that clients are OVEReager to get done with prototyping and get on with the code, so it doesn't happen very often. This means that on some prototypes, I'll lose money and on others, I'll make money. That's OK with me; I just want to get the process started and don't demand of myself that I get paid for every hour of work. Anyway, that's how I handle it. Hal -----Original Message----- From: Jeff Chastain [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 16, 2002 12:02 PM To: [EMAIL PROTECTED] Subject: RE: Conversations follow on ... Troy, It is always my choice, no matter what anybody says ... its called freedom of choice ;-> My question is more of a what are other people doing? I am not asking how much you charge, just how you base your charges. Is a prototype a fixed cost? or does the cost grow as the prototype grows? On a slightly different subject ... the spreadsheet idea from Steve was interesting, but how do you account for the time/cost spent outside of coding fuses? What about the mind mapping process or the actual development of the database? There are plenty of developers out there, so how do you do it? I am currently inside of a corporate team with salary, but consulting could be interesting some day - so I am interested in hearing from both fronts. Thanks -- Jeff ---------- Original Message ---------------------------------- From: Troy Murray <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] Date: Tue, 16 Apr 2002 11:38:24 -0400 >Jeff, > > I think that is just up to you. Since the majority of the time that >you spend will probably be on the prototype, I would say price >accordingly. You could do an hourly or per page estimate. > >-T > >-----Original Message----- >From: Jeff Chastain [mailto:[EMAIL PROTECTED]] >Sent: Tuesday, April 16, 2002 10:10 AM >To: [EMAIL PROTECTED] >Subject: Conversations follow on ... > > >In the conversations newsletter that just came out, Steve and Hal talked >mostly about pricing the design work of the fuses etc. How do people >handle the pricing of the prototype though? Is the prototype a cost >per time basis, cost per page, or is there a fixed cost for the >prototype? Is there any kind of agreement up front that says the >prototype will cost XXXX or is the cost of the prototype flexible >(because come clients can draw it out forever, versus some may sign off >on it right away?) > >Thanks >Jeff > > > > ==^================================================================ This email was sent to: [email protected] EASY UNSUBSCRIBE click here: http://topica.com/u/?bUrFMa.bV0Kx9 Or send an email to: [EMAIL PROTECTED] T O P I C A -- Register now to manage your mail! http://www.topica.com/partner/tag02/register ==^================================================================
