If you've ever done freelance work, or worked at a job where clients are billed by the hour (or per milestone), then you have very likely been in this situation before.
You make the last round of presentations, and the project/spec is just pending final approval.
Everything worked fine (within objective interpretation), and the client probably even said so themselves. But then they suddenly ask you to make modifications in some part of the process (that you worked on) that was not really part of the original spec, or something can be reasonably deemed as "fixing errors in the functionality". In other words, they're asking you to do something that is undoubtedly extra.
Now doing something extra is fine if it's something that can be done quickly; however, there are times when their additional request can take hours, even though it looks simple to implement in their eyes; that and/or they're out of budget. One common response would be to just suck it up and do it anyway. You just want to get it over with, and don't feel like going through the process of asking the client for more money or telling them that it's too much to do.
It's easy to say that we should put our foot down and tell the client to respectfully fuck off, but that might not be possible without ramifications on your job status or the cordiality that you currently have with your client. Or perhaps you just don't know how to say no professionally. Well this is not the article for that.
Instead, what I want to do here is to point out some possible ways to minimize the chance of a client asking for extra modifications--not so much with the politics, but more with the understanding of technical details.
Keep in mind that these pieces of advice below might not always be possible, or don't apply based on the type of work that you'll be doing. It might not be possible because of the timeline of your project, or the type of software development approach that your current team is using (i.e. scrum, agile). Rather, this serves as a general advice to people who regularly interact with clients regularly on websites or apps, and get their input on your work.
Here are the pieces of advice:
In summary, those are some pieces of advice that I think can save a lot of developers time in the process of development if they work with a client, and I hope it helps.
Everyone from your clientele, to sometimes even your project manager, underestimates the time that it takes to properly implement a spec and then test it. While the ideal thing to do is to just tell your client/boss that additional modifications are not possible given limited time/money, more often than not, that is not a possible scenario. If so, those are some things you can do to minimize that chance of the client asking for additional modifications from happening.