A written scope is a short document that says exactly what will be built, what will not, how everyone will know it is finished, and what happens if the request changes. We write one before we quote, because a price only means something next to a definition of the work.
What does a written scope contain?
- The goal. One or two sentences on what the project is for and who will use it.
- What is included. The screens, features, pages or integrations, listed so nobody has to guess.
- What is not included. Written down on purpose. Most disagreements start with something each side assumed was in, or out.
- How we will know it is done. The checks the work has to pass, and who decides.
- What we need from you. Content, logins and decisions, and when we need them.
- The order of work. What is built first, and what you will see along the way.
- How change is handled. If the request changes, the scope changes in writing, and the quote changes with it.
Who writes it?
We do, with you. You describe the problem. We ask questions until the answers are clear enough to write down. You read it and correct it. It is agreed when you can say, "Yes, that is what I want."
Why write it before the quote?
A quote built on a loose brief is a guess with a price on it. With a scope in hand, the number matches the work. The scope is also where we say so if part of the work is outside what we do well, and where we can we point you to someone better placed.
What if I do not know exactly what I need?
That is normal. Part of writing a scope is working out what you need. Bring the problem: what is slow, what is missing, who is affected. We turn it into a list you can react to.
What should I bring to the first conversation?
- What you want to achieve, in your own words.
- Who will use it.
- Anything that already exists: a current site, a spreadsheet, a product you like.
- Any fixed date the work has to meet, and why.
If that is enough to start, tell us about your project and we will reply with questions before any quote.