Web development frameworks in 2026: what we actually use for UK business sites

For most UK business websites in 2026 we build on classic WordPress with a hand-written theme. When the job is a web application rather than a website (a booking portal, a client dashboard, an internal tool) we use Laravel. React or Vue go on top when a screen needs to behave like an app. Node.js handles real-time features and integrations, and Flutter covers iOS and Android from one codebase. That is the short answer. The longer one is about why the choice of framework matters less than most people think, and where it matters a lot more.

We have been building on these tools for years, for organisations as different as UNICEF and an independent tattoo studio. What follows is how we decide, what each option costs to build and run, and the questions worth asking any developer who recommends one.

First, what counts as a “framework”?

The word gets used loosely, which is why comparison articles often set WordPress against React as if they were alternatives. They are not. There are really four layers:

• Content management systems such as WordPress. They give you an admin area, users, pages, media and a plugin ecosystem. Most business websites start and finish here.
• Back-end frameworks such as Laravel (PHP) or Express (Node.js). They give a developer the plumbing for a custom application: routing, database access, authentication, queues, email.
• Front-end libraries such as React and Vue. They run in the browser and handle interactive interfaces: filters that update instantly, multi-step forms, dashboards.
• Mobile frameworks such as Flutter. They produce real apps for the App Store and Google Play.

A typical project uses two or three of these together. A WooCommerce shop with a Vue-powered product configurator is WordPress plus Vue. A Laravel portal with a Flutter app is a back end plus a mobile front end sharing the same API.

Our stack at a glance

WordPress, built properly

WordPress runs a large share of the web (W3Techs has reported it at over 40% of all websites for several years) and that matters to you for practical reasons. Any competent UK developer can pick it up. Your marketing team probably already knows the editor. Hosting is cheap and plentiful.

The catch is that “a WordPress site” covers everything from a lean, fast build to a theme loaded with three page builders and forty plugins. We build classic themes by hand, with no Elementor or Divi, and use the block editor for content. The result loads faster, breaks less often on updates and is easier for the next developer to understand. We aim for Lighthouse 95+ and WCAG 2.2 AA on every template, and that is far easier to hit when you control every line of markup.

When WordPress is the wrong choice: when the site is really an application with complex user roles and data, when you need heavy transactional logic, or when you are trying to bolt a CRM onto it with plugins. Past a certain point, you are fighting the platform.

There is more on our approach in why we build on WordPress without page builders.

Laravel and custom PHP for applications

PHP has an unfashionable reputation and a very fashionable job market. It is everywhere, UK hosting supports it out of the box, and Laravel is a well-designed framework with sensible defaults for the dull but essential parts of an application: authentication, password resets, queued jobs, scheduled tasks, email and database migrations.

We reach for Laravel when the brief contains phrases like “customers log in to see their orders”, “staff approve bookings”, “sync with our accounts package every night” or “different permissions for each branch”. UNICEF’s donation platform and the keyword-analysis software we built for KDMasterKey are both examples of custom builds where an off-the-shelf CMS would have been the wrong shape.

The trade-off is simple: a custom application costs more up front than configuring a plugin, but you get exactly the workflow you need and nothing you pay for every month in plugin licences.

React and Vue for interactive interfaces

Both are mature, both have large communities, and either will do the job. Our rule of thumb:

• Vue when we are adding interactive pieces to a server-rendered site, such as a quote calculator in a WordPress page or a filtering panel in a Laravel view. It slots in without taking over.
• React when the whole product is an app in the browser, such as a dashboard with lots of state, or when the client’s in-house team already works in React.

What we try to talk people out of is building a brochure website as a single-page application. Search engines can render JavaScript, but a marketing site that ships a large bundle before showing any text is slower, harder to make accessible and more expensive to maintain than a plain server-rendered page. If someone proposes a React front end for a ten-page site, ask them what problem it solves.

Node.js for real-time and glue

Node is our choice for live features (chat, notifications, dashboards that update without a refresh), for webhook handlers that listen to Stripe or a courier’s API, and for small services that sit between systems. It is fast to write and runs well on modern hosting.

It needs more care in production than a PHP site on shared hosting. You want process management, logging and monitoring in place, which is part of why we often pair it with a cloud set-up rather than a basic hosting plan.

Flutter for mobile apps

Flutter lets one team ship an iOS and an Android app from a single codebase. For most small and medium UK businesses, that is the difference between an app being affordable and not. We used it for Washy, an on-demand car-wash app, and for the Tattoo-Art & Obsession app.

Native development (Swift for iOS, Kotlin for Android) still has its place for apps that lean hard on device features or need every last frame of performance. For booking apps, loyalty apps, field-service tools and marketplaces, Flutter is the sensible default. Firebase often sits behind it for sign-in and push notifications at the start; we move the back end to Laravel or Node when the app outgrows it or when usage-based pricing starts to bite.

What we do not use, and why that is fine

Angular, Django, Ruby on Rails and .NET are all good frameworks used by serious companies in London, Manchester and Edinburgh. We do not build on them because no agency should claim to be expert in everything. If you already have a Django product with a team behind it, hire people who live in Django. A good agency will tell you when you are better off elsewhere.

How the framework choice changes your budget

The framework itself is free in every case above. What you pay for is developer time, and different stacks lead to different amounts of it. Here are three realistic examples using our published hourly rates (all prices exclude VAT at 20%).

A ten-page business website on WordPress

Our Pro Website package covers this at £750 + VAT, with a CMS, ten pages and full deployment, delivered in two to three weeks. If you need something more bespoke and want to buy hours instead, 20 hours of WordPress development at £50 an hour is £1,000, less the 15% volume discount, so £850 + £170 VAT = £1,020.

A customer portal on Laravel

Say 80 hours of custom web development at £60 an hour. That is £4,800, less 20% for 50+ hours, so £3,840. Add VAT of £768 and the total is £4,608. Real portals vary a lot; integrations with third-party systems are usually where estimates grow.

A Flutter app for iOS and Android

Say 150 hours of mobile development at £70 an hour: £10,500, less 25% for 100+ hours, so £7,875, plus £1,575 VAT, total £9,450. Writing it natively twice would cost close to double the build time for the app screens.

These are illustrations, not quotes. They are here to show the shape of the numbers and why a “simple” stack choice made early has a long tail.

Running costs people forget

Build cost is only the first bill. Before you agree a stack, ask what the next three years look like:

• Hosting. A WordPress site runs happily on decent UK managed hosting. A Node service or a Laravel app with queues needs a server or cloud platform you can monitor.
• Updates. WordPress core and plugins need regular updates. Laravel has major releases roughly once a year. App stores require you to keep up with new iOS and Android versions, or your app can be pulled.
• Licences. Premium plugins, Firebase usage, map APIs and email services add up quietly.
• Hiring. If we were hit by a bus, could another UK developer take over? For WordPress, Laravel, React and Flutter, yes, easily. For a niche framework, maybe not.

Our recommendation, by situation

• You need a marketing or brochure site: classic WordPress. Start with a fixed-price package and spend the savings on content and photography.
• You sell online: WooCommerce for most shops; we explain the alternatives in our WooCommerce vs Magento vs PrestaShop comparison.
• Customers or staff log in and do things: Laravel, with Vue or React for the busier screens.
• You need an app in both stores: Flutter, with Firebase or a Laravel API behind it.
• You have an existing product on another stack: stay on it unless it is genuinely holding you back. Rewrites are expensive and rarely as clean as promised.

Questions to ask any developer about their stack

• Why this framework for this project, rather than the one you always use?
• How easy would it be for another developer to take this over?
• What are the hosting and licence costs per year?
• How are updates handled, and who pays for them?
• How will you hit performance and accessibility targets, and how will you prove it?

If the answers are vague, that tells you something. If you want a second opinion on a proposal you have been sent, or you want to scope a build, our web development service page explains how we work, custom software development covers the application side, and mobile app development covers Flutter. Fixed prices are on our packages page, and you can book hours if you would rather pay as you go. The team is based in St Albans and works with businesses across the UK, mostly remotely, with meetings in London when it helps.

Photo: Jakub Żerdzicki via Unsplash