Recommendations for finalizing the Business Requirements Document and handling post-sign-off change requests.
Process ideas to reduce scope creep and unnecessary change requests.
In the Google Meet set up by Herman and me — or any later discussion meeting — bring up the entire scope of the project in detail and ask if there is anything else the client would like to include before we finalize the BRD. That way everything is addressed upfront, and we won't have to keep saying no later simply because they didn't read the BRD properly.
We could start charging clients the moment they raise a change request. For example, once they've finalized the BRD and are ready to proceed, we usually collect the first instalment. After that, if they come back with new change requests, we can charge for them immediately. This creates a sense of monetary implication — since they've already invested in the project through the instalment, they'll be less likely to keep suggesting unnecessary changes. At the same time it isn't a loss for us: if a change is genuinely important to the client, they won't mind paying for it.
As an add-on, we could introduce an insurance-style plan where the client pays a small additional amount (e.g., ₹2,000–₹4,000) at the start. In return, any change requests raised after the BRD is signed are covered under that plan. Clients who don't opt in pay separately for each change request. This gives clients a safety net for future additions — and if they never use it, it simply becomes additional profit for us.
Proposed contractual language.
The Client shall carefully review the draft Business Requirements Document (BRD) and provide all comments, suggestions, and revisions in a consolidated manner during the designated review period, which shall be within two (2) days of receiving the draft BRD. Upon completion of the final revision round — or where the Client fails to provide comments within the stipulated two-day review period — the BRD shall be deemed final and approved, and any additional requirements shall be treated as a Change Request.
The Client is responsible for ensuring that all business requirements, stakeholder inputs, and suggestions obtained through internal discussions or third-party consultants are consolidated and communicated during the BRD review stage. DestinPQ shall not be responsible for incorporating requirements introduced after the BRD has been finalized, unless mutually agreed through the Change Request process.