How much does a custom WordPress website cost in 2027?

Visual reference: Lama Lama · Project and credits on Awwwards.

“We need a WordPress website” is a starting point, but it leaves most of the budget undefined. The project might be a five-page service website or an international catalogue managed by several people. The platform has the same name. The work inside it can differ considerably.

To plan the cost of a custom WordPress website in 2027, separate structure, design, editing, content, migration and integrations. You can then compare proposals describing the same engagement and decide where to focus the investment.

JED’s published starting point for a corporate website is from €6,000. It covers a project approach bringing strategy, structure, design, bespoke WordPress and launch into a defined proposal. This guide uses that current reference for 2027 planning. Each commission needs its own scope and confirmed price.

Starting prices to frame the conversation

The following figures appear in JED’s project investment information. They are references for my service, rather than a market survey. They help distinguish a corporate website from a shop or a platform supporting its own business processes.

A shop with demanding dependencies may require more work than an extensive corporate website. The starting reference opens the discussion; the scope explains the final proposal. Establish the treatment of taxes, licences, hosting, translation and recurring services according to what the engagement includes.

In a WordPress web design project, we review the current situation and the tasks the website must support. This separates the requirements for launch from future additions. A budget becomes more useful when you understand what will be working at the first handover.

Structure and content: the material to organise

A page map needs more than names. A service page may explain a specialism through cases, questions and contact. A project archive needs to help visitors find and understand the work. The initial task is deciding which information belongs in each place and how it connects to the next.

Content types make the effort more tangible. Products, projects, news and locations may need different fields and relationships. Shared page structures can become a reusable system. Where each page introduces distinct requirements, more decisions need defining, implementing and testing.

Inventory the available copy, images and documents. Mark what has been reviewed, what needs editing and what remains to be produced. A supplier can estimate an agreed content-entry task. They cannot reliably anticipate what will emerge from a folder that the business has yet to organise.

In a hypothetical example, one company supplies ten reviewed entries with photography. Another has presentations, duplicate documents and unfinished descriptions. They may need the same final design but different preparation work. Recognise that difference before setting the delivery schedule.

Original design and an understandable editing system

Bespoke design establishes a visual direction for the brand and develops it across the agreed pages. Typography, proportions, imagery and components need to work with real content. Ask the proposal to identify the templates, their variants and how desktop and mobile layouts will be reviewed.

The scope also needs less glamorous states: a long heading, a project without video, form errors or another language. These examples test whether the system is ready for publication as well as presentation. The homepage should leave some of the project’s patience available for the rest of the website.

Editing deserves its own handover. Define the fields in a project page, how a gallery is organised and what staff can modify without changing the structure. A demonstration with someone who will actually publish content can expose questions before development is considered complete.

WordPress supports different construction approaches, so naming the CMS does not describe the whole solution. The custom WordPress or pre-built theme comparison explains how to assess structure, tools and independence using your content as the test.

Ask about documentation and training at handover. Establish which changes require specialist support. Adding a new content type may be an extension even when editing an existing entry is straightforward. This distinction helps plan future work without promising an editing freedom the project has not prepared.

Migration and languages need a defined scope

If a website already exists, prepare an inventory of its addresses, content and functions. Some pages may stay, others may change structure and others may no longer be needed. The proposal should explain what moves, what is reviewed and how changed addresses will be checked.

The amount and condition of content affect the engagement. Moving a few reviewed pages and organising years of publications are different tasks. Links, forms, documents and business functions that must remain available during the transition also need attention.

My WordPress website migration service begins with that review. If the available information cannot support a final scope, establish the inventory and dependencies first. Migration needs its own checks. Changing the platform does not guarantee retaining every search position.

For languages, define who translates, adapts, enters and approves content. The design needs testing with those texts and their navigation. Longer wording or a different market offer may affect page structures and relationships. Identifying those differences early makes them easier to scope.

A multilingual website project should distinguish language and market. An English page does not automatically determine which products or documents belong in each country. Budget for the content model and review process the business actually requires.

Functions and connections follow the requirement

A contact form needs fields, validation, recipients and a confirmation message. If it also records information in a CRM, another relationship between systems enters the brief. Estimating that work requires documentation, data definitions, permissions and owners on both sides.

An integration needs to define what happens when information is missing or the destination system does not respond. What is recorded, who receives an alert and how can a pending operation be reviewed? Those decisions belong in the work even when they are invisible in a design screenshot.

If you need private areas, access-controlled catalogues or custom processes, describe users and tasks with a complete example. A feature called a “portal” can conceal many different engagements. A budget becomes more precise when we can follow each user from entry to the expected result.

Unknown dependencies may need a technical review before implementation can be priced. That phase should explain its output and the decision it supports. Recognising an open question is more useful than burying it within an apparently precise project figure.

Costs and responsibilities after launch

Publication begins the website’s operational life. Content changes, updates and decisions about new functions will follow. When planning the 2027 investment, separate initial development from hosting, licences and the maintenance services contracted to support the website.

Ask what maintenance covers: updates, backups, checks, recovery and support. Frequency and service levels depend on the agreed engagement. My WordPress maintenance page provides a starting point for reviewing the system and its dependencies.

WordPress documentation explains that a complete backup includes files and the database. For your project, establish who prepares copies, where they are kept and how recovery is organised. Saving material and being able to restore it need a procedure understood by the responsible people.

Licences need an owner and clear renewal terms. Ask what comes with the initial delivery, what is paid periodically and what may change if the collaboration ends. That information supports continuity and helps the business retain control of important accounts.

Separate support from development over time. Resolving an incident within the delivered scope and building a new feature are different tasks. Agree how each is requested and how additions are priced. Future investment can then follow identifiable improvements with defined deliverables and responsibilities.

Consider the internal time required too. Someone will prepare content, approve decisions and review the handover. Knowing who can do that work helps create a realistic production sequence. An external fee does not remove the need for the business to provide the information only its own team can approve.

How to request comparable quotations

Share the current website, the main objective and a sample of the content. Add priority pages, languages, functions, connected systems and review contacts. If a date matters, explain the event behind it and what needs to be ready by then.

Ask each proposal to identify structure, design, implementation, content, migration, training and launch. Some tasks can be grouped as long as their boundaries remain clear. Check which materials your company supplies and how many review rounds are planned.

A representative deliverable is particularly useful: an editable project page, a complete service page or an enquiry reaching the correct system. Ask how it will be prepared and checked. That explanation helps compare approaches and reveals dependencies still missing from the brief.

Review the change process. If another language or feature is added, its effect on cost and schedule should be agreed before development. The opportunity to evolve the project works better when both parties understand the first launch’s boundaries.

Define quantities through examples. “Catalogue entry” may mean entering twenty reviewed products or preparing hundreds of incomplete records. “Two-language website” may cover the structure while leaving translation to the business. The proposal should let you reconstruct which material the supplier receives and which content will be delivered ready for publication.

Ask how design reviews are organised. Who consolidates comments, which decisions are approved at each stage and what happens when an approved direction changes? A straightforward process prevents the same screens reopening repeatedly while nobody can identify the remaining decision.

If photography, video or documents are being produced during the project, identify delivery dates and owners. An intermediate review with provisional material and another with final assets may be sensible, but both need time in the schedule. Images can affect cropping, proportions and the balance of an apparently finished composition.

Before accepting the handover, agree tasks the team should be able to complete: publishing an entry, changing a link or reviewing an enquiry. Checking them with representative users and content helps expose questions. That exercise turns a feature description into a deliverable the business can recognise and use.

A first version with room to develop

A project can be phased when each phase leaves a useful deliverable. One business may begin with priority services and case studies, using a model prepared for a larger archive. Another may first need to resolve catalogue structure. The sequence should follow business requirements and actual dependencies.

If important decisions remain open, the website diagnostic offers a session and a strategic and technical plan with priorities. Its published fee is €1,500, deducted from the first invoice if the project continues. It provides a way to define the engagement before committing to broad implementation.

To review the collaboration model, see the guide to choosing a freelance web designer or an agency. The team structure should respond to the work you need to delegate, regardless of the chosen CMS.

I’m Jordi Ensenyat, founder of Code Barcelona. If you are preparing a WordPress website for 2027, tell me what your business needs. We can review the content, publishing tasks and technical requirements, then turn the idea into a proposal you can understand before development begins.