Handling scope creep
Say yes to the client without saying yes to free work.
Case study: Anjali's 'small' changes
Anjali led a fixed-price portal build for a London insurer from Chennai. Every demo, the product owner asked for "one small thing": an extra filter, a PDF export, a dark mode. Anjali always said, "Sure, we'll manage." By month four the team was working Saturdays and the project was six weeks late. The client was annoyed about the delay, not grateful for the extras. On her next project, she said, "Happy to add that. It's a change request: about eight days and a week on the timeline. Want it now, or after go-live?" The client chose after go-live twice out of three times.
Takeaway: Scope creep is rarely malicious. Make the cost visible every time, and clients make sensible choices.
Saying no to a client can feel disrespectful, so we absorb extra work quietly. Global clients expect a vendor to flag impact on time and cost; silence looks like the work was free.
Pushing back
Goal: Keep the relationship warm while every new request goes through a change request with a clear time and cost impact.
Step by step
- Welcome the idea. Show you like the request before discussing cost.
- Name it as new. Calmly point out it's outside the agreed scope.
- Show the impact. Days, cost and the effect on the release date.
- Offer options. Add it now, swap it for something, or do it in phase two.
Say this, not that
| That's a good idea, and I can see why your users would want it. | Agree with the value before talking about cost. | |
| That's outside what we signed off in the SOW, so let's treat it as a change request. | Okay, we will adjust somehow. | 'Somehow' means weekends, delays and resentment. |
| Roughly, it's eight days of effort and it pushes go-live by a week. | It is little bit difficult. | Numbers help the client decide. 'Difficult' just sounds like reluctance. |
| We could add it now, swap it for the reporting screen, or schedule it for phase two. | ||
| Which of those works best for you? | Give them the choice, so it's their decision. |
Model conversation
- Sophie
- This is looking great. Could we also add a PDF export on the claims page? Should be quick.
- You
- Thanks, Sophie. That's a good idea, I can see adjusters using it a lot.
- Sophie
- Brilliant. So it can go into this sprint?
- You
- It's outside what we signed off, so I'd treat it as a change request. Our rough estimate is eight days, which moves go-live by a week.
- Sophie
- Oh. I thought it was a small thing.
- You
- The formatting and security checks take most of the time. We have three options: add it now, swap it for the reporting screen, or put it in phase two.
- Sophie
- Let's do phase two. I can't move the launch.
- You
- Makes sense. I'll log it in the backlog and send you the change request so it's on record.
Requesting a change
Goal: Get the change you need at a fair cost and timeline, without souring the relationship with your vendor.
Step by step
- Explain the why. Share the business reason behind the change.
- Ask for the impact. Invite an honest estimate of time and cost.
- Negotiate trade-offs. Offer to drop or delay something else.
- Confirm in writing. Agree on the change request and the new dates.
Say this, not that
| Our compliance team has a new requirement, and I need to talk about adding it. | This is a small change only, you can do it. | Calling it small before they've estimated it sounds like pressure. |
| What would this do to the timeline and the cost? | ||
| If we drop the admin dashboard from this release, could the audit log fit in instead? | Offering a trade shows you respect their capacity. | |
| That estimate feels high. Could you walk me through where the days go? | Why so much? Reduce it. | Asking for the breakdown keeps it collaborative. |
| Great, please send the change request and I'll get it approved this week. |
Model conversation
- You
- Lars, our compliance team has asked for an audit log on every user action. I know it's new, so I wanted to discuss it properly.
- Lars
- Thanks for flagging it early. What exactly do they need?
- You
- Who changed what and when, stored for a year. What would that do to the timeline?
- Lars
- Our rough estimate is fifteen days. That would push the release by three weeks.
- You
- That's more than I hoped. Could you walk me through where the days go?
- Lars
- Most of it is storage design and testing every screen.
- You
- Makes sense. If we drop the admin dashboard from this release, could the audit log fit in instead?
- Lars
- That would bring it down to one week's delay. I'll send the change request today.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.