How to Quote a Small Business Website Project

DEV Community

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, not the price The first question is never about money. It is about what the website has to do: show services and prices, take bookings, sell products, or just be findable on Google. A simple brochure site with five or six pages is one job. A site with online booking or an online shop is a different job, with more moving parts and more testing. I ask the owner to describe the site in one sentence: "a website where customers can see my services and book an appointment." That sentence decides almost everything else. 2. Count the pages and the features separately A quote has two parts. The pages — Home, Services, About, Contact, and any others — are one part. The features are the other: a booking form, a WhatsApp button, a photo gallery, a map, a contact form that actually reaches the owner. Listing them separately matters, because it lets the owner change the quote. If a feature is not needed now, it can wait. A quote that hides everything in one number gives the owner nothing to decide about. 3. Say what is included — and what is not A good quote names what the price covers: the design and build, the basic SEO setup (titles and meta descriptions on every page), the site going live on the owner's domain, and a short handover showing the owner how to change text and photos. It should also name what it does not cover, so there are no surprises: the domain and hosting costs (paid to the hosting company, not to me), any paid plugin the site needs, and new pages or features added after launch. Those are separate, and the owner should know that before work starts. 4. Give one number, in writing I give a single fixed number for the agreed pages and features, in writing — usually by message or email — before any work starts. A simple small-business website typically falls in a range I can state upfront once I know the pages and features; a booking or shop feature moves it up, because it adds real work and testing. A range is honest at the quoting stage. A fixed number is what the owner gets once the scope is agreed. What a quote should never be is a number that grows during the work without anything being added. 5. Ask for a deposit, and say when the rest is due For a small project, I ask for a deposit before starting and the rest when the site is live and the owner is happy with it. The deposit protects the developer's time; paying the rest on delivery protects the owner. Both sides should know the schedule before the first page is built. 6. Show the work before it goes live Before a site goes live, the owner should see it — a preview link or a staging site — and be able to ask for changes. The pages, the text, the photos, the phone number: the owner checks all of it, because it is their business and their customers who will read it. A developer who launches a site without the owner seeing it first is skipping the most important step of the whole job. That is the whole process: understand the job, list the pages and features, say what is included, give one number in writing, agree the payment schedule, and show the work before launch. A business that gets a quote like that knows exactly what it is paying for. And a developer who quotes like that has nothing to hide. Author Bio Muhammad Asad Bukhari is a freelance WordPress developer based in Lahore, Pakistan. He builds WordPress websites for small and service businesses, including salons and spas, sets up AI automation with n8n workflows, and works on SEO for WordPress sites. His portfolio is at https://asadbukhari.site.

Powered by Readybot.io