DevGurux thumbnail for a website development quote checklist, showing a developer reviewing scope, pricing, timeline, payment terms and support.
|

What Should a Website Development Quote Include? 12 Things to Check

A website quote should tell you more than a total price. It should explain what will be built, what you need to provide, how revisions work, who owns the finished website, and what happens after launch. If those details are missing, two quotes that look similar on the surface may describe very different projects.

Use this checklist before you hire a freelancer or agency. It is designed for small-business owners comparing proposals for a new website, redesign, WordPress build, or online store. You do not need to understand every technical term; you do need clear answers in writing.

At a glance: the 12 things every website quote should clarify

  1. Business goals and project scope
  2. Pages, templates, and content responsibilities
  3. Design process and what “custom” means
  4. Features, integrations, and functionality
  5. Mobile, accessibility, and browser testing
  6. SEO and analytics deliverables
  7. Performance, security, and backups
  8. Hosting, domain, licences, and third-party costs
  9. Timeline, milestones, and dependencies
  10. Revisions, approvals, and change requests
  11. Ownership, access, and handover
  12. Support, maintenance, and payment terms

1. Business goals and a defined scope

A useful proposal starts with the outcome the website needs to support. Is the priority qualified enquiries, phone calls, online sales, appointment bookings, or explaining a complex service? The quote should connect the proposed work to that goal.

Look for a written scope that identifies the main audience, the primary calls to action, the required sections, and what is explicitly excluded. “Build a professional website” is not a scope. “Build a five-page service website with a contact form, service-area section, and editable testimonials” is much easier to evaluate.

Ask: What exactly will be delivered, and what is not included in this price?

2. Pages, templates, and content responsibilities

Count the pages or page templates included. A quote may include five designed page layouts but require you to add the content for ten service locations yourself. That can be reasonable, but it must be clear before work begins.

Confirm who writes and edits copy, sources images, enters products, supplies legal policies, and checks factual details. If the developer is migrating an existing site, ask whether old URLs, images, forms, and blog posts are included.

Ask: How many unique page layouts and how many total pages are included? Who supplies the final text and images?

3. Design process and what “custom” means

“Custom design” can mean anything from a tailored theme configuration to a fully bespoke design system. Ask which approach is proposed, whether a theme or page builder will be used, and what you will review before development is complete.

A sensible process usually includes a direction or wireframe, a design review, implementation, and a chance to check the working site. You should know whether the quote includes responsive layouts, brand styling, and the design of important states such as form errors or empty shopping carts.

Ask: What will I see and approve before the full build is completed?

4. Features, integrations, and functionality

List each functional requirement rather than relying on broad labels such as “dynamic,” “advanced,” or “fully functional.” A contact form, appointment scheduler, membership area, product catalogue, payment gateway, CRM connection, and multilingual setup all involve different work.

For every integration, identify the service, account owner, subscription cost, and who is responsible for configuration. Also ask whether the quote includes testing the complete journey—for example, a booking confirmation or a successful test payment—not just placing a button on the page.

Ask: Which features are included, which rely on paid third-party services, and who pays those recurring fees?

5. Mobile, accessibility, and browser testing

Responsive design should be part of the agreed deliverable, not an optional afterthought. Ask how the site will be checked on common phone, tablet, and desktop screen sizes, and which browsers will be tested.

Clarify the accessibility basics included in the project: semantic headings, keyboard-operable navigation, visible focus states, form labels, sufficient colour contrast, and useful alternative text for meaningful images. A quote should not promise perfect compliance without defining a standard and testing process.

Ask: What devices, browsers, and accessibility checks are included before launch?

6. SEO and analytics deliverables

Be precise about what “SEO included” means. A responsible website build can include crawlable page structure, editable title tags and meta descriptions, logical headings, descriptive URLs, image alt text where appropriate, XML sitemap support, canonical handling, and redirects for URLs that change.

It may also include connecting analytics and search performance tools, but those are separate tasks that should be named. Content strategy, keyword research, link building, ongoing publishing, and ranking improvements are not automatically included just because a proposal says “SEO-friendly.” No developer can guarantee a first-place Google or Bing ranking.

Ask: Which specific technical SEO tasks will be completed, and what ongoing SEO work is outside the scope?

7. Performance, security, and backups

Ask what the developer will do to avoid unnecessary scripts, oversized images, and plugin bloat. Find out whether performance will be measured and whether the handover will include the results. A target should be realistic and tested on the actual site; a guaranteed score or load time without conditions is not a meaningful promise.

For security, clarify whether the work includes SSL configuration, software updates, spam protection, form safeguards, backups, and a recovery plan. A one-time build is not the same thing as ongoing monitoring or maintenance.

Ask: What performance and security checks are included, and who maintains them after launch?

8. Hosting, domain, licences, and third-party costs

The development fee is only one part of the website’s total cost of ownership. Your domain, hosting, premium themes or plugins, email, payment processing, booking software, stock images, and maintenance may be billed separately.

Ask for a list of recurring charges, their billing frequency, and the account that owns each subscription. Ideally, domain registration, hosting, analytics, and paid service accounts should be registered to your business, with the developer granted the access needed to work.

Ask: What will I pay once, what will I pay monthly or annually, and which accounts will be in my name?

9. Timeline, milestones, and dependencies

A timeline should show the major stages: discovery, content collection, design, development, review, testing, and launch. It should also identify what the developer needs from you and when. Delayed copy, product data, approvals, or account access can move a launch date.

Ask whether the schedule uses calendar days or business days and whether the clock starts after the deposit, signed agreement, or receipt of all materials. A realistic timeline is more useful than an impressive but unexplained promise.

Ask: What are the milestones, what do you need from me at each stage, and how are delays handled?

10. Revisions, approvals, and change requests

Every proposal should explain how feedback is collected and how many revision rounds are included at each stage. It should distinguish corrections to work that does not match the agreed brief from new requests that expand the project.

For out-of-scope work, ask for a written change request with the added cost and schedule impact before the work starts. This protects both sides from surprise invoices and misunderstandings.

Ask: How many revision rounds are included, and how will additional work be priced and approved?

11. Ownership, access, and handover

Do not leave ownership vague. The agreement should state who owns the final design and custom code after payment, what happens to any pre-existing themes or third-party components, and whether you receive administrator access and a copy of the site.

At handover, you should know how to update ordinary content, manage forms or orders, access hosting and domain accounts, and request support. If the site is built on WordPress, confirm that you will receive an administrator account and that any paid licences can be transferred or renewed appropriately.

Ask: What exactly will I own, what access will I receive, and what training or handover documentation is included?

12. Support, maintenance, and payment terms

Ask how long post-launch bug fixes are covered, what counts as a defect, and how quickly urgent issues are handled. Ongoing maintenance—updates, backups, monitoring, content changes, and new features—should be described separately with its own price and cancellation terms.

Payment milestones should be tied to understandable deliverables or review points. The agreement should state the currency, due dates, accepted payment methods, taxes if applicable, and what happens if either side pauses or ends the project.

Some providers require an upfront deposit; others may agree to staged payments. Neither arrangement is automatically safer. What matters is a written scope, visible progress, clear acceptance criteria, and a payment schedule both parties understand.

Ask: When is each payment due, what does each milestone represent, and what support is included after launch?

How to compare two website quotes fairly

Do not compare only the headline price. Put the proposals side by side and mark each item as included, excluded, optional, or unclear. Then compare the total first-year cost—not just the build fee—including hosting, licences, integrations, and maintenance.

CompareQuote AQuote B
Pages and templatesCount and listCount and list
Content and migrationIncluded / excludedIncluded / excluded
Required featuresNamed and testedNamed and tested
Technical SEO and analyticsSpecific tasksSpecific tasks
Hosting and licencesOne-time + recurringOne-time + recurring
Revisions and change requestsRounds and ratesRounds and rates
Ownership and handoverAccess and rightsAccess and rights
Support after launchDuration and termsDuration and terms
Total first-year cost

CalculateCalculate

If a quote is much cheaper, find out what has been left out before assuming it is better value. If it is much more expensive, ask which additional deliverables, expertise, or ongoing responsibilities justify the difference.

A simple website quote request you can copy

Send the same brief to each provider so you can compare like with like:

I need a website for [business type] whose main goal is [leads / bookings / sales / information]. The intended audience is [audience and location].

Please quote for [number] pages, including [list the key pages]. Required features: [forms, booking, ecommerce, integrations, languages, or other requirements].

Please itemise the design and development scope, content responsibilities, technical SEO, mobile and browser testing, hosting and third-party costs, timeline, revision rounds, payment milestones, ownership, handover, and post-launch support. Please identify all exclusions and recurring fees.

This brief will not replace a discovery conversation, but it gives every provider the same starting point.

Estimate your budget before requesting proposals

If you are still deciding which features you need, start with the DevGurux website cost calculator. It provides an initial planning estimate based on project type, page count, platform, and features. Treat the result as a guide for planning—not a fixed quote or a substitute for reviewing scope.

When you are ready to discuss a project, review our website design and development services or learn what to look for when you hire a web developer. We agree on deliverables, timeline, responsibilities, and payment milestones in writing before work begins.

Frequently asked questions

How detailed should a website development quote be?

It should define the deliverables, number of pages or templates, functionality, content responsibilities, timeline, revision rules, costs, ownership, handover, and support. If a detail could change the price or launch date, get it in writing.

Should a website quote include SEO?

It can include foundational technical SEO tasks such as editable metadata, crawlable structure, sitemap support, and redirects where required. Ongoing content, link building, and ranking work should be scoped and priced separately.

Are hosting and maintenance included in the website development price?

Sometimes, but never assume so. Ask whether hosting, domain renewal, premium licences, backups, updates, monitoring, and support are included, and identify recurring costs separately.

Who should own the website and domain?

In most small-business projects, the business should control its domain, hosting, analytics, and key third-party accounts. The agreement should also explain ownership of the finished work and any third-party components.

Can a developer guarantee Google rankings?

No. A developer can implement technical foundations and improve usability and performance, but search rankings depend on many factors outside a developer’s control. Be cautious of guaranteed positions or traffic promises.

Final checklist: do not approve the quote until these are clear

  • The scope, page count, features, and exclusions are written down.
  • You know who supplies content, images, and account access.
  • Testing, technical SEO, and launch tasks are defined.
  • One-time fees and recurring costs are separated.
  • The timeline, milestones, revisions, and change process are clear.
  • Ownership, administrator access, handover, and support are agreed.
  • Currency and payment dates are stated in the contract.

A good website proposal makes the work understandable before money changes hands. Choose the provider whose scope, communication, and handover you can evaluate—not simply the proposal with the lowest number.

Similar Posts