Separate the core website from integrations
Design, copy, content migration and responsive development form one part of the scope. A supported booking widget is different from a custom API integration, which needs its own access, testing and failure handling.
Count the real content work
The number of pages matters less than how much useful, distinct content each needs. Case studies, original imagery, service information and source review should be visible line items rather than assumed to appear later.
Ask what happens after launch
Hosting, maintenance, provider fees, content changes and ongoing marketing may be separate services. Ask who owns accounts and source files, what support includes and how future changes are priced.
Compare the same scope
Request a written list of included pages, functions, dependencies and acceptance criteria. A smaller clearly defined first release can be a sensible option when the larger vision depends on access or evidence you do not yet have.