Interesting article for me as I just rolled out an app for a client and a lot of this feels familiar. Firstly I was lucky I didn't have a PSD driven design, bu

Interesting article for me as I just rolled out an app for a client and a lot of this feels familiar. Firstly I was lucky I didn't have a PSD driven design, but my client demanded a fixed price quote, so I insisted they pay me to do fairly comprehensive spec, including a clickable wireframe prototype, bdd behaviour spec, architecture design, background, requirements, objectives.... I went with lo-fi hand drawn pages which I scanned and wired up as a clickable prototype via https://marvelapp.com/ https://marvelapp.com/ In the end it was fairly successful for me, as the comprehensive spec allowed me to estimate fairly accurately. However I don't think it was the most cost effective outcome for the client. Because of their rigid nature, instead of collaborating through the process (aside from the specification phase of course), I built them exactly what we agree and invoiced them and was paid. However, within a week of the first pilot they had come up with about 100 hours worth of changes they wanted. In the end I spent about 100 hours in the spec / design phase (which I was paid by the hour), 300 hours building the app (which was a fixed price) and now I have about 100 hours of changes to make. If we had worked to a budget rather than a fixed price, then by my estimate I would have spent about 400 hours collaborating and iterating (basically removing about 90% of the time creating and writing a spec) and they would have had an app which they were involved in crafting the whole way through. Basically I think they have blown about 100hours and they have to live with lots of little nuances that they would have otherwise been able to decide upon.