Website design costs: how to plan a useful budget

Define what needs to be delivered

A brochure site, a transactional store and a custom customer portal are different scopes. Content readiness, product data, integrations, migration and accessibility requirements all influence the work.

Compare complete scopes

Compare proposals by discovery, design, development, testing, migration and handover. Confirm what is excluded and how changes are priced. A low initial fee can be misleading when essential work is omitted.

Plan for the life of the site

Hosting, licenses, backups, maintenance and ongoing content need owners. Ask for a scoped estimate rather than treat generic industry price ranges as a quote for your business.

Questions to put beside every proposal

Ask who supplies and approves the copy, how many unique page types are included, which integrations will be tested and whether old URLs are mapped. Then identify hosting, licenses and maintenance responsibilities. Compare the same scope across proposals. Optional items should be visible so a lower initial price does not quietly exclude a required piece of the launch.

Build a proposal comparison you can actually use

Use the following as a working brief. It is a planning example, not a client result, a quotation or a forecast.

1. List the unique templates, rather than only the number of URLs. A service page reused ten times is a different design task from ten unrelated layouts.
2. For each integration, name the source, destination, account owner and acceptance test. “CRM integration” without those details is not a comparable line item.
3. Separate launch work from recurring responsibilities: hosting, licenses, backups, security reviews, content and support. Ask which costs are paid directly to a provider.
4. Mark assumptions about copy, photography, product data and approval turnaround. A fixed quote can still depend on inputs arriving in an agreed form.

A worksheet to bring to the conversation

Page/template inventory

What the visitor needs to decide

Content owner and readiness

Who supplies and approves each asset

Integration and migration tests

The result that proves a connection works

Recurring costs and ownership

The named person responsible after launch

Discuss the next step

Bring the question to a project conversation. We can review the current setup, explain the tradeoffs and define a useful scope.

Planning guidance by Social Saturation. Reviewed November 7, 2026. Decisions depend on your actual scope and available evidence.