billed for. Thus unless a project is very large, it's generally not worth
client's while to have a binding estimate created as it consumes time that
otherwise could already be used for developing the project.
You're right, a binding estimate is not always worthwhile, but a binding
*contract* stating your expectations to be paid for your time regardless of
how many times they change their mind, your right to adjust the cost as new
features are added, what the resulting source code should look like, and who
owns the rights to what after it's all said and done. That way you're
covered even if they're not happy at the end.
But it's "live and learn" :). This was a good learning experience even
though it's unfortunate that a client relationship had to be destroyed in
the process.
I've found that sometimes client relationships aren't worth keeping,
regardless of the history. As you grow as a developer, your rates should
increase to reflect it. Not many clients want to pay someone more than what
they've paid them in the past, regardless of what they may have learned.
ryanm
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
