You don't have to know what to automate
You see what causes friction. That is enough — turning observations into a task for the system is my job.
If you recognized at least two of these — your business already has work that can be handed over to a system.
“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.
Don't worry if everything is currently set up “wrong”
Almost no business starts with a perfect system. Most processes grow organically: first a spreadsheet, then a chat, then another spreadsheet, then a person who “just knows how things work around here”. That is normal.
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.
I have never seen a perfectly organized business. And I have never looked for one.
Transparent time tracking and payroll
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.
Payroll stopped being a source of arguments: employees get transparency, the owner gets control without endless back-and-forth.
Result: payroll for 10 employees takes at most 10 minutes instead of several hours a month.
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: 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 not a new program — it's 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 — see the system →
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
Here is a system I run in this format — see the system →
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 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.
Who I am
I'm not a consultant and not a dev studio: I build digital products myself and work every day with systems that live inside a real business. So I know not only the technology, but the problems that start after launch.
My profession is digital systems where interfaces, data, automation, AI and real human processes meet: from payment services to my own products. 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.
Every solution I offer clients grew out of real practice. I first built them for problems I faced myself as a business owner. Today that experience helps me find working solutions for other companies faster.
