The short answer: WordPress is the right choice for content-led businesses that need editorial control and a vast plugin ecosystem. Custom development wins when you need unique workflows, complex integrations, performance at scale, or full ownership of your technology stack.
Where WordPress makes sense in Kenya:
- Service businesses (law firms, agencies, consultants) where the site is primarily a brochure + blog + contact form
- Content publishers (news, blogs, media) who need multi-author workflows, scheduling, and taxonomy
- E-commerce stores with standard product catalogs — WooCommerce handles M-Pesa via Pesapal/IntaSend plugins
- Teams with limited technical capacity who need non-developers to update content daily
- Budgets under KES 400,000 where you need maximum features per shilling
Where custom development (Next.js, React, Vue, Laravel, Django) wins:
- Marketplaces and platforms (like Enkaji) with multi-sided user roles, complex search, and transaction flows
- SaaS products requiring custom dashboards, real-time data, API-first architecture
- High-traffic applications where Core Web Vitals and server-side rendering directly impact revenue
- Complex integrations — ERP sync, custom M-Pesa STK Push flows, bank API reconciliation, CRM automation
- Businesses building IP they need to own, license, or sell — you cannot "own" a WordPress site the same way
- Long-term cost control — no plugin license renewals, no forced PHP/MySQL upgrades, no vendor lock-in
The hidden costs that change the calculation:
- Plugin debt: The average WordPress site runs 20–40 plugins. Each is a maintenance liability, a security surface, and a potential conflict. Custom code has zero plugin debt.
- Performance ceiling: WordPress on shared hosting hits TTFB of 800ms–2s. Custom Next.js on Vercel/Netlify/Cloudflare hits 50–150ms. For e-commerce, every 100ms delay costs ~1% conversion (Google data).
- Security ownership: WordPress core is secure; the ecosystem is not. 97% of WordPress vulnerabilities come from plugins/themes (WPScan 2024). Custom apps only expose the attack surface you deliberately build.
- Developer availability: Kenya has abundant WordPress freelancers. Senior custom-stack engineers are scarcer and cost 2–3x more per hour — but you need fewer hours for a focused build.
Decision framework — answer these 5 questions:
- Is content publishing your primary activity? Yes → WordPress. No → continue.
- Do you need user accounts, dashboards, or multi-step workflows? Yes → Custom. No → continue.
- Are your integrations standard (WooCommerce + Pesapal) or custom (bank APIs, ERP, proprietary CRM)? Custom → Custom build. Standard → WordPress works.
- What is your 3-year horizon? If you are building a product to scale, raise funding, or exit → Custom. If the site serves a stable local business → WordPress.
- Who owns updates? Marketing team daily → WordPress. Engineering team sprints → Custom.
Real Lumyn perspective:
We build both. Dwell KE runs on Next.js with a custom CMS because property discovery needs map-based search, saved searches, agent dashboards, and M-Pesa booking flows that no plugin handles cleanly. A law firm client runs WordPress because they publish three legal guides a week and need the editorial team to self-serve. Both are correct decisions.
The hybrid path:
Some teams run WordPress for marketing pages (blog, landing pages, SEO content) and a custom Next.js/React app for the authenticated product experience — connected via shared authentication and design system. This works when the marketing velocity and product complexity justify the split.
Still unsure? Share your brief and we will map your requirements to the right architecture — no bias toward either stack.
Build what comes next
Want to explore what these ideas could mean for your business? Start a conversation with our team.