Focused Business Tool
A defined process. A focused operational need.
- Internal workflow tools
- Approval systems
- Focused dashboards
- Small internal CRM systems
- Departmental applications
- Process tracking
FromR75,000
Every engagement starts with your business problem, the operational workflow and the outcome you need. We define the system properly before committing to a production build.
Custom software engagements
typically start from R75,000.
Discovery engagements from R20,000
Larger or more complex Discovery phases are scoped and priced individually.
Custom software is an investment in business infrastructure. Start with a clear definition of what it needs to do.
A preliminary sales conversation can be free. Detailed workflow analysis, architecture and specification are professional project work, carried out through paid Discovery. A vague phone conversation is not enough to price a serious system responsibly.
Depending on the engagement, Discovery can include:
A defined system, a prioritised roadmap and a commercial proposal you can assess before committing to the build.
A focused departmental tool and a connected enterprise platform solve different problems. These starting points help frame a useful conversation.
A defined process. A focused operational need.
FromR75,000
Connected workflows, records and responsibilities.
TypicallyR150,000+
One operating environment across teams and functions.
TypicallyR300,000+
A wider ecosystem, engineered around operational complexity.
TypicallyR600,000+
These are indicative investment ranges, not fixed software packages. Complex systems can extend beyond R1 million, depending on scope. There is no artificial ceiling on what a project may require.
Final pricing depends on functional scope, the number of workflows, roles and permissions, integrations, migration, mobile requirements, infrastructure, data volumes, automation, AI requirements and security or compliance requirements.
All figures are in South African rand. Final fees, VAT treatment, deliverables and exclusions are set out in the signed proposal or Statement of Work.
Larger projects typically use milestone-based payments, with defined progress points agreed before development begins.
This is a typical commercial structure, subject to the signed proposal or Statement of Work. Smaller projects may use an alternative structure, such as 50/50. The website does not create binding payment terms.
The agreed Statement of Work defines what is included in the build. It gives both teams a shared reference for deliverables, responsibilities and acceptance.
New functionality or material changes outside that scope are handled as Change Requests. We assess the effect on cost, timing and implementation before the change is agreed.
That clarity protects delivery timelines, development quality and project budgets—for both Corvanta and the client.
Describe the new requirement and why it matters.
Make the scope, cost and timeline implications visible.
Approve a clear change before adding it to the build.
The operation will change. Your system can evolve with it through clearly scoped work, prioritised around the next business requirement.
Ongoing development is agreed around defined outcomes, responsibilities and capacity.
Choose an agreed level of care for the system’s operational importance. Support commitments should be as clear as the build itself.
From R3,500/month
Monitoring, backups, security updates, maintenance, incident support and infrastructure oversight.
From R7,500/month
Priority support, proactive technical review, minor configuration work, ongoing maintenance and an agreed support allocation.
From R15,000/month
Higher-priority support, proactive monitoring, optimisation reviews and a greater support allocation for business-critical environments.
Custom SLA
Individually scoped support for larger or mission-critical systems, aligned with their operational and availability requirements.
The above describes typical support scope. Actual coverage, support allocation, exclusions and response commitments are defined contractually. New development is scoped separately.
Managed infrastructure from R1,500/month
The environment must fit the application. Cost depends on its architecture, database, storage, backups, traffic, monitoring, environments, external infrastructure and availability requirements.
Larger environments are scoped individually. The starting figure is an entry point, not a hosting price for every application.
Support, infrastructure and ongoing development are identified separately in the commercial proposal so responsibilities and costs remain clear.
The interface is only one part of a working system. These disciplines shape how it operates, how it is maintained and how it moves into production.
The proposal defines the deliverables for your project, including the agreed provision for infrastructure and post-launch support.
Company size alone doesn’t determine the fit. The question is whether a purpose-built system is the right investment for the work you need to do.
For a small template website, or where the lowest initial cost is the main priority, a specialist template-based provider may be a better fit. Enterprise requirements need a budget that reflects their scope; an initial conversation can help establish whether a focused first phase is practical.
Tell us about your business, the problem you’re working through and the outcome you need. That gives us a useful place to start.