Web Apps & Portals
Web apps for customers, staff and partners
Online systems where people can log in, submit information, track work, manage records or complete a process.
If people need to do something on the site rather than simply read it, you are probably looking for a web app.
Website or web app?
| Criterion | Business website | Web app |
|---|---|---|
| Purpose | Explain the business | Let users perform tasks |
| Login | Usually not required | Often required |
| Data | Mostly public content | User or business information |
| Examples | Company site, portfolio, landing page | Portal, dashboard, booking system |
| Best for | Marketing and enquiries | Running a digital process |
Business website
Purpose
Explain the business
Login
Usually not required
Data
Mostly public content
Examples
Company site, portfolio, landing page
Best for
Marketing and enquiries
Versus
Web app
Purpose
Let users perform tasks
Login
Often required
Data
User or business information
Examples
Portal, dashboard, booking system
Best for
Running a digital process
What we can build
Customer portals
Customers can view information, documents, orders or requests.
Staff portals
Give staff one place to access the tools and information they need.
Operations dashboards
See status, workload, activity and business information in one interface.
Booking & request systems
Let users submit, schedule and track requests.
Admin panels
Manage users, content, records and system settings.
Self-service tools
Let customers complete routine actions without contacting staff each time.
Common capabilities
Examples — final features depend on the project.
- Login & accounts
- User roles
- Forms
- Search & filters
- Dashboards
- Notifications
- Document access
- Status tracking
- Approvals
- Third-party integrations
How the project moves
- 01
Understand users
Clarify who will use the app and what they need to do.
- 02
Design the flow
Agree screens, access rules and the main workflows.
- 03
Build & connect data
Develop the application and connect agreed data sources.
- 04
Test & launch
Test, deploy, hand over and support go-live.
Pricing
- Starting from
- KES 100,000
- Typical range
- KES 100K–700K+
- Estimated delivery
- 6–10 weeks focused10–16 weeks larger
Timing depends on scope, integrations, feedback and existing data.
What changes the price
- Number of user types
- Number of screens / workflows
- Authentication
- Permissions
- Data complexity
- Dashboards
- Integrations
- Notifications
- Migration of existing data
Frequently asked questions
What is the difference between a website and a web app?
A website mainly explains the business. A web app lets people perform tasks — for example logging in, managing an account, placing or tracking orders, uploading files or viewing reports.
Can customers and staff have different accounts?
Yes. Different user roles can see different information and actions. That is a common part of portal and admin work when the process needs it.
Can a web app connect to systems we already use?
Often, yes, where the other systems provide a suitable supported connection. We confirm the practical options during scoping.
Can we start with a smaller first version?
Yes. Many projects start with one useful workflow and expand once that part is working properly.
What happens after launch?
Projects include a defined launch-support period for launch-related fixes and handover. Ongoing changes or maintenance can be scoped separately if needed.
How long does a web app take?
A focused web app typically takes 6–10 weeks. Larger multi-role applications may take around 10–16 weeks depending on features, integrations and data requirements.
Discuss your project.
Tell us what the business needs to do and where the current process falls short.