Will my non-technical team actually use it?
Yes — that's designed in, not hoped for. Systems are built for the phones your team already has, in plain language with big buttons. I import your existing spreadsheets so nothing gets recaptured, we run the new system alongside the old way until everyone trusts it, and I train your people myself. After launch, questions go straight to me on WhatsApp.
We're not a tech company. Is a custom system overkill for us?
Most of my clients aren't tech companies — they're construction, security, retail, logistics and medical businesses between 5 and 100 people. If your team runs on spreadsheets, WhatsApp and paper, you're exactly who this is for. And in the free chat I'll tell you honestly if a system won't earn its keep — some headaches don't need software yet.
How much does a custom business system cost?
A custom system starts with a once-off setup from R4,999, then a monthly from R2,499 that includes hosting, support and backups. Most systems land between R2,499 and R4,999 a month, depending on size.
Do I own the system?
You own all your data and can export it anytime. The system's code stays ours and is licensed to you while you're on a plan. If you want to own the code outright, that's a separate buyout — just ask.
What happens to my system if I cancel?
You get a full export of your data and your system access ends. There are no per-user fees, and after the first 12 months you can cancel with one month's notice.
Do you charge per user?
No. You pay for your plan, not per login. As your team and data grow, you simply move up a tier — never a per-seat charge.
Is my data safe and POPIA-compliant?
Yes. Your data is hosted securely, backed up, and never used for anything but running your system. You stay in control of it, and it's exportable anytime. For data in your system you're the responsible party and I act as your operator.
Custom system or off-the-shelf software — what's better?
Off-the-shelf is faster to start, but you bend your process to fit it and pay per user. A custom system fits exactly how you work, with no per-seat fees and your data in your hands.
Do you build websites too?
Yes. Websites are a once-off build that you own outright — one-page from R6,499, business sites from R11,999, online stores from R19,999. No Wix, no monthly platform fees, and the website files are yours to host anywhere.
Where are you based?
I'm based in Pretoria and work with companies across South Africa. Everything runs remotely, and I usually reply within a few hours.
How long does it take to build?
A proven system can be live in about two weeks. Larger custom builds take longer — you'll get a clear timeline in your quote before anything starts.
Do you use AI when building systems?
Yes — as a tool, the same way I use a database, a compiler or a test suite. Modern AI-assisted development lets me design, build, test and change systems considerably faster than typing every line by hand, and that speed is part of why a custom system starts at R4,999 rather than R80,000. What it does not do is the work that decides whether the system is any good: understanding how your business actually runs, designing the process, choosing the architecture, testing it against real use, deploying it and supporting it afterwards. That judgement is mine, and so is the responsibility for it. You are paying for a system that works — not for a word count.
Can you replace our spreadsheets?
Usually, yes — and the existing spreadsheet is the best possible starting point, because it already describes how your business works. I import what is in it so nothing is recaptured, and the system keeps the parts that were doing real work while removing the parts that break: broken formulas, five versions of the same file, and no record of who changed what.
Can it work with software we already use?
Often, yes. If your accounting package, payroll or supplier system has a way to export or connect, data can move between them instead of being retyped. Some products make this easy and some deliberately make it hard — I will tell you which yours is before you commit, not after.
Can we start with just one process?
That is usually the right way to do it. Pick the one that hurts most, get it live and in daily use, then decide whether the next one is worth it. A smaller first build is cheaper, faster to get value from, and tells you whether working together suits you before anyone commits to anything larger.
What if I do not know exactly what I need?
Most people do not, and you are not expected to arrive with a specification. Show me the spreadsheet, the WhatsApp group, the paperwork or the software that does not fit, and I will map what actually happens and tell you what is worth building. If the honest answer is that a system will not earn its keep yet, I will say so.
