How to think about website pricing before asking for a quote
There is no useful universal price for every website. A better starting point is to define what the site has to do, which parts are genuinely custom and what needs to happen after launch.
Website scope becomes easier to discuss when you separate the business problem, required functionality, content work and long-term maintenance.
Define scope before chasing a number
A simple brochure site, a booking experience, an ecommerce build and a custom lead system are different projects. Comparing them only by page count can hide the work that actually changes complexity.
Before asking for a quote, describe the business goal, the important user actions and any systems the website needs to connect with.
Separate the main cost drivers
The amount of custom design, content preparation, integrations, forms, ecommerce logic, migration work, testing and ongoing support can all change the size of a project. Not every business needs all of them.
- How much of the design is custom versus based on an existing system.
- Whether content and imagery already exist or need to be prepared.
- Whether booking, payments, CRM or other tools need to connect.
- Whether the site needs ongoing maintenance, experiments or content support.
Compare proposals like for like
Two proposals can describe different amounts of strategy, design, implementation and post-launch support. The useful comparison is what each proposal includes, what it leaves out and what responsibility stays with the business.
A clear scope makes the conversation more useful than choosing a number before the work is understood.