Getting a Website Quote: How It Works, What to Check, and Pitfalls to Avoid

You have decided to invest in a professional website. You reach out to a few developers, and soon you have a handful of quotes in your inbox. One is €600. Another is €3,500. A third is €8,000. They all seem to describe roughly the same project. How do you know which one is serious, which is a trap, and which is simply overpriced?

Getting a website quote is a skill — and most small business owners have never had to develop it before. This guide walks you through the entire process, from first contact to signed contract, with a clear focus on what separates a trustworthy proposal from one that will cause you problems.

Step 1: The discovery call

Before any developer sends you a quote, there should be a conversation. This is called a discovery call, and it is where a serious professional learns about your business, your goals, and your constraints.

A good discovery call covers:

• What your business does and who your clients are
• What the website needs to achieve (generate leads, sell products, inform, book appointments)
• Whether you have existing branding, content, or photos — or whether these need to be created
• Your timeline and your rough budget range
• Any specific technical requirements (booking system, online payment, multilingual content, integration with your existing tools)

If a developer sends you a quote without any of this conversation — based only on a short email you sent — be cautious. They may be quoting a template they will apply regardless of your actual needs. A quote built without understanding your business is rarely accurate and even less rarely right for you.

Step 2: The brief

After the discovery call, a well-organised developer will summarise what they understood in a written brief — a short document describing the scope of the project, the pages included, the functionality required, and the key objectives.

You should read this brief carefully. Does it match your understanding of what was discussed? Are there things missing that you assumed were included? Are there items listed that you do not actually need?

The brief is the foundation of the quote. If the brief is wrong, the quote will be wrong. And if there is no brief at all — if the developer skips straight to sending a price — you have no shared understanding of what is being built, which leads to disputes, extra charges, and disappointment.

Some developers call this a "specification document" or a "scope of work." The name matters less than the principle: before money is discussed, you should both be describing the same project.

Step 3: The proposal

A professional website proposal is more than a number at the bottom of an email. Here is what a good proposal contains:

A summary of your project as understood. This confirms that the developer listened and understood what you need. It should be specific to your business — not a generic paragraph that could describe any client.

A list of deliverables. Exactly what is included: how many pages, which specific features (contact form, photo gallery, booking system, e-commerce, blog), which languages if applicable, whether copywriting or photography is included or excluded.

A fixed price or clearly bounded estimate. For most small business sites, a fixed price is the right structure — you know what you will pay, full stop. An open-ended "depends on how long it takes" quote puts all the financial risk on you. If the developer works on an hourly basis, the proposal should clearly estimate the total hours and cap the maximum.

A payment schedule. Typically a deposit upfront (30 to 50%), a milestone payment mid-project, and a final payment on delivery. Avoid any arrangement that requires full payment before work begins, or where no payment is due until the very end — both are unusual and both carry risk.

A timeline. A realistic schedule with key milestones: when you will receive a first draft, when you will provide feedback, when the site will be tested, when launch is targeted. This does not have to be exact, but it should be specific enough to set expectations.

What is explicitly not included. Good proposals are clear about exclusions: SEO content writing, professional photography, domain name purchase, hosting costs, ongoing maintenance. These items may come later, but they should not be surprises.

Post-launch support. What happens if something breaks after the site goes live? Is there a warranty period? How are small corrections handled?

Red flags to watch for

Not every developer you contact will be equally serious. Here are the warning signs that should make you slow down or walk away.

Vague deliverables. "A modern website with good design" is not a deliverable. A professional proposal lists exactly what is being built, page by page, feature by feature. Vagueness protects the developer, not you.

No contract. A quote is not a contract. A professional project has a written contract — even a simple one — that specifies the scope, the price, the timeline, the payment terms, and what happens in the event of disputes or significant changes. If someone resists putting things in writing, that is a serious warning sign.

Suspiciously low prices. A website that genuinely required 40 hours of skilled work cannot be delivered for €300. Ultra-low prices almost always mean one of three things: a template with minimal customisation, work delegated to an offshore subcontractor with no oversight, or a developer who will disappear mid-project. The question to ask is not "is this cheap?" but "how is this possible at this price?"

No questions about your business. A developer who quotes without understanding your clients, your goals, or your competitive context will build something generic. Generic websites do not perform well.

Promises that sound too good. "Guaranteed first position on Google within a month." "We'll build 20 pages in two days." "You'll get 500 leads in the first week." These claims are not credible and often indicate either inexperience or dishonesty.

Hosting locked to their platform. Some developers build on platforms where they retain control of the hosting — meaning you cannot move your site without losing it. Always confirm that you will have full ownership of and access to your site files and domain. I cover domain ownership in detail in my article on how to choose a domain name.

No portfolio or references. Every experienced developer has examples of previous work they can show you. If they cannot — or if the examples shown look low-quality — that tells you something important.

Questions to ask before you sign

Whether you are speaking with a freelance developer or an agency, these questions will give you a clearer picture of what you are actually buying.

"What exactly is included in this quote?" Ask them to walk through the proposal with you, line by line. Any hesitation or vagueness on specific items is informative.

"What is not included?" Equally important. You want no surprises after the invoice is paid.

"Who will actually build my site?" Some agencies sell the project and subcontract the work. This is not always a problem, but you deserve to know.

"What happens if the project takes longer than planned?" Does the price change? Who bears the risk of delays? The answer reveals how the developer manages uncertainty.

"How will we communicate during the project?" Weekly updates? Access to a project management tool? Ad hoc emails? Knowing this upfront prevents frustration during the project.

"What access will I have to my own site after launch?" You should be able to update content, add photos, and make basic changes without needing to call and pay someone each time. If the developer's answer is vague or restrictive, that is a structural problem with the proposal.

"Can I speak with a previous client?" A confident, experienced developer will say yes without hesitation. References from real previous clients — particularly other small businesses in your sector — are one of the strongest trust signals you can ask for.

How to compare quotes

When you have two or three proposals in front of you, resist the temptation to compare only the total price. A €1,500 quote and a €3,500 quote are not comparable if they describe different projects.

Read each proposal against your brief and ask: which one actually addresses what I need? Which deliverables are included in each? What is excluded?

Sometimes a higher-priced quote includes things you genuinely need — professional copywriting, a booking system, multilingual support — while a cheaper quote assumes you will provide everything yourself. Sometimes it is the reverse: an agency is including features you do not need and billing accordingly.

The most useful comparison is cost per deliverable. What is each party offering to build, and what does each element cost? Once you break it down, the decision often becomes much clearer.

Consider also the long-term. A site that costs €1,000 more upfront but is built on a solid technical foundation — fast, secure, easy to maintain, good for SEO — will outperform a cheaper site within a year. The difference in cost is often recovered in a few additional client enquiries. The relationship between site quality and long-term results is something I discuss in my articles on website maintenance and why your site might not be bringing in clients.

The working relationship matters too

A website project is a collaboration. You will need to provide content, feedback, approvals, and decisions throughout the process. The developer's technical skill matters, but so does their communication style, their responsiveness, and their ability to explain things without overwhelming you with jargon.

If a developer makes you feel confused or condescended to during the sales process, it will not improve once the project starts. Equally, a developer who asks sharp questions, listens carefully, and explains their recommendations clearly is likely to be a reliable partner through the more complex moments of the project.

For many small businesses, the right developer is not the cheapest or the most prestigious — it is the one who understands your business and communicates well. That combination is harder to find than it sounds, and it is worth taking the time to identify it.

---

Wondering what a clear, honest quote for your project would look like? Visit my services page — I work with small businesses and tradespeople across France, with fixed pricing, a written contract, and direct communication throughout.