We have rebuilt sites for happy clients only to see them return six months later frustrated by a slow admin panel, plugin conflicts, or a hosting bill that tripled without warning. The technology choice — WordPress or custom PHP — matters less than whether the build matches how that business actually operates. For Ugandan businesses, the trade-offs are concrete: team capacity, content update frequency, budget, and how much traffic you expect.

In our work on sweetcakesuganda.com and hereinuganda.com, we have delivered both custom PHP builds and lighter static or CMS-based solutions. The decision process we use is not ideological. It is practical.

The core distinction

WordPress gives you an admin dashboard, plugin ecosystem, and a large talent pool. Custom PHP — the kind we build for clients who need full control — gives you exact performance, a leaner database footprint, and zero dependency on plugin authors who may stop maintaining their work next year.

When a Kampala bakery contacts us, the first question is not "what looks better." It is: who will update the site? If only the business owner updates prices and new cake photos twice a month, WordPress is often the faster, cheaper initial build. If a business directory like Finalheights needs complex filtering, user accounts, and custom query logic, custom PHP keeps the codebase aligned to the actual data structure rather than forcing it into post types and custom fields.

When we recommend WordPress

We recommend WordPress when the team is small or non-technical, when content updates are frequent (weekly or more), and when the budget for initial development is under roughly 4 million UGX. WordPress excels for blogs, portfolios, and small e-commerce shops that do not need highly customized checkout flows.

The hidden cost is maintenance. A standard WordPress site with five plugins requires security updates, compatibility checks, and occasional debugging. Over a year, that overhead often equals the cost of one small custom PHP feature update. Hosting costs for WordPress sites typically start around 150,000 UGX per year for shared hosting, but performance-focused setups on managed WordPress hosts climb to 800,000 UGX or more.

When we recommend custom PHP

Custom PHP is the right choice when performance is non-negotiable, when the site structure does not map cleanly to pages and posts, or when the business expects the site to serve as a platform rather than a brochure.

For sweetcakesuganda.com, we rebuilt the site as a static catalogue — no database, no admin overhead, just a lean HTML/CSS/JavaScript catalogue that links directly to WhatsApp. Load times are under 0.5 seconds on a 3G connection, compared to 2.5 to 4 seconds for a typical WordPress site running on shared hosting with unoptimized images. That is not a marginal improvement. It is the difference between a customer staying or leaving.

Custom builds do require a developer for updates. We budget roughly 8 to 15 hours per quarter for small maintenance updates — adding a page, tweaking a form, or adjusting database queries. If a business does not have someone who can handle basic HTML edits or pay for that support, custom PHP is the wrong investment.

Concrete comparison

Here is how we evaluate the two paths side by side for a typical Kampala small business:

  • Initial build cost: WordPress: 2–4 million UGX. Custom PHP: 4–8 million UGX.
  • Monthly hosting: WordPress shared: 30,000–70,000 UGX. Custom PHP on a lean VPS: 50,000–120,000 UGX.
  • Average homepage load time (mobile 3G): WordPress with basic optimization: 2.8–4.2 seconds. Custom PHP with minimal assets: 0.5–1.2 seconds.
  • Content update effort: WordPress: owner can update in minutes. Custom PHP: requires developer or basic HTML knowledge.
  • Security update burden: WordPress: ongoing plugin and core updates required. Custom PHP: minimal — mostly server-level patches and our own code review.

These numbers are not estimates from forums. They come from our hosting invoices and performance logs on live projects.

The maintenance reality

We see the same pattern repeatedly: a business chooses WordPress to save on initial cost, then struggles with plugin conflicts or slow load times after six months. The site works, but it does not work well. Alternatively, a business commissions a custom PHP site, saves on plugins and bloat, but fails to budget for quarterly updates and ends up with outdated content.

Neither path is wrong. The mistake is choosing technology without aligning it to who will maintain it. Before we sign off on any build — whether a directory site, a bakery catalogue, or a service business page — we ask the client to confirm their update frequency for the next 12 months. If the answer is "monthly or less," we recommend a lean static or custom approach. If it is "weekly," WordPress or a headless CMS is usually more practical.

If you are considering a rebuild and want to talk through which approach fits your team, contact us. We will not recommend custom PHP just because we build it. We recommend what fits the project.

Our practical recommendation: For most Ugandan small businesses with non-technical staff and frequent update needs, WordPress remains the sensible default — but only if paired with disciplined plugin management and performance optimization. For businesses with specific data structures, high performance requirements, or low update frequency, custom PHP delivers lower long-term overhead and faster load times. The right choice is the one you can maintain without regret.