Insight / Pricing
How much does a corporate website cost — and what actually shapes the budget?
Page count alone says very little about complexity. Architecture, content types, unique templates, integrations, migration and launch assurance are the real cost drivers.
- 11 September 2026
- 13 min read
- Cost and scope
Cost equation
Budget ≠ page count
Choose a level for each factor. This is a causal model, not a price calculator: it shows which decisions expand design, engineering and QA scope.
Audiences and structure
One audience → several roles and business lines
Unique templates
Repeatable pages → distinct journeys
Content and migration
Ready material → inventory and restructuring
CMS and integrations
Static pages → related entities and external systems
Motion and QA
Simple transitions → bespoke interactions
Factor 01 / 02
Architecture and templates matter more than raw page count
Ten independent pages may be simpler than a system serving three audiences across eight business lines, products, documents and case studies. The latter needs relationships, navigation rules and a scalable model.
Flat site
- one primary journey
- repeatable structure
- few relationships
Structured corporate system
- several audiences
- business lines and products
- documents and work
- cross-links
30 pages using 3 templates may be simpler than 15 pages using 12 unique templates.
Every unique template adds a separate architecture, design, responsive engineering and QA task. A repeatable content model lets the site grow without complexity rising at the same rate.
Factor 03 / 04
Content is both readiness and a management system
The estimate depends on who defines hierarchy, naming and relationships, not only on word count. Editorial work is agreed in scope; unspecified copywriting is not included automatically.
Client-ready content
Copy, structure and assets are ready to place.
Structured with EO Labs
Hierarchy, naming and presentation need to be shaped from available material.
Content-heavy project
Many lines, products, documents or legacy records require an inventory and migration map.
A page or a managed entity?
Service, Product, Case, Document, Person and Location can each have fields and relationships. More types and rules mean deeper CMS, interface and migration scope.
- Service
- Product
- Case
- Document
- Person
- Location
Factor 05 / 06
Catalogues and integrations change the technical boundary
Simple catalogue
Categories and entries without complex logic.
Technical catalogue
Filters, specifications, documents and related products.
Ecommerce
Basket, checkout and payments are a different scope.
CRM, forms, analytics, booking/service tools, APIs and external catalogues are categories, not a promise to support every product. Each adds implementation, failure states, testing and maintenance.
Factor 07 / 08
A second language and migration are separate workstreams
Multilingual
This includes localised content, metadata, hreflang, route parity, language switching and QA. Some versions may need structural differences, which should be resolved before development.
Migration
For an existing website we account for content inventory, URL mapping, redirects, metadata and documents, production QA and analytics continuity. The goal is to reduce migration risk, not promise retained rankings.
- Content inventory
- URL mapping
- Redirects
- Metadata
- Documents
- Analytics continuity
- Launch QA
Factor 09 / 10
Bespoke interaction requires bespoke assurance
- Simple transitions
- States and transitions within the design system.
- Interactive blocks
- Dedicated logic, states and responsive behaviour.
- WebGL / custom systems
- Specialised engineering, a performance budget and broader QA.
A mature budget includes responsive QA, browser testing, forms, metadata, analytics, redirects, accessibility, performance and production checks. These tasks are absent from a static mock-up but decisive at launch.
The work a layout never shows: each version was checked at a real mobile width.
Pricing scenarios
Three complexity levels — and one public reference point
EO Labs' current commercial model starts corporate or premium websites at $2,500, with a typical published range of $2,500–5,000. This is a reference point, not a package price: the final estimate follows scope review, while CMS, integrations, multilingual delivery and custom functionality are quoted separately.
Lean Corporate
One company, simple structure, few templates and no complex catalogue.
- + ready content
- + repeatable templates
- + one primary language
Structured B2B
Several audiences, services or products, case studies and documents, CMS and migration.
- + content model
- + several journeys
- + legacy content
Complex Corporate Platform
Multiple business units, catalogues, integrations, languages and complex data relationships.
- + integrations
- + multilingual
- + bespoke logic
Planning risks
What tends to move the budget — and what helps control it
Increases uncertainty
- scope changes after design
- missing content
- unclear decision ownership
- too many unique templates
- late integrations
- uncontrolled animation
- inconsistent legacy data
- multilingual added at the end
Reduces unnecessary scope
- clear project boundaries
- design-system reuse
- fewer unique templates
- prepared material
- phased launch
- deferred non-critical integrations
- an existing CRM or booking tool instead of custom development
- business-critical journeys first
This is not a list of client mistakes. These are planning risks the project team can identify before expensive implementation work begins.
EO Labs estimate
The estimate follows the project map
We define the system first, then confirm budget and schedule. The estimate reflects real dependencies instead of an average page count.
- Understand the business
- Map the structure
- Define templates and content types
- Identify integrations
- Assess migration
- Set design complexity
- Estimate implementation and QA
Useful inputs before an estimate
- business lines
- key audiences
- catalogue need
- CMS need
- languages
- integrations
- existing website
- migration volume
- target deadline
- content readiness
Continue from here
Move from a cost framework to a concrete scope
Next step
Discuss the structure and budget
Share the current website, available material or an early map of business lines. That is enough to decide the next level of detail.