Custom business applications
The system your business actually needs, instead of the one a generic package forces you into. Web applications, internal tools, customer portals and line-of-business systems built around your process.
Services
Software that fits the business you already run.
We build operational systems for South African companies — the software that handles the counter, the fleet, the stock and the money. Six things we do, and we do them properly.
ERP & point-of-sale systems
Stock, assets, orders, invoicing and ledgers in one place, with a counter interface fast enough for a queue. Barcode and QR scanning, receipt printing and offline-tolerant workflows.
Process automation & integration
Connecting the systems you already pay for — accounting packages, payment gateways, SMS and email — so data stops being re-typed and starts moving on its own.
Compliance engineering
POPIA consent and data-retention workflows, SARS-compliant invoice structuring, 15% VAT handling and audit trails that stand up to scrutiny. Built into the system, not bolted on afterwards.
Cloud, data & reporting
Managed database design, secure hosting, backups tested by restore, and reporting built on live operational data. Exports formatted for Xero, Sage and QuickBooks.
Desktop & hardware integration
When the browser is not enough: desktop applications with native access to barcode scanners, receipt printers, signature pads and scales, sharing one codebase with the web app.
Where the money leaks
Most operational losses happen in the handoffs.
Not in the work itself — in the gaps between it. A hire that goes out on a paper docket and comes back three days late without anyone noticing. A damage charge nobody raised. An invoice re-typed into the accounting package with a transposed figure.
Automation is not about replacing people. It is about removing the places where information falls on the floor between one person and the next.
- Quote to invoice — one record, carried through, never re-keyed.
- Return to charge — damage and cleaning fees calculated on the workflow, not on memory.
- Service due to reminder — calendar intervals and recorded usage raise the alert before a unit falls due, not after.
- Ledger to accountant — clean exports to Xero, Sage or QuickBooks instead of month-end archaeology.
- Every action logged — who changed what, when, and what it was before.
Engagement models
Three ways to work with us.
Pick the one that matches where you are. Most clients start with a discovery sprint and decide from there — it is the cheapest way to find out whether the project is worth doing at all.
Discovery sprint
A fixed-scope, fixed-price engagement that produces a written specification, a data model and a costed build plan. You own the output whether or not we build it.
Fixed-scope build
Defined deliverable, agreed milestones, agreed price. Best when discovery has already happened and the requirements are stable.
Retained partner
An ongoing monthly arrangement covering development, maintenance and support. Best for systems that keep evolving with the business.
How it is built
Deliberately unfashionable technology choices.
We pick tools that will still be maintainable and hireable in five years, not whatever launched last quarter. Your system should outlive our involvement in it.
Data layer
PostgreSQL or Azure SQL with row-level security, so multi-tenant data separation is enforced by the database itself rather than by application code that can be bypassed.
Application layer
Server-rendered web applications and typed APIs. Fast on a rural 3G connection, indexable by search engines, and simple enough to debug at 5pm on a Friday.
Security layer
Role-based access control, secrets in a managed vault, web application firewall and rate limiting in front, structured logging and audit trails behind.
Questions
Before you enquire.
The things people ask on the first call, answered up front so the call can be about your business instead.
What does custom software actually cost?
It depends entirely on scope, which is why we start with a fixed-price discovery sprint. That produces a written specification, a data model and a costed build plan with milestones — so you see the number before you commit to the build, not after.
You own the discovery output whether or not we build it.
Who owns the code and the data?
You do. Both. You get the source, and you get full data export in an open format at any time. We do not hold either as leverage.
How long does a project take?
Discovery is usually a couple of weeks. Build length depends on scope, which is exactly what discovery exists to establish — you get milestones and dates in writing before anything is committed. We work in short cycles with something usable at the end of each one, so you are never waiting months to see progress.
Do you work with businesses outside Limpopo?
Yes. Discovery happens on site anywhere in South Africa. Everything after that runs remotely, which keeps cost in the build rather than in travel. Same time zone, same working week.
Can you fix or take over a system someone else built?
Often, yes. We will assess it honestly and tell you whether a rescue or a rewrite is the cheaper path — including when the answer is that you should keep what you have and change a process instead.
What if custom software is the wrong answer for us?
Then that is what you will hear on the first call. If a spreadsheet, an off-the-shelf package or a process change solves it better, we will say so. A project that should not exist is bad for both of us.
Next step
Start with a conversation about the process, not the software.
Tell us what the business does and where it hurts. We will tell you honestly whether custom software fixes it, and roughly what that would take.