> how do you deal with bad estimation? I think in part it depends on the type of client you're working with and the type of relationship you're building. Non-

> how do you deal with bad estimation? I think in part it depends on the type of client you're working with and the type of relationship you're building. Non-tech/software clients (ie a business paying for custom software they're going to use themselves) care a lot about the total cost of $features, and often try to manage risk of cost overrun by treating estimates as part of the contract with the developer (even if it wasn't a fixed bid contract), and will hold you accountable to the project milestones: eg they don't care why things are taking longer - 'you should have considered that risk in the estimate - it's your fault'. Tech customers (ie a software licensing or sass company) that use contractors to supplement their internal workforce usually understand the variability better, think of the contract more as buying the (expertise and) time of the developer, and they're managing more of the project and risk themselves. When things don't go to plan, they understand that many/most times this isn't the 'fault' of the developer, it's simply the inherent risks in the task being uncovered. It's much simpler to arrange weekly rate contracts with the second type of customer than the first.