The quality of our analytical thinking
Framing the question properly, choosing the method it needs, and testing the answer before anyone relies on it.
About SA Informatics
SA Informatics is an African data analytics and data science firm. We combine data science, analytics engineering and product development around one analytical problem at a time.
Why we exist
Most organisations don't have a shortage of data. They have a shortage of analysis they can rely on.
When an important question has to be answered, the work is still manual, fragmented and dependent on one or two people.
The same questions are rebuilt from scratch. Models are built and never reach a decision. Useful findings disappear into a slide deck when the engagement ends.
Framing the question properly, choosing the method it needs, and testing the answer before anyone relies on it.
Some problems stay bespoke. Others show patterns that justify a product: a method that reruns on new data, without being rebuilt each time.
The expertise behind the work
Applied AI applications
Applications that read enquiries and documents, apply business rules and product knowledge, and prepare the work for review.
See the applicationsForecasting and demand planning
Outlooks built on a business's own history, compared against simpler methods on unseen months, with ranges and scenarios.
See a forecast evaluationMarket and competitor analysis
Share tracking across competitors and periods, with every movement traced to who drove it.
See the vehicle-market analysisPerformance analysis
Price separated from volume, contributions that reconcile to the total, and unusual movements checked before they are acted on.
See the retail analysisAnalytics engineering
Pipelines pinned to the data release they came from, so every result reproduces and every refresh runs the same way.
See how a result reproducesHow we work
Answer needed once
Answer needed repeatedly →
Routine question
Answer needed once
A one-off question with clean data rarely needs outside help.
Answer needed repeatedly
A standard report that recurs is what reporting tools are built for.
Complex question
Answer needed once
A hard question you'll ask once needs rigour, not a system. We do these too.
Answer needed repeatedly
A hard question you'll keep asking: we answer it, then build the method into something your team keeps using.
We agree the decision the analysis serves, what counts as an answer, and whether the question will recur.
We assemble the data, reconcile definitions across sources, validate inputs and record where each value came from.
Descriptive, diagnostic or predictive methods, as the question requires, and only the ones it requires.
You get the answer with its uncertainty and assumptions, in a form built for the decision.
If the question recurs and the value justifies it, we build the method into a system that reruns on new data.
Analytics engineering happens at the Structure stage, as part of the work rather than a separate project. Product engineering happens at the last stage, when a recurring question justifies it.
A dashboard shows what happened. It doesn't explain why, what is likely next, or which factors matter.
If it can't be validated, explained or used in a real decision, its sophistication is beside the point.
AI, machine learning, a data lake or a dashboard may be part of the answer. They are not the starting point.
If an important question is answered every month, rebuilding the analysis by hand each time is not sustainable.
You should be able to see what the data represents, what was assumed and how it was validated. False precision damages decisions.
We use AI in two ways: as methods within data science where a question needs them, and in applications that take on work your team repeats, such as turning enquiries into quotations. Either way we start from the task and the result, and your team stays in charge of what goes out.

Describe the question, the data you have, and whether you'll need the answer again. We'll tell you whether we're the right fit.