Your team is losing hours to admin a system could do.
I build what takes it off their desk: chasing payments, month-end admin, typing the same info in twice. Here’s what one hour a week, at R350 an hour, costs you over a year, and what’s left once it’s fixed.
Today
R0
After
R0
You keep
R0
Per year, in year one
That’s 0 working hours a year back, and a R5 000 fix pays for itself in about 5 months.
3 to 5 quick questions → what that admin costs you each year → a call only if you want one.
Or skip it and just book a callHow it works
Three steps, and you can stop after any of them.
Jordan van Schalkwyk
I ran operations at a Cape Town gym and took revenue growth from 8% to 21% a year. Now I build the systems I wish I’d had.
LinkedInA 20-minute call. Not a pitch.
I ask what the job is, who does it, and how often it goes wrong. That’s the whole call.
I sit in on the real job happening, once.
Not a description of it, the actual thing, as it actually runs, with the actual exceptions. Free, no obligation.
One page: what it costs, and a fixed price to fix it.
A week later, you get a number and a quote. If it’s not worth it, you’ve lost 20 minutes and an hour of sitting in. Nothing else.
What gets built
Operational efficiency, not a product
- Custom, not off-the-shelf. Built for the one job, not adapted from a template that mostly fits.
- Inside your own systems. Your workspace, your login. If I disappear tomorrow, it keeps running and you keep everything.
- Revocable access, wherever that’s possible. No passwords change hands. Any access I need lives inside your own systems, so you can revoke it in one click. If a job genuinely needs a live third-party connection, I’ll say so upfront.
- Measured, not assumed. The baseline is taken before anything is built, so the after number means something.
Before you ask
The questions people actually have
How much does this cost?
I can’t give you a firm number until I’ve had the walkthrough. Guessing now would be making it up. As a guide:
A single fix, one repetitive task, like payment reminders that send themselves: R5,000 to R15,000, plus R750 a month.
A system, several connected steps, like orders, stock and commission in one flow: R20,000 to R38,000, plus R1,500 a month.
A connected operation, several processes sharing data: R45,000 to R80,000, plus R2,750 a month.
The price is fixed and agreed before anything is built. The walkthrough is free either way. Don’t want the monthly? You can pay per repair instead, agreed upfront.
We tried something like this before and it didn’t work.
That’s most people, and usually for a specific reason: it got pointed at a process nobody mapped first. Automating a broken process just gives you a faster broken one. That’s why I watch it before I quote it.
The other common failure is that the fix gets bolted onto the existing workflow instead of built into it: an extra tool, an extra login, an extra step someone has to remember. That adds adoption cost instead of removing it. What I build integrates into how the work already happens, and uses automated systems and AI to take steps out, not add them.
What happens if you get busy, or this doesn’t work out?
It’s built inside your own systems, under your own login. If I vanish tomorrow it keeps running and you keep everything. That’s on purpose.
Can I not just use Zapier, ChatGPT, or hire a VA?
Sometimes, yes, and if that’s the honest answer, I’ll tell you and won’t charge you for finding out. Those are tools; the job is working out what the process should be before pointing a tool at it.
Is this AI? Is my data going into a model somewhere?
Some of what I build has no AI in it at all. It’s just properly built. Where a model genuinely is involved, I’ll be precise about exactly what it sees and where your data goes, before anything is agreed. What I build is POPIA and GDPR compliant.
Ready when you are
Book the 20 minutes
No pitch, no slide deck. I find the one job worth fixing, or tell you honestly that there isn’t one this time.