ABOUT.
THE PERSON BUILDING YOUR SYSTEM
FOUNDER
THE BUILDER.
Luke Petzer
I build the systems businesses run on — ordering portals, client platforms, and the automations that take manual admin off your team. One person, start to finish. I take the scoping call, write the code, run the deployment, and pick up the phone when something needs changing. That is not a caveat I am apologising for: it means the person who understands your workflow is the same person changing it, usually in the same week you ask.
Formally trained in software development through to honours level, then straight into building things people actually put work through. The ordering platform on the Products page is live and taking real orders — not a concept, not a mock-up. I am based in Cape Town and work with businesses across South Africa.
$ whoami
Luke Petzer — founder, and the one writing the code
$ cat what-i-build.txt
Ordering portals · Client platforms · Automations
$ cat who-for.txt
Wholesalers, distributors, and service businesses buried in manual admin
$ cat where.txt
Cape Town — clients across South Africa
$ cat you-own.txt
Source code, database, deployment — transferred to you on delivery
$ availability
TAKING ON NEW PROJECTS ●
HOW_I_WORK
“A system is only worth building if it removes work. If your team still has to re-type an order after it arrives, I built the wrong thing.”
So the first conversation is not about features or which framework I use. It is about where the work actually piles up — who re-types what, who chases which spreadsheet, what breaks when three orders land at once and two people are on leave. I build for that, and I leave out the rest. Anything that does not take work off someone's desk does not need to exist.
WHY WORK WITH ONE PERSON
WHY_LP_WEB
You Talk To The Builder
You explain the problem once, to the person who is going to solve it. No account manager translating in both directions, no scope getting lost between the person who heard it and the person who builds it. Changes get discussed and priced in the same conversation.
The Code Is Yours
On delivery the repository transfers to your account — source code, database, deployment config, all of it. A care plan keeps me maintaining it, but it is optional. If you ever want to hand the system to another developer, you can, and you do not need my permission to do it.
Built Around Your Workflow
Nothing here is a template with your logo on it. If your pricing is per-client and your reps quote off a printed list, the system does that — not the generic version of that. Your team should not have to be retrained into somebody else's process.
STILL READING?
Then something in your process has probably outgrown WhatsApp and a spreadsheet. Give me twenty minutes and I will tell you straight whether a system is worth building for it.