What Is a Custom Web Application? SA Examples

A developer or a competitor has used the phrase and you want to know what it actually means. So, what is a custom web application? It is software that runs in a web browser, with nothing to download, built around the way one specific business works. Think of a booking platform, a staff portal or an ordering system, rather than a site that only shows information.

Below I explain how it differs from a website and from off-the-shelf software, show real examples built in South Africa, and say honestly when you do not need one.

What is a custom web application, in plain terms?

One clear definition from the pages that rank for this: a custom web application is a software program that runs in your web browser, does not need to be downloaded or installed, and is built to perform a specific set of tasks for a specific group of users ^[1]. Behind the screens there is a backend and a database, and the app is built around user actions such as logins, permissions, forms, dashboards, saved data, notifications and integrations ^[2].

"Custom" is a spectrum, not a yes or no. A WordPress site with a purpose-built plugin that runs your whole booking workflow is a custom web application. So is something written from scratch on cloud services. What makes it custom is that the logic follows your process, not that every line of code is new.

Custom web app vs a website vs off-the-shelf software

Most confusion comes from three comparisons:

• Website vs web app: a standard website is mainly informational and the interaction is mostly one-way, while a web application is mainly functional and the interaction is two-way ^[1]. A brochure site tells people about you. A web app lets them, or your staff, get something done.
• Off-the-shelf software (SaaS) vs custom: with a subscription tool you have a low upfront cost but you are renting the software, while a custom app costs more upfront and is built to be yours ^[1]. Whether you actually own the code depends on your contract and on the licences of any third-party components, so check what is handed over.
• Web app vs mobile app: a web app works in any phone or computer browser without an app store. In my experience, needs like heavy offline use or deep access to the phone's hardware are what usually tip a project towards a native app instead.

Many businesses start on a template or a SaaS tool and only hit the wall later. I wrote about spotting that moment in when to move from template to custom.

Custom web application examples built in South Africa

The ranking pages use global examples like Gmail or big-brand ERPs. These are real South African projects I have built:

• Delta Tutoring: a two-sided tutoring marketplace on WordPress with a custom marketplace plugin. It handles tutor vetting, owner-mediated matching between students and tutors, bookings, manual EFT payment tracking, messaging, contracts, and a staff admin dashboard with role-based access and an audit log. It shipped as a first phase before the University of Pretoria reopened. I explain the architecture in building a two-sided tutoring marketplace.
• Westerwick: a full rebuild on Next.js, hosted on AWS Amplify, that integrates with Microsoft Dynamics 365, the client's business system. This is the integration case: the web app talks to software the business already runs. More in the Next.js and Dynamics 365 rebuild.
• A fraud risk engine dashboard: an interactive tool that scores transactions against 25 risk signals and lets you simulate South African attack patterns such as SIM swaps and card testing. Here the app is the product. You can try it on the risk engine project page.

None of these fit a standard product-and-cart store or an off-the-shelf booking tool, and that is exactly why they were built custom.

What drives the cost of a custom web app in South Africa?

There is no sticker price, and I would be wary of anyone who gives you one before understanding the workflow. The foreign guides quote US dollar ranges that do not translate to a South African project. What actually drives cost:

• The number of distinct user roles and what each can see and do.
• Integrations with accounting, ERP, courier or payment systems.
• How much of the process is automated versus handled manually in an admin screen.
• Whether you build in phases. Delta Tutoring tracked EFT payments manually in phase one and scoped a payment gateway for phase two, which kept the first release lean.

Then there are running costs people forget. If the app takes payments, every transaction carries a gateway fee. Checked on 4 October 2026, PayFast charges 3.2% plus R2.00 per card transaction and 2.0% (minimum R2.00) for Instant EFT, excluding VAT ^[3], and Yoco charges 2.55% to 2.95% excluding VAT per online payment ^[4]. Add hosting, the domain, and ongoing maintenance for security updates.

“The build is a one-off. The hosting, fees and upkeep are the cost you live with, so plan for them from day one.”

The South African details foreign guides miss

• POPIA: once your app stores customer or staff personal information, the Protection of Personal Information Act applies, and the Information Regulator requires organisations to register their Information Officers ^[5]. Plan data collection and access controls into the design, and get professional advice on your obligations.
• Local payments: South African customers expect options such as card, Instant EFT and Capitec Pay, which local gateways like PayFast offer through one integration ^[3]. I recommend choosing the gateway from your customers' payment habits, not from a foreign guide's default.
• Hosting in the country: AWS has run its Africa (Cape Town) region since April 2020, with three Availability Zones ^[6], each an isolated location made up of one or more data centres with redundant power and networking ^[7], so your data can stay in South Africa with fast response times for local users.
• Load-shedding: in my experience, managed cloud hosting is the sensible default for a business app, because it keeps running when a single office server would go down with the power.

Do you actually need a custom web application?

Often, no. If a template website, a WooCommerce store or a well-known SaaS tool covers your process, use it. It will be cheaper and faster. A custom build earns its cost when your workflow genuinely does not fit the existing tools, and when working around them is costing staff hours or losing customers every week.

A simple test: if you can describe the job in one sentence and a product already exists for it, start there. If the honest description involves "except that we also need it to..." three or four times, that is usually a custom web app.

What to do next

• Write down the one workflow that your current tools handle badly, step by step, including who does each step.
• List the systems it must connect to (accounting, ERP, payments, couriers) and the user roles involved.
• Check whether an off-the-shelf tool already does 80% of it before committing to a build.
• If you will store personal information, note what you collect and why, so POPIA is designed in rather than added later.
• Ask for a phased scope: the smallest version that removes the biggest pain first.

If you have a process that does not fit the tools you have, send me the step-by-step and I will tell you honestly whether it needs a custom build.