Scope creep starts with "while we're at it."

Cost & Funding · 5 min read

We were three weeks into the design process. The scope was locked. The screens were mapped. The developer was already lined up. And then I got the message: "Hey, while we're at it, can we add a chat feature?"

That single sentence, "while we're at it," is the most expensive phrase in app development. It sounds harmless. It sounds efficient. Like you're being smart by bundling things together. But every time someone says it, the scope grows, the timeline stretches, and the budget climbs. And the worst part is it never feels like it's happening until you look back and realise the project is twice the size it started.

Why small additions feel harmless

Each individual addition is small. A chat feature. A favourites list. A notification preference screen. On its own, each one takes maybe a few days of design and a week of development. That doesn't sound like much. So you say yes. And then you say yes to the next one. And the next.

The Project Management Institute found that 52% of projects experience scope creep, and it's one of the leading causes of budget overruns. Not because anyone made one bad decision. Because twenty small decisions compounded into a big one.

Five "small" additions, each adding a week of development at $1,500 to $2,500 per day for an Australian developer, adds $37,500 to $62,500 to your build. That's not a rounding error. That's your marketing budget. Gone. Before you've launched.

How to spot it in yourself

Scope creep isn't always someone else adding things. Most of the time it's you. You're excited about the product. You're thinking about it constantly. And every time you think of something new, it feels essential. The trick is recognising that the idea is good but the timing is wrong.

Watch for these phrases in your own messages: "While we're at it." "It would be quick to add." "Can we just." "One more thing." Each one is a flag. Not because the idea is bad, but because it's a new commitment of time and money that wasn't in the plan.

I keep a running list for every project. When a client has a new idea mid-build, I don't say no. I say "that's a great idea, let's put it on the phase two list." The idea gets captured. The momentum stays. And the current scope stays intact.

The phrase that saves your budget

"That's a version two feature." Say it early. Say it often. Every feature that doesn't need to be in the first release should go on the phase two list. Not because it doesn't matter. Because it doesn't matter yet.

Your MVP has one job: prove that the core idea works. Every addition that doesn't directly serve that goal is a distraction. It's not discipline for the sake of it. It's discipline because your money is finite and your launch date matters.

The clients I work with who ship on time and on budget aren't the ones with the best ideas. They're the ones who learned to say "not yet" to their own good ideas. That's harder than it sounds. But it's the single biggest factor in whether a self-funded project succeeds or stalls.

Sources
Managing Project Scope (Project Management Institute) - 52% of projects experience scope creep, a leading cause of budget overruns.
CHAOS Report (Standish Group) - Projects with tightly controlled scope are significantly more likely to succeed.

Related blog posts:

Self-funding your app →

What is an MVP? →

The difference between a feature and a solution →