Hi Michael, As long as the purchaser is willing to pay more up-front then that sounds reasonable. With complex systems there is always an element of risk - the issue is who carries that risk. One arrangement might be for the purchaser to pay a lesser amount up front and pay separately for maintenance etc as required. The purchaser gambles that it might not be necessary and often they will be correct. But if they want the developer to carry that risk then they need to pay for that. And given that bug fixing can sometimes take a lot more resource than the original feature itself, the extra amount could be quite high. It is unfair, and ultimately self-defeating, to expect both a cheap price and for the developer to carry all the risk.
All the best, Grant Michael wrote: > This claptrap is why I.T people are not widely trusted. > > If the product you supply is broken, fix it and stop making excuses or trying > to wriggle out. > > I am sure if you went and bought a TV set from Noel Leeming, and it didn't > work properly, you would not be in the mood to discuss service contracts and > who's responsibility it is. > > Now in the same way try and see this from the customer's perspective. > > They are not interested in "open source" or any other geek lingo. > > They bought a website and they want one that works. end of story. > > > > > --~--~---------~--~----~------------~-------~--~----~ NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected] -~----------~----~----~----~------~----~------~--~---
