Awhile back, I was approached by a prospective client with a project. She had a pretty grand vision of what she wanted, but I managed to get her to agree to a limited scope for a first iteration.
She seemed happy, and we started to move forward. A contract was drafted, and an invoice for a down payment was sent out.
A week later, she wanted to meet again, and she had some changes to make to the scope. Specifically, she wanted to expand it.
As soon as she said this, I felt my stomach twist, but I didn't know why.
I explained that the additional scope would mean higher cost and later delivery date, which she was ok with (even though she had initially indicated that there was a hard deadline on the project).
I recommended that we start with a limited scope so that we can create an MVP before adding more features, but she was adamant that the additional features were necessary for the initial iteration (even though there would have been no difference in terms of pricing and time between producing the MVP in iteration one and then immediately beginning the second iteration to add the extra features that she wanted).
But, I agreed to the increased scope, she agreed to the increased cost and new delivery date, everybody seemed happy, and we got ready to start up again (at this point, the contract was still unsigned, and the initial invoice was still unpaid).
A week later, she emailed me to let me know that she was dropping the project.
Was my instinct correct? Is increasing the scope before work has started a "red flag"? Or is that not usually a problem, and there was more likely something else going on here?