Workflow automation for the admin that sits between your systems
Workflow automation hands the repetitive steps between your systems — the copying, the chasing, the re-typing — to software that does them the same way every time. Most operations lose money not on the work itself but in the gaps between WhatsApp, the spreadsheet, the accounting package and the person reconciling all three, where jobs stall and errors hide. We close those gaps using the systems you already pay for, and leave the judgement with people.
Built for how business actually runs here
Automation designed for a European office assumes one currency, stable power, cheap data and a clean API — a way for two systems to exchange data without a person in the middle. We assume the opposite: quotes priced in more than one currency, a customer who will only ever use WhatsApp, a supplier who photographs an invoice on a phone, a connection that drops mid-submission. Every workflow queues and retries, and we design around fiscal receipting, mobile money confirmations and local bank statement formats rather than pretending the process is the same as somewhere else.
Connecting the systems you already own
The cheapest automation project buys no new software. We connect your accounting package, payroll, dealer or property management system, Microsoft 365 or Google Workspace, the Excel and Sheets files that have quietly become systems of record, and InOne CRM where you want pipelines, invoicing and a unified inbox together. Where a system has a proper API we use it; where it does not — and many long-serving local systems do not — we work with scheduled exports, watched folders and emailed reports. Unglamorous, but reliable.
Approvals, exceptions and a trail you can audit
A workflow that cannot be questioned later is a liability, so every step records what it did, what it read and who approved it. Rules decide what runs unattended and what stops for a human: a purchase above an agreed threshold, a supplier not on the approved list, an invoice that does not match the delivery note. Exceptions go to a named person with the evidence attached, not into a shared inbox.
When a physical event starts the workflow
Automation is worth more when the trigger is a real event rather than someone remembering to type something. A vehicle recognised at a gate, a tag read on a pallet or a scan at a store room can open a job, notify a supervisor or raise the invoice. Harris Auto runs our Front Door WhatsApp concierge in production, where an inbound message becomes tracked work instead of a note on someone's phone. At Highlands House, a boutique guest lodge in Harare with 36 en-suite rooms, we are building a hotel operating system in which bookings, housekeeping and billing move through one flow.
You own the automation
We use established automation engines — among them n8n, Make and Zapier — and write custom services where a packaged tool would be forced. The choice is an engineering decision based on your data sensitivity, volume and where the workflow must run. Every workflow is documented in plain language, and if you part ways with us you keep the diagrams, credentials and logic.
What it covers
Document and invoice handling
Supplier invoices, delivery notes and statements are read, matched to the order and posted for approval. Anything that does not match cleanly is flagged for review.
WhatsApp as a front door
Enquiries and job requests arriving on WhatsApp become structured records with an owner and a due date. Customers keep the channel they use; you get a queue you can manage.
Reconciliation and data hygiene
Payments, bank entries and mobile money confirmations are matched to invoices on a schedule, so the exception list becomes the day's work instead of the whole ledger.
Approvals with real thresholds
Spending limits, discount bands and credit rules live in the workflow rather than in someone's memory, and requests above a limit route to the right approver with evidence attached.
Resilient to interruptions
Workflows queue when network or power drops and resume in order when service returns. A failed step alerts a person rather than failing silently.
How it works
Site assessment
In week zero we walk the operation and follow one process end to end, recording every handover, spreadsheet and message thread, and documenting the systems you already hold. We then agree which single bottleneck is worth automating first.
Integration
Over weeks one to three we connect the systems involved — accounting, CRM, HR, point of sale, scanners or site hardware — and let the workflow observe and record before it may act. That shakes out awkward data before anything runs on live work.
Rules and guardrails
In week four we write the decision rules with your team: what runs unattended, what needs approval, what must escalate and to whom. We test them against real or historical transactions, so you can see how the workflow would have behaved on last month's work.
Go live and optimise
From week five the system takes the workflow, with weekly reviews of exceptions and failures. Rules are tuned as the operation changes, and the next process is scoped once the first runs quietly.
Questions buyers ask
Our accounting system is old and has no API. Is automation still possible?
Usually, yes. We automate around the exports, emailed reports, database views and file drops the system already produces. It is less elegant than a direct connection, but it is stable and avoids forcing a system replacement you did not ask for.
How long before a first workflow is live?
A typical first system takes approximately four to six weeks from site assessment to go live. Anything touching payroll, tax or multi-currency billing takes the full period, because those rules need testing against historical data before they are trusted.
What happens when the internet or power goes down mid-process?
The workflow queues the work and retries in order when service returns, and anything that cannot complete alerts a named person. Where a process must keep running through an outage, we run the automation engine on site and synchronise afterwards.
Will this put our administrative staff out of work?
That is your decision, not a promise we make. Automation removes the copying and chasing; the judgement, exceptions and customer relationships stay with people, and the exception queue still needs someone who understands the business.
Who can see our data, and where does it live?
Workflows run in your own environment or a dedicated tenant, with retention agreed in writing before we build. Access is controlled and logged, and you are told where each piece of data sits and which third parties a workflow touches, if any.
Book a platform briefing
Bring one process that frustrates you — the invoice run, the job card trail, the report nobody has time to build. In a 15-minute technical discussion we will tell you whether it can be automated with the systems you already own. Email sales@eigenstatesystems.com or message us on WhatsApp at +263 77 636 6999.