SCOPE
What will be built
Pages, templates, languages, functions, integrations and quantities must be named. “Professional website” is not a measurable deliverable.
Guides
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.
Price is the last comparison column, not the first. At least four dimensions must be made equivalent beforehand.
SCOPE
Pages, templates, languages, functions, integrations and quantities must be named. “Professional website” is not a measurable deliverable.
RESPONSIBILITIES
Copy, images, legal information, translations, approvals and access credentials need an owner and a deadline.
QUALITY
Responsive behaviour, browsers, accessibility, technical SEO, security, performance and functions must be described as verifiable activities and outcomes.
AFTERWARDS
Handover, support, maintenance, renewals, account ownership and the exit process affect the real cost.
A list of pages without an objective produces a fragile estimate. The quote should connect the work to real users, actions and constraints.
A new project, redesign, migration or expansion require different work. An existing website should be reviewed before it is estimated.
Who needs to understand, find or complete what? The same organisation may have customers, partners, applicants and distributors with different journeys.
An enquiry, booking, sale, application, consultation or support request are not the same: they change architecture, content and testing.
Locations, languages, markets, catalogues, restricted areas, payments and integrations must be explicitly included or excluded.
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.
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.
“Ten pages” can mean ten designed layouts or one template repeated ten times. A sound quote distinguishes quantities, types and depth of work.
Content map, navigation, hierarchy and journeys must either be included or clearly assigned.
Homepage, service, archive, detail, contact and landing pages require different logic even when components are shared.
Forms, search, filters, bookings, payments, multilingual support and panels should be described alongside limits and failure cases.
CRM, newsletters, maps, gateways, APIs and internal systems require access, documentation, testing and sometimes provider fees.
Code, non-secret configuration, optimised images, documentation and credentials may each follow different handover conditions.
Preview, domain, hosting, DNS, initial backup and publication need a named owner.
A quote should explain where a project-specific solution is designed and where existing tools or components are reused.
DESIGN
“Custom” should identify which decisions arise from content, brand and objectives—not merely a colour change applied to a theme.
CODE
Frameworks, CMSs, builders, libraries and proprietary code bring different licences, dependencies and responsibilities.
COMPONENTS
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
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.
Copy and images affect timing, design, accessibility, SEO and responsibility. “Content excluded” cannot remain a generic note.
COPY
These are different activities. Clarify whether the professional writes, organises, edits or inserts material that has already been approved.
IMAGES
Client photos, stock, illustrations and generated content require provenance, usage rights, formats and explicit responsibility.
TRANSLATIONS
Duplicating a page is not the same as translating it. Supply, native review and upload must be assigned.
APPROVALS
One decision-maker, complete material and approval windows prevent external delays being confused with production delays.
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 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.
The quote should state who registers the service and which details identify the account owner.
Initial price, renewal, currency, taxes and the provider’s invoicing should not disappear inside an indistinct fee.
Where the service allows it, technical access remains separate from the client’s primary credential.
State who receives alerts and who decides whether to renew the domain, hosting, privacy service, analytics or other services.
Plans, quotas, APIs, support and unilateral changes belong to the relationship with the third party and can affect the project.
The client must be able to revoke the technician while retaining accounts, invoices, recovery options and control of purchased services.
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
Executable files, source files, configuration and documentation must be distinguished from the supplier’s reusable internal tools.
LICENCES
Fonts, stock, libraries and third-party software remain subject to their respective licences even when they appear in the project.
DATA
Enquiries, orders, analytics and content need defined access, export, retention and deletion methods.
EXIT
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.
Writing “SEO included” or “fast website” does not define any work. The quote should state what is designed, implemented and verified.
URLs, status codes, titles, descriptions, canonicals, sitemaps, relevant structured data and migration need a concrete scope.
Readable HTML, entities, sources and direct answers help search and AI systems; no sound proposal can guarantee citations or rankings.
Semantics, keyboard use, focus, contrast, forms and errors should be integrated into the project; a full documented conformance review is a separate scope.
Inputs, outputs, dependencies, privileges, secrets, headers, logs and updates require decisions proportionate to actual risk.
Images, fonts, CSS, JavaScript, server and cache are designed together. A single score does not replace real user behaviour.
Viewports, browsers, keyboard, touch, reduced motion, errors and complete journeys need testing—not merely showing in a demo.
Revisions correct and refine what was agreed. A new function or different architecture changes the scope instead.
ROUNDS
The number matters less than the timing: wireframes, design, content and a functioning website require different approvals.
DECISION-MAKER
Conflicting comments from several people create rework; the process should identify who consolidates and approves.
CHANGE
New pages, functions, languages, integrations or changed objectives should be estimated as a change request before work begins.
IMPACT
Each approved change should state its cost, effect on the date and dependencies, avoiding surprises at the end.
Delivery depends on technical work, but also on material, access, approvals and third-party responses.
Acceptance, deposit, briefing, assets and access may be necessary conditions before the calendar begins.
Analysis, structure, design, development, content, testing and launch make progress observable.
Missing feedback, copy, images, company details and credentials should transparently pause or reschedule the affected stage.
DNS, providers, APIs, gateways and account checks may have response times the technician does not directly control.
Amounts, tax basis, taxes, due dates, deposits and balance should be connected to clear conditions or milestones.
Offer validity, expenses, travel, urgency and excluded work should be declared without relying on generic formulas.
Uploading files does not complete a redesign. It needs a procedure, checks on the public result and assigned responsibilities.
PREPARATION
Hosting, DNS, certificates, backups and publication timing need to be available before the transition.
MIGRATION
During a redesign, every important address must remain, move, be replaced or end with the correct status.
CHECKS
Cache, assets, forms, email, analytics, robots, sitemap, canonicals and critical journeys must be checked in the environment actually served.
RECOVERY
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.
Initial delivery and ongoing management are different services. Mixing them makes total cost impossible to understand.
WARRANTY
Duration, reporting method and the line between a defect and a new request should be defined in the applicable terms.
TRAINING
Sessions, manuals, recordings and participant numbers should be included only where specified.
SUPPORT
Channel, hours, priority, rate and response should be distinguished from monitoring and ongoing maintenance.
RECURRING COSTS
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.
Copy the items into one table. Where a proposal is silent, write “not stated”: that is more accurate than inventing the answer.
| Item | What should be written | Control question |
|---|---|---|
| Objective and scope | Audience, actions, pages, functions, languages and boundaries | Do both proposals solve the same problem? |
| Design and technology | Design depth, technical base and reused components | What is genuinely custom? |
| Content | Who writes, supplies, translates, licenses and approves | Is the material ready, and who is responsible? |
| External services | Accounts, holder, renewals, costs and technical access | Does the client retain direct control? |
| Ownership and licences | Code, data, assets, sources, usage rights and handover | What remains available at the end? |
| Technical quality | Activities and tests for SEO, accessibility, security and performance | Which result is verified, and how? |
| Revisions | Stages, rounds, decision-maker and change rules | When does a request become an extra? |
| Timing | Milestones, dependencies, approvals and delay conditions | Does the date account for assets and third parties? |
| Launch | Backups, DNS, redirects, public checks and incident handling | Who controls the transition, and with what plan? |
| After launch | Warranty, training, support and maintenance | Which work continues, and at what cost? |
| Commercial terms | Tax basis, taxes, due dates, validity and exclusions | Does the total really include the same things? |
| Exit | Access revocation, exports, handover and technical transition | Can 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.
The answers should live in the proposal or linked terms, not depend on the memory of a phone call.
Check that objectives and audience match the real need.
Count types and complexity, not merely a total number.
Ask for transparency about templates, components, CMSs, frameworks and dependencies.
Assign responsibility, licences and dates to each item.
Prefer control, invoicing and recovery to sit directly with the client.
Distinguish ownership, licence, access, export and portability.
Look for concrete work on responsive behaviour, browsers, accessibility, SEO, security and performance.
Stages, feedback, change requests and commercial impact should be predictable.
The date should account for feedback, access and external provider times.
Backups, redirects, public checks, initial monitoring and incident handling are not automatic.
Separate third-party renewals, on-demand support and scheduled maintenance.
Accounts, access, handover and any transition support need a process.
These sources do not set project prices: they document responsibilities, migrations, accessibility, search, performance and security that a scope may include.
Definition of a registrant and rights concerning domain registration, management, transfer, renewal and recovery.
URL mapping, permanent redirects, canonicals, links, sitemaps, checks and monitoring required for a migration.
Security, speed, accessibility, devices and Google readability as parts of a website’s technical quality.
Accessibility planning, roles, responsibilities and user involvement throughout the project.
Including accessibility requirements in requests for quotations, contracts and checks during development.
Technical recommendation for making web content more accessible and a verifiable basis for defining a conformance target.
Real-experience metrics, the distinction between laboratory and field data, and measuring loading, interactivity and stability.
Verifiable requirements for defining and checking application security without relying on a generic label.
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.
Direct answers to the ambiguities that make comparison difficult.
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.
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.
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.
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.
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.
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.
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.
Not necessarily. It should clarify warranty, initial support, training, optional maintenance and recurring costs so that delivery is not confused with ongoing management.
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.
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.
Next step
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.