The short version
- A website communicates. A web app performs a task and remembers the result.
- The test: does a visitor need an account for the thing to make sense? If yes, you need an application.
- Apps cost more to build and considerably more to run, because a database and its backups never sleep.
- Most businesses need a strong website first and an application later, connected to it.
A client once asked us for “a simple website where our drivers can log in, upload delivery photos, and the office can track the fleet on a map.” That is not a website. That is a logistics platform, and calling it a website had already anchored their budget at about a tenth of what the work required. Getting the vocabulary right is not pedantry; it is the first act of scoping.
The actual difference
Both run in a browser. Both can look identical. The difference is what happens to information.
A website delivers content that is broadly the same for everyone who visits. Your services page says the same thing to a customer in Kisumu and a customer in Mombasa. The site can accept a form submission and send it on, but it does not really remember you, and nothing changes about the page because you came back.
A web app does work. It takes input, stores it, changes it, applies rules to it, and shows different people different things depending on who they are and what they are allowed to see. A school portal where a parent sees only their own child’s results is an application. So is an inventory system, a booking engine, a member directory, or a dashboard.
A website is read. An application is used.
A one-question test
Ask this: does the core thing you want people to do require them to have an account?
If the honest answer is no (they read about you, look at your work, and then call, WhatsApp, or fill in an enquiry form), you need a website, and you should spend the budget on making that website excellent rather than on machinery you will not use.
If the answer is yes (they log in, and what they see is theirs), you need an application, and pretending otherwise will produce something you outgrow before the invoice is settled.
A blog and a content manager do not make it an app. Your team logging in to publish a news post is administration, not usage. The public still just reads. That is a website with a CMS, which is a very common and very sensible thing to buy.
When a website is the right answer
For most Kenyan SMEs, most of the time. Specifically:
- Professional services: law firms, clinics, consultancies, contractors. The job is credibility and a phone call.
- Local service businesses: garages, salons, restaurants, hardware suppliers. The job is being found on a map and being trusted enough to visit.
- Companies selling to other companies where the sale happens in a meeting. The site qualifies you before the meeting is agreed.
- Organisations that need to publish: NGOs, schools, associations. A good content manager covers this entirely.
None of that is a lesser project. A website that ranks for the right local searches and converts a visitor into a WhatsApp conversation is doing more commercial work than most half-finished applications ever will.
When you genuinely need a web application
- Money changes hands on the site. Carts, orders, stock levels, refunds. Once you take payment you have state, and state needs an application. See our guide to M-Pesa payments online.
- Different people must see different things. Patients and doctors, parents and teachers, drivers and dispatchers.
- You are replacing a spreadsheet that has become load-bearing. If the business would stop if one Excel file were lost, that file is already an application without backups.
- Something must happen automatically. Reminders, recurring invoices, low-stock alerts, an approval that moves to the next person.
- You need to report on your own operations. Not website analytics, but how many jobs closed, by whom, at what margin.
Why most businesses eventually need both
These are not rival options; they are different organs. The website is how strangers find you and decide to trust you. The application is what they use once they have. A store has a homepage and an about page as well as a checkout. A hospital has a public site and a separate appointment portal.
The practical sequencing question is which to build first, and for a business with limited capital the answer is almost always the website. It starts working immediately, it is cheaper to run, and the traffic it earns tells you what the application should do. Building the application first means guessing at requirements with no users to correct you.
What each costs to run
Build cost gets all the attention, but the running-cost gap is larger and permanent.
| Website | Web application | |
|---|---|---|
| Typical build time | 1–9 weeks | 4–14 weeks, often longer |
| Hosting | Often free or negligible for a static site | A real monthly bill: server, database, backups |
| Maintenance | Content edits, occasional refresh | Security patches, dependency updates, monitoring |
| If it breaks at 2am | A page is stale. Inconvenient. | Work stops. Someone must be on call. |
| Data responsibility | Minimal: enquiries in an inbox | You are a data controller under the Data Protection Act, 2019 |
That last row deserves emphasis. Holding customer records in Kenya carries legal obligations around consent, access, correction, and security. It is entirely manageable, but it is a commitment you take on with the application, not a footnote.
The two expensive mistakes
Buying an application when you needed a website
Symptoms: months of build time, a login page almost nobody uses, an admin area with three records in it, and a monthly hosting bill for capacity that sits idle. The money would have bought a superb marketing site and a year of running it.
Buying a website when you needed an application
Symptoms: a beautiful site, and a team quietly running the actual business through WhatsApp groups and a shared spreadsheet. Every process is manual, nothing is auditable, and the “system” lives in one person’s head. This one is more common, and more damaging, because it looks like success from outside.
How to decide without guessing
Write down, in one sentence each, the three things you most want to happen on the site. Not features, but outcomes. “A car owner in Migori books a service without calling.” “A procurement officer downloads our capability statement.” “A tenant reports a maintenance issue and can see it was received.”
Then check each sentence for the account test. If none of them need one, build the website. If one does and the others do not, build the website and add that one capability deliberately. If all three do, you are building an application and should budget accordingly.
We scope this with clients before quoting anything, because the wrong classification cannot be corrected later with more effort. Our services page lays out both families in full: Web Presence for sites, Web Applications for platforms, with fixed-scope tiers in each. If you want a sense of the money involved before you talk to anyone, start with what a website costs in Kenya.
Common questions
What is the difference between a website and a web app?
A website delivers content that is broadly the same for everyone who visits. It can accept a form submission and pass it on, but it does not really remember you. A web app takes input, stores it, changes it, applies rules to it, and shows different people different things depending on who they are and what they are allowed to see. A website is read. An application is used.
How do I know whether my business needs a website or a web application?
Ask one question: does the core thing you want people to do require them to have an account? If the honest answer is no, and they read about you, look at your work and then call, WhatsApp or fill in an enquiry form, you need a website. If the answer is yes, and what they see is theirs, you need an application. A blog and a content manager do not make it an app, because your team logging in to publish is administration rather than usage.
Is a web app more expensive to run than a website?
Yes, and the running-cost gap is larger and more permanent than the build-cost gap. A static site often hosts for free or close to it and needs occasional content edits. An application carries a real monthly bill for a server, a database and backups, plus security patches, dependency updates and monitoring. Holding customer records also makes you a data controller under the Data Protection Act, 2019, which is manageable but is a commitment rather than a footnote.
Should I build the website or the web application first?
For a business with limited capital, almost always the website. It starts working immediately, it is cheaper to run, and the traffic it earns tells you what the application should do. Building the application first means guessing at requirements with no users to correct you.
Not sure which one you are describing? Send us your three sentences. Tell us what you want to happen and we will tell you honestly which family it belongs to, including when the answer is the cheaper one.
Joseph Ng'era
Joseph co-founded ByteFrame in 2025 and builds the databases, APIs, and integrations behind every project. Meet the team.