What is Scope Creep?
Scope Creep: The gradual, unplanned growth of a project's requirements after work has started, usually without matching changes to budget or timeline.
Scope creep happens when small additions pile up: one more report, a second user role, "while you are in there, can it also." Each request looks cheap on its own. Together they push dates, raise cost, and blur what the product is for. It is the most common reason software projects run late.
Scope creep is not the same as learning. Changing direction because users showed you something important is healthy. The problem is unmanaged change: additions that are not written down, priced, or traded against something else. The standard defense is a written scope with acceptance criteria, a change process where every addition is either swapped for an existing item or scheduled for a later phase, and a fixed delivery date that forces those trade-offs.
Why it matters when you build or buy AI
On hourly contracts, scope creep is the vendor's revenue and your risk. On fixed-scope contracts, it becomes a negotiation every week. We handle it by fixing the scope for the first release and moving every new idea to a backlog that feeds paid iteration sprints after launch. If a vendor will not say what is out of scope in writing, expect your budget to grow.
Example
Halfway through an MVP build, the founder asks for Slack notifications, a mobile view, and CSV export. Each goes onto the post-launch backlog with an estimate, and the launch date holds.
Related terms
More in MVP & Product
Book 20 minutes, or send a brief
A former CTO replies. You leave with a written plan and a fixed estimate.
Prefer LinkedIn? Connect with Harish.