Start with the job
A company website might need to explain a complex service, create qualified enquiries, support a sales process or become the public entrance to a larger product. Those are different jobs, even when the navigation has a similar number of pages.
Begin with the decision or action the website needs to support. That gives the budget a reason.
What changes the investment
- The depth of the content and positioning work
- The number and complexity of distinct page experiences
- Research, flows, prototypes and a reusable design system
- CMS roles, integrations, forms and business workflows
- Accessibility, performance, search foundations and testing
- Content migration, launch planning and ongoing responsibility
A useful way to phase the work
If the full ambition is larger than the first budget, identify the smallest coherent release. A focused first stage should still feel complete for the people it serves.
Discovery can help define the architecture, content and risks before committing to the full build. That is often more useful than forcing an uncertain product into a fixed package.
Ask for the assumptions
A proposal should explain what is included, what the client supplies, what happens after launch and which third-party costs sit outside the fee. The number is easier to judge when the work behind it is visible.