South African software pricing guide

How much does custom internal software cost in South Africa?

For 2026 planning, allow approximately R75,000 to R350,000 for many focused custom internal applications. A small workflow tool may fall below this range, while a complex operational platform can cost substantially more.

Request a planning estimate Jump to planning ranges

Draft for review · 26 August 2026 · 11 minute read

The short answer

A focused internal application with several users, clear permissions and one valuable workflow may require a planning budget of R75,000 to R180,000. An application with several workflows, integrations, roles, notifications and reporting may fall between R180,000 and R350,000. Complex platforms, difficult migrations or commercially strategic capabilities generally start above R350,000 and need discovery.

These are LCR Technologies' indicative 2026 planning ranges, not a fixed price list or a claim about every South African supplier. A proposal depends on confirmed scope, risk, dependencies and acceptance criteria.

Indicative custom internal software planning ranges

Type	Planning budget	Typical boundary
Prototype or tightly bounded tool	Below R75,000	Validation, one narrow task or limited production responsibility
Focused internal MVP	R75,000 to R180,000	Several users, roles and one complete workflow with limited integration
Integrated workflow application	R180,000 to R350,000	Several workflows, systems, permissions, notifications and reporting
Complex operational platform	R350,000+	Advanced rules, migration, audit, high scale or several business domains

Hosting, third-party licences, unusual migration and ongoing support depend on the solution. A proposal should identify these costs, responsibilities and boundaries explicitly.

What changes the cost?

Workflow

Rules and exceptions

States, decisions, escalation, correction and acceptance complexity.

Integration

Systems and interfaces

API quality, legacy constraints, identifiers, failure and reconciliation.

Access

Roles and sensitive data

Organisation scope, approvals, audit, support access and security testing.

Data

Migration and quality

Cleaning, mapping, history, duplicates, source ownership and validation.

Operations

Reliability expectations

Monitoring, recovery, environments, release controls and support hours.

Uncertainty

Unknown requirements

Unproven dependencies and unclear acceptance need discovery or contingency.

Match the commercial model to the work

Work	Suitable treatment	Boundary to make explicit
Discovery or risky prototype	Paid focused phase	Questions answered, artefacts and decision at completion
New defined capability	Fixed-price module or project	Scope, acceptance, dependencies, changes and payment milestones
Ongoing reliability and support	Platform care agreement	Response, monitoring, maintenance and exclusions from development
Predictable improvement backlog	Evolution retainer or enhancement pack	Capacity, priorities, rollover and acceptance
Revenue-enabling product expansion	Separate value-based scope	Commercial trigger, reusable capability and strategic outcome

Care is not unlimited feature development. Separate the cost of keeping a system healthy from new workflows and capabilities so both parties know what is funded.

Budget for the full ownership lifecycle

discovery, design and technical validation;
development, review, testing and deployment;
data migration and reconciliation;
hosting, storage, messaging and third-party licences;
monitoring, backups, security and dependency maintenance;
user onboarding, documentation and process change;
support, incident response and small operational adjustments; and
future enhancement or integration changes.

A cheaper initial build can become expensive if it omits support tooling, recovery, ownership and change boundaries.

What is needed for a useful estimate?

Business outcome and consequence of doing nothing.
Users, roles, locations and access boundaries.
Current process, volume, delay, exceptions and manual effort.
Systems, interfaces, data owners and representative samples.
Required workflow, reports, notifications and administration.
Security, audit, availability and support expectations.
First release boundary, exclusions and acceptance criteria.
Target timing, decision process and budget assumptions.

Control the budget without creating hidden risk

select one end-to-end workflow instead of many partial features;
reuse proven identity, notification and integration patterns where they fit;
validate the least certain integration before committing the full build;
keep existing systems as sources of truth when replacement adds no value;
defer optional reports and variations behind a stable core process;
use a configured product when the workflow is standard and the ownership model fits; and
make assumptions, exclusions and change control visible in the proposal.

Estimate the benefit as well as the cost using the workflow automation ROI framework.

Sources and basis

Planning basis

The ranges are LCR Technologies' indicative 2026 planning guidance and require scope confirmation.
OWASP Application Security Verification Standard