How I Quote a Website Project: What a Small Business Should Expect
When a small business asks me "how much for a website?", the honest answer is always the same: it depends on what the site has to do. A quote is not a price pulled from thin air. It is a short list of decisions, and the business owner should be able to see every one of them. This is how I build a quote, and what a business should expect from any developer who quotes one. 1. Start with the job,…
When a small business inquires about the cost of a website, the straightforward response remains consistent: the price depends on the site's functionality. A quote is not an arbitrary figure but a breakdown of decisions that the business owner should see. Here is how I create a quote and what a business can anticipate from a developer who provides one.
First, the focus should be on the project, not the price. The initial question is not about money but about the site's purpose: displaying services and prices, booking appointments, selling products, or simply being discoverable on Google. A simple brochure site with five to six pages is one task. A site with online booking or an online shop is a different task, involving more components and testing.
I ask the owner to describe the site in a sentence, such as: "a website where customers can view my services and book an appointment." This single sentence determines many other aspects.
Next, the quote consists of two main components: the number of pages and the features. The pages include Home, Services, About, Contact, and any additional ones. Features add functionality such as a booking form, WhatsApp button, photo gallery, map, or contact form that reaches the owner. Separating them is crucial because it allows the owner to adjust the quote. If a feature is unnecessary at the moment, it can be deferred.
The quote should also specify what is covered and what is not. It should detail the design and build, basic SEO setup (titles and meta descriptions on each page), the site going live on the owner's domain, and a handover explaining how to update text and photos. It should also clarify what is not included to avoid surprises: domain and hosting costs (paid to the hosting company, not to me), any necessary paid plugins, and new pages or features added post-launch.
A single, fixed number is given in writing before any work begins for the agreed-upon pages and features. A typical small-business website falls within a range I can state upfront once the pages and features are known. A booking or shop feature increases the cost due to the additional work and testing required. A range is honest at the quoting stage, while a fixed number is what the owner receives once the scope is agreed upon. A quote should never be a number that escalates during the project without any added work.
Payment is handled by requesting a deposit before starting and the remainder upon the site's launch and the owner's satisfaction. The deposit safeguards the developer's time, while the remainder on delivery protects the owner. Both parties should be aware of the payment schedule before the first page is created. Before a site goes live, the owner should review it—via a preview link or staging site—and have the opportunity to request changes.
The final product should be thoroughly checked by the owner because it represents their business and will be seen by their customers. A developer who launches a site without the owner's approval at this stage is overlooking a critical step. This comprehensive approach ensures the business understands what it is paying for, and the developer has nothing to conceal.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.