Scope changes are normal. Once people see working software, better ideas appear. We handle them openly rather than absorbing them silently or refusing them.
When a change is requested, we describe it, estimate its effect on cost and timeline, and ask for approval in writing before starting. Small adjustments within the spirit of the agreed scope are often absorbed. Larger additions are handled as change requests at published rates or as a follow-on phase.
If a change makes something else unnecessary, we say so and adjust. The aim is a budget everyone can see and a timeline that stays honest.