Freelancer's Scope Creep Lesson: Why Discounts Without Boundaries Cost More

A software developer recounts how a Canadian client negotiated a reduced rate for minor WordPress updates, which gradually expanded into a full site rebuild at the original discounted price. The developer completed the work but ended up losing both time and money due to unchecked scope creep. The core mistake, he explains, was not re-scoping the project each time the client added new requests beyond the original agreement. He now sets written scopes upfront, ties any discount explicitly to a reduced scope, and treats every out-of-scope request as a separate billable item. The experience led him to adopt a firm policy: if a revised price does not work for the client, he walks away rather than accept terms that guarantee an unprofitable engagement.