A price increase can reflect new work, an unclear initial brief, or a provider's poor estimating. The label 'scope creep' does not tell you which. Compare each added charge against the signed deliverables and the moment it was approved.
Check the real path
- Keep the original proposal, assumptions, exclusions, and acceptance criteria together.
- Match each added item to a written request or a discovered requirement.
- Ask whether the provider priced the change before starting it and explained schedule effects.
- Challenge charges for work already promised or defects against agreed acceptance criteria.
Decide what to change
Pause disputed additions and obtain a revised scope before proceeding. A realistic quote often depends on content, integrations, migration, and approvals being known. The buyer should see those dependencies before committing.
Put it in the project brief
Before paying for a fix, ask the provider to name the affected page or workflow, the change they will make, how they will test it, and which dependencies or exclusions could change the estimate. Keep the baseline and the completed test so both sides can see what improved.
How ARCHV can help
ARCHV provides project-specific scopes and prices; any change to deliverables should be documented in the project agreement. Share the current page and the problem through ARCHV's website estimate form. If you are an agency seeking delivery support, see the partner route.