You are your company's entire knowledge base
What's the price for this client? Ask the owner. Was the deposit returned? Ask the owner. Who's working Saturday — you get the idea. No engineer would design a server this way. Yet that's exactly how companies end up once they've grown.
If you recognized at least two of these — your business already has work that can be handed over to a system. And you don't have to know which: you see the friction, I'll turn it into a task.
“Oh, that takes us only five minutes”
— what I usually hear at the first meeting
An hour later it turns out those “five minutes” add up to several hours a day.
I have never seen a perfectly organized business
Almost no business starts with a perfect system. Processes grow one step at a time: first a spreadsheet, then a chat, then another spreadsheet, then a person who “just knows how things work around here”.
First we look at how people actually work — the way a gardener first watches where people prefer to walk, and only then lays the paths.
And I have never looked for one.
Payroll stopped being something to argue about
in daily use
the problem
Every month the owner and the staff burn hours on the same questions:
- what time did the employee come in?
- why was overtime added?
- why the fine?
- why this salary amount?
- where can I even see the history?
what we did
Employees clock in and out from their phone, with geolocation when needed. The system counts hours, shifts and overtime, calculates salaries, bonuses and fines by your rules, and shows each employee their pay in real time. Non-standard cases the manager adjusts manually — with a comment.
before
- overtime was checked by hand
- mistakes surfaced after payroll was done
- shifts lived in people's memory
after
- it counts itself
- a discrepancy shows up before payday
- every shift has a record
Employees get transparency, the manager gets control without constant back-and-forth.
Result: payroll for 10 employees takes at most 10 minutes instead of several hours a month.
Shifts are logged only through the system — the paper logbooks are gone.
You've tried before — and got burned
That's why the work is structured so you risk little:
I watch how people use the system: if it's inconvenient, the system needs fixing — and I fix it
I stay inside: I maintain and evolve what I built
the working version appears inside your actual process — you can touch it
we start with one task that pays for itself — the risk is capped by the size of the first step
the system lives on your servers from day one, you hold the documentation and the access. Any developer can take over: you don't depend on my personal involvement
I work until the result.I don't sell hours and I don't bill for every new idea inside the agreed task: until your people use the system the way it was meant, the job is not done.
principle #1How the work is structured
No months-long specifications, no analyst department, no tender. Six steps — through the owner's eyes.
Why so fast
Usually there is a chain of people between an idea and a working system: a business consultant studies the process, an analyst writes requirements, a developer writes code. Every handover costs time, approvals and meaning lost along the way.
In my work these roles are not split: I study the process myself, design the solution myself and bring it to a working system myself. That is why the first working version appears in days, not months.
You pay neither for code nor for advice — you pay for a system your people are using within a week.
What changes after the rollout
The result is a business that needs less manual work. I won't promise percentage savings; here is what actually happens:
Everyone spends the freed-up time differently. Some launch new projects. Some stop hiring for every growth spurt. Some simply start going home earlier.
There is a task. Do you know what it is?
yes, I know → one-off project
You hand the task over — I carry it to the result.
from AED 7,000
price and timeline are locked before we start
Payroll: 10 minutes instead of several hours — open the demo →
not yet → ongoing partnership
We start by choosing the tasks and build from the foundation up: in the right order every next block lands faster.
from AED 20,000 /mo
improvements included — no separate bills
This is how I have run my own business for ten years, system after system — open the demo →
One-off — when you already know what needs to be done. Ongoing — when you want to improve the business systematically without hunting for what to change first.
Why the price comes after we meet
I don't take on dozens of projects at once: it matters to me to understand your process personally and answer for the result. Two businesses with the same headcount can differ in complexity several times over. So first I look at how your processes work and size the job — only then do I fix the price. After the start it doesn't change: I answer for the result, and inside the agreed task every new idea doesn't turn into another invoice.
Six months in, the company works differently: every change closes another bottleneck — and the effect compounds.
I was the owner who needed these systems
For ten years that owner ran Go Rent: event rentals, a warehouse, staff, payroll, four locations. I built every system for myself because I was drowning without it — and I know what happens to a system after launch.
I built every Go Rent system myself: shift tracking and payroll, deposits that never touch personal cards, analytics, the client platform, the mobile app. Technology is the arsenal: code, integrations, payment mechanics, AI. First I look at how the process works and where it breaks — only then do I build. I have no ready-made methodology: the tool appears once it's clear what exactly keeps the business from working simpler.
My dissertation was about multi-million decisions based on data that could be off by as much as twenty percent. The real question was: which decision holds up even when the input data is wrong? I use the same discipline to decide what to change first in your business — and what not to touch at all.
