
What AI actually costs in South Africa
Rand-denominated budgets, dollar-denominated APIs, and the costs South African teams keep missing.
AI Agents South Africa
Build AI agents, knowledge and RAG systems, and custom AI features around your business systems. Custom AI development from South Africa.
Free consultation
Six questions, then pick a time.
Would rather just email? support@webparam.org
Four shapes custom AI work usually takes.
Multi-step AI systems capable of working with relevant tools, data and business systems.
Systems that retrieve the relevant information before answering or acting on it.
Adding AI capability to software you already ship, designed around how it is actually used.
Internal systems and tools that let a team do AI-enabled work without rebuilding it each time.
Not the model. The loop around it, and the systems it is allowed to touch.
Described by capability rather than by vendor. What is possible in a given case depends on what your systems expose.
Patterns rather than case studies — these describe the shape of the work, not named engagements.
Answers from your own material, and says where the answer came from.
Reads what arrives, extracts what matters, and routes the exceptions to a person.
Carries out recurring multi-step operational work across more than one system.
Classifies a request, gathers context, drafts a reply and escalates when it should.
Gathers and summarises material across sources for a decision that needs it.
An agent embedded in a product, working within that product's own rules.
A trigger starts it, the agent works with what it has been given access to, and a person stays in the loop where it matters.
The capabilities agent work usually draws on. Most systems end up using more than one.
What the agent is for, what it may touch, and what must never happen without a person.
Tools, data access, memory, rules and the points where a human stays in the loop.
One task, done properly, in production. Narrow is what makes it possible to evaluate.
Measure it against real use, then widen the scope only where the results justify it.
And, just as usefully, where it does not.
Not every problem needs an agent: If a task follows the same path every time, ordinary automation is cheaper, faster and easier to reason about when it goes wrong. An agent earns its complexity when the path genuinely varies.
Agents make more model calls than a single-prompt system — each step is a call, and each call carries context. That multiplies a per-token price into something worth modelling before a build, particularly against a rand budget and dollar-denominated provider pricing.
It is also why the model choice per step matters. Using a reasoning model for every step of a system when most steps are classification is one of the more expensive habits to fall into.

Rand-denominated budgets, dollar-denominated APIs, and the costs South African teams keep missing.
A local region doesn't mean local inference, a rand invoice doesn't mean rand exposure, and POPIA doesn't require in-country processing. The three questions South African teams should answer before committing to an AI provider.
An AI agent is a system that works towards a task over several steps rather than answering a single prompt. It interprets what needs doing, chooses an action, uses a tool or business system to carry it out, checks the result, and then continues or hands over to a person. The difference from ordinary AI use is the loop and the tools, not the model.
Typically: answer questions from internal material, process incoming documents, carry out recurring operational work that spans several systems, handle first-line support with escalation, or add an AI capability inside an existing product. The common thread is work with several steps and access to systems.
Yes. Custom AI development is one of the core services, covering agents, retrieval systems, AI features inside existing products and internal AI platforms, built around your requirements rather than configured from a template.
Yes, and it usually has to in order to be useful. At a capability level that means CRMs, databases, internal APIs, document stores, email, knowledge bases and approval workflows. Exactly what is possible in your case depends on what those systems expose, which is one of the first things a scoping conversation establishes.
Retrieval-augmented generation. Instead of relying on what a model learned during training, the system first retrieves the relevant passages from your own documents or data, then answers using them. It is how you get answers grounded in your material, and how an answer can cite where it came from.
Almost certainly not. Most business problems are solved by combining existing models with your own data, tools and workflow. Training a model is expensive, slow to iterate on, and rarely the thing that determines whether the result is useful.
By the job each step does. Agentic work leans on reasoning and reliable tool use, retrieval leans on embeddings, and the drafting steps are ordinary language work. Often more than one model is used in a single system. The catalogue groups models by what they are built for, which is where that comparison starts.
The agents that work start small and specific. Tell us the task, and we will tell you whether it needs an agent at all.
Free consultation
Answer six questions and pick a time. No charge, no obligation.
Would rather just email? support@webparam.org