ScopeProcessApprovalPricingFAQDone for youBlogToolsProtect a project →

Replies / add a quick feature

How to say no to "add a quick feature"

"Can you add a quick feature while you are in there?"

"While you are in there" assumes the feature is a door you leave open on the way out. It is usually new code, new testing and new stuff that can break.

Get the repliesLock your scope in Scopease, free

Why this is scope creep

  • A feature that sounds quick to the client often touches data, edge cases and design you never quoted for.
  • You own the bugs afterwards. Unquoted features become unpaid support.
  • It pushes the original deadline, and the client will remember the late date, not the free feature.

Copy-paste replies

Fill the [brackets] and send. Pick the tone that fits the client.

Firm

Hi [Name], good idea. It's not part of the current build, so I'd rather not squeeze it in and risk the launch date. Let's ship what we agreed first, then I'll scope this as a separate piece with its own price and timeline.

Friendly

Love that you're already thinking about what's next! Let me finish the agreed version properly first. I'll write up [feature] as a small add-on so you can see exactly what it involves before deciding.

Yes, for a fee

Hi [Name], can do. Here's the change order for [feature]: roughly [X] hours including testing, [price] total, and it moves delivery from [old date] to [new date]. Approve it and I'll fold it into this sprint.

The "yes, for a fee" reply works best when the scope was written down first. In Scopease the client approves the scope through one private link, every extra ask becomes a priced change order they approve or decline, and the invoice builds itself from approved work. Free for your first project.

Start freeHave us set it up for you ($79)

Questions

Is "Can you add a quick feature while you are in there?" scope creep?

Yes, if it was not in the agreed scope. A feature that sounds quick to the client often touches data, edge cases and design you never quoted for. The fix is not a fight, it is a clear reply that points to the scope and offers a priced option.

How do I price a feature a client calls quick?

Estimate the build, then add testing, edge cases and a buffer for things it breaks. Quote the total, not just the coding time. If you cannot estimate it yet, charge for a short discovery first.

What if the client says it is only 10 minutes of work?

Then it is a cheap change order. Agree on the number, write it down, get the approval. Clients rarely argue with a small, clear price.

Free tools that help you say no

More ways to say no