How much does a website cost in Kenya?

"How much does a website cost in Kenya?" is the first question almost every business owner asks us, and the honest answer is a range, because a website is not one thing. A one-page site for a new salon and a content-managed site for an engineering firm are both "websites" and they cost very different amounts. Here is how the numbers break down in 2026, what moves them, and how to brief a developer so the quote comes back honest.

The realistic ranges

For a professional, custom-built site in Nairobi, plan for roughly these bands. They assume real design and clean code, not a KES 5,000 template resold fifty times.

Those bands overlap on purpose. A five-page site with one awkward integration can cost more than a twelve-page site with none. Page count is the number everyone asks about, and it is rarely the number that decides the price.

The running costs nobody puts in the quote

The build is a one-off. Keeping the site alive is not, and this is where budgets quietly break. Three line items, every year, for as long as the site exists:

• Domain: around KES 1,500 a year for a .co.ke or .com. Renew it on time. Letting a domain lapse is the most expensive small mistake on this list.
• Hosting: anywhere from nothing to about KES 15,000 a year. A brochure site on a modern platform can genuinely sit in a free tier. A store with real traffic will not.
• Maintenance: optional, and the one people skip. A site nobody updates does not stay still, it rots. Dependencies age, forms stop delivering, and the contact page can fail silently for a month before anyone notices.

So the five-year cost of a KES 60,000 site is not KES 60,000. With a domain and modest hosting it is closer to KES 75,000 before any maintenance, and that is the fair number to compare against the alternatives.

What moves the price

Four things, roughly in order of impact.

• Content readiness. If your text, photos, and service descriptions exist and are approved, the build runs. If they do not, someone has to write them, and that someone bills for it. Having content ready is the cheapest way to lower a quote.
• Custom design versus a theme. A design built around your brand costs more than a theme, and usually earns it back in credibility. That matters most if you compete on trust rather than price.
• Features. A booking system, an M-Pesa checkout, or a member login each adds development time, and each adds one more thing that can break later.
• Structure and speed. The technical groundwork costs a little more once and saves a rebuild later.

A worked budget

Suppose you run a three-branch clinic and you want a site that brings in booking enquiries. Work it through:

Now the part that decides whether that was a good buy. If the clinic charges KES 3,000 a consultation and the site brings four new patients a month, it returns KES 144,000 in the first year. If it brings one a month, it returns KES 36,000 and takes three years to pay back. A site is not expensive or cheap in the abstract, only relative to what one customer is worth to you. Work out that number before you ask anyone for a quote.

Where the money gets wasted

Two failure modes, and they end the same way. The first is paying premium prices to an agency that disappears after launch, leaving a site nobody can edit and no one to ask. The second is paying almost nothing for a template that is slow, generic, and impossible to update. Both lead to a rebuild inside a year, which means the real cost was the first build plus the second. The cheapest website is the one you only pay for once.

There is a quieter waste too: buying capability you will never use. A content management system is worth paying for if somebody will post to it. If nobody will, you have bought a login screen. Be honest about who is going to sit down and update the site, and how often.

What to have ready before you brief anyone

Roughly half the delays we see on a website build are content delays, and they are the most frustrating kind because nobody is working while everyone is waiting. The build finishes in three weeks; the launch happens in nine because the About page text never arrived. Gather these before you start and you will pay less and launch sooner:

• Your services, written out, one short paragraph each. Rough is fine. A developer can edit prose; they cannot invent what you do.
• Prices, or a decision that prices are on request. Deciding this late changes page structure, not just words.
• Photos you own. A real photo of your premises, your team, or your work beats stock, and it is the one thing a competitor cannot copy.
• Your logo as a vector file (.svg, .ai, or .eps), not a JPEG pulled off an old brochure.
• Access to your domain registrar. Not the name of the cousin who registered it in 2019.
• The three sites you like and the reason why, which is more useful than the ones you dislike.

The domain access one catches people constantly. If nobody in the business can log in to the registrar, budget an extra week and some awkward emails, and start that recovery process on day one rather than the week of launch.

How to get an honest quote

Tell the developer three things: what the site is for, who it is for, and what success looks like as a number you already track. "More enquiries" is a wish. "Twenty booking enquiries a month, up from six" is a brief. A studio that scopes against that number can tell you when you are over-buying, because it can see which parts of the build move the number and which do not.

Then ask for a fixed scope in writing, with the exclusions listed. "It depends" is a reasonable position on a first call. A quote that never becomes specific is a warning: it usually means the scope was never pinned down, and unpinned scope comes back later as a change request with your name on the invoice.

• Ask what happens after launch, and who fixes a broken form in month four.
• Ask whether you own the code, the domain, and the hosting accounts. The answer should be yes to all three.
• Ask to see the site on your own phone, on mobile data, before you sign anything off.
• Ask what is deliberately not included. A developer who can answer that has thought about scope.

If a clean five-page site does the job, that is what you should be quoted for. Being talked down to a smaller build is a good sign, not a lost opportunity.