Web Applications

Logins, dashboards, bookings and payments — software that runs in the browser and does real work.

What you get

Software that runs in a browser and does real work: user accounts, dashboards, bookings, approvals and payments. No installation, and reachable from any device your team already has.

A web application is what you need when a website is not enough. A website tells people about you. A web application does something for them, or for your staff. The moment you need someone to log in, submit something, be approved, be charged, or see information that belongs only to them, you have crossed from one to the other.

Who this is for

Web application development usually starts from one of a few recognisable situations:

• A spreadsheet that has become the system, and is now too important and too fragile to trust
• A process that runs on email threads, where things are lost because nobody owns the next step
• Off-the-shelf software that does most of what you need and blocks the part that matters
• A manual process that works fine at your current size and will not survive doubling
• Information scattered across several tools, so no single person can see the whole picture

If any of that sounds familiar, the problem is rarely a lack of effort. It is that the work is being done by tools never designed for it.

What is included

• Secure login and role-based access, so people see only what they should
• Dashboards and reporting built around your actual questions, not generic charts
• Booking, scheduling or approval flows that match how the work really moves
• Payment integration where it is needed
• An admin area your team can operate without technical help
• Data export, so your information is never trapped
• An audit trail where accountability matters

Roles and permissions

Most real applications have more than one kind of user, and the difference between them is where systems succeed or fail.

An administrator, a manager, a staff member and a customer each need a different view of the same information. Getting that wrong is not a cosmetic problem: it is how confidential data reaches the wrong person, and how someone deletes a record they should never have been able to reach.

We work out the roles with you early, in writing, before anything is built around the wrong assumption.

How we work

We scope the application in writing first, then build in stages you can see and comment on. You are not handed a finished thing you have never used.

This matters more for applications than for websites. A website is largely judged on appearance and can be assessed from a picture. An application is judged on whether it fits the way your organisation actually operates, and that only becomes clear when someone tries to use it for real work. Building in stages means the mismatch surfaces while it is still cheap to change.

We also agree what the application will not do. Scope on software expands quietly, and an honest boundary at the start protects both the budget and the delivery.

Built to be maintained

Applications live longer than websites and change more often. Yours will need adjusting as your organisation changes, and that work should not require rebuilding from scratch.

So we keep the structure clear, document what matters, and hand over the code and the accounts. If you later want a different developer, you can appoint one. Being difficult to replace is not a business model we are interested in.

Questions we are often asked

What is the difference between a website and a web application? A website presents information. A web application does work: logins, records, approvals, payments, reporting. If users need accounts, you need an application.

Do users need to install anything? No. It runs in a browser, on a phone, tablet or computer. That is the main advantage over traditional software.

Can it replace our spreadsheets? Usually, yes, and that is one of the most common reasons people come to us. We map what the spreadsheet is doing before replacing it, because spreadsheets often carry undocumented rules that matter.

Can it connect to systems we already use? Often, depending on what those systems allow. We check what is genuinely possible before committing to it rather than discovering the limitation later.

Is our data secure? Access is controlled by role, connections are encrypted, and sensitive information is handled deliberately. We will also tell you plainly where the real risks sit, which are usually passwords and staff habits rather than the software.

Who owns the application? You do. The code, the data and the accounts are yours, and you are given access to all three.

Where are you based? Pretoria, working with organisations across South Africa. Application work is done remotely as a matter of course, with meetings where they add something.