Home / Custom software
Every business has one or two processes that no packaged product handles properly, the ones your team has built a spreadsheet and a set of rules around. Those are worth building software for. Most things are not, and we will say so.
Book a call if you want one, or just send the form. We reply within one business day. POPIA-compliant.
Custom software development means building an application around how your business actually works, instead of bending the business around an off-the-shelf tool. For most South African SMEs that means a web app, internal tool or client portal, built on a fixed scope and price, with the code and accounts in your name.
Not a screenshot and not a video. A working dispatch board running in this page. Assign a job, start it, close it, and watch the clocks and the on-time figure react.
This example needs JavaScript to run. It is a live job board: you move jobs through assign, start and complete, and the timers and on-time figure update as you go.
Six jobs, one action each, nothing saved. A real build would carry your job types, your sites, your people and your SLA rules, and it would keep its data.
We would rather configure something you already own than build from scratch. Here is how we decide, and we apply the same test before quoting you.
If you do build, who builds matters as much as what. How building with a forward deployed engineer differs from an outsourced dev shop.
Working systems for the inside of a business, not consumer apps. Boring in the way that infrastructure should be boring.
The interface your operations team uses all day, replacing the shared spreadsheet that three people have accidentally overwritten this month.
Somewhere your customers can check status, submit information and pull documents, instead of emailing someone on your team to ask.
The connective work between systems that were never designed to meet. Often the smallest build with the largest effect on a working day.
Built on infrastructure you own, with credentials in your name and documentation for whoever maintains it next.
How we work →Ask whether the process is genuinely specific to how you compete, or just familiar. Familiar processes usually have a product that handles them. If you have already tried configuring a tool and the workarounds have become their own problem, that is the honest signal.
You do. It sits in a repository you own, deployed to infrastructure in your name, documented for whoever maintains it next. No licence fee to keep paying us, and no lock-in built in on purpose.
That is a normal outcome and we write code expecting it. Standard tools, no exotic frameworks chosen to be clever, and documentation aimed at a developer who has never met us. If you outgrow us, handing over should be uneventful.
Anyone quoting a number before understanding your process is guessing. What we commit to is that the price is agreed and fixed before building starts, quoted in rands, and that first engagements are deliberately scoped small so you can judge the work before committing further.
Sometimes, and we are careful about it. We will review what exists and tell you honestly whether continuing is cheaper than restarting. Occasionally it is not, and hearing that early is worth more than a comfortable quote.
Tell us about the process and we will tell you whether to build, configure something you already own, or leave it alone for now.
Book a call if you want one, or just send the form. We reply within one business day. POPIA-compliant.