On this page
The short answer to WordPress vs custom website: pick WordPress when your site is mostly pages and articles that staff need to edit, and pick a custom build when the website has to run part of your business, such as bookings, member accounts, approvals or connections to your own systems. Price matters less than people think. What decides it is how much the site has to do, and who will look after it in three years.
We build both at Edgecom, usually WordPress for content sites and Laravel for custom work, so this is not a sales pitch for one side. It is the conversation we have with clients before quoting.
What WordPress is good at
WordPress is free, open-source software for managing website content. You pay for the design and setup, hosting, and any premium themes or plugins, but not for WordPress itself.
Where it shines:
- Editing without a developer. Staff can update prices, add news, change opening hours and publish blog posts through a familiar editor.
- Content-heavy sites. Blogs, news, church sermon archives, NGO reports and school announcements all fit naturally.
- Plugins for common needs. Contact forms, SEO settings, galleries, simple event listings and online shops through WooCommerce are a few clicks away.
- A large talent pool. If your developer moves on, finding another person in Nairobi, Kisumu or Mombasa who knows WordPress is not hard.
- Lower upfront cost for standard brochure and blog sites.
Its weak spot is that every plugin is code written by someone else, on their own update schedule. Ten plugins means ten sets of updates, ten possible conflicts and ten possible security holes.
What a custom build is good at
A custom website is written specifically for your business, usually on a framework such as Laravel. There is no pile of features you do not use; the code does what your process needs and nothing more.
- Business logic. A SACCO's loan application with guarantors, a school's fee balances linked to M-Pesa Paybill, a clinic's appointment slots per doctor. These are awkward to fake with plugins and natural to build.
- Integrations. Connecting to M-Pesa Daraja, KRA eTIMS, an accounting package or an internal database is cleaner when you control the code.
- Performance. A lean custom site loads only what each page needs, which helps visitors on mobile data.
- A smaller attack surface. There is no public plugin list for bots to probe, and no shared admin login page that every attacker on the internet already knows.
- Exactly your workflow. Admin screens match how your staff actually work instead of how a plugin author imagined it.
The weak spot is dependence. Fewer people can step in quickly, so the documentation, code ownership and handover matter much more than with WordPress.
Security and maintenance burden
This is where most Kenyan businesses get caught. A website is not a signboard you put up once. It is software, and software needs care.
| Task | WordPress | Custom (e.g. Laravel) |
|---|---|---|
| Core updates | Frequent; many minor ones apply automatically | Framework updates applied by the developer, less often |
| Plugin and theme updates | Constant; each can break the layout | Few third-party packages, usually updated together |
| Typical break-in route | Outdated plugins, weak admin passwords | Coding mistakes, unpatched framework, leaked server access |
| Who can patch it | Many local developers | Ideally the original team, or anyone with the code and documentation |
| Licence renewals | Premium plugins and themes often renew yearly, often in dollars | Usually none beyond hosting and domain |
If you go with WordPress, read our guide on how to update WordPress plugins safely before you change anything on a live site. Either way, make sure someone is named as responsible for updates and backups, whether that is an in-house person or a support and maintenance plan.
Speed and performance
A well-built WordPress site can be fast. A badly built one, with a heavy page-builder theme, sliders, three analytics scripts and a chat widget, can easily weigh several megabytes per page. On a 3G connection upcountry that means a long wait and a visitor who leaves.
Custom builds start lean, but nothing stops a careless developer from bloating one too. Do not choose either option on speed alone. Instead, ask any developer you are considering to share a site they have built, then run it through Google's PageSpeed Insights on your phone. The result tells you more than any promise.
Total cost of ownership: a worked example
Here is a hypothetical comparison for a mid-sized hotel in Naivasha that wants an information site plus room enquiries, looked at over three years. The figures are illustrative; your quotes will differ.
- Option A, WordPress: a business website build, a premium theme, a booking plugin and a form plugin with yearly licences, hosting and a domain, plus a few hours a month of updates. Low start, steady running costs, and the booking plugin may not handle M-Pesa deposits the way the hotel wants.
- Option B, custom: a booking system built around the hotel's room types, seasonal rates and M-Pesa deposits. Higher start, then mostly hosting, domain and occasional changes.
At Edgecom, a business website starts from KES 20,000 plus 16% VAT and a booking or reservation system from KES 60,000 plus VAT. For a hotel that only needs enquiries, Option A wins. For one that wants to take deposits and stop double-booking rooms, Option B often costs less by year three, because it replaces paid plugins and the manual work around them. Our website cost guide explains what else moves the price.
Who can maintain it after launch
Ask this before anything else: if your developer disappears tomorrow, what happens?
With WordPress, a new developer can usually log in and carry on within a day. With custom code, it depends on what you were handed. Insist on these, whichever you choose:
- The domain registered in your business name, with your email on the account.
- Hosting in your name or with login details you hold.
- Full admin access to the website, not just an editor account.
- For custom builds: the source code in a repository you own, plus a short document explaining how to deploy it.
- A list of every paid licence, what it does and when it renews.
A developer who will not hand these over is a bigger risk than either technology.
Decision matrix by business type
| Business and main need | Better fit | Why |
|---|---|---|
| Consultancy, law firm, agency: pages and articles | WordPress | Content-led, staff edit often, standard features |
| Church or NGO publishing sermons, reports, news | WordPress | Regular publishing by non-technical staff |
| Small shop with under a hundred products | WordPress with WooCommerce, or a hosted shop | Proven, cheaper to start |
| Hotel or clinic taking bookings with deposits | Custom | Availability rules and M-Pesa payment flow |
| SACCO, school or microfinance with member or parent logins | Custom, or a purpose-built product | Sensitive personal data, balances and approvals |
| Business replacing spreadsheets with an online system | Custom | The website is really an application |
The middle path: a hybrid
You do not always have to choose one. Plenty of businesses run a WordPress site for the public pages and a separate custom system behind it for the work that matters. A school might keep news, admissions information and the term calendar on WordPress, where the communications teacher can update it, and link to a separate portal for fee balances and report cards. A logistics company might publish its services on WordPress and give clients a custom tracking page on a subdomain.
This split has real advantages. Marketing staff can change wording freely without risking the system that handles money or personal data. The custom part stays small, because it only does the jobs WordPress is bad at. And if one side has a problem, the other keeps running.
The cost is two things to look after instead of one, and a design that has to look consistent across both. Agree at the start who owns each part, and make sure login pages, colours and the logo match so customers do not think they have landed somewhere suspicious.
Questions to ask before you sign
Whichever direction you lean, these questions sort out careful developers from the rest:
- Which plugins or packages will you use, and which ones have yearly fees?
- Who applies updates after launch, how often, and what does that cost per month?
- Where are backups stored, and when did you last restore one to test it?
- Can you show me a site you built two or more years ago that is still running well?
- If I add a feature next year, will it be a plugin, a custom change or a rebuild?
Vague answers to the update and backup questions are a warning sign, regardless of the technology.
A quick rule: count the things your site must do rather than show. Zero or one, use WordPress. Three or more, get a quote for custom as well. In between, ask both questions and compare.
If you are still unsure, it helps to plan first. Our guide on how to plan a business website gets your goals and features onto one page, and if you are weighing DIY tools as well, read website builders vs hiring a web designer. When you are ready for quotes, see our web development and system development services.
