Skip to content

Stop retyping the same figure into three systems

System integration

The most expensive job in many businesses is a person moving numbers between systems that were never introduced to each other.

What you get.

Accounting that fills itself in

Invoices, payments and credit notes reach your accounting package on their own, on a sequence that survives a SARS audit.

Payments reconciled automatically

Yoco, Payfast and Paystack settlements matched against orders, so the end of the month stops being a day of detective work.

Stock that agrees with itself

One stock figure across the shop floor, the website and the supplier order, instead of three that drift apart by Friday.

Honest about what cannot be connected

Some systems have no way in. We say so rather than promising an integration that quietly becomes a screen-scraping project that breaks every update.

How this one runs.

  1. Inventory what you run

    Every system, who owns it, what it holds, and whether it has a usable way in. This alone usually finds a subscription nobody is using.

  2. Follow one number

    We trace a single figure through every system it touches and count the hands it passes through. That count is the business case.

  3. Connect the highest-cost hop first

    One integration that removes a daily hour beats four that each remove a monthly ten minutes.

  4. Make failures visible

    Integrations break when a supplier changes a format. Ours alert rather than failing silently, which is the failure mode that actually costs money.

Questions about integration.

Our accounting package is quite old. Can you still connect it?

Sometimes. If it has an API or a scheduled file export, yes. If it is a desktop program with no way in and no export, then honestly no, and the real conversation is whether the cost of moving off it is now lower than the cost of the person retyping into it.

What happens when the other side changes something?

It alerts. Every integration we build reports its own failures rather than going quiet, because the dangerous version of this problem is the one nobody notices for three weeks.

Is this cheaper than replacing everything?

Usually, and that is the point. If the tools you have work and only the joins between them are broken, fixing the joins is a fraction of the cost of a new system. We will say when it is the other way round.

Can you automate a process that is currently email and a spreadsheet?

Yes, and that is the most common version of this job. The trick is not the automation, it is agreeing what the process actually is, because the version in people’s heads and the version in the spreadsheet are rarely the same.

Tell us what your business is running on right now.

Thirty minutes, no charge, no slide deck. We will tell you whether this is something we can build and roughly what it would take. If it is not a fit, we will say so on the call.