A website quote becomes useful when you know what it covers. A service business collecting enquiries, a shop selling products and a company with several customer groups may all ask for “a new website”. The work behind those requests can be very different.
Before comparing totals, write down what a visitor needs to understand and do. That gives you a way to compare proposals on the same basis. This guide explains the main cost drivers; it is not a price list or an estimate for your project.
Pages are only part of the scope
Page count gives a rough sense of size, but complexity matters too. Several pages using one agreed layout may need less work than a single quotation journey with conditional questions, calculations and an integration.
List the distinct types of content: services, products, staff profiles, locations, articles or project examples. Then identify the actions visitors need to take. An enquiry form, an appointment request and a booking with live availability are different requirements.
Agree who prepares the content
Copy, photographs and product information need time and an owner. Supplying an existing brochure is useful, but someone still needs to adapt it for the website, check the details and approve the result.
- Which text will you supply, and which needs writing or editing?
- Are photographs ready to use, with the necessary permissions?
- Who will organise product descriptions, prices and variations?
- Who gives final approval when colleagues disagree about content?
Put those responsibilities in the proposal. Include mobile layouts, accessible interactions, performance checks and basic search discoverability in the discussion rather than assuming every supplier means the same thing by “finished”.
Connections and migration add work
Connecting a website to a booking tool or customer database involves checking what that system supports, what access is available and how failures should be handled. A named integration should have an agreed purpose and test, not just appear on a feature list.
An existing website also brings content, URLs and account access to consider. Moving a catalogue, preserving useful page addresses and planning the switch from the old site are part of delivery. See our guide to redesigning or rebuilding before treating migration as a minor extra.
Separate the build from running costs
Ask for initial delivery, hosting, domain renewal, paid tools and ongoing care to be identified separately. Check who holds each account and whether you can change providers. For automation or AI features, ask about usage charges as well as setup.
Support needs a defined scope. Establish which updates are included, how extra work is agreed and what happens when a third-party service changes. Our ownership and maintenance guide gives you questions to bring to that discussion.
A brief you can send to a developer
Describe your business, your main customers, the action you want visitors to take and what is difficult about the current site. Add the content you already have, any systems it must connect to and any timing constraints. If you have a budget in mind, share it as a planning constraint.
You do not need to choose the technology first. Digital Marvels scopes business websites around those requirements, with deliverables and costs agreed in the proposal. Discuss your project.
Ready to discuss your requirements?
Tell us about the website or workflow you want to improve.