How to Scope a Website Project Before You Ask for a Quote
By the CodyFlect team · 28 September 2026
Most quotes are wrong before they are written, because the question underneath them was never answered. Scope first, price second — here is the order that works.
Start with the job the site has to do
Before anyone talks about pages or technology, write down what the site is for. "Take bookings", "show the catalogue and get enquiries", "let customers log in and see their data" — one sentence, no adjectives.
That sentence decides almost everything else. A site that has to take payments has a different security conversation than a site that mainly has to look credible and make the phone ring.
List the people who will use it
Write down who arrives, what they already know, and what they want in the first ten seconds. Two audiences are common: the person deciding whether to trust you, and the person who has already decided and wants to act. Design for the first, keep the path short for the second.
Inventory the real requirements
Requirements are easier to agree when they are concrete. Walk through the site as if you were the visitor and write down every distinct thing that has to happen:
- Pages or screens, with a one-line purpose each.
- Content you already have versus content that must still be written, photographed or filmed.
- Integrations: payments, email, CRM, analytics, maps, calendars, your existing stock or booking system.
- Roles: who logs in, what each role can see and do.
- Languages, currencies and devices that must work.
- Anything legal or internal that must hold — accessibility, privacy, approval steps.
Anything on this list you cannot answer yet is not a blocker — it is exactly what a discovery call is for. Flag it rather than guessing.
Decide constraints before you get attached to a design
Three constraints shape every project more than taste does: timeline, budget range, and who owns the work on your side. Saying them out loud early keeps the conversation honest.
A useful habit is to separate must-haves from nice-to-haves and be willing to cut the second list. A smaller project shipped well beats a large one that stalls halfway, because the budget ran out before the value arrived.
Put a number on the first release
Your first release does not need every feature — it needs the shortest path from visitor to outcome. Everything else can be phase two, once real usage shows you what matters.
What a good brief produces
When the brief covers audience, pages, integrations, content and constraints, a quote can be compared with another quote, because both are answering the same question. You should get a written scope, a timeline in phases, a price, and a list of what is explicitly not included.
| A quote you can compare | A guess in a nice PDF |
|---|---|
| Written scope, page by page | One lump-sum number |
| Phased timeline with assumptions | A single optimistic delivery date |
| Price with what is included stated | Price with "as discussed" |
| Explicit exclusions and change process | Silence on what happens next |
If a proposal arrives with none of that, the number in it is a guess — and guesses get corrected later, usually at your expense.
- 1 Write the one-sentence job the site must do.
- 2 List pages, integrations, content and roles.
- 3 Set timeline, budget range and an owner on your side.
- 4 Mark must-haves versus nice-to-haves and cut from the second list.
- 5 Ask for the quote against that written brief — then compare like with like.
Two follow-ups are worth reading before you brief anyone: what a business website costs in India, and whether you need a website or a web app.
The short version
Write one sentence for the job, inventory the pages and integrations, name your constraints, then ask for the quote. Send that same summary to us and we will give you an indicative scope, timeline and starting range.