Every agency has a favourite answer to this question, usually the one that matches what they're good at. We build WordPress sites and we build custom PHP applications, so we'll try to give you the version we'd give a friend.
When WordPress is the right call
WordPress is a fantastic fit when:
- The site is mostly content: pages, blog posts, a portfolio, a team page.
- Your team wants to edit things themselves without calling a developer.
- You need common features like contact forms, SEO settings, or a simple shop, and a well-maintained plugin already does it.
- Budget is tight and time matters.
A clean WordPress site with a good theme and a handful of trusted plugins can be live in two to four weeks. The editor is familiar to a lot of people, and you're never locked in to one agency because thousands of developers know the platform.
Where WordPress starts to hurt
The problems usually show up a year or two later.
Plugin sprawl. Sites gather plugins like a kitchen drawer gathers rubber bands. Each one is a dependency that needs updates, and each one is a possible security hole. We recently cleaned up a site with 47 active plugins. It needed 11.
Performance. Page builders make editing easy, but they often output heavy HTML and load scripts on every page. Getting a page-builder site to pass Core Web Vitals is possible, but it's work.
Custom logic. The moment you need something specific to your business, like a quote calculator with your own pricing rules or a dealer portal, you're writing custom code inside WordPress anyway, often in awkward ways.
When custom makes more sense
We recommend a custom build, typically on a PHP framework like CodeIgniter or Laravel, when:
- The website is really a web application: user accounts, dashboards, workflows, bookings with business rules.
- You need to integrate with internal systems such as an ERP, a CRM, or a billing tool.
- Performance and security are critical and you want a small, controlled codebase.
- You expect the product to grow for years and want to own its structure.
The trade-off is cost and time upfront. A custom site takes longer to build, and content editing needs a purpose-built admin panel. The upside is that there's nothing in the system you didn't ask for.
The hybrid option
Sometimes the answer is both. A WordPress marketing site at the main domain, and a custom application on a subdomain for the customer portal. Marketing teams keep their familiar editor, and the application gets proper engineering.
Questions to ask yourself
- In two years, will this site mostly be pages and articles, or tools and data?
- Who will update it, and how often?
- What happens if the person who built it disappears?
- Is there a feature that no existing plugin quite does?
If your answers lean towards content, editing and speed to launch, WordPress. If they lean towards logic, integrations and long-term ownership, custom. And if you're not sure, talk to someone who builds both and isn't trying to sell you the one they happen to know.
