Software Engineering.
Rapid Efficiency.
The engineering team for companies whose systems cannot stop.
We build the systems businesses run on, we take over the ones somebody else built, and we stay on afterwards to run them. Asset management, mining operations, compliance, and the automation that sits inside those processes.
Two ways in
Scoped or embedded
A defined outcome for a defined price, or open-ended capacity up to running your whole technology function.
Where it runs
Cloud, on-premises, offline
The same engineering discipline whether the target is Kubernetes or a server on a mine site.
01
Start here
Start where you are.
Four ways in, depending on what is actually in front of you.
02
Where most people start
You do not need to know what your system is built in.
Most of the people who call us cannot tell us what their software is written in, where it is hosted, or who holds the passwords. That is a normal position to be in, and it is usually sorted out in days rather than months.
We map what you have, document it, and give you costed options in plain English before you commit to anything. If it turns out you do not need us, we will put that in writing too.
01
Map
What exists, where it runs, and who holds the keys.
02
Document
Written down, in plain English, and yours to keep.
03
Cost the options
Including the option that says you do not need us.
03
Who we are
Building something a business can actually run on.
Claer & Volker was founded in 2020, out of frustration with the dazzle-and-bill end of our industry. Building something shiny at a large price point is easy, and a lot of software gets sold that way. Building something a business can actually run on is harder, and it is the only work we are interested in.
We are a small engineering team in Pretoria. You deal with the people writing the code, including whoever is making the architectural decisions, rather than with an account manager who relays your questions to a team you never meet.
Founded
2020
Based
Pretoria, South Africa
You deal with
The people writing the code
The team, Pretoria
fig. 02
04
Disciplines
What we actually do.
Six disciplines. Most engagements draw on three or four at once, and they are not sold separately.
05
Agentic process automation
Where automation pays.
Software that carries out a multi-step task inside your business, using your systems and your data, and hands off to a person at the points where a person should decide. Not a chatbot on your website, and not a subscription to somebody else’s platform.
Most of the interest we get in this is genuine, and most of the processes people bring us should not be automated this way. Some are better handled by ordinary code, which is cheaper and produces the same answer every time. Some should be simplified out of existence instead. A few are worth real money, and those are the ones we build.
Which is why we start by working out which is which, in a paid assessment, rather than agreeing to build an agent and finding out together during delivery.
06
How we work
Two ways to work with us.
We work in a version of Agile. The textbook assumes a team size and a client relationship most of our engagements do not have, so the ceremonies that do not earn their place have been dropped.
Defined outcome, defined price
Scoped Delivery
We consult, design, build, run it through UAT, host what needs hosting, and maintain it afterwards. This suits you when you know what needs to exist.
Open-ended capacity
Embedded Function
Engineering capacity, up to and including running your entire technology function. For one client we are their in-house engineering department. This suits you when the work is continuous, or not yet defined enough to price.
You own what you pay for
The code, the data, the credentials, the infrastructure accounts and the documentation are yours. We treat it as work product, and we do not hold any part of it back.
Discovery before commitment
We do not price a build off a first conversation. What we find is written down and it is yours, including the parts that argue against the work.
Documented handover from the start
Every system we run has a written inheritance document covering what it does, how to run it locally, how to deploy it, and where the decisions were made.
07
Case studies
Case studies.
Three engagements, written up in enough technical detail to be useful. Client names are withheld by agreement.
Case 01 / Cloud and on-premises
Asset management and maintenance
One architecture deploying as a multi-tenant cloud platform and as a genuine on-premises install, covering eleven functional areas of an industrial operation.
Case 02 / Agentic process automation
Agentic process automation in production
An agent doing real work inside an operational system, with guardrails, an audit trail, and a person in the loop at the points that matter.
Case 03 / Offline-first
Mining operations without a signal
An offline-first operations application built so that losing connectivity is an expected state rather than an outage.
08
Insights
What we are thinking about.
We write about problems we have actually had to solve, which is why there is less here than on a site that publishes weekly.
The Future Belongs to Businesses That Put People First
AI is becoming table stakes, which is exactly why customer experience, not technology, will separate the companies that thrive from the ones that merely keep up.
Andrea Dugmore
·
·
·
·
Agentic Process Automation
Scaling correctly comes first.
Automation applied to a process nobody has defined does not produce scale. It produces the same confusion, faster.
Ruben Coetzee
·
·
·
·
Software Design & Development
Just because you can build it, does not mean you should.
AI has lowered the cost of building software to almost nothing. It has not lowered the need for judgement, and that gap is where the value is won or lost.
CE van der Dussen
·
·
·
·
Software Design & Development
09
Two ways in
Free, self-service
Start with a health check.
Answer some questions about your systems and we will write back with what we see. It is free, it takes about 15 minutes, and there is no call at the end of it unless you ask for one.
Fixed fee
Or book an assessment
A fixed-fee engineering assessment. Two weeks, a written report, costed options with the trade-offs stated. The report is yours to keep and act on, whoever ends up doing the work.
Claer & Volker
453 Winifred Yell St, Garsfontein
Pretoria, South Africa
info@claervolker.com
© 2026 Claer & Volker
·
·