This is one of the reasons that referring to the prototype as the "front end" to the client can help. Once you've agreed on the front end, you can then build the back end and the database. Even if they don't really understand it, most clients will accept this explanation as reasonable.
- Jeff On 8 Jun 2002 at 13:58, John Jonathan Kopanas wrote: > 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 ==^================================================================
