Nothing lives in one place
A bit in someone's head, a bit on paper, a bit lost along the way.
Technologies I build with
A brief introduction.
A short video about how I work and what I do for you.
Nobody's lying. Nobody just knows.
The information exists. It's just scattered across people, paper and chats.
Nothing lives in one place
A bit in someone's head, a bit on paper, a bit lost along the way.
Scheduling is chaos
Appointments over WhatsApp, paper and memory, all at once.
Every report eats half a morning
Five spreadsheets, copy, paste, reconcile by hand.
Everything lives in WhatsApp
A chat nobody can look up later.
Apps that do one thing and do it well.
I don't sell abstract services. This is what ends up installed and in use.
01Inventory control
Before: Monday's count is worthless by Wednesday.
After: stock updates itself the moment someone logs an entry or an exit.
02Work orders and maintenance
Before: each machine's hours live in a notebook, and maintenance happens after something already broke.
After: every machine flags by hour meter before it breaks, and that creates the order, with an owner, a deadline and a closing photo.
03Invoicing
Before: invoices are typed by hand from data copied elsewhere, and some never get collected.
After: they come straight from what you already recorded, and what's still unpaid is in plain sight.
04Appointment booking
Before: appointments live in a notebook or a chat, and every so often two collide.
After: your clients book themselves, get a reminder, and you open it and see the whole day.
05Client portal
Before: they call to ask where their goods are.
After: they log in and see it, with photo and time.
06WhatsApp assistant
Before: someone answers the same questions all day.
After: the assistant answers with real data from your operation.
07Management dashboard
Before: you ask for a report and wait.
After: you open the dashboard and it's there.
08Website
Before: your website is years out of date, or you don't have one at all.
After: a modern website that works, loads fast and looks right on any screen.
-
Before: Monday's count is worthless by Wednesday.
After: stock updates itself the moment someone logs an entry or an exit.
-
Before: each machine's hours live in a notebook, and maintenance happens after something already broke.
After: every machine flags by hour meter before it breaks, and that creates the order, with an owner, a deadline and a closing photo.
-
Before: invoices are typed by hand from data copied elsewhere, and some never get collected.
After: they come straight from what you already recorded, and what's still unpaid is in plain sight.
-
Before: appointments live in a notebook or a chat, and every so often two collide.
After: your clients book themselves, get a reminder, and you open it and see the whole day.
-
Before: they call to ask where their goods are.
After: they log in and see it, with photo and time.
-
Before: someone answers the same questions all day.
After: the assistant answers with real data from your operation.
-
Before: you ask for a report and wait.
After: you open the dashboard and it's there.
-
Before: your website is years out of date, or you don't have one at all.
After: a modern website that works, loads fast and looks right on any screen.
Working with me takes work off your plate, not onto it.
What I need from you: one call with you or someone on your team. That's it. Servers, domains and backups are on me.
- 30 minutes
A call
You tell me how you work today.
- 48 hours
Fixed-price proposal
Scope and number, in writing.
- 3 days
Clickable prototype
You try it before the code exists.
- 2 weeks
In production
Your team using it from day one.
The questions people don't always ask out loud.
You approve the scope and the number. No surprises halfway through.
A repository in your name from day one. If someday you stop working with me, your system keeps running.
Maintenance and new features, if you want them.
Servers, domains, backups. You manage nothing.
Working with me is simple. I build systems that feel intuitive from day one — not something your team has to fight to learn. I've seen too many companies stuck with systems their own staff doesn't know how to use, or uses wrong, because nobody built it with them in mind. And every change afterward costs a fortune. That doesn't happen with me: I build it around the people who'll actually use it, and making changes later will be easy.
Tell me what's getting out of hand.
I reply within 24 hours. If it's not a fit, I'll tell you on the first call and won't waste your time.
