sPiKeRs said:
A more believable story would have been paying the budget of $200k, making another installment of let's say $100k to complete the web project. If the project is still not completed after that, you stop payments and file legal action against the web designer company.
That's generally now how software development works. There is very rarely a true definition of "done" or "complete."
This is usually how it goes...
Customer: I want an app that does X, Y, Z.
Developer: Ok, that will cost about $N.
Customer: Sounds great, let's go.
Developer: Ok, here it is.
Customer: Hmm, well now that I see it, I'd like to make some changes. Let's change X, Y, Z.
Developer: Ok, that'll be another $N.
Customer: Ok
Developer: Done
Customer: Looks good, but I thought of another feature I want.
Developer: Ok, that'll be another $N.
Customer: Ok
Developer: Done
Customer: Hmm, well now that I see it, I'd like to make some changes. Let's change X, Y, Z.
... repeat forever.
These iterations can be really small, or really large, but that's often the general the pattern.
I've been in projects that were a few hundred thousand dollars. The point is Mike's making installments throughout the project. He didn't make a lump sum of $200k, and then another lump sum of $450k. Once he overspent his initial $200k budget, an intelligent person like Mike would have been on high alert. You would be a fool to keep paying on broken promises. A greater fool to pay with money you don't have. And a criminal to pay with customer deposits.