A tech decision left pending costs more than the decision itself. I step in a few days a month to diagnose the situation, make the call with you, and structure what comes next.
Founders reach out when a technical decision blocks everything else — choosing a stack, deciding between refactor and patch, hiring the right person, getting a team moving again.
My role: diagnose the situation, make the call with you, structure what comes next. I don't produce 40-page reports. I unblock what's blocked.
"The real cost of a bad tech decision isn't what it takes to fix it. It's everything you couldn't build while you were hesitating."
You move fast but tech decisions pile up with no one to arbitrate. You need that expertise without the cost of a permanent hire.
You understand your business perfectly — but not always your tech vendors. You want to understand without having to depend.
Your CTO is overwhelmed or the team needs an outside perspective to decide on architecture, hiring, priorities.
Three formats, depending on what you need — from a one-off decision to ongoing co-piloting.
Clarify the situation, identify the real blockers, and leave with clear priorities and an actionable roadmap. One-off engagement, concrete deliverable.
One or two days a week to co-pilot decisions over time. Hiring, architecture, tooling choices, calls made with the team.
A tech hire to validate, a vendor to assess, an architecture decision to settle. One day, one topic, one outcome.
I've built software, led teams, created products from scratch. PhD in Computer Science, management-certified (CMgr MCMI), I also teach at university (MMI — Digital Media & Internet).
I've worked across corporate environments and independent projects alike. Which lets me speak tech and business in the same sentence — without losing either one.
My roots in the social and solidarity economy taught me to do more with less, and to value decisions that hold over time rather than those that impress in the moment.
From AI to woodworking planes, from software architecture to traditional craft — I believe in a life of independence and reasoned co-dependence. Technology should empower, not entangle.
Alongside my main work, I keep building. These projects are not trivial: they prove that I understand what it means to build something from nothing.
Open rural fablab — makers, repair, local craft knowledge.
The art of getting by — making do, working it out, figuring it out. A celebration of self-reliance.
Explaining everyday science in plain language.
No-code platform for custom information systems. V2 in progress.
Describe your situation in a few lines. I'll get back to you shortly to see whether I can help.
[email protected]