How-to guides 7 min read · published September 23, 2026 · updated September 23, 2026

Website quotes: what should you check before signing?

Wail Saidani Wail Saidani Founder of DevDream
Summarize this article with: Claude ChatGPT Perplexity Le Chat Grok
Illustration: a scale compares the same elements of two website projects
Illustration: to compare two estimates, start with the same services.

Before signing a website quote, check which pages are included, who prepares the content, what will be tested before delivery and what costs remain afterward. Compare proposals on those same points, not just the final price. Ask for a written answer to any unclear line before agreeing.

"Professional, modern and optimized website" can describe very different services. My approach is simple: replace each promise with something you can see, use or verify. Your quote then becomes a clear basis for discussion.


How can you compare website quotes on equal terms?

Describe the result you need in the same terms to each provider. List the pages you need and the main action visitors should take: call, send an inquiry or book. Then label each response as included, optional, your responsibility or needing clarification. A service left unmentioned in a quote cannot be assumed to be included or excluded.

Point to compareQuestion to askResponse to note for each offer
PagesWhich pages will actually be delivered?Exact page list and any special pages
Copy and photosWho produces, corrects and integrates the content?Who is responsible for each task
Contact optionsWhere does the visitor's request arrive?Destination and planned test
ChangesWhat revisions are included before approval?Stages, limits and cost of additions
After deliveryWhich interventions remain included?Duration, scope and conditions

Copy this table and add a column for each proposal. A "needs clarification" box is a question to resolve, rather than a fault to assume. A short offer can be completed; a long offer may leave unclear areas.

A project brief is simply a document describing your needs. France Num provides templates for preparing that brief and tracking the work. For a small business website, adapt them to your project: you do not need a public-procurement-style document.


Who prepares the website copy, photos and information?

Distinguish creating the content from adding it to the pages. "Client-supplied content" means you are expected to contribute; it does not say who rewrites the copy, chooses the photos or checks that everything is complete. Ask for a clear split of responsibilities and a list of what is needed to start and publish.

  • You: business details, actual services, contact information and approval of any claims.
  • The provider, if agreed: writing, image selection, layout and the agreed revisions.
  • To clarify: image purchases, photography, translations and legally required content.

For example, imagine an electrician requesting an "electrical renovation" page. Supplying a list of services is a different task from turning that list into clear website copy. The quote should make clear which task has been priced.

A delivery deadline only makes sense when its starting point is clear. Does it run from signing, project kickoff or receipt of the content? Ask what happens if a photo or approval is missing. To prepare your images, use my guide to photos for a contractor website.

Let's start with what your site actually needs to do. 5.0/5 on Google · 16 reviews
Let's talk

How to check that the delivered site really works?

Plan an acceptance review: a check before you approve the website. It should cover the agreed features and important visitor journeys. A screenshot of the homepage shows the design; it does not prove an inquiry reaches you. Ask for a demonstration on a working version and a record of the checks performed.

Illustration: a site model delivered in a trunk with its key and the elements to be checked
Illustration: upon delivery, check the site, the access provided and the planned follow-up.
Estimate promisePractical checkUseful evidence
Mobile friendlyRead the pages and use the menu on a phonePages tested and issues corrected
Contact formSend a test request and check receiptMessage received in the right inbox
BookingGo through the steps until confirmationTest appointment and notification
Editable websiteMake an agreed content change yourselfWorking access and a demonstration
Replacing an existing websiteOpen important old URLsList of checked destinations

Match the tests to the project. A website without a form does not need one just to check a box: a call button or booking link may meet the need. The expected proof must correspond to the promised service.

Good to know

If the website collects contact details, its form also needs appropriate information about how the data is used. In France, the CNIL provides examples of notices. Clarify who prepares this information and who approves it; a checkbox alone does not settle every question.


What should a promise of included SEO actually specify?

Ask for a list of actions delivered at launch, and distinguish them from work after publication. Writing page titles, checking that Google can access the pages and organizing content differs from tracking results each month. The proposal should name the tasks, pages involved and deliverables.

  • What pages and content will be worked on?
  • What checks will be carried out when it is put online?
  • Will there be follow-up, with what reports and corrections?

A service can involve specific work without guaranteeing a place in Google. Google says no one can guarantee top position. So ask for commitments on actions and their verification, rather than a promise of unconditional ranking.

To see how this fits into the wider project, read about professional website design. The goal is a useful website for visitors, with room to explain each service clearly.


What will you still need to pay for and manage after launch?

Separate the initial design cost from recurring expenses and one-off changes. Ask what each renewal covers, who pays and what happens if it stops. Distinguish fixing something that fails to meet the agreed scope from adding a new requirement. The terms should be explicit.

  • Domain name and hosting: account ownership, expiry dates and renewals.
  • External services: booking, email or other necessary subscriptions.
  • Changes: what is included, how new requests work and how they are priced.

Also check the access and documents provided. The subject of property deserves a separate reading: what to check to keep control of your site. To compare amounts, the article on contractor website costs adds context to this table.


What should you ask before agreeing?

Your final discussions should resolve anything that affects the decision: what you receive, what you provide and what triggers an extra charge. Keep these answers with the chosen proposal. Here are useful questions when a quote is too brief or a new idea comes up during the project.

Ask for a list of the pages, features and services included, plus the content responsibilities. A short document is not automatically bad; it needs enough detail, possibly in an appendix, to show what will be delivered.

If you want to make changes yourself, specify which changes and ask for a demonstration. Not every project needs an editing dashboard. What matters is knowing how an update works and what it costs.

Ask whether it fits the agreed scope. If it does not, clarify the price, schedule impact and approval process before the work starts. Adding a page differs from fixing a broken link.


What should you clarify before signing?

You should be able to explain what will be prepared, published and followed up, with someone responsible for each stage. If an answer is missing, ask for it in the proposal or accompanying documents. I recommend settling these points before negotiating design details: they define what you are buying.

StepWhat to obtainMistake to avoid
PreparationPages, content, responsibilities and scheduleFinding out later that the copy was your responsibility
PublicationScheduled testing and proof of deliveryApproving only the appearance
SupportAccess, renewals and interventionsConfusing a correction with a new request

Bring your list of pages, your objective and your remaining questions: let's talk about the scope of your project. A useful comparison begins with clear answers.

Portrait of Wail Saidani, founder of DevDream
Published September 23, 2026 · updated September 23, 2026 Wail Saidani

Founder of DevDream, a web and AI workshop for contractors and small businesses in Villeneuve-la-Garenne, near Paris, France (92). I build websites and help small businesses improve local visibility.

Follow me on LinkedIn →

Need to clarify your website project?

An introductory conversation to clarify your needs, content and what to plan for.

Discuss my project →