Gian Luca Partengo Gian Luca Partengo

Guides

Website quote: what it should include and how to compare proposals properly

Two proposals with the same total can buy very different projects. Before price, compare scope, responsibilities, ownership, verifiable quality, future costs and the exit procedure.

The short answer

A useful quote does not merely state what the website costs: it defines what will be designed and delivered, who supplies content and external services, which checks are included, how changes are handled and what the client actually retains. If an item is not described, do not assume it is included.

Gian Luca Partengo

Gian Luca Partengo
Web developer since 1995 · Published

A quote is comparable only when it describes the same problem

Price is the last comparison column, not the first. At least four dimensions must be made equivalent beforehand.

SCOPE

What will be built

Pages, templates, languages, functions, integrations and quantities must be named. “Professional website” is not a measurable deliverable.

RESPONSIBILITIES

Who must supply what

Copy, images, legal information, translations, approvals and access credentials need an owner and a deadline.

QUALITY

What will be checked

Responsive behaviour, browsers, accessibility, technical SEO, security, performance and functions must be described as verifiable activities and outcomes.

AFTERWARDS

What happens at launch

Handover, support, maintenance, renewals, account ownership and the exit process affect the real cost.

Objectives and scope: define the expected outcome first

A list of pages without an objective produces a fragile estimate. The quote should connect the work to real users, actions and constraints.

01

Starting position

A new project, redesign, migration or expansion require different work. An existing website should be reviewed before it is estimated.

02

Audience and needs

Who needs to understand, find or complete what? The same organisation may have customers, partners, applicants and distributors with different journeys.

03

Website objectives

An enquiry, booking, sale, application, consultation or support request are not the same: they change architecture, content and testing.

04

Project boundaries

Locations, languages, markets, catalogues, restricted areas, payments and integrations must be explicitly included or excluded.

05

Completion criteria

Is the project finished when pages are designed, when content is loaded, or when journeys are tested on the public website? It must be written down.

06

Constraints and priorities

An event date, existing systems, obligations, budget and available assets may change the solution more than the number of pages.

Price bands and the factors that change a budget are covered in how much a professional website costs. Here, the point is to understand what that figure actually buys.

Pages, functions and deliverables: quantities need meaning

“Ten pages” can mean ten designed layouts or one template repeated ten times. A sound quote distinguishes quantities, types and depth of work.

01

Information architecture

Content map, navigation, hierarchy and journeys must either be included or clearly assigned.

02

Page templates

Homepage, service, archive, detail, contact and landing pages require different logic even when components are shared.

03

Functions

Forms, search, filters, bookings, payments, multilingual support and panels should be described alongside limits and failure cases.

04

Integrations

CRM, newsletters, maps, gateways, APIs and internal systems require access, documentation, testing and sometimes provider fees.

05

Delivered assets

Code, non-secret configuration, optimised images, documentation and credentials may each follow different handover conditions.

06

Environments and launch

Preview, domain, hosting, DNS, initial backup and publication need a named owner.

Custom work, templates and components: the technology’s name is not enough

A quote should explain where a project-specific solution is designed and where existing tools or components are reused.

DESIGN

Design or adaptation

“Custom” should identify which decisions arise from content, brand and objectives—not merely a colour change applied to a theme.

CODE

Technical base and customisation

Frameworks, CMSs, builders, libraries and proprietary code bring different licences, dependencies and responsibilities.

COMPONENTS

What is reused

Reusing proven systems is normal; you need to know whether the method, a component or the whole visual structure of another project is being reused.

DEPENDENCIES

Who can intervene later

Updates, supplier accounts, premium plugins and closed services can constrain maintenance, migration or a change of technical partner.

To distinguish architectures, read WordPress or a custom website; to assess process and supplier, also use how to choose who builds your website.

Content: who writes, approves and is responsible for supplied material

Copy and images affect timing, design, accessibility, SEO and responsibility. “Content excluded” cannot remain a generic note.

COPY

Writing, editing or layout

These are different activities. Clarify whether the professional writes, organises, edits or inserts material that has already been approved.

IMAGES

Production, selection and licences

Client photos, stock, illustrations and generated content require provenance, usage rights, formats and explicit responsibility.

TRANSLATIONS

Languages and localisation

Duplicating a page is not the same as translating it. Supply, native review and upload must be assigned.

APPROVALS

Decision-maker and response times

One decision-maker, complete material and approval windows prevent external delays being confused with production delays.

Domain, hosting and external services: ownership and costs must remain visible

A service purchased for the website does not automatically become part of the website. It has a contract, an account, a renewal and someone who controls access.

The GLP method

The client owns the services from day one

The domain, hosting, iubenda, Plausible, stock images, gateways and every other third-party purchase are registered by the client with their own details, paid using their own method and invoiced directly to them.

I access them as a technician when required, preferably through a separate, revocable role. At the end of the relationship, I do not need to transfer what is already under the client’s control. This is a transparent operating choice, not a universal legal guarantee.

01

Account holder

The quote should state who registers the service and which details identify the account owner.

02

Payment and invoice

Initial price, renewal, currency, taxes and the provider’s invoicing should not disappear inside an indistinct fee.

03

Access roles

Where the service allows it, technical access remains separate from the client’s primary credential.

04

Renewals and expiry

State who receives alerts and who decides whether to renew the domain, hosting, privacy service, analytics or other services.

05

Provider limits

Plans, quotas, APIs, support and unilateral changes belong to the relationship with the third party and can affect the project.

06

Exit

The client must be able to revoke the technician while retaining accounts, invoices, recovery options and control of purchased services.

Code, licences, material and source files: “the website is yours” is too vague

Ownership, rights of use, technical access and portability are not the same thing. The quote should point to clear terms consistent with applicable licences.

CODE

What is delivered

Executable files, source files, configuration and documentation must be distinguished from the supplier’s reusable internal tools.

LICENCES

What can be used or transferred

Fonts, stock, libraries and third-party software remain subject to their respective licences even when they appear in the project.

DATA

Who controls exports and access

Enquiries, orders, analytics and content need defined access, export, retention and deletion methods.

EXIT

How the relationship ends

Revoking technical access, final handover, transition support and any associated costs should be clear before they become urgent.

Important note

This guide helps describe a technical and commercial scope. Clauses, rights, responsibilities and legal applicability must be checked in the contract and, where necessary, with a legal professional.

For a full check of domains, hosting, accounts, data and portability, read who really owns your website.

SEO, GEO, accessibility, security and performance: ask for activities, not labels

Writing “SEO included” or “fast website” does not define any work. The quote should state what is designed, implemented and verified.

01

Technical SEO

URLs, status codes, titles, descriptions, canonicals, sitemaps, relevant structured data and migration need a concrete scope.

02

Relevant GEO and AEO

Readable HTML, entities, sources and direct answers help search and AI systems; no sound proposal can guarantee citations or rankings.

03

Accessibility

Semantics, keyboard use, focus, contrast, forms and errors should be integrated into the project; a full documented conformance review is a separate scope.

04

Security

Inputs, outputs, dependencies, privileges, secrets, headers, logs and updates require decisions proportionate to actual risk.

05

Performance

Images, fonts, CSS, JavaScript, server and cache are designed together. A single score does not replace real user behaviour.

06

Responsive testing

Viewports, browsers, keyboard, touch, reduced motion, errors and complete journeys need testing—not merely showing in a demo.

Revisions and change requests: defining change protects both parties

Revisions correct and refine what was agreed. A new function or different architecture changes the scope instead.

ROUNDS

How many review stages

The number matters less than the timing: wireframes, design, content and a functioning website require different approvals.

DECISION-MAKER

Who collects feedback

Conflicting comments from several people create rework; the process should identify who consolidates and approves.

CHANGE

What is outside scope

New pages, functions, languages, integrations or changed objectives should be estimated as a change request before work begins.

IMPACT

How time and price change

Each approved change should state its cost, effect on the date and dependencies, avoiding surprises at the end.

Timing, dependencies and commercial terms: a date without assumptions is not a plan

Delivery depends on technical work, but also on material, access, approvals and third-party responses.

01

Effective start

Acceptance, deposit, briefing, assets and access may be necessary conditions before the calendar begins.

02

Stages and milestones

Analysis, structure, design, development, content, testing and launch make progress observable.

03

Client dependencies

Missing feedback, copy, images, company details and credentials should transparently pause or reschedule the affected stage.

04

External dependencies

DNS, providers, APIs, gateways and account checks may have response times the technician does not directly control.

05

Payments

Amounts, tax basis, taxes, due dates, deposits and balance should be connected to clear conditions or milestones.

06

Validity and exclusions

Offer validity, expenses, travel, urgency and excluded work should be declared without relying on generic formulas.

Launch, redirects and SEO continuity: publication is a project stage

Uploading files does not complete a redesign. It needs a procedure, checks on the public result and assigned responsibilities.

PREPARATION

Access, backup and launch window

Hosting, DNS, certificates, backups and publication timing need to be available before the transition.

MIGRATION

URL map and redirects

During a redesign, every important address must remain, move, be replaced or end with the correct status.

CHECKS

Tests on the public website

Cache, assets, forms, email, analytics, robots, sitemap, canonicals and critical journeys must be checked in the environment actually served.

RECOVERY

Plan for critical failures

The quote should clarify who decides on a rollback, which evidence is retained and how a post-launch issue is handled.

For a redesign, the scope should reference the process in redesigning a website without losing SEO.

After launch: training, support, maintenance and renewals

Initial delivery and ongoing management are different services. Mixing them makes total cost impossible to understand.

WARRANTY

Correcting defects

Duration, reporting method and the line between a defect and a new request should be defined in the applicable terms.

TRAINING

Using delivered tools

Sessions, manuals, recordings and participant numbers should be included only where specified.

SUPPORT

On-demand work

Channel, hours, priority, rate and response should be distinguished from monitoring and ongoing maintenance.

RECURRING COSTS

What continues

Hosting, domain, privacy services, analytics, gateways, licences and care should appear with owner, frequency and a separate estimate.

To distinguish ongoing checks, updates and responsibilities, read website maintenance: what it includes and what it costs.

How to compare two quotes without being misled by the total

Copy the items into one table. Where a proposal is silent, write “not stated”: that is more accurate than inventing the answer.

ItemWhat should be writtenControl question
Objective and scopeAudience, actions, pages, functions, languages and boundariesDo both proposals solve the same problem?
Design and technologyDesign depth, technical base and reused componentsWhat is genuinely custom?
ContentWho writes, supplies, translates, licenses and approvesIs the material ready, and who is responsible?
External servicesAccounts, holder, renewals, costs and technical accessDoes the client retain direct control?
Ownership and licencesCode, data, assets, sources, usage rights and handoverWhat remains available at the end?
Technical qualityActivities and tests for SEO, accessibility, security and performanceWhich result is verified, and how?
RevisionsStages, rounds, decision-maker and change rulesWhen does a request become an extra?
TimingMilestones, dependencies, approvals and delay conditionsDoes the date account for assets and third parties?
LaunchBackups, DNS, redirects, public checks and incident handlingWho controls the transition, and with what plan?
After launchWarranty, training, support and maintenanceWhich work continues, and at what cost?
Commercial termsTax basis, taxes, due dates, validity and exclusionsDoes the total really include the same things?
ExitAccess revocation, exports, handover and technical transitionCan I change supplier without buying my services again?

Compare total cost, not just the deposit

A lower figure can be correct for a smaller scope. It becomes misleading only when differences, exclusions and recurring costs are not visible. An honest comparison does not seek the longest proposal; it seeks one precise enough to be verified.

Twelve questions to ask before accepting the quote

The answers should live in the proposal or linked terms, not depend on the memory of a phone call.

  1. 01

    Which problem and users does the project cover?

    Check that objectives and audience match the real need.

  2. 02

    Which pages, templates and functions are delivered?

    Count types and complexity, not merely a total number.

  3. 03

    What is custom and what is reused?

    Ask for transparency about templates, components, CMSs, frameworks and dependencies.

  4. 04

    Who produces and approves copy, images and translations?

    Assign responsibility, licences and dates to each item.

  5. 05

    Who opens and pays for external accounts?

    Prefer control, invoicing and recovery to sit directly with the client.

  6. 06

    Which code, data and assets do I receive?

    Distinguish ownership, licence, access, export and portability.

  7. 07

    Which technical checks are included?

    Look for concrete work on responsive behaviour, browsers, accessibility, SEO, security and performance.

  8. 08

    How do revisions and extras work?

    Stages, feedback, change requests and commercial impact should be predictable.

  9. 09

    Which materials does the schedule depend on?

    The date should account for feedback, access and external provider times.

  10. 10

    What does launch include?

    Backups, redirects, public checks, initial monitoring and incident handling are not automatic.

  11. 11

    Which costs continue after launch?

    Separate third-party renewals, on-demand support and scheduled maintenance.

  12. 12

    What happens if I change technical partner?

    Accounts, access, handover and any transition support need a process.

Primary sources supporting the guide’s technical criteria

These sources do not set project prices: they document responsibilities, migrations, accessibility, search, performance and security that a scope may include.

  1. ICANN — Information for Domain Name Registrants

    Definition of a registrant and rights concerning domain registration, management, transfer, renewal and recovery.

    Open source
  2. Google Search Central — Site moves and migrations

    URL mapping, permanent redirects, canonicals, links, sitemaps, checks and monitoring required for a migration.

    Open source
  3. Google Search Central — Developer guide

    Security, speed, accessibility, devices and Google readability as parts of a website’s technical quality.

    Open source
  4. W3C WAI — Planning and Policies

    Accessibility planning, roles, responsibilities and user involvement throughout the project.

    Open source
  5. W3C WAI — Implement

    Including accessibility requirements in requests for quotations, contracts and checks during development.

    Open source
  6. W3C — WCAG 2.2

    Technical recommendation for making web content more accessible and a verifiable basis for defining a conformance target.

    Open source
  7. web.dev — Web Vitals

    Real-experience metrics, the distinction between laboratory and field data, and measuring loading, interactivity and stability.

    Open source
  8. OWASP — Application Security Verification Standard

    Verifiable requirements for defining and checking application security without relying on a generic label.

    Open source

Sources reviewed and verified on 5 October 2026. Services, interfaces, standards and provider terms can change: always check current versions and the terms applicable to the project.

Frequently asked questions about website quotes

Direct answers to the ambiguities that make comparison difficult.

What should a website quote include?

At minimum: objectives, scope, deliverables, content responsibilities, technology, external services, technical quality, revisions, timing, commercial terms, launch, support, recurring costs, ownership and exclusions. Detail should be proportionate to the project.

How do I compare two quotes with very different prices?

Move the items into a common table and mark each one as included, optional, separately quoted, purchased from a third party or not stated. Only then compare the total and lifetime cost.

Is the number of pages enough to set the price?

No. Different templates, content volumes, functions, integrations, languages, migration, testing and responsibilities matter. Ten pages based on one template are not the same as ten separately designed journeys.

Should domain and hosting be included in the price?

They can be included or separate, but the account holder, provider, renewal, invoice and access must be clear. Under the GLP method, the client purchases them directly and grants technical access where necessary.

What does “SEO included” mean?

On its own, it is too vague. It should at least identify the planned work on URLs, metadata, canonicals, sitemaps, relevant structured data, HTML, redirects and checks. It is not a ranking guarantee.

Are accessibility and security always included?

The quote should say. A structural foundation may be the supplier’s standard, while audits, documented tests, specific adaptations or conformance reviews may be separate services.

How many revisions should be included?

There is no universal number. It is more useful to define stages, decision-maker, feedback times and the distinction between refining approved work and a new request that changes scope.

Should the quote include maintenance?

Not necessarily. It should clarify warranty, initial support, training, optional maintenance and recurring costs so that delivery is not confused with ongoing management.

What should I receive at the end of the project?

It depends on the agreement and licences: access, code, non-secret configuration, assets, data, documentation and any source files should be listed. “The website is yours” does not replace this information.

Is a very short quote necessarily unreliable?

No. It may refer to well-built specifications and terms. It becomes risky when scope, responsibilities, exclusions and ownership are left to interpretation or verbal promises.

Did you find this guide useful? Share it.

No social tracker loads before you choose an action.

Next step

Want a clear scope before comparing the price?

GLP services separate what is included, optional, purchased from third parties and quoted separately. Start with the objective: the proposal should describe the project you actually need.

Test evidence

IT/EN homepages: 100 median in every category

Five tests per language and device profile: 20 live checks. Median 100 in every category; Performance 99–100, Accessibility, Best Practices and SEO 100 throughout the final series. These results describe the lab tests, not every visit or every page on this website.

Original mobile Lighthouse screenshot of the Italian homepage, run 3 on 5 October 2026: 100 for Performance, Accessibility, Best Practices and SEO.
5 October 2026 · Italian homepage · mobile · run 3, selected by median LCP Open the verifiable report Method, all results and IT/EN reports
History · 28 July 2026
Historical mobile PageSpeed Insights result from 28 July 2026: 100 in all four categories. Open the original screenshot.
Google PageSpeed Insights · Lighthouse mobile · 28 July 2026 Historical PageSpeed Insights report
© 1995–2026 Gian Luca Partengo · All rights reserved.

GLP AI

GLP AI assistant

Answers based on the public content of this website.

Tell me what you need from your website. I will look through GLP services and Articles and point you towards the most relevant route.

Ready

You are interacting with an AI system, which can make mistakes: its answers are not binding quotations. Do not enter personal, sensitive or confidential data. Questions are sent to OpenAI to generate the answer and are not saved by this website. Read the Privacy Policy.

Search