Lessons on managing scope creep in freelance software projects

Short summary

A freelancer shares lessons from their first major app project: every new feature request is a decision that spends time, scope, or money, and AI coding tools make scope creep more dangerous by hiding the true surface area behind fast initial output. The author recommends pausing before implementing, running an impact scan, and presenting clients with a three-way trade: move the date, remove something else, or add budget. A free prompt pack is linked for scoping AI-assisted builds.

• •Scope creep happens because clients see better ideas after seeing v1, not from malice
• •AI coding tools speed up initial output but hide the full surface area of a feature
• •Use a three-way trade framework: keep date and cut scope, keep scope and move date, or add budget

Generated with AI, which can make mistakes.