---
title: "WordPress or a bespoke website: deciding for your business · Lyntev"
description: "Choose between WordPress and bespoke development through editing tasks, integrations, maintenance and handover. Includes a demonstration matrix."
url: "https://lyntev.com/en/guides/wordpress-or-bespoke-website"
language: "en-GB"
date_published: "2026-11-21T17:20:13.047Z"
date_modified: "2026-11-21T17:20:13.047Z"
---

1. [Home](<https://lyntev.com/en>)
2. [Practical guides](<https://lyntev.com/en/guides>)
3. WordPress or a bespoke website: compare editing, operations and continuity

# WordPress or a bespoke website: compare editing, operations and continuity

WordPress and bespoke development can both produce suitable or unsuitable websites. The choice depends on publishing tasks, integrations and who takes responsibility for operations. A bespoke website can also have a content management system; WordPress can also receive custom development. Compare specific proposals and avoid deciding solely by the technology’s name or a promise that one approach never needs maintenance.

By [Lyntev](<https://lyntev.com/en/company>). Updated on 20 November 2026.
About 6 minutes to read.

[Start reading](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#leitura>)[Download worksheet](<https://lyntev.com/recursos/en/wordpress-ou-site-a-medida.txt>)

**A request that stays connected**The same reference follows the request and prevents duplicates.

Translation published on 21 November 2026. [Original Portuguese guide](<https://lyntev.com/guias/wordpress-ou-site-a-medida>); source revision 20 November 2026.

By the end, you can:

- Distinguish the platform from the project scope
- Prepare a comparable demonstration
- Document maintenance and handover for both approaches

In this guide

1. [Start with who will edit and how often](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#publicar>)
2. [Separate content, business rules and integrations](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#funcoes>)
3. [Use the same demonstration for both proposals](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#matriz>)
4. [Request an operating plan for any technology](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#manutencao>)
5. [Fictitious scenario: a training business](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#exemplo>)
6. [Compare the full period and likely changes](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#custos>)
7. [Record the choice using observable criteria](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#ficha>)
8. [Sources and criteria](<https://lyntev.com/en/guides/wordpress-or-bespoke-website#fontes>)

## Start with who will edit and how often

List the changes the business has made in recent months or expects to make: news, staff, services, catalogue and campaign pages. Identify who prepares content, who approves it and who publishes. Include an urgent situation, such as removing outdated information. The need for autonomy should appear in a demonstrable task, with appropriate permissions and training.

WordPress documentation describes pages, posts, revisions, scheduled publishing and user roles. These capabilities help formulate requirements, but a particular installation may have restrictions or customisations. Ask the future editor to make a change in the demonstration. Make exactly the same request for a bespoke project. Do not confuse being able to change one field with freely reorganising an entire page.

## Separate content, business rules and integrations

Organise requirements into three groups. The first presents information, such as services and opening hours. The second applies rules, such as preventing two bookings for the same resource. The third exchanges data with other systems. A visually complete page may address only the first group. For the others, identify the source of information and confirmation of each operation.

Ask each supplier to classify the implementation: platform functionality, a third-party-maintained extension, configuration or new code. This answer helps assess dependencies and maintenance. A recognised extension may be a proportionate solution; custom code may suit particular rules. Neither option removes the need for tests, error handling and defined responsibility. Do not commission an integration with only the vague instruction to connect everything.

## Use the same demonstration for both proposals

Prepare five tasks with fictitious data. Do not let each supplier choose only the journeys where its demonstration works best. Also observe what happens with missing information, insufficient access or an unavailable integration. The useful result is knowing whether the system confirms, blocks or refers the operation in an understandable way.

Record where help was needed and which steps require a technical person. This does not automatically eliminate a proposal; it helps define the support service needed. Avoid awarding points for features you do not need that increase complexity. The matrix should contain a small set of essential requirements, followed by convenience criteria whose importance the team has discussed.

Use the same demonstration for both proposals

| Task | Evidence requested | Continuity question |
| --- | --- | --- |
| Update a service | Edit and publish without affecting other pages | Who can make and roll back the change? |
| Add an editor | Give access only to authorised content | Who removes access when they leave? |
| Receive an enquiry | Confirm recording and the message destination | How is a failure detected? |
| Connect a system | Carry out the operation and handle a communication error | Who maintains integration versions? |
| Change supplier | Show the content and files handed over | What work will the transition require? |

## Request an operating plan for any technology

For WordPress, official updating guidance recommends backups and dependency checks. Ask who monitors the core, theme and extensions, how changes are tested and how a working version is recovered. Avoid assuming automatic updates solve every incompatibility. A support request should have a channel, a person responsible and an agreed scope.

For a bespoke website, likewise inventory libraries, hosting, form service, content management system and integrations. Even a static page may depend on external services to receive enquiries. Request the procedure for publication, recovery and service renewals. The argument for fewer components is useful only when the inventory shows which were actually removed. Less frequent change does not mean an absence of technical responsibility.

## Fictitious scenario: a training business

A fictitious business publishes new training courses weekly and has two editors and one reviewer. It needs to prepare a course without making it public, schedule registration opening and correct a date. One WordPress proposal demonstrates these tasks with separate roles. A bespoke proposal demonstrates a simpler dashboard, built for the catalogue and connected to the registration system.

The team compares the whole journey, catalogue export, learning time and the cost of adding a new course type. It discovers that the simple dashboard needs technical intervention for a structural change, while the other proposal needs more editorial training. Neither finding automatically chooses a winner. The decision depends on the likely schedule and contracted support. The scenario does not represent an implementation or results for a Lyntev customer.

## Compare the full period and likely changes

Request a comparison over the same period, including construction, hosting, licences, maintenance and changes. Add two specific changes you expect to make, such as a new language or a restricted area. The first delivery’s price may be small relative to ongoing work, but one model should not be presumed always cheaper overall.

Confirm handover of content, access and code where this forms part of the contract. Distinguishing a licence to use, ownership and repository access avoids misunderstandings. Request a demonstrable copy and a transition procedure without demanding disclosure of secrets or other customers’ data. The proposal should clarify what can be reused and what depends on separately contracted services.

- Do not accept security, speed or autonomy guaranteed solely by a technology’s name.
- Identify a person responsible for updates and recovery.
- Test the most specific function before approving the solution.
- Compare the same scope, period and set of changes.

## Record the choice using observable criteria

Complete the matrix with the future editor and the business lead. Ask for clarification when an answer says only included or unlimited. Convert those expressions into a list of operations and conditions. A proposal may be suitable today and need development later; record the signal that would justify it without trying to anticipate every possibility for growth.

Before approval, keep a short video or screenshots of the demonstrated tasks and a list of handover items. Use fictitious data and a test environment. Then compare the delivered version with that evidence. The worksheet does not replace a security analysis or contract review; it organises decisions that must be explicit for the project and the team maintaining it.

### Worksheet for your project

```
WordPress / bespoke development comparison
Editors, reviewers and permissions:
Publishing frequency and types:
Specific business rules:
Extensions, services and new code:
Five demonstrated tasks and their results:
Update and recovery plan:
Costs over the comparison period:
Two simulated future changes:
Content, code and access handed over:
Condition for further development and reasoned decision:
```

## Sources and criteria

Content prepared with AI assistance and research using technical sources, with checks of the relevant examples and calculations. The references support the guide’s decisions; examples identified as fictitious let you try out the method.

- [WordPress.org — funções de publicação e utilizadores](<https://wordpress.org/about/features/>)
- [WordPress.org — atualização e cópias de segurança](<https://wordpress.org/documentation/article/updating-wordpress/>)

## Continue to your next decision.

- [Specify the project before requesting proposals](<https://lyntev.com/en/guides/prepare-a-website-brief>)
- [Organise maintenance](<https://lyntev.com/en/guides/business-website-maintenance-plan>)
- [Explore bespoke websites](<https://lyntev.com/en/website-design>)

This guide is part of [Create or improve your website.](<https://lyntev.com/en/guides#sites-e-presenca>)

- [Free or paid website: avoid discovering the limits too late](<https://lyntev.com/en/guides/free-or-paid-website>)
- [Landing page or full website: choose a structure that helps your customer decide](<https://lyntev.com/en/guides/landing-page-or-full-website>)

[Explore the guide library](<https://lyntev.com/en/guides>)

## Would you like to apply this to your business?

Send us your worksheet or explain what you need to improve. We help you choose the next step for your project.

- [Lyntev assistant Immediate answers about services, prices and timescales, with a cost estimate. Read the assistant guide](<https://lyntev.com/en/help/ai-assistant>)
- [WhatsApp +351 928 412 891. The message is only sent when you confirm it in WhatsApp. Write on WhatsApp](<https://wa.me/351928412891?text=Hello!%20I%20came%20from%20the%20Lyntev%20website%20and%20would%20like%20to%20discuss%20a%20project.>)
- [Form Describe what you need and receive the reply by email. Complete the form](<https://lyntev.com/en/contact>)
- [Email contacto@lyntev.com Send an email](<mailto:contacto@lyntev.com?subject=Request%20for%20information>)

![Wellinton Oliveira](<https://lyntev.com/media/autores/wellinton-oliveira.webp>)

Written by

[Wellinton Oliveira](<https://lyntev.com/en/company>)

CEO of Lyntev

Technology with context, original analysis and sources you can consult.
