Development

Custom software built around how your business actually works

Off-the-shelf software makes you change how you work to fit the product. Custom software does the opposite. We build business systems, portals and internal tools around your process, starting with the smallest version that delivers real value.

Discuss your system

When custom software is the right answer

Two colleagues working side by side with laptops and notebooks.
Illustrative photography · Christina @ wocintechchat.com M / Unsplash

Custom software makes sense when your process is a competitive advantage, or when the tools on the market force your team into workarounds. Typical signs:

The same information is typed into two or three systems. Reports are assembled by hand at month-end. Staff keep private spreadsheets because the official system doesn’t do what they need. Customers phone in for information they should be able to see themselves.

It’s not always the right answer. If a well-configured existing product would do the job, we’ll tell you, and we’ll often help you set it up. We’d rather win your trust than an unnecessary build.

What we build

  • Internal business systems that replace spreadsheets and email chains with one source of truth.
  • Customer and partner portals where your clients log in to see accounts, orders, reports or documents.
  • Reporting and assessment platforms that collect data in the field and turn it into comparisons and PDF reports.
  • Workflow automation that moves records between people and systems without retyping.
  • MVPs that test a new product idea with real users before you commit to the full build.
  • AI-assisted workflows using OpenAI, where it measurably saves time.

Built for real businesses

Suzuki secret shopper platform. Mystery-shopper assessments for a dealer network: a weighted question system, branch-by-branch comparison, categorical breakdowns, video uploads and automatically generated PDF reports. What used to be scattered forms became one comparable picture of every branch.

Bonus app for Pretorium Trust. A secure way for customers to log in and access and manage their credit accounts.

Vassco. A bespoke B2B ordering platform: product tables with powerful search, a real-time cart and delivery timelines.

Kriptolink and Afrikode. MVP builds that got new products in front of users quickly.

How we build it

  1. Discovery. We sit with the people who do the work, follow a task from beginning to end and note where information is copied, checked or lost.
  2. Feature list. Everything the system must do is written down in plain language and agreed.
  3. MVP definition. We separate what the first release needs from what can follow, so you start getting value sooner.
  4. Costing by unit and hours. Each feature is estimated individually. You see what you’re paying for and can trade features in or out.
  5. Build in stages. You test working software as it develops, not a big reveal at the end.
  6. Launch and support. We host, monitor and maintain the system, with a 24-hour response time and direct access to the people who built it.

Configure, integrate or build?

We always weigh three options before recommending custom development.

Configure an existing product when it covers most of your needs and the gaps are small. It’s usually the fastest and cheapest route.

Integrate when your existing tools are fine individually but don’t talk to each other. A focused API integration can remove the retyping without replacing anything.

Build when the process itself is what makes your business different, or when the workarounds cost more each year than the software would. That’s where custom software pays for itself.

Rescuing a stalled project

A surprising number of our clients arrive with software that has been “in development” for years. Before quoting, we:

  • review the code, database and hosting to see what’s genuinely usable;
  • explain plainly what we found, including the good parts;
  • compare the cost of fixing against a structured rebuild.

In our experience a rebuild is usually the cheaper option when the foundations are weak. We’ll show you the numbers either way.

Technology chosen for the long run

New systems are built on Laravel and PHP with MySQL or MariaDB, a stack that’s mature, fast to develop and easy to support in South Africa. Interfaces use Bootstrap for speed and consistency, and mobile companions use Expo and React Native. We host on AWS, DigitalOcean or Vultr, or on your own infrastructure. For corporate clients, documentation, POPIA considerations and service-level agreements are part of the handover, not extras.

Questions to ask any developer before you sign

Whoever you choose to build your software, these questions will tell you a lot about how the project will go:

  • Can I see the feature list and the cost of each feature? If the quote is one number with no breakdown, you can’t make trade-offs later.
  • What’s in the first release, and what comes after? A sensible MVP gets value into your hands sooner.
  • Where will the code live, and who can access it? It should be in version control, with your access agreed.
  • Who hosts it, and what does that cost each month? Running costs matter as much as the build.
  • What happens when something breaks after launch? You want a response time and a named route to the people who built it.
  • What will it cost to keep current? Some technology choices need constant updating; ask how much.
  • Can someone else take it over if needed? Good documentation and clean code are your insurance.

We’re happy to answer every one of these in writing before you commit.

What you receive at handover

A finished system is more than working screens. At launch you receive:

  • The working system, deployed and tested against the agreed feature list.
  • Access to the hosting, administration and code, as set out in the agreement.
  • Documentation of how the system works, its integrations and its configuration.
  • User guidance for the people who will use and administer it.
  • A support arrangement, with a 24-hour response time and direct access to the developers.

For corporate clients we also provide the documentation procurement and IT teams typically ask for, including data-flow descriptions for POPIA reviews and service-level terms.

Estimate your system

We price custom software from an agreed feature list. For a first view, try the customer portal and web app estimator or the business process automation estimator. We confirm the actual cost after discovery.

Custom software questions

A few useful answers before you decide.

How long does custom software take?
It depends on the feature list. Defining an MVP first means you usually have something useful in your team’s hands much sooner than the full system. The timeline is set out per feature in the proposal.
What happens if our needs change during the build?
They usually do, a little. Because every feature is costed separately, a change is a clear decision: add it, swap it for something else or schedule it for the next release.
Can our customers log in to the system?
Yes. Customer and partner portals are a common part of our builds, with access controlled so each person only sees what they should.
Who maintains the software afterwards?
We do, unless you’d prefer to take it in-house. Hosting, updates, backups and support are available from launch, and we document the system so another developer could pick it up.
Can you build an MVP to test an idea first?
Yes. We’ve built MVPs such as Kriptolink and Afrikode. An MVP puts the core idea in front of real users quickly, so you invest in the full product with evidence rather than guesswork.
Can the system use AI?
Where it genuinely saves time. We integrate OpenAI into workflows such as drafting, classification and summarising, with a person staying in control of decisions. Many clients know AI matters but aren’t sure where to apply it; we’ll help you find the places it pays off.

Tell us about the workaround

Describe the spreadsheet, the retyping or the stalled project, and who it slows down. We’ll come back quickly with how we’d approach it.

Discuss your system.

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Discuss your system