Solutions
We build it, and hand it over
When you have neither the time nor the wish to do it yourself, I take the project: design, development, deployment, documentation. It is vibe coding, with 30 years of IT behind it — that is why I am effective with coding agents. You receive a working tool, which you own.
What “delivered” means here
In production, not in demo
The tool is genuinely used by your teams before we talk about the project ending.
Documented
Enough to take over: how it is built, where it is hosted, what to watch.
Without depending on me
Mainstream technologies, nothing proprietary, code and data yours. Anyone who vibe-codes well can pick up the project with their agent.
How a project runs
- 01Scope comes from the diagnosticFraming is already done and paid for, so the price does not shift mid-way without a conversation.
- 02You see progress every week — even every dayNo three-month tunnel. What is done is visible and usable as it goes.
- 03Going live is part of the projectHosting, backups, security, documentation. A tool running on my machine is not delivered.
- 04We look together at what changedHow long things took before, how long now. That decides what follows.
Frequently asked
- Who can take over the project after you?
- Someone who vibe-codes well, with their agent. The project is vibe-coded for that: it is not a secret of mine.
- Do you take over a project already started?
- Often yes — including work produced with AI. We first look at what holds, and usually more holds than people expect.
- Who hosts it?
- You do, with the provider of your choice or on your own hardware. I can operate it as part of piloting, but the hosting stays in your name.
Describe what you need
Even vaguely. Framing is part of the diagnostic, and that is exactly where it becomes precise.