There is no useful one-price answer to the cost of a corporate website. Two websites with the same page count can require very different amounts of work because the real cost sits in requirements, content, integrations, migration, governance and what happens after launch.
Start with the job the website must do
A brochure site, an institutional publishing platform, an ecommerce store and a portal are different products. Before comparing quotations, define the audiences, actions, information and systems the website must support.
The main cost drivers
Discovery and information architecture, UX/UI design, content preparation, CMS development, ecommerce or booking logic, payment or API integration, migration, search-engine preservation, accessibility, testing, training and support all change the level of effort.
Compare scope, not just totals
A lower quotation may exclude content migration, redirects, analytics, training, backups, security hardening or post-launch support. Ask every supplier to state what is included, what is excluded and which recurring costs begin after launch.
Budget for operation
The website will still need hosting, domain renewals, maintenance and technical ownership after it is launched. For an organisation that depends on the website, those operational costs should be considered during procurement rather than discovered later.
Useful next step: prepare a requirements list before asking for prices. A clearer brief produces quotations that are easier to compare.