Explain the process. There are actually two separate contracts. One is for the prototype, one is for the application. They are separate. Once we got passed the wireframe (free) We sat down, I gave them an approximate cost for the prototype. I told them should they want to add things, this is the time to do it, and it will end up costing them less in the long run. Educated them on 70% failure rates, and how if they went we the developer who just quoted them a flat rate, they could very well be a part of that statistic. Once we came to the end of the prototype, they saw how huge the application they wanted was going to be and backed out. hehe Now that I think about it, may be best not to listen to me all the time :)
Tim -----Original Message----- From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] Sent: Saturday, June 08, 2002 3:47 PM To: [EMAIL PROTECTED] Subject: Re: FLiP and Prototyping Most clients though want to know what the price of the contract will be before anything is started. How do you structure your contracts to allow you to do that and still get the contract over someone who gives a fixed rate right away? If you don't mind me asking. > I would go so far as to say that you shouldn't tell them how long it will > take until you have completed the prototype, and know exactly what you have > to do. The last contract work I did (also only about the 2nd big one I had > done solo) fell apart because the client wasn't prepared for either the time > or the money involved. The client didn't loose out and neither did I. I > got paid for the prototype, which the client got to keep, and we didn't get > into the big circle of scope creep I normally would have associated with a > project like this, because we both knew from the prototype what would be > involved. During the whole process I made sure to tell the client, this is > only the HTML representation of what this project will look like when > complete, and they understood that the coding was going to take some time. > Too bad the contract went away, but that's better then doing a bunch of work > and not getting paid, or having continuous requests for additions and > changes once you have the application already half done, right? > > Tim > > -----Original Message----- > From: John Jonathan Kopanas [mailto:[EMAIL PROTECTED]] > Sent: Saturday, June 08, 2002 1:59 PM > To: [EMAIL PROTECTED] > Subject: Re: FLiP and Prototyping > > > Now the problem that I get with clients showing them the prototype is that > they are happy with it and then say ok now put it up, I'll give you till > tomorrow. Personally I just think within the contract you specify once the > prototype is signed off it takes x weeks to code it. Any other suggestions? > > > > I am creating Montreal's CFUG website right now and this is the first > > > project I am using the FLiP process. I have done the wireframe and now > I am > > > on to the prototype. One of the people I work with who does the HTML > > > integration always tells me I should program only after having the first > > > template because coding HTML takes so long compared to programming. > What do > > > you say to a person like that? > > > > Race them. Say: "Let's pick one template, you build the CFML and the > Database > > THEN build the HTML interface that we will 'slap' on, I'll build just the > HTML. > > Whoever finishes first wins and we'll do it that way." > > > > Then tell them that you could show both versions to the client and 99% of > the > > time the client won't see the difference. But will understand the > application > > enough to tell you they want something slightly different. > > > > Steve Nelson > > > > > > > > > > ==^================================================================ 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 ==^================================================================
