Chapter 2 of 8 · 4 checks · 2 min
Discovery and scope
Turn a conversation into a written scope that both sides agree on. A clear scope is what makes change requests and payments easy later.
Run a discovery call with a prepared list of questionsMust
Why it matters and how to check
A discovery call is where you learn enough to estimate. Prepare questions about users, features, existing systems, integrations (payments, maps, SMS), hosting, content and who maintains the result after launch.
Take notes and send a written summary the same day. You are done when the client has confirmed your summary in writing and you know of no major unknowns, or you have listed the unknowns explicitly.
Do
- Ask about existing systems, data and integrations
- Send a written summary within a day
Avoid
- Relying on memory of a call to write a quote
Write the scope as a list of features, with an "out of scope" listMust
Why it matters and how to check
List exactly what you will build: pages, features, integrations, platforms and browsers or devices supported. Then add an out of scope list for things the client might assume are included, such as content writing, logo design, app store submission, hosting costs or ongoing maintenance.
Freelancers Union advises being as specific as possible about scope. You are done when someone who missed every meeting could read the scope and know what will and will not be delivered.
Do
- List supported devices and browsers
- Name who provides content, images and accounts
Avoid
- Phrases like "a complete website" or "all features needed"
Agree how each deliverable will be acceptedShould
Why it matters and how to check
For each feature or milestone, write how the client will check it is done: "user can register, log in and reset a password on Chrome and Safari" is testable; "login works well" is not.
Also agree how long the client has to review and what happens if they do not respond. You are done when every deliverable in the scope has a clear acceptance check and a review window.
Do
- Write acceptance checks the client can test themselves
- Set a review window, such as five working days
Avoid
- Open-ended approval with no time limit
List what you need from the client and by whenShould
Why it matters and how to check
Projects stall when the freelancer waits for content, API keys, server access or feedback. Write these dependencies into the scope with dates, and state that delays on the client's side move the deadline.
Ask for access to existing code, hosting and third-party accounts in the first week, so surprises show up early. You are done when the scope lists every input you need, who provides it and the date you need it.
Do
- Ask for access to existing code, hosting and accounts early
Avoid
- Committing to a deadline that depends on inputs with no date