I was coordinating a Project and we constantly faced a problem where the customer was not ready to pay for change requests.
The project was to automate most of the processes of an existing system i.e. instead of manually uploading a file using forms in existing system, know the source of files and automatically upload them at specified time and update reports accordingly.
We created the scope statement by interviewing client and documented the source of information, the type of action required to be applied on those sources, the time of taking that action and the expected outcomes.
This was a Fixed Price Project and the domain was new for us.
As we kept progressing, we came to know about the more information/sources and more dependencies due to which we had to do extra work to achieve the documented outcomes resulting in added efforts.
Many a times the customer gave feedback on the features implemented based on agreed upon solutions and those feedback led to alternative solutions which should be accepted as change request.
Every time we represented those added efforts to customer as a change request, he rejected the same saying this feature is the part of scope and we will not pay extra for this.
I tried convincing by showing the initially approved and documented solution VS changes proposed in the solution as feedback which demanded added efforts. But the only efforts he approved was the new features requested to add in scope.
How can we handle such situation?