From insight to impact

I advise AND I code, on the same mission. Concretely: we define the architecture, the stack and the priorities together (the advice part), and I get my hands on the code to ship what we decided (the execution part). Not a consultant who stops at PowerPoint, not a dev who executes silently — a partner who thinks with you and ships.

Long ones, clearly. My best fit is becoming your long-term technical partner — someone who knows your product, your market and your constraints. My most recent clients kept me between 3 and 7 years. I also take shorter missions (audit, targeted dev) when they make sense, especially if they then lead into ongoing work.

With an agency, you pay for the project manager, the salesperson, the technical director and the overhead. With me, you talk directly to the person who codes, decides and ships. Over the long run, it's faster, more committed and cheaper. If you need a team of 5+ people in parallel, I'm not the right fit — and I'll tell you so.

It's 2 days of analysis for €1,500–2,000. I run a full diagnosis of a project or codebase: identified risks, estimated technical debt, prioritised recommendations. You leave with a clear deliverable, whether you go on working with me or not. It's also the simplest way to start a collaboration: 60–70% of audits lead to a longer mission.

€800 excl. VAT per day, fully remote, on Malt. It's a benchmark, not a fixed price: depending on the format (fixed-price vs T&M, length of engagement, scope), we can adapt. Easiest is to talk it through in a 30-minute call.

I work solo, by choice. No middlemen, no overhead, you talk directly to the person doing the work. For occasional needs that fall outside my scope (design, content, very specific expertise), I can rely on a network of trusted freelancers — but I keep the steering.

At every stage — what changes is the nature of the intervention. Idea stage: design + first prototype, from scratch. MVP / early stage: development, architecture choices, shipping to production. Growing product: technical refactor, debt to clear, scaling. Pivot or rebuild: audit, repositioning, targeted reconstruction. I've worked across each of these contexts, with a preference for non-technical founders and SMEs going through a digital transformation.

It varies depending on current missions. Easiest is to take 30 minutes to talk. If I'm not immediately available, I'll tell you straight away and we'll see if the wait fits your timeline.

It depends. I don't have a fixed price grid, so we can often find a format that fits your stage and your means — for example starting with an audit, scoping aggressively, or spreading things over time. But if the goal is "the cheapest provider on the market", I'm not the right fit. Best is to talk for 30 minutes — no commitment.

Yes, systematically. It's part of my daily workflow — for code, documentation, audits, technical watch. A few concrete results: IMMERSION site shipped in 3 days, Wedding SaaS MVP in under 10 days, CV Builder in under a day, JLink MVP in under an hour. AI accelerates what I already know how to do — it doesn't replace understanding the need, choosing the architecture, or debugging a tricky case in production. To me, in 2026, a developer who doesn't use AI is no longer competitive. But a developer who only uses AI, with no experience to steer its outputs, produces code no one can maintain. I sit in the middle: 15 years of experience to frame what we build, AI to move fast, and an advisory posture to make the right calls.