Custom software is a long-term commitment. The system will hold your data, shape how your team works and need support for years, so the company that builds it matters as much as the features on the list. These are the questions worth asking any South African software development company before you sign.
1. Do they start with your process, not their product?
A good developer wants to understand how the work happens today before proposing anything: who does what, where information comes from, where approvals sit and what goes wrong. Be cautious of a team that quotes a fixed feature list before it has seen your process. Ask how they run discovery, and what you will receive at the end of it: a process map, a scope, or only a price.
2. Can they show systems like yours?
Ask for case studies close to your problem: a leave workflow, a multi-site operation, a school, a client portal. A useful case study explains the problem, the people who use the system, what was built and what changed. Screenshots alone tell you little. Where possible, speak to a client.
3. Will they deliver in stages?
Large builds delivered in one piece months later carry the most risk. Prefer a company that delivers in stages with clear milestones, so you can test real screens early, change direction cheaply and start getting value before the whole system is finished. Ask what the first usable release will contain and when.
4. How do they handle personal information?
Most business systems hold personal information, so POPIA applies. The developer and any hosting provider that process data on your behalf are operators, and POPIA requires a written contract that obliges them to keep it secure. Ask how access is controlled by role, whether permissions are enforced on the server, where the data will be hosted and how they would tell you about an incident. Our POPIA checklist for business software lists the questions in full.
5. Who owns the code and the data?
Agree in writing who owns the source code, the database and the documentation, and what happens if you change supplier. You should be able to get a full export of your data at any time. If the system runs on the developer's own platform, understand what you are licensing rather than owning.
6. Is the pricing clear, including the running costs?
The build is only part of the cost. Ask for the ongoing costs in writing as well: hosting, support and maintenance, third-party subscriptions and, for AI features, usage fees that are often billed in US dollars. Ask which assumptions the quote depends on, such as the number of users, roles, integrations and how much existing data has to move, and how changes to scope are priced.
7. What happens after launch?
Every system needs updates, fixes and small improvements once people start using it. Ask what support is included, how quickly they respond, who monitors the system and backups, and how new features are quoted. A company that plans for life after launch is more likely to design a system that is easy to maintain.
8. Will they integrate with what you already use?
Replacing every tool at once is rarely necessary. A good partner connects the new system to the accounting, HR, email and CRM tools you already rely on, so data is captured once. Ask which integrations they have built before and how they handle a system without a ready-made connection.
Key takeaways
- Choose a team that maps your process before it proposes a solution.
- Ask for case studies that match your problem, and speak to a client if you can.
- Prefer staged delivery with early, usable releases.
- Get POPIA, hosting, code ownership and data export terms in writing.
- Compare total cost, including hosting, support and usage fees, not only the build price.
The right development partner asks more questions about your business than about your feature list.
At Auris Nexus we start every project by mapping the process, and you can see the systems we have built in our case studies. Business systems start from R30,000; see pricing for what each level includes, or read about our custom software development in Johannesburg.
