To Scope or Not to Scope – Coding Ninjas
Coding Ninjas
July 2019
« Jun    


To Scope or Not to Scope

Adam RitchieAdam Ritchie

When you run a web development business, you’re bound to come across some challenges.

You’ll likely find that the biggest obstacle is attracting attention and convincing anyone interested in your services to become an actual client. This is a very time-consuming and expensive process, considering all the marketing and reputation-building that’s required.

So it’s hard enough just to get someone who needs help with a web development product to actually contact you. But even once you’ve achieved that victory, your work isn’t over yet.

Before you can start working on a project for someone, you’ll have to sit down and draft a scope statement that details what exactly you’ll be doing for the project – that can take a lot of time.

This is the big issue with scoping projects. It allows you to reach a detailed yet clear agreement with a client, but it’s also a lot requires a significant time investment, especially for something that’s not guaranteed to work out.

In fact, in most cases the deal falls through and you don’t end up making a sale, even when you’ve taken the time to scope the project.

That’s just frustrating. If scope statements take so much time to make and there’s not even a guarantee that all your efforts will pay off, what’s the point of even bothering with them in the first place?

To answer that question, let’s first take a more detailed look at what scope statements consist of:

What’s in a scope statement?


I’ve already started ranting about scope statements, but you might not even know what those are exactly.

Allow me to explain:

A scope statement details the “scope”, i.e. all the relevant information, of a project. This usually includes:

What makes a good scope statement?


Using the SMART method is a good way to write a clear and effective scope statement.

If it takes so much time, why scope at all?


Well, good luck finding clients that are willing to hire you for a project without first defining what you’ll be doing.

It’s in the best interest of both you and the client to work out a detailed arrangement that defines exactly what’s expected of you for a project. You’re liable if you don’t hold up to the agreement, but you also have something to point to if the client starts being unreasonable.

And even if you’re still somehow convinced that scope statements aren’t worth your time, you should know that you don’t live in a bubble. You work in an environment where other businesses, the vast majority of other businesses, in fact, are willing to provide scope statements. So if you tell a client that you’re not willing to provide such a statement, they’ll just abandon you and find a web developer that will. It’s just not a viable option.

Adam is a freelance writer based in Seattle. His work has been featured on Groupon, Empire News, Menguin, and many other sites.

Comments 0
There are currently no comments.