A website budget becomes useful when it is clear which choices it funds. Asking only for the number of pages gives an incomplete picture. The same ten pages may reuse existing copy or require extensive research, new imagery and a redesigned enquiry journey. Discuss what needs investigating, creating and handing over before treating an amount as a fixed starting point.
Where the scope of work really comes from
Divide the request into content, design, functionality and launch. Content includes inventory, writing, reviewing and entry. Design covers the patterns and exceptions needed. Functionality includes the actions visitors and administrators must perform. Launch includes checking existing URLs, forms and administration agreements, among other things.
These elements affect each other. A multilingual website requires more than extra copy: it also needs decisions about administration and cross-links. An enquiry form may look simple while its assignment process remains unclear. Make these dependencies visible in the conversation. Otherwise, content decisions later look like unexpected additional work even though they were part of the original ambition.
A fictional organisation asks for “a website like the current one, but more modern”. Discovery reveals that two old services have been discontinued and a new advice journey is being introduced. The project therefore also involves restructuring content. Include that explicitly in scope before different proposals can be compared meaningfully.
Work with options that support a decision
Create a base option that fully supports the most important visitor task. Then describe extensions and their practical consequences. An extra language, extensive knowledge base or integration can add value, but only if content and administration resources are available. Avoid options that differ only in numbers of decorative pages.
For a new website the first option might include a clear service structure, representative case studies and a contact route with proper follow-up. An environment for existing customers can be investigated separately for later development. Comparing existing or custom-built software then becomes a concrete follow-up question rather than an invisible assumption in the website quotation.
For each option, record who supplies what and which decisions remain outstanding. “Customer supplies copy” is clear only when the quantity, quality and timing are known. The same applies to photos and product data.
Assess a proposal for completeness
Compare proposals against the same assumptions. Look at the intended outcome, included work, acceptance, handover and maintenance. A lower amount may represent a different division of responsibilities. That is not inherently good or bad, but must be visible.
Ask focused questions: which exceptions are included, which assumptions determine the schedule and what happens if content arrives late? Also ask how new requests are assessed during the project. A workable change agreement first describes the impact, then enables a choice.
Finally, record what remains necessary after handover. Editing, technical maintenance and further development are different kinds of work. Separating them lets an owner organise capacity deliberately. The budget conversation aims for a shared scope, not false precision in advance, so client and builder recognise the same assignment and can make interim decisions with enough context.