About Paicer
Automation that gives people
their time back.
Paicer builds AI automation for South African firms, on the tools they already use. The repetitive work runs on its own, and the judgement stays with the person who should be making it.
Founder
Kobus Kunz, founder
Kobus trained as an architect at the University of Pretoria and practised in workspace and housing design.
In 2014 he moved into enterprise HR systems consulting, and has spent more than a decade implementing time and leave processes for large employers, work that has to hold up in production.
He started Paicer in 2024 and builds every Paicer automation himself, from the discovery call to the handover.
You'll be working directly with the person designing and building your solution. No handoffs, no misunderstandings, no bureaucracy.
Problems
I'm running the business instead of practising.
- 01
The inbox after hours
An enquiry lands at eight in the evening. You see it the next morning, reply by ten, and the person has already booked with whoever answered first.
- 02
Quoting instead of the craft
Quoting eats hours per project. The cover letter, the firm directory and the pricing sheet get rebuilt from the last submission, and the hours come out of the work you trained for.
- 03
The spreadsheet that runs the business
Project tracking is held together with spreadsheets. One person knows how it works, updates happen at night, and nobody trusts the numbers until someone has checked them by hand.
The repetitive part of each of these can run on its own. Automation handles that part and hands the judgement back to the person who should be making it.
Outcomes
Three things every build is measured against.
01
Time back
The repetitive part of the work runs on its own, so people spend their hours on the work that needs them.
02
Lower costs
Fewer errors, faster processes and no extra hire to keep up with the admin.
03
More business
Enquiries answered the moment they arrive, and nothing lost because nobody got to it in time.
How we work
Four rules on every build.
01
Fixed price
Every build is quoted before work starts, and the quote is the invoice.
02
Delivered in sprints
You see working pieces early and test them on your real data before handover.
03
You work with the builder
Kobus Kunz scopes, builds, tests and supports every automation himself. There is no handoff.
04
Your tools, your accounts
Built on what you already run, with every account in your name. Paicer holds none of your data after handover.
Principles
Three questions get asked before any build starts.
01
It never pretends to be human.
Nothing we build depends on fooling someone into thinking they are dealing with a person. If a build only works because of that deception, we do not build it.
02
It removes a burden, not a relationship.
A bot that replaces the person who answers the phone is not the same as automation that sorts the queue so that person has time for the hard conversations. We build the second kind.
03
The freed-up time goes back to the craft.
We ask what the recovered hours are for. If the answer is more time on the craft and with the people, we build. If the answer is more volume with fewer people, we do not.
Our focus
AI that works for people.
There is a version of automation that replaces judgement with scripts and people with bots. That is not what we build.
We automate the repetitive work so your people can focus on the work that needs them, and every system we build hands off to a person at the right moment. We believe technology should serve the team, not the other way around.
Contact
Talk it through first.
A discovery call is 20 minutes and free. You describe the process, and we tell you whether automation is the right move and roughly what it would cost.