Studio open · Accepting briefs / Q3 2026
/
25°43′27″ S   28°19′12″ E  ·  Pretoria, ZA
/
—:—:— SAST  ·  v.2026.05
Acusoft  /  Software studio
Founded MMXX  ·  Pretoria
Edition № 06

Software,
intelligence,
& the patience
to engineer
them well.

We are a small studio of engineers and applied scientists building quietly capable software for organisations whose work cannot afford to fail. We choose long projects over loud ones, and we stay until the system is true.

Currently engaged: 4 active engagements
Chapter 01
The disciplines

Four practices, one studio.

01 ⁄ 04

Software
engineering

Custom systems, designed and written by hand. We work in long-lived stacks that we can reason about — Java, Spring, TypeScript, Postgres — and we instrument what we ship so that the people who run it can see what it is doing.

We treat tests as the documentation that compiles, and migrations as decisions, not chores.

Java / Spring TypeScript Postgres Vaadin Event-driven
02 ⁄ 04

Applied
intelligence

We deploy machine learning where it pays its rent — classification, extraction, forecasting, agentic workflows — with attention to evaluation, drift, and the cost of being wrong. No magic, no demos that don't survive contact with production.

We are equally comfortable fine-tuning a small model and wiring a frontier model into a careful agent loop.

LLM agents Embeddings & RAG Forecasting NLP pipelines Eval harnesses
03 ⁄ 04

Cloud
architecture

Infrastructure as a long-term decision, not a checkout. We design systems that scale where they need to and stay quiet where they don't — because operational simplicity outperforms architectural fashion.

We work across AWS, Azure, GCP, and self-hosted environments, with a strong preference for what an engineer on call at 02:00 can actually understand.

AWS / Azure / GCP Kubernetes (when warranted) Terraform Observability Cost discipline
04 ⁄ 04

Technical
consulting

An outside perspective from people who still ship. We sit alongside in-house teams to assess architecture, recover stuck programmes, and make the kind of clear written recommendations that survive being forwarded to the executive.

Engagements run from a three-week audit to a quarterly retainer.

Architecture review Programme recovery Diligence Embedded leadership
Chapter 02
Selected work

A ledger of quiet systems.

Year
Client
Engagement
Sector
Status
2025
ICE Tech — platform
Long-running platform engineering and reliability programme.
Industrial
ongoing
2024
Tshiamiso Trust
Claims-processing intelligence: extraction, triage, and case routing.
Public benefit
in service
2024
Harmony Gold
Operational data platform — from shaft sensors to a single ledger.
Mining
in service
2023
Jalia Technologies
Cloud migration and re-architecture of a core telecommunications product.
Telecommunications
handed over
2022
Cellstop
Real-time telemetry pipeline for a national vehicle-security fleet.
Vehicle security
in service
2022
Confidential — financial services
Anti-fraud model and decisioning service for a payments processor.
Fintech
under NDA
Chapter 03
The numbers

Five years, compounding.

Founded
MMXX·zar
A studio with the shape of a small workshop, by design.
Combined experience
50+
Years of engineering across the team, in industry & research.
Active engagements
04
We deliberately keep this number small.
Located
25°43′ S
28°19′ E
Olympus, Pretoria. Working hours on SAST.
Chapter 04
The method

How a piece of work moves through us.

M.01

Listen — closely, before assuming.

A first engagement is a series of long conversations. We want to understand the system you already operate, the people who depend on it, and the constraints we cannot see from outside.

M.02

Specify — written, not implied.

We produce a written brief that says, in unambiguous language, what we are about to build and what we are deliberately not building. You sign it. We sign it. It becomes the only source of truth for scope.

M.03

Build — deliberately, with tests.

We work in short iterations against a real environment, with continuous integration and meaningful tests from day one. You see progress weekly. Nothing is hidden until launch.

M.04

Ship — and stay until it's true.

A release is the beginning of a system, not the end of a project. We stand behind what we ship until it is observed to behave as specified, under real load, with real users.

M.05

Maintain — software is a relationship.

Where it is welcome, we continue. Where it is not, we hand the system over with the kind of documentation that we would want to inherit ourselves.

Chapter 05
Begin a brief

Talk to us.

We answer every brief by hand — usually within two working days. The first conversation is free; if we don't think we are the right studio for the work, we will tell you who is.

A brief usually contains:
  • — who you are, and what you do today
  • — the system or capability you would like to build
  • — the constraints we should treat as fixed
  • — a date by which the matter becomes urgent
Studio
17 Midas Avenue
Olympus, Pretoria 0081
South Africa
Voice
+27 12 991 4400
Weekdays · 09h00 – 17h00 SAST
Letters
[email protected]
Replied to by hand
Careers
[email protected]
Open to engineers and applied scientists