Stop Scope Creep Before It Turns Good Clients Into Time Vampires

It starts with a small favour. "Oh, can we do this?" Then another. Two months into the project the workload has expanded, the fee hasn't moved and you can't quite remember agreeing to any of it.

That's scope creep. The name says it all: it creeps up on you, one little request at a time. If you run a consulting, coaching or professional services business, you've almost certainly lived through it. Once you've said yes a few times, saying no starts to feel awkward.

In this video, David Jenyns explains how to manage scope creep the way he learned to in his own systems consulting business. The answer isn't to get tougher with clients. It's to get clearer, before the work begins.

What Scope Creep Looks Like in a Service Business

Scope creep is when the work on a project keeps growing beyond what you originally agreed. It arrives as a little thing here and a little thing there. "Oh, can we do this?" Most of the time you don't even notice it happening.

Dave saw it all the time as a consultant, particularly when he started his systems consulting business. He'd start a project and two months later the workload had expanded, without anyone sitting down to renegotiate it. It had simply crept.

The trap is in how it compounds. Say yes a couple of times and you condition the client. They learn that you always say yes, so they keep asking. Then the day you need to say "that's outside of scope", it feels awkward for both of you.

Unless you have a way to manage it, scope creep becomes frustrating for you, frustrating for the client and overwhelming for everyone involved.

The Real Cost: Lost Profit and Time Vampire Clients

The first cost is obvious. Scope creep turns a profitable project unprofitable. You quoted for one amount of work and you're delivering another.

The second cost is harder to see. Scope creep sets an expectation and that expectation creates what Dave calls time vampire clients. They suck up your time, bang the loudest on the drum to get your attention and call you directly wanting everything done for them.

Eventually you reach the point where, even if it's unconscious, they call and you think, "Ugh." That's a painful client. Those clients are also poor sources of repeat work and they rarely send referrals.

So the problem doesn't stop at one blown-out project. It quietly eats into the two things that grow a service business: clients who come back and clients who tell their friends. That's why you're far better off solving scope creep upfront than mopping it up later.

What Causes Scope Creep? A Lack of Clarity

When Dave put this question to a live audience, he offered a few suspects. Is it the expectations you set? Is it not being clear? Or is it just the nature of the beast, something every consultant has to live with?

One attendee nailed it in the chat: a lack of clarity on time, task and territory. Dave's response was simple. That's 100% it. You need a very clear scope upfront.

He learned that the hard way. Think about what "systems consulting" means to a client. Where are the edges on that? A client would say, "You said you were going to come in and systemise my business. Now I've got all these other departments that need systemising too." How do you put the bookends on that?

Dave struggled with exactly this for his first few clients. Then he saw the real problem. The client has a picture in their head of what you're doing. You have a different picture in yours. That misalignment is what creates the problem.

Fix the clarity and most of the creep goes away with it.

How to Manage Scope Creep in 5 Steps

Here's the approach Dave developed in his consulting work. It works by deciding things before the project starts.

1. Build your offer around one specific problem

Scope is easiest to control when your offer is narrow. Dave ties this to the idea of a Trojan horse offer. The key is making sure that offer solves a very specific problem. "Systemise my business" has no edges. A clearly defined problem does. Once you know exactly what you're solving, it's much easier to say what's in the project and what isn't.

2. Agree the deliverables and timeline upfront

With the problem defined, spell out the deliverables and set a clearly established timeline. Then agree all of it with the client before work starts.

In Dave's systems consulting, the first engagement with a client ran for three months. The scope of works for that engagement was defined by the client's Critical Client Flow, the core systems that take a client from first contact to a happy result. Both sides agreed: this is what we're doing.

That agreement becomes your reference point. When the client drifts off track and starts nudging, "Can you do this and that?", you don't need to argue. You come back to the document and say, "Here's what we've agreed on."

3. Get sign-off on what you're not doing

Another attendee added a smart twist: have the client sign off on what they don't want as well. Dave called it a great idea, because it brings even more clarity.

In practice, that sounds like this. Using SYSTEMology itself as the example, Dave might say: "You have loads of leads at the moment, so leads aren't your problem. We don't need to focus on your lead generation systems just yet."

Naming what's out of scope does two jobs. It keeps the work pointed at where the client's real pain is. And it stops the scope of works from quietly opening back up later.

4. Underpromise, then overdeliver

Dave is honest about this one. With clients, he's a bit of a people pleaser. In the early days he always wanted to go above and beyond. The trouble was he didn't know how to rein it in. That made it easy for some people to ask for a little more, then a little more again.

So he flipped it. During scoping, he deliberately underpromises what he's going to give the client. That makes it far easier to overdeliver. He creates more systems than agreed and goes beyond what the client expected. They feel great about it.

The extras still happen. The difference is they arrive as a pleasant surprise on top of a clear agreement, rather than as an open-ended expectation.

5. Park new requests on a "coming soon" list

Dave turned the agreed scope into a scope of works document: a simple spreadsheet listing the systems his team would work on during the engagement.

At the bottom sat a section called "coming soon". Any time the client asked for something outside the agreed works, it went there. The conversation sounded something like: "That's a great idea, let's capture it. We know our order of priority, so let's finish this first and come back to it at the end of the initial engagement."

Notice what that does. The client's idea is heard and written down, so nobody feels brushed off. The current work stays on track. And because the scope was agreed upfront, it's hard for the client to dispute. In Dave's experience, they don't even try. Of course it goes on the list. It's what you both agreed.

Why Limiting Scope Makes Clients Happier

Here's the part that surprises most business owners. You'd expect a tighter scope to annoy clients. Dave found the opposite. Limiting scope, he says, will skyrocket your customer satisfaction.

After those early clients, he started defining the scope of works. That enabled him to overdeliver on his promises. Clients knew what they were getting, saw him hit it and then got more than they expected.

That pattern became a core part of how Dave markets SYSTEMology. In his view, the best proof is always a client who had the problem, worked with you, got a fantastic result and is happy to share it. A clear scope makes those results far easier to produce.

You can even build it into your sales process. Dave's framing goes something like this: "Once I deliver on this, you absolutely love it and we solve this problem for you, I'd love to tell your story. That way other people in a similar situation can hear it and think, this could work for me too."

If you'd like to see what that looks like in practice, this consulting business case study follows one consultant's journey.

Make Your Scope Part of How You Sell and Deliver

A scope of works document only protects you if it's used every time, not just the projects you happen to remember. Dave's advice is to think about your offer and its clear deliverables, then think about how you'll use them in two places: the selling process and delivery.

In sales, the scope sets the expectation before the client signs. In delivery, it's the document you return to whenever a new request lands. When it's built into both, managing scope becomes part of how you work rather than a tense one-off conversation.

That's the systems mindset at the heart of SYSTEMology. If you're a consultant wondering where to begin, start with systems for consultants, or map your business processes from first enquiry to final delivery. Protecting your margins is one of the ways business systems increase profit. Scope is a good place to see it in action.

As Dave says, run these ideas through your own filter. Think about your offer, your clients and where your projects tend to blow out. Then pick one change and put it in place on your next engagement.

Frequently Asked Questions