Digigen uses R150,000 to R500,000+ as a planning band for custom software. This is our scope guidance, not a survey of South African prices. A prototype can cost less; complex integrations, migration, offline work and several user roles can cost more. We agree a quote once the workflow, risks and first release are defined.
What are you asking the software to do?
A portal for sharing a document is a different project from a portal that handles client billing, approvals and several company accounts. Before comparing prices, describe who will use it, what they need to finish, which data they need and what should happen when something goes wrong.
The four commercial layers
A complete plan separates discovery, product design, implementation, and operation. Discovery reduces uncertainty. Design makes workflows testable. Implementation connects interface, rules, data, integrations, and tests. Operation covers hosting, monitoring, support, security care, and controlled improvement. Removing a layer from the proposal does not remove the work; it usually moves the risk to the client or launch.
The cost drivers that change the range
Roles and permissions, external integrations, poor source data, migration, offline support, payments, files, notifications, reporting, device capabilities, compliance, and strict availability requirements all add real delivery and testing work. A long feature list is less informative than a small number of high-risk workflows.
How to compare proposals
Compare the problem boundary, included user journeys, responsibilities, environments, testing, release plan, ownership, exclusions, and change process. A low number with undefined migration, content, credentials, acceptance, or support is not directly comparable with a proposal that makes those obligations explicit.
What could a first release include?
For a delivery business, an illustrative first release could assign a job, show it to a driver, collect proof of delivery and flag incomplete work for dispatch. Payroll, route optimisation and a customer app could stay outside that release. This example describes a scope boundary, not a completed client result.
How do we reach a quote?
Start with a discussion about the process, budget and intended outcome. If important questions remain, agree a paid discovery phase. The proposal should then set out milestones, assumptions, exclusions, responsibilities and how changes will be priced.
| Option | Best fit | Watch for |
|---|---|---|
| Decision-ready discovery | Unclear scope, workflows, integrations, or delivery risk | It produces a plan and evidence, not the full product |
| Focused MVP | One complete outcome or an important commercial assumption | Keep launch, security, data, and ownership appropriate to the risk |
| Operational platform | Multiple roles, core workflows, integrations, and ongoing use | Release in milestones instead of one large reveal |
| Modernisation programme | A live system that must change without interrupting operations | Migration, coexistence, rollback, and support can dominate the plan |
Cost and timing examples are Digigen planning guidance, not market averages or a fixed quote. Confirm the scope, assumptions and current provider requirements before making a project decision. About Digigen.