WordPress or custom code? What I tell small businesses before they choose
Advice · October 18, 2026 · 3 min read
WordPress is right for most brochure sites and blogs. Custom code is right the moment you need logins, workflows or real speed. Here is how I decide for clients, with examples from sites I built.
Half my clients arrive with a strong opinion: "WordPress is cheap and slow" or "custom code is for big companies". Both are half true. I build both, so here is the honest version of how I choose.
Pick WordPress when
- The site is mostly pages and posts: a shop, a clinic, a coaching centre, an agency, a portfolio.
- You want to edit text and photos yourself without calling a developer. WordPress's editor, or Elementor, is the easiest tool for that.
- You will publish a blog or notices regularly. WordPress has done this well for twenty years.
- The budget is on the smaller side and the timeline is short. A WordPress site with a custom theme can go live in days.
Two sites I built this way: NLPZen, for an NLP trainer in Delhi, runs on Elementor because the client updates course pages and blog posts herself. ThisBrand, a branding agency, got a custom WordPress theme built from their Figma design, with a Vite build for the assets, so it looks exactly like the mockup and still lets them add work to the portfolio.
The catch with WordPress is not WordPress. It is the thirty plugins and the heavy theme that get bolted on. A custom theme with three or four plugins is fast. A marketplace theme with a page builder, a slider, two SEO plugins and a form plugin is what gives WordPress its slow reputation.
Pick custom code when
- People log in. Students, patients, employees, members. Roles, permissions, dashboards. This is application work, and Laravel or Node.js does it properly.
- There is a workflow. Approvals, bookings, invoices, attendance, anything with steps and states.
- Speed and control matter more than editing. A landing page for an ad campaign, or a site where every millisecond on mobile data counts.
- You already have a design system or an app and the website is one piece of a bigger product.
For Global Matrix Solution I built the company website in React with a Laravel admin panel: the marketing site is fast and animated, and the team edits every service page from a custom CMS. For a university I built ILMS, a legal management system, and a RAG assistant that answers from scanned circulars. Nobody would do those in WordPress.
The hybrid nobody tells you about
A lot of real projects end up as both: a WordPress site for the public pages, and a custom app behind a login for the actual work. The school's website runs on WordPress so the office can post notices; the admissions portal runs on Laravel so applications, fees and documents are handled properly. They share a domain and a design, and visitors never notice the seam.
A quick way to decide
Ask yourself three questions:
- Will someone who is not a developer need to change the site's content every week? Yes points to WordPress.
- Does anyone need to log in to do something? Yes points to custom.
- Is the site itself the product, or is it a brochure for a product? Product points to custom; brochure points to WordPress.
If you get mixed answers, it is probably a hybrid, and that is fine.
What I use, so you know my bias
- WordPress with a custom theme, Tailwind and a Vite build for most business sites. Elementor when the client wants full editing control.
- Laravel with MySQL or PostgreSQL for applications and admin panels.
- React or Next.js for frontends that need to feel like an app.
- WooCommerce for stores, unless the catalogue or checkout is unusual.
Whatever you pick, insist on the same things: the domain in your name, a site that is fast on a phone, and a clear handover. The stack matters less than those three. If you want a second opinion on your project, a scope call is free.
Tags: WordPress, Laravel, React, custom website, small business