What Should Be in a Web Development Quote?

A web development quote should name eleven things: scope, deliverables, exclusions, ownership, revisions, timeline with your obligations, payment schedule, the change-request rate, post-launch support, ongoing costs, and what happens if either side walks away. A quote missing any of them isn't cheaper — it's incomplete, and the gap becomes an invoice later.

This is the checklist version. Print it, open your quote beside it, and tick line by line. If you want the reasoning behind each check rather than the list, how to compare web developer quotes is the fuller version.

Want me to run this checklist over a quote you've received? Send it across — free, and I'll tell you if it's a good quote. Get in touch.

The checklist

1. Scope — what's being built

Pages named individually. Features described by what they do. Integrations named by product. If you can't tell from the quote what you're getting, neither can the developer — and that ambiguity resolves in whichever direction is cheaper for them once work starts.

What a missing line means: every future disagreement becomes your word against theirs.

2. Deliverables — what you actually receive

A live website is one deliverable. The others are frequently assumed and rarely listed: source code, design files, the CMS with your content in it, documentation, and any accounts created on your behalf.

3. Exclusions — the most-skipped line, and the most useful

Ask for this explicitly if it isn't there. Good providers write an exclusions list quickly, because they've been burned before; vague answers here are where variation invoices are born. The usual suspects: content writing, image licensing, migration of an existing site, redirect mapping, third-party subscription fees, training, and anything described in a meeting but not in the document.

4. Ownership — who owns what, and when

The clause should say that on final payment you own the code, the domain (registered in your name), the hosting account, and the design files. Get the specific list rather than a general assurance.

What a missing line means: you may be renting your website without knowing it. This is the single most expensive omission on the list, and it surfaces years later — see taking over a website from another developer for what it costs to unwind.

5. Revisions — how many, and what counts as one

A number, attached to a stage. "Two rounds at design, one at build" is a real term. "Unlimited revisions" is either untrue or already priced in. Check whether a round means one batch of consolidated feedback or one individual change — the difference is enormous.

6. Timeline — including what you have to do

Dates for the developer's milestones, and dates for your content, feedback and approvals. A timeline that names only their obligations will slip, and the argument about whose fault it was is avoidable by writing both sides down now.

7. Payment schedule

Roughly a third up front with the remainder tied to milestones or launch is standard for freelancers and small studios. 100% up front to someone you've never worked with is not, and it removes your only leverage if the project stalls. Watch for a final payment due before you've seen the finished site.

8. Change requests — the rate and the process

An hourly rate for out-of-scope work, and a stated process: request, written quote, approval, then work. NZ providers commonly bill changes at $50–$150/hr for content-level work and their standard rate above that.

What a missing line means: every new idea becomes a negotiation, and every verbal agreement becomes a dispute about what was agreed.

9. Post-launch support

Is there a warranty period on their own work, and how long? Thirty days of bug fixes on defects they introduced is a common and reasonable term. Distinguish clearly between fixing what's broken (should be free within the warranty) and changing what works (a change request).

10. Ongoing costs — all of them

Hosting, domain, SSL, maintenance, and any third-party subscriptions the build depends on. NZ published figures: hosting $39–$99/month, domain $25–$50/year, maintenance $50–$200/month. In Cyprus, maintenance runs €100–€500/month with hosting and domain around €80–€180/year.

Ask for the twelve-month total, not the build price. That's the number you're actually committing to.

11. What happens if either party walks away

The clause nobody wants to discuss and everybody needs. What do you owe for work completed? What do you receive — does partial work transfer to you, and in what form? How much notice does either side give? This matters most when the relationship is going badly, which is exactly when nobody wants to negotiate it from scratch.

Copy this into your reply

If a quote is missing several of the above, you don't need to write a careful email. Send this:

Thanks for this. Before I compare it properly, could you confirm in writing:

1. What's explicitly NOT included in this price?
2. On final payment, do I own the code, the domain (in my name),
   the hosting account and the design files?
3. How many revision rounds, at which stages, and does a round mean
   one batch of feedback or one change?
4. What do you need from me, and by when?
5. What's the payment schedule?
6. What's the rate for work outside this scope?
7. Is there a warranty period on defects after launch?
8. What are the total ongoing costs for the first 12 months?

Happy to jump on a call, but I'd like these in writing so I can
compare quotes side by side.

The wording of the answers usually tells you more than their content. Fast, specific replies mean someone who has done this before. Defensiveness about question 1 or question 2 is the signal you came for.

What a good quote looks like

It constrains the developer as much as it constrains you. It names what's excluded before you ask. It states what happens when things change, because things change. And it tells you what you have to do and when — which is the part that most often decides whether a project lands on time.

Frequently asked questions

What should a website quote include?

Scope with pages and features named, deliverables, an explicit exclusions list, an ownership clause covering code, domain, hosting and design files, the number of revision rounds and what counts as one, a timeline that names your obligations as well as theirs, a payment schedule, the rate for out-of-scope changes, any post-launch warranty, all ongoing costs, and what happens if either party terminates.

What's usually left out of a web development quote?

Exclusions, most often — which is why asking for them directly is the highest-value question you can ask. After that: content writing, image licensing, migration and redirect mapping from an old site, training and handover, third-party subscription fees, and the twelve-month total of hosting and maintenance rather than just the build price.

Is a one-page website quote a bad sign?

Length isn't the issue; specificity is. A one-page quote that names the pages, the exclusions, the ownership terms and the payment schedule is better than five pages of marketing copy around a single total. A quote reading "Website — $3,500" can't be compared with anything, and won't help either of you when you ask for something that was never priced.

Should a web developer quote include ongoing costs?

Yes, and a quote that omits them isn't cheaper — it's incomplete. Hosting, domain renewal, SSL, maintenance and any third-party subscriptions the build depends on all continue after launch. Ask for the twelve-month total, since that's the figure you're actually committing to rather than the one-off build price.

What if the developer won't put the scope in writing?

Treat that as your answer. "We'll figure it out as we go" reliably means you'll pay for it as you go, and without a written scope you have no basis for saying that something should have been included. Even a single page covering scope, price, timeline, ownership and payment protects both sides — and a developer who resists writing one is telling you how disputes will go.

Where to start

Send the eight questions above to everyone who has quoted you. It takes two minutes, the replies arrive in writing so you can compare them side by side, and the quality of the answers will sort the field faster than the prices will.

If you'd like a second opinion on what comes back, send it to me. Free, no expectation you hire me, and I'll say so if the quote is a good one. Get in touch, or see what I build.