A website project scope says what you are building, for whom, which pages and features are in the first version, which integrations it needs and what is explicitly out of scope. A PRD (product requirements document) goes further, with user stories and acceptance criteria that define how each feature should behave. Write the scope first, and add a PRD when the project has app-like features. My free Project Scope Generator and PRD Generator draft both from a short description.
What is the difference between a project scope and a PRD?
| Factor | Project scope | PRD |
|---|---|---|
| Answers | What are we building, and what are we not? | How exactly should each feature behave? |
| Main readers | Client, developer, whoever quotes | Developer, designer, tester |
| Contents | Goal, pages, ranked features, integrations, phases, exclusions | Problem, goals, metrics, personas, user stories, acceptance criteria, edge cases |
| Best for | Marketing sites, stores, redesigns | Web apps, marketplaces, booking flows, complex features |
For a five-page company website, a scope is enough. For a marketplace with vendor accounts, commissions and memberships, like the UK grocery marketplace I built in 2025, you want both.
What should a website project scope include?
- Summary. One paragraph a stranger would understand.
- Goal. The business outcome, such as more enquiries, online orders or fewer phone bookings.
- Audience. Who visits and what they need to do.
- Pages. A list or sitemap of every page or template.
- Features, ranked. Must have, Should have, Could have.
- Content. Who writes the copy, who supplies photos, and when.
- Integrations. CRM, payments, email marketing, analytics, maps, accounting.
- Who edits after launch. This decides the stack more than anything else.
- Stack. Or the constraints on it, such as "must stay on WordPress".
- Phases. What ships first and what follows.
- Out of scope. What you are deliberately not doing now.
- Open questions. What still needs a decision.
How do you write features so a developer can quote them?
Vague features get vague quotes. Compare:
| Vague | Quotable |
|---|---|
| Online booking | Booking page with a date picker, per-date packages, Stripe payment, past dates disabled, customer and admin confirmation emails and a daily booking summary email |
| Delivery | Geocode the customer's address, hide delivery beyond 10 miles, charge a fee by distance and fall back to pickup or dine-in |
| Lead form | Every form submission written to a Google Sheet the CRM reads from, with the service the person asked about |
| Phone verification | One-time code sent to the phone, enquiry reaches the team only after the number is verified |
Each quotable line is a real feature I built: the Wimbledon booking page on Ravens Ait, the delivery plugin on Whitfield Service Station, lead handling on Taxocity and OTP verification on PropAlert.
When do you need a full PRD?
When a feature has rules, states or several types of user. Marketplaces and ordering systems are good examples. That grocery marketplace had vendors, commissions and membership plans. Whitfield Service Station has delivery rules, opening hours and a store that can be closed from the admin. Each of those has states and edge cases, which is PRD territory.
The core of a PRD is user stories with acceptance criteria. The PRD Generator writes them in Given/When/Then form. For the PropAlert enquiry flow, one would read:
Story: As a home buyer, I want to enquire about a project so the team can call me back.
Given I have filled in the enquiry form with my phone number
When I submit it
Then a one-time code is sent to that number
And the enquiry reaches the sales team only after I enter the correct code
A developer can build and test that without guessing.
What usually gets left out of a scope?
These are the items that turn into surprise costs later:
- Accounts and keys. HubSpot, Stripe, Xero, a Google Maps API key, an IPinfo token. Who owns each, and who sets it up?
- Content. Writing copy for many pages is often bigger work than building them.
- Migration. Redirects from old URLs, moving hosting, and DNS with email on the domain.
- Analytics. GA4, Google Tag Manager and Search Console setup, as on Aura Clips.
- Legal pages. Privacy, cookies and terms. The old Crowne Plaza London Kingston site lacked privacy and cookie pages.
- Documentation and training for the team that runs the site.
- Changes after launch. How they are requested and priced.
How can AI tools help you write a scope?
They give you a structured first draft in seconds, which you then correct. All my free tools need no sign-up.
| Tool | What you get |
|---|---|
| Project Scope Generator | A summary, MVP features ranked Must, Should and Could have, the pages or screens, a user flow diagram, a suggested stack with reasons, and build phases with risks and open questions |
| PRD Generator | Problem statement and goals, success metrics, personas, user stories with acceptance criteria, in and out of scope, a user flow, edge cases and open questions |
| Tech Stack Advisor | A recommended stack layer by layer, an alternative, the trade-offs and an architecture diagram |
| Architecture Diagram Generator | A system, flow, sequence or database diagram from a plain description, with Mermaid code to paste into your docs |
Treat the output as a draft. The tool does not know your budget, your team or your customers. Edit the feature ranking, delete what does not apply, and add the open questions only you can answer.
How do you use a scope to hire a developer?
Send the same scope to everyone you are talking to. The quotes become comparable, and the questions each developer asks tell you a lot about how they work. For Warren House, a 24-page site plan was scoped and quoted, which let the hotel start with the homepage and key fixes while the wider redesign waited.
For what else to check before hiring, see hiring a freelance web developer in India. Or send your scope to me and I will reply with questions, an approach and a timeline.
