Estimates, scope and change requests

Why projects run late, and how to say yes without losing money.

An estimate is a careful guess, not a promise from the sky. Break the work into small pieces (login, product list, cart, payment, admin), estimate each, then add time for testing, client feedback and surprises.

DoAvoid
Estimate in ranges: "3 to 4 weeks"Promising the earliest possible date
List what is NOT includedLeaving scope vague to win the deal
Add 20โ€“30% for testing and feedbackEstimating only the coding time
Re-estimate when you learn something newHiding a delay until the deadline

Scope creep

"Can you just add one small thing?" Each small thing is easy alone. Ten of them make the project late and unpaid. The answer is not "no". The answer is a change request: write what is being added, the extra time and the extra cost, and let the client decide.

๐ŸŽญ What would you do?

Two days before go-live, the client asks to add online payment, which was not in the proposal.

โ† Understanding what the client needsTalking to clients: updates, messages and bad news โ†’