Free tool · runs in your browser
Website Project Scope Planner
Describe the website you have in mind — type, size, features, integrations and design ambition — and get a structured scope: delivery phases, a requirements checklist, an indicative complexity level and the risks worth planning for. No prices, because honest pricing needs a real conversation.
Guide
Understanding the numbers
Why scope matters more than page count
Two websites with the same number of pages can differ enormously in effort. A brochure site with ten pages of supplied copy is a short project; a ten-page site with online booking, payments and user accounts is a software project. Features and integrations — not pages — usually decide the size of the job.
What raises complexity
Anything that stores data about people (accounts, bookings, payments) brings security, privacy and edge cases with it. Integrations depend on another system's documentation and reliability. Custom, motion-rich design needs a performance budget from day one so it stays fast on phones. And large page counts usually make writing and migrating content, not code, the critical path.
How to use the plan
Treat the output as a conversation starter. The phase list shows the order work usually happens in; the checklist turns vague wishes into concrete requirements you can share with any designer or developer; and the risks section highlights where projects most often slip. Copy the plan, remove what you don't need, and add the details only you know — your content, your audience and your deadlines.
The planner deliberately shows no prices. Cost depends on who builds the site, where and how, and a complexity estimate is a more honest way to compare options.
How it works
The logic, in plain English
- 1
Each project type starts with a baseline complexity score.
- 2
Every five pages, each feature and each integration adds weight.
- 3
Design ambition adds weight for custom and motion-rich work.
- 4
The score maps to a complexity band, and features expand into concrete checklist items and risks.
All rates live in one audited module with unit tests. Why that matters →
Questions
Why doesn't it show a price?+
Price depends on who builds it, where, and how. A complexity estimate is more honest and more useful for comparing options.
Is my plan saved?+
No. Everything runs in your browser. You can copy the checklist to your clipboard.
What should go into a website brief?+
The site’s purpose, audience, pages, features, integrations, content responsibilities, design references, budget range and deadline. The checklist from this planner covers the technical part.
Which features make a website project bigger?+
Payments, user accounts, booking systems, AI features and integrations with other software add the most work, because each brings data handling, edge cases and testing.