Skip to content
KordelData

Data, analytics & AI engineering · Harare, Zimbabwe

Most organisations already have the data. Far fewer can act on it.

The numbers exist — in an ERP, a dozen spreadsheets, a scheduling tool, someone’s inbox. We build the pipelines, models and interfaces that turn them into something a decision can rest on, and we say so plainly when the answer is not more software.

Get in touch

A free 30-minute call, no obligation. We scope the problem and tell you if we're not the right fit.

ERPSpreadsheetsSchedulingInboxpipelineone agreed layerdecisions

What we are usually called in for

Four situations, in roughly the order they tend to appear.

The same number has three answers
Finance says one thing, operations says another, and the board pack says a third. Nobody is wrong exactly — each figure is built from a different source on a different definition. Decisions wait for a reconciliation that nobody owns.
The data arrives too late to act on
The report is accurate and it is also history. By the time it has been assembled, checked and circulated, the window it describes has closed and the decision has already been made on instinct.
Skilled people doing mechanical work
Someone capable spends the first week of every cycle exporting, pasting and reformatting to rebuild a file that looked the same last month. The work is necessary, repetitive, and invisible until they leave.
AI with nowhere to stand
A model, a pilot or a tool bought on promise, sitting on data the business does not trust. It produces confident answers that no one is willing to act on, which is worse than producing none.

The pattern does not change much whether the source is a plant, a clinic, a fleet or a trading desk. What changes is the vocabulary.

What we build

Four things. Most engagements start with the first two.

Full detail on each →

Data pipelines and definitions

One place where the operational, cost and volume numbers agree, updated automatically from the systems that already hold them.

Replaces: emailed spreadsheets, manual re-keying, and three departments quoting three different figures for the same month.

Dashboards and reporting

The numbers the organisation runs on, current to the last update rather than to last month.

Replaces: the first week of every cycle spent rebuilding the same workbook by hand.

Process automation

The repetitive work between systems, done by software, with an audit trail.

Replaces: hours of copy-paste, and errors that only surface at audit.

AI systems

Applied where there is enough clean history to justify it — and we will say so when there is not.

Most organisations need the three services above first. AI on data nobody trusts produces confident answers nobody will act on.

How we work

The operation first, the stack second

We start from the decision you are trying to make and the data you already generate. The tooling follows from that, and is usually less exotic than expected.

You own what we build

Source code, schemas and documentation are yours. No proprietary runtime, no licence that stops working if you stop paying us.

Small scopes, fixed prices

Work is broken into pieces with a stated output and a stated cost. If a piece turns out not to be worth building, we say so before it is built.

We will tell you when it is too early

Plenty of organisations do not need a model, a warehouse or a platform yet. Saying so costs us a project and saves you a year.

Automation moves people, it does not remove them

The point of taking mechanical work off a desk is to put that person's judgement somewhere it counts. We do not scope systems on the basis of headcount reduction, and we will not build a business case that rests on it.

How an engagement works

Four steps. You can stop after any of them.

  1. 01

    Brief

    A few minutes

    A short note through the form: what you are trying to get out of your data, and what currently produces it. Enough that the call starts at the problem rather than at introductions.

  2. 02

    Call

    30 minutes

    You describe the organisation and where the numbers currently come from. We tell you whether the problem is worth solving with software yet.

  3. 03

    Scoping

    1–2 weeks

    We map the data you already have, agree what the system must produce, and put a fixed price and delivery date against it.

  4. 04

    Delivery

    Agreed up front

    We build it, connect it to your source systems, and hand over documentation so your team can run it without us.

Not sure whether your data is ready?

That is usually the first thing worth finding out. Bring the reports you rely on now and we will tell you what is fixable and what is not.

A free 30-minute call, no obligation. We scope the problem and tell you if we're not the right fit.