About this practice
One engineer, six services, and a strong preference for telling you when something is not worth building.
What this is
This is the freelance side of AI Business OS, a multi-tenant AI platform I built and run for live businesses. That product handles customer conversations, catalogues, orders, bookings and analytics across several industries, in two languages, against real traffic.
It matters here for one reason: almost everything I would build for you, I have already had to keep running for someone else. The difference between a demo and a system is what happens on the bad days — when a vendor is down, a webhook arrives twice, a model changes underneath you, or the data turns out to be messier than anyone admitted. That is the experience I am actually selling.
How I work
- Fixed-price proposals. Scope, approach and timeline in writing before anything starts. If the scope changes we agree a change, rather than discovering it on an invoice.
- Built in your accounts. Your platforms, your credentials, your hosting, your repository. Nothing I build should require me to still be here in a year.
- Weekly visible progress. Something you can look at early and often. A project whose first demo is at the end has no way to correct course.
- Documentation as a deliverable. What it does, what it touches, how to change it, how to turn it off.
- Thirty days of support after go-live, because the real edge cases surface in the first month of genuine use.
What I will turn down
A short list, offered up front because it saves us both time:
- Automating a decision where being wrong is expensive and cannot be undone. Those want a person, possibly assisted.
- Projects that depend on data nobody has yet. No amount of modelling replaces missing history, and I would rather say so than bill for finding out.
- Work that plainly will not repay its cost. If a task runs twice a month, automating it is a hobby.
- Content or engagement systems designed to mislead the people receiving them, including SEO tactics that violate search engine guidelines. They also stop working, usually abruptly.
Working across time zones
I work remotely with clients worldwide, with a real working overlap across Europe and Asia and early-morning availability for North America. Written updates are the default, so progress never depends on catching each other live, and calls are scheduled in your time zone rather than mine.
All work, documentation and communication is in English.
Start with a conversation
Thirty minutes, free, and you will leave it knowing whether this is worth doing.
Start with a free discovery call