How it works
From “this takes forever” to “this runs itself”, in six steps
Small first job, real data, a person in control at every stage.
The path
Six steps. One job at a time.
Each stage keeps scope honest and a person in the loop.
01
The audit
We look at one ordinary week of your work: where the hours go, which systems hold the information, what keeps falling through the cracks. You get a written shortlist of three jobs, each with its size and its risks.
02
Pick one job
Not a programme. One job with a clear before and after, like "overdue invoices get chased" or "supplier bills get captured". We agree in writing what done looks like.
03
Build in a sandbox
We connect read-only first, to a test copy or a sample of your data where possible. You get a private link to try it before it touches anything live.
04
Shadow mode
The tool runs alongside your team for a week or two, drafting but never sending. Your people compare its drafts with what they would have done. We tune it until the drafts are boring in the good sense.
05
Go live, with approvals
Drafts start going out once someone approves them. You decide who approves what, and which low-risk steps (if any) can run on their own.
06
Keep it sharp
Systems change, suppliers change their invoice layouts, staff leave. We monitor the runs, fix what breaks and adjust as your business changes. When the first job is steady, we look at the next one on the shortlist.
Questions people ask
Plain answers before you start.
Do we need to buy new software?+
Usually not. We build on top of the email, spreadsheets, WhatsApp number and accounting system you already have. If something genuinely needs a new piece, the audit will say so.
What happens when the AI gets it wrong?+
Then a person catches it before it goes anywhere, which is why the approval step exists. Every draft shows where its information came from, so checking takes seconds. Mistakes go back into the tuning.
What about POPIA?+
We design for it from the start. We only touch the data a job needs, keep consent records where messages are involved, control access by role, and log who approved what. We'll work with your Information Officer, and we'll tell you plainly which AI providers process what.
Who owns what you build?+
Two options. Buy it outright: a one-off build, and you own the code. Or run it as a managed service: a monthly fee, where we host, maintain and improve it, and Pragmex keeps the code. We agree which path in writing before work starts.
Will this replace my staff?+
It replaces the copying, chasing and retyping. The people who did that work get to do the part that needs judgement: the tricky customer, the exception, the decision.
How long does a first job take?+
It depends on the job and how clean your data is. Small jobs are quick; the audit gives you a realistic size for each one before anything starts.
Start with the audit
Request my auditPick the job everyone avoids. We'll start there.
Or write to logiq@pragmex-agentics.com · Mon–Fri 08:00–17:00 SAST