A technical choice, but not an ideological one
As soon as a website project lands on the table, the technology question almost always comes up alongside the budget: WordPress, a no-code tool like Webflow or Wix, or custom development? Each camp has its convinced defenders, and that's exactly the problem: most answers you find online are advocacy pieces, not real comparisons.
The reality is simpler than it looks. None of these three options is universally better. Each has ground where it is clearly the right choice, and ground where it becomes a problem disguised as a solution. This article sets out five concrete criteria — total cost over three years, time to launch, editorial autonomy, security, scalability — so you can decide based on your actual situation, not a technical preference.
The three families, in one sentence each
WordPress is an open-source content management system (CMS), customisable through thousands of themes and plugins, that powers a very large share of websites worldwide. It works just as well for a simple blog as for a complex e-commerce site, depending on how it's configured.
No-code (Webflow, Wix, Squarespace) refers to proprietary platforms that let you build a site visually, without writing code, with hosting and security managed by the tool's provider. The emphasis is on speed to launch and ease of use.
Custom development means designing a site with code built specifically for your project, without relying on a generic CMS or a third-party platform. It's the most demanding option to build, and potentially the most durable.
Comparison on five criteria
1. Total cost over three years, not just the starting price
This is the most misleading criterion if you only look at the initial invoice. WordPress and no-code often show a lower entry ticket, but recurring costs change the picture: hosting, premium plugin licences, a paid theme, a monthly no-code platform subscription, and above all the time (or budget) spent keeping WordPress security updates current. Custom development costs more to build, but has no dependency on a third-party licence and generally ages better if the code is well structured from the start.
In practice, over three years, the gap between the three options narrows much more than it appears at the initial quote stage — which is why it's worth reasoning in total cost rather than headline price.
2. Time to launch
No-code almost always wins this one: a simple brochure site can go live within days thanks to ready-made templates. WordPress sits in between, its speed depending heavily on the chosen theme and the amount of customisation requested. Custom development is the slowest of the three to build — there's no shortcut when every component is designed for the project — but it's also the only one of the three where the final page load speed (and therefore the actual visitor experience, and search rankings) is entirely under your control.
3. Editorial autonomy
WordPress and no-code are designed so a non-technical person can update their own text and images day to day — that's a large part of their reason for existing. Custom development can offer the same autonomy, but only if a suitable back office was planned from the design stage; without it, every change turns back into a ticket sent to the developer, which entirely reverses the advantage a custom site is supposed to provide.
4. Security
No-code fully outsources technical security to the platform provider, which is a real comfort. WordPress, conversely, owes its popularity and its vulnerability to the same cause: its wide distribution makes it a prime target, and a poorly maintained site (an abandoned theme, unpatched plugins) quickly becomes exposed. Custom development doesn't eliminate the risk, but reduces the attack surface by installing only what's genuinely needed — provided ongoing security monitoring is maintained, which is never a one-time achievement regardless of the technology.
5. Scalability
This is where the three options diverge most clearly over the long run. No-code quickly hits its limits as soon as you go beyond a classic brochure site: specific business logic, advanced integrations, complex user accounts are often impossible or heavily constrained by the platform. WordPress stretches much further thanks to its plugin ecosystem, but every added piece is one more dependency, with a risk of fragile stacking. Custom development is the only option that scales without a predefined technical ceiling, which makes it the right choice as soon as a project has a clear applicative ambition, even if that ambition isn't there yet at launch.
Summary table
| Criterion | No-code (Webflow, Wix) | WordPress | Custom-built |
|---|---|---|---|
| Total cost over 3 years | Low to moderate | Moderate, varies with plugins | Higher upfront, stable afterwards |
| Time to launch | Very fast | Medium | Slower |
| Editorial autonomy | High by default | High by default | Depends on the planned back office |
| Security | Managed by the platform | Requires active monitoring | Smaller surface, ongoing monitoring needed |
| Scalability | Limited | Good via plugins, fragile at scale | No predefined technical ceiling |
Which choice for which profile
- You're launching a business and need visibility fast, on a tight budget: no-code is often the right starting point, provided you accept its limits if the project grows.
- You have a content site (blog, news, service catalogue) that needs regular updates: WordPress remains relevant, provided it gets serious, regular technical upkeep.
- Your site needs to support demanding advertising acquisition, or evolve toward applicative logic (accounts, bookings, custom business logic): custom development becomes the rational choice, despite a higher upfront investment.
None of these three answers is inherently better — it's the nature of the project and its two- to three-year horizon that should decide, not a preference for one technology or another.
What we recommend at ÜMAIN
We mainly build custom sites, but we don't recommend it systematically: for a simple brochure site with no applicative ambition, a less demanding project is sometimes the more sensible choice. At ÜMAIN, a brochure site starts at €1,990, and a site paired with setting up acquisition (Google Ads, Meta Ads) starts at €4,500; in both cases, ongoing maintenance is available from €150 a month, which includes security monitoring — whichever technology is chosen, it's this ongoing monitoring, far more than the initial choice, that determines whether a site ages well or badly.
The most common mistakes
- Choosing no-code for a project that already has a clear applicative ambition at launch — the wall arrives fast, and migrating later costs more than making the right choice from the start.
- Choosing WordPress with no dedicated maintenance budget — this is the number one cause of hacked or broken sites after an automatic update.
- Choosing custom development without planning a suitable back office — this loses one of its main expected advantages, editorial autonomy.
- Comparing only the initial quotes — without factoring in recurring costs over three years, the comparison doesn't reflect the real total budget.
- Changing technology with no redirect plan — a poorly prepared CMS migration can wipe out existing search visibility, a topic covered in detail in our article on website redesigns.
In summary
No-code suits fast launches on a constrained budget and needs that will stay simple. WordPress remains relevant for content sites provided they get serious upkeep. Custom development becomes necessary as soon as a project has applicative ambitions or performance requirements beyond a classic brochure site. The right choice depends less on the technology itself than on the project's two- to three-year horizon — and on how seriously maintenance will be handled, whichever option is chosen.
Torn between these three options for your project? Describe it in a few minutes and we'll come back to you with a reasoned recommendation in under 24 hours. Describe your project — or see the details of our web design and development offer.