What determines the cost of a website

A catalogue, campaign landing page and partner portal can all look minimal while requiring very different work. Describe the main visitor action, user roles and essential journeys. List what the first release excludes, such as payments, multiple languages or stock synchronisation.

Clear exclusions make estimates comparable. Without them, one supplier may price a static presentation while another includes an editable catalogue and operational workflows.

Twenty product pages sharing one template are not twenty individual designs. List page types and their editing requirements: home, service, category, product, article and search. Include loading, empty, error and success states.

A short enquiry form also differs from a multi-step calculator with uploads, validation and CRM delivery. The visible number of fields does not describe its complete implementation.

“CRM integration” needs a field map, direction of transfer, duplicate policy and delivery monitoring. Ask who supplies credentials, test data and an API environment. Catalogue integrations also need rules for price changes, variants and deleted products.

Writing, photography, migration, licences, hosting and maintenance may sit outside a development quote. Identify each cost and its owner. Specify who enters launch content and who maintains it afterwards.

If a marketing team needs to create services without a developer, the editing model must be designed before the final screens are built.

Put estimates into one table: deliverable, covered journeys, acceptance criteria, dependencies and exclusions. Separate fixed work from work that requires discovery.

For example, a manually maintained catalogue may cost less initially while consuming editorial time. Automated synchronisation requires more development but removes routine operations. Evaluate the total operating model, including domain ownership, source access and the process for scope changes.