How I can help
Four ways to work together. They all start the same way: understanding your operation before proposing technology, and agreeing the scope in writing before a line of code is written.
- 8 to 16 weeks
End-to-end custom product
Your operation lives scattered across spreadsheets, WhatsApp threads, and the memory of whoever has been there longest. Information gets lost every month, nobody knows which number is the right one, and growing means hiring someone else to hold the chaos together.
- A complete web application, with an admin panel and role-based access control
- Your own API and backend, with the database modelled on how you actually operate
- Architecture documentation with every decision and the alternative it beat
See details
- 6 to 12 weeks
Mobile applications
Your team works away from the office and needs the system in their pocket, not on a desk. And quoting iOS and Android separately doubles the price, the timeline, and the bugs, because you end up maintaining two products that merely resemble each other.
- An iOS and Android app from a single codebase
- The backend and API behind it, sharing domain and types with the web
- Works with intermittent connectivity, built for fieldwork
See details
- 4 to 10 weeks
Automation and artificial intelligence
Your team answers the same questions on WhatsApp every day, copies data from one place to another, and builds reports by hand. Those hours show up in no metric, but you pay for them all the same. And when people get tired, replies start arriving late or steps get skipped.
- A WhatsApp chatbot on Meta's official API, not a personal number wired up through workarounds
- An assistant that answers with your business context, not with a menu tree
- Natural-language search over your own documents, catalogues, and manuals
See details
- 4 to 10 weeks
Architecture and modernisation
You have a system that works but gets harder to touch every month. A small change breaks something unrelated, nobody dares open certain files, and the team now takes weeks on what used to take days. You do not need to start over: you need to know which boundaries are missing.
- A written diagnosis of the current system, with problems ranked by real cost
- Target architecture design, with the decisions and their alternatives
- Phased migration plan, each phase deliverable and reversible
See details
- 1 to 3 weeks
Technical consulting
You have a technical decision to make that will outlive several team members, and nobody to test it against. Choosing a stack, evaluating a proposal that landed on your desk, understanding why your team has slowed down, or knowing whether what you are being quoted makes any sense.
- Architecture review with findings ranked by impact
- Written stack recommendation, with the alternatives evaluated and discarded
- Code review focused on structure, not style
See details
How it works commercially
The model is chosen per project. In every case the scope is agreed in writing before anything starts.
Fixed-scope project
Scope and price agreed up front. You know what you will pay from day one.
Phases with milestones
The project is split into phases, each with its deliverable and its payment. Lower risk on both sides.
Monthly retainer
A fixed monthly fee for ongoing availability. For products under constant evolution.
Hourly
Billed by time worked. Fits consulting and open-ended scopes.
After delivery
I offer maintenance on a monthly plan: fixes, dependency updates, and small improvements. It is not mandatory — the system is delivered documented so your team can carry on without me.
What I do not do
Saying it also defines the work. If you need something from this list, I will save you time: I am not the right person.
- Sites on WordPress, templates, or visual page builders
- Graphic design, brand identity, or marketing assets
- SEO campaigns, digital marketing, or social media management
- Patching someone else's code without a proper diagnosis
Not sure which one you need?
That is completely normal. Tell me what hurts in your operation and I will tell you where to start — even if the answer is that you do not need software yet.