Updated 30 October 2026 · EcommFusion
Start with the business purpose
Write down what the website should help a customer do: understand a service, request a quote, browse a catalogue or buy a product. Decide which customer and offer the first version serves.
This sounds obvious, but it changes the whole quote. A consultant who needs three service pages and a contact form needs a very different project from a distributor who wants 200 products online. If you cannot describe the main action in one sentence, spend an hour on that before you ask anyone for a price. It will save you from paying for features that do not help the customer take that action.
It also helps to name the visitor. “Purchase managers at mid-sized factories” or “families looking for a home tutor nearby” gives a designer and a copywriter something concrete to work with. A site that tries to speak to everyone usually ends up saying very little to anyone.
Separate necessary and later features
A useful initial site may need clear service pages, contact options and mobile usability. A large catalogue, login area or ERP integration changes the project substantially. Keep a short list of must-have features and a separate list for later.
A simple way to sort the list is to ask, for each feature, “Would a customer fail to contact or buy from us without this?” If the answer is no, it probably belongs in phase two. Common phase-two items are blogs with many categories, multi-language versions, customer portals, live chat and detailed analytics dashboards. They can all be useful, but they rarely need to delay the first launch.
Write both lists down and share them with every company you ask for a quote. That way each one is pricing the same thing, and you can ask what it would cost to add the phase-two items later.
Compare quotes on the same scope
- Number and type of pages or product entries.
- Who provides copy, images and product data.
- Forms, integrations and platform setup.
- Revision rounds, testing and acceptance criteria.
- Handover access and ongoing support.
Two quotes that look far apart are often describing different projects. One may include copywriting and photography; another may assume you will supply every word and image. One may include two rounds of design revisions; another may include unlimited changes but no testing on mobile devices. Put the quotes side by side in a simple table using the points above, and ask each provider to fill in any gaps in writing.
Also ask what “page” means in each quote. A long service page with several sections, a product page and a thank-you page are very different amounts of work.
Understand the recurring costs
Domains, hosting, licences, platform subscriptions and usage fees may be outside the build price. Ask what is included, who owns the accounts and what support you will need after launch.
Ownership matters as much as cost. The domain, hosting, analytics and email accounts should be registered in your business name, with your own login, even if someone else manages them for you. If a provider leaves or a relationship ends, you should still be able to keep the website running. Ask for a short list of every account the site depends on and who holds the access.
Ongoing care is a separate decision. Some businesses update the site themselves; others prefer a monthly website care plan for backups, updates, small edits and checks. Price it in from the start so it does not come as a surprise.
Agree the delivery conditions
A timeline should start after required content, access and payment are ready. Confirm how approvals are handled and how extra work changes cost and schedule.
Most delays come from waiting for content, not from design or development. Before the project starts, agree who will write each page, who supplies photos and who has the final say on approvals. A named person on your side who can make decisions quickly is often the single biggest factor in launching on time.
Agree, too, what happens when you want something that was not in the original scope. A short written change request with a price and a revised date keeps both sides clear.
Choose the smallest useful first version
Build the version that can serve the customer and produce a usable enquiry. Improve the next feature using feedback and actual business data.
After launch, look at what people actually do: which pages they visit, which forms they submit and what they ask about when they call. Those answers are a better guide to the next investment than guesses made before the site existed. Manufacturers and exporters, for example, often find that a clearer product catalogue and RFQ form matter more than design extras; our manufacturer website scope is built around that.
EcommFusion business websites start at ₹25,000. See starting prices and exclusions, or read about our business website service, then request a written quote.
Frequently asked questions
How much should a small business website cost?
It depends on the number of pages, who supplies the content, the features and the integrations. EcommFusion business websites start at ₹25,000 for an agreed scope; compare quotes only after confirming each one covers the same pages, content and support.
Should I build every feature in the first version?
Usually not. Launch with the pages and features a customer needs to understand your offer and contact you, then add the next feature once you have real enquiries and feedback to guide it.
Who should own the domain and hosting?
Your business should. Register the domain, hosting, analytics and email accounts in your business name with your own login, even if a provider manages them for you.