Ask five agencies for a corporate website and you will get five wildly different numbers. That is not because some are dishonest; it is because 'a website' describes anything from a five-page template to a multilingual platform with a custom CMS and three integrations.
Here is what actually moves the price, so you can read a proposal properly and compare like with like.
Number of unique templates, not number of pages
Fifty pages built from six templates cost far less than fifteen pages that each need their own design. Design and build effort scales with unique layouts, not with the page count in your sitemap.
When you get a quote, ask how many unique templates it covers. It is the single most useful number for comparing two proposals that look superficially similar.
Who writes the content
Content is the most commonly underestimated line in the whole project — and the most common reason launches slip by months. If the quote assumes you will supply final copy and images, and you have not started, the timeline is fiction.
Professionally written, conversion-focused copy costs real money, and it is usually the highest-return part of the budget. A beautiful page with weak copy converts worse than a plain page that answers the buyer's actual questions.
Integrations and anything that touches another system
A contact form is trivial. A form that creates a CRM record, triggers a WhatsApp message and books a slot in a calendar is a small software project. Payment, ERP, booking engines, marketplaces and login areas all belong in this category.
Ask which integrations are included, which are estimated, and what happens if the third-party API turns out to be badly documented — because roughly half of them are.
Languages, and what they multiply
Each additional language adds translation, layout checks, localised metadata, hreflang setup and ongoing maintenance. It is not a percentage on top of the build; it is a recurring commitment for as long as the site exists.
Right-to-left languages cost more than left-to-right ones because the layout must be mirrored and every interactive component retested. Budget for it properly rather than discovering it after launch.
Performance, accessibility and SEO groundwork
A fast, accessible, technically clean site is not a feature you bolt on afterwards — it is a set of decisions made throughout the build. Cheap quotes usually save money exactly here, and it is invisible until the site launches and does not rank.
Ask what performance targets the agency works to, whether structured data and metadata are included, and who is responsible if Core Web Vitals fail after launch.
What happens after launch
Hosting, updates, backups, security patches, small content changes and someone to call when something breaks. If none of that is in the proposal, the price is not comparable to one that includes it.
Also ask what you own. Getting a site you cannot edit, on a platform you cannot leave, is expensive in a way that never appears on the invoice.
Key takeaways
- Compare unique templates, not page counts.
- Budget for content properly — it is the usual cause of delays.
- Anything that touches another system is a software project, not a form.
- Each language is a recurring commitment, not a one-off percentage.
- Include post-launch support and ownership in every comparison.
Services:Web Design & Development →
