You are probably choosing between four options. Here they are, fairly described.
Very few buyers are choosing between us and one competitor. The real comparison set is broader and less flattering to everyone in it: a global platform vendor, a local automation firm, building something in-house, or carrying on with spreadsheets. Each of those is the right answer for some sites. This page sets out when each one wins, so the conversation can start from the same map.
What each option is genuinely good at.
A global platform vendor
Wins when: you are a large group standardising across many sites and several continents, you have an internal automation team, and you need the vendor's name on the architecture for corporate or lender reasons.
The friction on an African site: licensing is priced for a different cost base; the architecture generally assumes reliable connectivity and a local integrator to configure it; and the support relationship runs through a partner who may be in another country. When you need a report in your regulator's format, it is a feature request.
A local automation or electrical firm
Wins when: the work is panel building, PLC programming, motor control or site electrical installation. They know your plant, they are down the road, and they should be doing that work.
The friction: most assemble someone else's platform rather than owning one, so the software layer is a reseller relationship. Historical data, retention, reconciliation and reporting tend to be the weakest part of the offer, because they are the part nobody in that supply chain actually built.
Building it in-house
Wins when: you have a capable automation or IT team, a narrow requirement, and a genuine appetite to own it for a decade. Plenty of good systems start this way.
The friction: the first version is cheap and the tenth year is not. The predictable failure is personnel — the system runs until the person who built it leaves, and then it becomes something nobody wants to touch and nobody can replace quickly.
Spreadsheets and the shift log
Wins when: the site is small, the process is stable and the numbers genuinely are captured. This is the real incumbent almost everywhere, and pretending otherwise wastes everyone's time.
The friction: it records twelve moments a day, stops at handover and at weekends, and cannot answer a question about a specific night three months ago — which is exactly when the questions arrive, from a customer, an auditor or a regulator.
Four things that follow from owning the whole stack.
- One team from the terminal block to the chart. We build the sensors, the gateway firmware, the platform and the dashboards. When a reading looks wrong, the diagnosis does not cross three support contracts — see the technology.
- Engineered for the conditions rather than adapted to them. Battery-buffered logging through outages, store-and-forward over marginal links, hardware designed for months between visits. Those are not features added for Africa; they are the design brief, because that is where the company was built.
- Delivery that does not wait for a flight. Remote assessment, hardware pre-configured in Johannesburg, installation by your own technicians under live guidance, first deployment typically live in two to six weeks — see how we deliver.
- We read your equipment before selling you ours. New instrumentation only where a measurement is genuinely absent. On most plants a large share of what you want to see already exists in a PLC, a drive or a meter and is simply not retained — which is the single biggest lever on what a project costs.
The commercial consequence of the last point is worth stating. A supplier whose margin sits in hardware has an incentive to specify more of it. Ours sits in the platform and the engineering, which is why the first thing we ask for is photographs of your existing panels and meters — and why the assessment often reduces the quote rather than growing it.
Three questions buyers use to separate us from the alternatives.
- "Will the record have holes in it?" On sites where power and connectivity are intermittent, this is the question that eliminates most options quickly. Monitoring that stops when the supply does produces gaps precisely at the events worth analysing.
- "Can it produce what my regulator asks for?" Increasingly the deciding factor. Kenya's water regulations require an automated meter and a two-year daily record; Nigeria's require monitoring equipment installed at the permit holder's cost; Zimbabwe's effluent band is calculated from concentration and mass flow; Uganda's Q-Mark scheme requires process monitoring records. Export in the required shape is a build decision, and we can make it.
- "Who answers when it breaks?" Engineers, on WhatsApp, in your working hours — because the people who designed the system are the people supporting it.
If, after reading the four options above, one of the others describes your situation better, that is a useful outcome and worth acting on. Where it is genuinely close, the cheapest way to decide is the assessment: it produces a written scope and cost band you can put next to any other quote.
Compare us against a written number, not a brochure.
An hour on a call and some panel photographs produce a scope and cost band you can take to any other supplier.