What a small-business website actually costs — and what changes the price
A plain breakdown of what you are paying for when you buy a website, the choices that move the price up or down, and how to compare quotes fairly.
Nine questions that reveal how a website project will really go — what is included, who owns what, and how changes, timelines and life after launch are handled.
Vikas Digital
Most website problems do not start during the build. They start in the first conversation, with questions nobody asked. A designer who answers these nine questions clearly is telling you how they work. A designer who dodges them is also telling you something.
A good answer lists the scope: how many pages, which features, what setup is included. "We'll see as we go" with an hourly rate is how budgets quietly double. Fixed scope does not mean nothing can change — it means changes are agreed and priced before they happen, not discovered on the invoice.
This is the more useful half of the first question. Content writing, a logo, an online shop, booking systems, photography — are they in, or are they extras? Honest designers name their exclusions upfront, because surprises help nobody. If everything seems to be included at a very low price, ask this question twice.
The answer you want: you do. Your domain should be registered in your name, and you should be able to take your website and its content to another provider if you ever choose to. If a designer insists the domain stays in their account "for convenience", understand what that convenience costs you later.
Design is a matter of taste, so changes are normal. What matters is the structure: how many rounds of revisions the price includes, what a "round" means (usually one consolidated list of changes, not one change per email), and what an extra round costs. A project with no stated rounds either prices in endless changes — rare — or argues about them later — common.
Websites stall more often on content than on design. Ask whether the designer writes the pages, edits what you provide, or expects finished text from you — and be honest with yourself about which of those you will actually do. If writing is on you and you know it will slip, paying for copywriting is cheaper than a three-month delay.
A realistic answer has two parts: the designer's timeline, and the list of things only you can supply — logo, photos, page content, decisions. Most delays in website projects are waiting delays, on one side or the other. Knowing your part upfront lets you prepare it while the design is being built.
Timings change, prices change, a page needs a line added. Ask whether the site has a content management system you can log into, and whether you will be shown how to use it. If every small change needs a paid request to the designer, that cost belongs in your comparison — it is part of the real price of the site.
Sites need small ongoing care: updates, backups, the occasional fix, and someone who answers when something looks wrong. Ask what the designer offers — a maintenance plan, pay-as-you-go help, or nothing — and what each costs. "Nothing" is an acceptable answer if it is a deliberate one. What you want to avoid is discovering it during an emergency.
Ask this one last, and treat it as a test. The honest answer is no — nobody can guarantee a search ranking, because nobody controls Google. A designer who explains what they can do — a site Google can read properly, correct technical setup, pages written around real searches — is being straight with you. A designer who guarantees a position is selling you something they cannot deliver, and it will not be the only thing.
None of these questions needs technical knowledge to ask, and a good designer will be glad you asked them — clear answers protect both sides. If you would like to put them to us, our process page shows how a project here runs from first conversation to launch, and you can start an enquiry whenever you are ready.