Describe the handover that needs improving
Choose a repeated task with a named user, a starting record and a clear completed state. A quote moving to an approved job or a customer request moving to an assigned staff member is a more testable brief than a request to automate the whole business.
Write down the exceptions as well: an approval is refused, a document arrives twice or a customer changes the scope. Those decisions often explain why a spreadsheet is difficult to replace. Include the person who handles them in discovery.
Compare buying, configuring and commissioning
An existing product may already meet the need with suitable configuration and training. An integration can remove retyping while retaining useful systems. A custom build becomes worth assessing when important rules or handovers remain unsupported after those options are reviewed.
Bespoke software development, customised software and custom development are overlapping descriptions. Ask what is delivered, how the workflow is tested and which limitations remain. The label by itself does not establish quality or fitness for your business.
Make outsourcing responsibilities concrete
For a delivered development project, agree the review milestones, acceptance scenarios and person who can approve changes. If you need developers embedded in an existing team, clarify that staffing model separately. A project fee does not automatically provide a permanent dedicated team.
Confirm business data access, commissioned code rights, third-party licences and handover materials before work starts. Ask who controls hosting and provider accounts and how an export is obtained. Retain a usable record of operational decisions as well as screen designs.
Plan the first release and its support
Give the first release a bounded workflow and a small set of acceptance examples. Include an integration failure and a restricted user role. Avoid postponing every exception until after launch; decide which exceptions the team can safely handle manually and record that arrangement.
Remote discovery and reviews can support businesses in Cape Town, Johannesburg, Kempton Park and other South African service areas. Ask about response hours, training and the rollout plan rather than assuming that a city phrase implies an office or on-site attendance.
Useful questions
Can this guide help us prepare a software development brief?
Yes. Describe your users, records, operating rules, existing systems and exceptions, then use the worksheet to compare available products and a scoped development approach.
Does this guide establish the best product or a fixed market price?
No. This is an editorial decision framework, not a hands-on vendor benchmark or current price survey. Ask suppliers for comparable demonstrations and written quotations for your actual requirements.
Sources and further reading
Reuse and attribution
Reuse the original blank PCube workflow evaluation worksheet under CC BY 4.0 with attribution and a note of changes. Third-party documentation and provider content are excluded.
Suggested citation: PCube Innovations editorial. “Custom software for South African SMEs: scope, outsourcing and ownership”. Updated 20 October 2026. https://pcubesolution.com/blog/custom-software-for-smes-south-africa.
