A website does not have one dependable UK market price. A focused landing page built from approved content is a different product from a custom marketing website, an ecommerce store or an application with user accounts. The useful question is not only “How much does a website cost?” but “What work, risk and responsibility does this particular website require?”
The short answer: website cost follows scope and risk
A credible estimate needs to identify the type of website, its starting point, the number of distinct layouts, content readiness, functionality, integrations, migration and approval process. Without those inputs, a broad average can create confidence without telling either party what will actually be delivered.
Two websites with ten URLs can have completely different costs. One might reuse three simple templates and an existing design system. The other might require ten bespoke layouts, structured CMS content, account functionality and migration from an old platform. Page count is useful only when the pages are understood as a system.
What changes the cost of a website?
The visible interface is only part of the work. Website cost also reflects the decisions, production stages, technical dependencies and quality checks needed to reach an approved launch.
- Strategy: objectives, audience, journeys and measurement requirements
- Structure: sitemap, page purposes, navigation and CMS relationships
- Design: visual direction, unique templates, components and responsive states
- Content: copywriting, editing, imagery, population and migration
- Functionality: forms, search, filtering, accounts, payments and integrations
- Production: development, CMS setup, environments and deployment
- Quality: responsive QA, accessibility, performance, tracking and launch checks
- Management: stakeholders, feedback rounds, approvals and changing requirements
1. Starting point and design readiness
An approved responsive design can move directly into technical review and development. A desktop-only concept still needs mobile hierarchy, component states and intermediate-width decisions. A brief without structure or visual direction requires strategy and design before a responsible build can begin.
Ask what has genuinely been approved. A Figma link containing unfinished screens is not the same as a complete design system with representative content, responsive intent and agreed interactions.
2. Unique templates and reusable components
Estimate the number of distinct page systems rather than counting every URL equally. Fifty articles using one template can be less work than five pages with unrelated layouts and behaviours. Reusable components reduce repeated production, but they still require rules, variants and testing.
- Unique landing and campaign page layouts
- Service, location, article, case-study and team templates
- Reusable navigation, forms, cards, calls to action and content blocks
- Empty, loading, error, success and validation states
- Desktop, tablet and mobile behaviour for each important pattern
3. CMS, content and migration
A CMS adds value when its content types, fields, relationships and editing responsibilities are planned. It adds cost when the model is unclear or when old content must be cleaned, mapped and redirected rather than simply copied.
Clarify who writes, approves and uploads each content type. Content delays often extend the calendar even when they do not increase development effort. Large or inconsistent migrations can affect both.
4. Ecommerce and custom functionality
Commerce work includes more than the storefront. Catalogue structure, variants, payments, shipping, tax, apps, merchant workflows, migration and transactional messages all affect scope. Custom accounts, dashboards, permissions or application logic should not be priced like ordinary marketing pages.
When functionality or architecture is still uncertain, use a discovery phase. It is better to price the work required to resolve the unknowns than to hide them inside a fixed quote that will later need to change.
5. Accessibility, performance and technical SEO
Quality requirements belong in the original scope. Accessibility is more dependable when it is considered throughout design, development and content production rather than treated as a final audit. Performance work also depends on the chosen platform, media, third-party scripts and implementation decisions.
Technical SEO may include crawlable navigation, metadata templates, structured data, redirects, canonical rules and sitemap handling. A redesign with many existing URLs requires more planning than a new website with no migration history.
6. Feedback, urgency and delivery conditions
A fixed deadline can increase risk when content, access or approvals are not ready. Record the decision-makers, review windows and acceptance criteria before scheduling production. If several stakeholders can reopen approved work, the estimate needs to reflect that delivery model.
Separate supplier production time from elapsed calendar time. A team may complete its stage on schedule while the project waits for client copy, legal review or access to a third-party system.
Which website pricing model fits the work?
Fixed project pricing suits a defined outcome with stable requirements, named exclusions and an approval process. Monthly delivery capacity suits agencies with recurring work that can be prioritised through one queue. Discovery-led pricing suits projects where architecture, integrations or data still need investigation.
- Fixed project: defined deliverables, assumptions, revisions and change control
- Monthly capacity: an agreed team and workflow across one active priority
- Paid pilot: one small, production-ready task used to test the working relationship
- Discovery-led: a separately priced phase that turns material unknowns into scope
How Oncreation’s published options should be interpreted
Oncreation’s packages are delivery models, not claims about the average price of every UK website. The £550 paid pilot is for one tightly defined task. Website Partner capacity is £1,200 per month flexibly, or £1,050 per month when £6,300 is paid once for six months. Shopify has separate capacity from £1,800 per month with a three-month minimum. Next.js applications and materially complex integrations are scoped separately.
The total project value depends on how many billing cycles or separately scoped stages the work requires. Content services, platform fees, paid applications and third-party licences may sit outside the delivery package. Review the current package page before using any number in a client proposal.
Remember the cost after launch
A website budget should include the costs of operating the finished system. These may include hosting or platform subscriptions, domain renewal, premium licences, ecommerce applications, monitoring, maintenance, content production and future improvements.
Ownership matters as much as price. Confirm which accounts the client or agency will own, who can publish, who receives alerts and who is responsible for updates, backups, security and incident response.
How to use a website cost calculator responsibly
A useful calculator asks about the requirements that change delivery rather than multiplying a page count by a fixed number. Use the result to identify the likely delivery route and prepare better questions. Do not present it as a quotation before the actual brief and dependencies have been reviewed.
Oncreation’s free Website Cost and Scope Estimator uses six decisions: project type, design readiness, distinct templates, functionality, content and readiness to begin. It recommends a published package where the answers fit one and recommends discovery where an instant figure would be misleading.
Checklist before accepting a website estimate
Before comparing proposals, make sure each supplier is pricing the same responsibility. A lower number may exclude content, responsive design, migration, testing or launch work that another estimate includes.
- Business outcome, audience and priority conversion
- Confirmed pages, templates and CMS content types
- Design starting point and responsive deliverables
- Content creation, population and migration ownership
- Required functionality, integrations and licences
- Accessibility, performance, analytics and SEO requirements
- Feedback rounds, approver and expected review windows
- Hosting, deployment, training, maintenance and post-launch support
- Assumptions, exclusions, payment terms and change-request process
Turn the guidance into a dependable delivery system.
Oncreation works behind agencies on website structure, custom UI, development, QA and launch—with the agency remaining in control of its client relationship.
