I've noticed that clients often treat the QA phase as a time to request new features with phrases like, "While you're fixing that, can you also add..." It leads to scope creep since each request seems too minor to bill separately. What's the threshold you use before you address it with them? How do you handle this situation?
5 Answers
If I notice that all the additional requests add up to 30-60 minutes, that’s when I present additional development costs. It helps the client see the value in sticking to the original plan.
Everything I do is planned with phases and milestones. This way, I can easily say, "Let’s save that for the next phase." It keeps the workflow organized and makes those requests feel more like an extension of the project rather than an interruption.
I generally bill a 4-hour minimum for additional requests, which helps curb scope creep. It creates a buffer for minor extra work while managing expectations around what constitutes a separate item.
I have a hard rule: if it’s not in the original specs or agreed scope, I log it in a separate change request list with estimated time. I keep a document during QA called "additional requests" to track these things. At the end, I share it with estimates so the client can decide what’s worth paying for. This has saved me from a lot of unpaid hours! I like to frame it positively as, "I’m happy to add this, here’s what it will take." Most clients don’t even realize they’re pushing boundaries until they see the accumulated hours!
Whenever I hear, "While you're fixing that, can you also add..." I just firmly say no. I make it clear that any new requests need to be made as a new JIRA task that must be approved first.
Gold Advice! Surely will follow this man.