The set
Disciplines.
This is how we describe our own work to each other, written for someone who wants to know whether we know what we are doing.
If you would rather start from your situation than from ours:
In sequence
How these fit together in an engagement.
We do not sell these separately. Most engagements draw on three or four at once, and the order they arrive in matters more than the list does.
01
Design comes first, and it constrains everything after it
Software Design & Development sets the domain model and the service boundaries. Nearly everything expensive later is decided here, which is why it happens before anyone opens an editor.
02
Data decisions get made at the same time, not later
Data Engineering is part of that first conversation, because tenancy and isolation are architecture rather than configuration. Retrofitting a tenancy model into a live platform is one of the more expensive pieces of work in this trade.
03
The pipeline exists before the first release
Platform & DevOps comes in early enough that the first deployment to production is boring. A pipeline added after a system is live is retrofitted around habits that have already formed.
04
Quality runs alongside rather than at the end
Quality Engineering is not a phase before launch. Architecture rules and test coverage are part of the build, and on an inherited system they come first of all, before anyone changes behaviour they cannot yet describe.
05
Support inherits something documented
Support & Maintenance takes over from delivery with runbooks and an inheritance document already written. Where we did not build the system, that documentation is the first piece of paid work rather than an optimistic assumption.
06
Automation sits on top of a system that already works
Agentic Process Automation needs somewhere to act and something to act on. An agent pointed at a process nobody has modelled produces confident answers nobody can check.
Delivery management is bundled inside this rather than sold beside it. Planning and architecture stay on one accountable line, because the failure mode of separating them is that nobody owns the result.
The six
The six.
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
Claer & Volker
453 Winifred Yell St, Garsfontein
Pretoria, South Africa
info@claervolker.com
© 2026 Claer & Volker
·
·