If your team retypes it, I can probably automate it.
Automation and AI for South African businesses, built by one engineer in Gauteng.
The work nobody hired anyone to do
In most businesses, someone spends part of every week copying information from one place to another.
- Typing delivery notes and invoices into a spreadsheet, line by line.
- Chasing the same confirmation from the same supplier every month.
- Building Friday's report by hand from four different files.
- Answering the same three questions from customers, again.
None of it is difficult. All of it takes time, and a tired person makes mistakes a system would catch.
Watch one get read
A delivery note goes from an email to a row in a tracker, checked on the way.
A delivery note arrives by email.
Load tracker Sample data
| Reference | Date | Customer | Weight | Amount | Status |
|---|---|---|---|---|---|
| DN-20417 | 13 Sep | Example Freight | 11 870 kg | R 5 200.00 | Checked |
Made-up example data. The values are found by a small parser running in this page.
What I build
Six kinds of work. I scope each job to what your business needs, not to a package.
- Document automation
- Invoices, statements, delivery notes and forms read, checked and written into your spreadsheet or system.
- Workflow automation
- The manual steps between the systems you already use: reminders, forwarding, reports and alerts when something stops.
- AI agents
- An assistant for one job, such as sorting incoming email or drafting a reply from your own documents for a person to approve.
- Lead automation
- Enquiries captured, qualified against your criteria and followed up, so none wait unanswered in an inbox.
- Research and analysis
- Research where every source is opened and recorded, and analysis of data or results for business and academic work.
- Consulting
- A look at how your team works, a ranked list of what is worth automating, and a plain plan you can build with me or anyone else.
A Gauteng logistics operator received load confirmations and supplier invoices by email, and staff retyped them into a tracker. The workflows I built now read each document, check the figures and write the data in. Anything the software is unsure about goes to a person.
How we would work
You see a written scope and a fixed price before any work starts.
A conversation
You describe the work your team repeats. If automating it will not pay for itself, I say so.
A written quote
What will be built, how it will be tested, how long it takes and what it costs. Nothing starts until you approve it.
Built on your documents
You watch it work on your own examples. What it gets wrong, I fix before it goes live.
Handover
A plain explanation of what runs and what to do if it stops. I keep watching it for an agreed period.
Who you would work with
I am Mualusi Mutele, an engineer in Gauteng with a BEng in Computer Engineering from the University of Pretoria. I build automation with Python, n8n and language models.
I work alone. The person you talk to is the person who builds it, and I would rather tell you a task is not worth automating than build something you will not use.
How I handle your data
- Your documents are used only for the work we agreed.
- I ask for the access the job needs and remove it when the work ends.
- Personal information is handled under POPIA. Where it is stored, and for how long, is agreed in advance.
- Your data is not shared with anyone.
Tell me about one task your team repeats
I will reply with whether it is worth automating and what a first step would cost.
Write to info@stanautomate.co.za