Most disagreements between a business and its web designer do not start with bad work. They start with a quote that left something unsaid, so each side filled the gap with a different assumption. A clear written quote prevents that before it begins.
Use the checklist below whenever you receive a quote, whoever it comes from. If an item is missing, you do not need to walk away. Ask for it to be added in writing before you pay a deposit.
Scope: exactly what will be built
The core of a quote is a list of deliverables. That means the pages by name (home, about, each service, contact, and so on) and what each page contains, plus every feature that does something: a contact form, a booking calendar, a quote request form, a product catalogue, a second language, an admin area. If a feature is not written down, assume it is not included.
Look for the technical basics too. Will the site work properly on phones and tablets? Is basic search setup included, such as page titles, descriptions, a sitemap and submission to Google Search Console? Is analytics connected? These are cheap to agree on at the start and frustrating to argue about at the end.
Content: who provides what
Someone has to write the text and supply the photos, and the quote should say who. If you are providing content, it should say in what form and by when. If the studio is drafting text for your approval, it should say how much and in which languages. If stock photos or professional photography are involved, it should say who sources them and who pays for licences.
This matters for the timeline as much as the budget. A timeline that starts “after receiving content” is fair and common, but you should know that in advance, because late content moves launch by the same amount of time.
Revisions, timeline and approval
A good quote states how many rounds of revisions are included and what a round means. Typically, you review a version, send your consolidated feedback, and the studio applies it. Two clearly defined rounds, with one person on your side collecting feedback, work far better than an unlimited promise with no structure.
The timeline should give a delivery period and say what it depends on, such as receiving content or approvals. It should also describe how the project is accepted: a final review on a staging link, then your approval, then launch. Knowing what “finished” means protects both sides.
If you work across time zones, as many Gulf and international clients do with a remote studio, it helps when the quote names the main communication channel and the usual response window, so nobody waits days for a reply they expected in hours.
Payments and the change process
The payment schedule should be written out: how much is due at the start, at which milestones, and before or after launch. A deposit at the start and the balance on final approval is a common, balanced arrangement. The quote should also state the currency, the accepted payment methods and whether transfer fees or taxes apply.
Equally important is how new requests are handled. Something will come up, perhaps an extra page or an integration you had not thought of. The healthy rule is that anything outside the written scope is priced and approved in writing before work starts on it. That keeps the project moving without turning the final invoice into a surprise.
Ownership, accounts and third-party costs
The quote should state plainly that the domain, the hosting account and the site files belong to you, and that accounts are registered in your name with an email address you control. If the studio sets things up for you, ask for full access to be handed over at launch, not held back.
It should also list the costs you pay to other parties: domain renewal, hosting, business email, any paid plugins or services, and payment gateway fees if you accept online payments. These are normal costs. They just need to be visible, with the provider named, so you can plan for them.
Exclusions and support after launch
A list of what is not included is a sign of an honest quote, not a stingy one. Common exclusions are copywriting beyond a certain length, photography, ongoing search optimisation, content updates after launch and features not listed in the scope.
Finally, look for a support period: how long after launch the studio will fix anything that does not work as agreed, and what happens after that. Some businesses need a light monthly maintenance agreement, many do not. Either way, it should be a choice you make knowingly.
Put simply, a quote should answer five questions in writing: what will be built, who provides what, when and how it is approved, how and when you pay, and who owns everything at the end. If all five are clear, you can compare quotes fairly and start the project with confidence.
Every SITELESS quote is written this way, with the scope, timeline, two revision rounds, payment schedule and ownership set out before any payment. Our how we work page shows the stages from the first message to launch.
Related guides
- How we work: first message to launch
No surprises halfway through: every stage has what you give and what you get, and every commitment is written into your proposal before any payment.
- Packages
Three levels with their scope written line by line, and what each excludes written explicitly. The price is written for your project in a formal quote once we understand your business, before any payment.
- What does a business website cost?
The factors that really move the price of a business website, the yearly costs people forget, and how to compare written quotes without guessing.
- How to choose a remote web designer
How to judge a freelancer or remote studio before you pay: real work versus concepts, ownership, communication, process and the red flags worth noticing.