How to Handle a Client Who Keeps Changing Their Mind

Scope changes are part of client work. A client sees a mockup and realizes they want something different.

That happens. But there's a difference between one thoughtful scope change and a client who changes direction every other day.

When scope is constantly in flux, you can't deliver good work. Your team wastes time rebuilding. Deadlines slip.

Quality suffers. And you lose money because you end up doing 50% more work for the agreed-upon price.

At some point, you need to address it. Not aggressively, but clearly. You need to help the client understand that constant changes aren't helping them - they're slowing down the project and creating chaos.

Diagnose the Real Problem

Before you push back, understand why they're changing direction so much.

Sometimes it's because they don't really know what they want. You presented option A, they said yes, but deep down they weren't sure.

Now seeing it, they're second-guessing. This is a brief clarity issue - you didn't get clear direction upfront.

Sometimes it's because new information is coming in. Leadership changed their mind. The market shifted.

A competitor did something that affects their strategy. These are legitimate reasons to change scope.

Sometimes it's because they're not engaged and they're using scope changes as a way to stall. They haven't provided feedback in two weeks, then suddenly they have five changes. This is often a sign they're unsure about the investment or the direction.

Sometimes it's indecision from multiple stakeholders. The CEO wants X, the CMO wants Y, the VP wants Z. They're all weighing in separately, creating conflicting direction.

Once you understand the cause, you can address it.

If It's a Brief Clarity Issue

If the root cause is that they didn't really know what they wanted upfront, go back to basics.

Have a strategy conversation. "Before we keep iterating, let me understand your real objective. What are we trying to accomplish?

Who's the audience? What should they do after they see this?" Go back to first principles.

Propose specific directions instead of open-ended options. Instead of "What do you think?" try "I see two paths: (A) emphasize social proof with testimonials and case studies, or (B) emphasize innovation with new features. Which direction feels right?"

Build in a decision-making process upfront. Before you design, agree on three things: (1) Brand positioning. (2) Key differentiator.

(3) Main call-to-action. Everything else flows from those.

Consider doing a deeper discovery phase. If they're clearly unsure, investing in clarity upfront prevents constant changes later.

If It's New Information

If the changes are coming from new information - market shifts, competitive threats, leadership changes - that's legitimate.

Acknowledge it: "I see why you're asking for this change. That shift in the market does affect what we're doing." This shows you understand the business context.

Then set a boundary: "We can absolutely adapt to this. But this is a scope change, which means we either extend the timeline or adjust what else is included. How do you want to handle it?"

This isn't being difficult - it's being professional. Change is fine. But change has consequences, and the client needs to understand them.

Request a freeze on further changes for a defined period. "We've made three changes in the last week. I want to lock in the direction for the next two weeks so we can make real progress.

After that, we can assess and make adjustments if needed. Does that work?"

This gives you a window where you can actually build momentum without constant rebuilding.

If Multiple Stakeholders Are Causing Conflict

This is the trickiest situation. Different people at the client organization want different things.

Identify one decision-maker. "I'm hearing different perspectives from your team, which is helpful context.

But I need one person who's making the final call on direction. Who's that person?"

Request a stakeholder alignment meeting. "Before we keep iterating, let's get your whole team aligned.

I'll present the options and the tradeoffs. You guys decide which direction you're going, and then we'll execute from there."

This meeting might take an hour, but it saves weeks of back-and-forth. Once the stakeholders have agreed, they can't blame you for the direction they chose.

Document the decision. "Here's what we agreed on as a team.

Direction A with B modifications. Is that correct?" This prevents the "But I said something different" conversation later.

When to Charge for Changes

Scope changes mean additional work. Some changes are small and part of normal revision. Some require re-scoping and a change order.

In your contract or brief, define your revision policy. "Two rounds of revisions are included. Additional revisions are $X per round."

Draw a line between feedback and scope change. "Feedback: 'The headline doesn't pop.' Scope change: 'Can you redesign the entire layout?' The first is revision. The second is a change order."

When they ask for a scope change, you have options:

1. Add it and extend timeline

Add it and increase investment 3. Push it to a follow-up phase 4.

Present it this way: "This change will take about three more days of development. We can (1) extend the launch by three days, (2) you can pay an additional $2,000 for the rush work, or (3) we can include this as part of a Phase 2 after launch. Which works for you?"

This puts the responsibility back on them to decide what change means.

The Conversation With the Client

At some point, you might need to have a direct conversation about the changing scope.

Pick the right moment - after they've asked for the third or fourth change, not the first one.

Be empathetic: "I know you're trying to get this right, and I appreciate that. I want to help you build something great."

Be clear about the impact: "But when we keep changing direction, it actually slows us down and makes it harder to deliver quality work. Here's what's happening - we redesigned that section twice in two days. That time could have gone to other improvements."

Propose a process: "Here's what I suggest: Let's lock in the direction for the next phase. We execute without changes.

At the end, we review and make adjustments if needed. This gives us momentum to build something really good."

Ask for their input: "What would help you feel more confident about the direction so we're not constantly adjusting?"

This conversation is respectful but firm. It's not blaming them - it's solving a real problem together.

Preventing This Upfront

The best solution is preventing constant scope changes from the start.

Get very clear direction upfront. Don't move forward with ambiguous direction. Slow down the discovery phase to get alignment.

Define the revision process in writing. Make it explicit: "Two revision rounds are included. After that, each revision is a change order."

Set a review cadence. "We'll review progress every Friday.

Feedback is due by Wednesday. We'll implement feedback by Friday." This creates structure instead of random changes.

Use Huddle or a similar tool to track what's approved and what's not. Having a clear record of decisions prevents the "But I didn't approve that" conversation later.

FAQ

What if they refuse to pay for scope changes? Then you don't make the scope changes. "The budget covers A, B, and C. If you want D, that's an additional charge. Or we can drop something from the original scope."

Should I be flexible with changes? Yes, within reason. Minor changes are part of any project. Major changes or constant small changes are different and should be addressed.

How do I handle a client who's genuinely indecisive? You might need to help them decide. Present two options and explain the tradeoffs. "Option A is faster but less expensive. Option B is more strong but costs more and takes longer. Which fits your needs?"

Can I refuse to make changes mid-project? You can set boundaries. "We're in execution mode now. Change requests will push us past the deadline. Let's finish this phase and address new requests in Phase 2."

What if changing direction is actually the right business move? Then absolutely change. But get agreement on the impact - timeline extension or budget increase. Don't absorb changes for free.

How do I document that a change was their request? Email them after they request it: "Just confirming - you'd like us to change X to Y. This is a scope change that will require [timeline extension / additional investment]. Shall we proceed?" Document their approval.

Should I charge for changes they request but then want to revert? Yes, if it's significant work. "You asked us to change this. We spent two days on it. If you want to revert, that's additional work." Charge for the revision.