"How much does a website cost" is a bit like asking how much a house costs. The honest answer is that it depends entirely on what's inside it, and most of the price difference between quotes has nothing to do with the number of pages.
Page count is the least useful way to estimate a website. The real cost drivers are how much of the content and structure already exists, how custom the design needs to be versus working from a proven template, and how much backend functionality sits behind the pages people see.
The two most common budget-killers are scope creep during the build, and discovering mid-project that the content isn't ready. Both are avoidable with a clear brief and a content plan agreed before design work starts, not during it.
The corners that get cut on a low-cost build are rarely visible on day one. They show up as slow load times, a site that breaks on half the phones people actually use, or a CMS so awkward that every future update needs a developer. Cheap upfront often means expensive later.
Instead of "how much will this cost," ask "what does this need to do." A site that exists to be a digital business card costs a fraction of one that needs to convert cold traffic, integrate with internal systems, and be managed by a non-technical team afterward. Scope the job before pricing it.