The senior technical lead your team can't yet afford to hire.

Who I work with

I work with organizations that have a real product or operation, a team that's moving forward, and nobody above to make the calls.

Two ways to work together

How I price

I charge a flat fee or monthly rate, never hourly — you're buying a result, not my time.

The price depends on scope and the market you operate in, like any vendor working across multiple countries.

I'll tell you on the first call, before any written proposal. You won't waste three meetings discovering we're not on the same scale.

How we work remotely

I work exclusively remote, and I'd rather say so in the first line than at the third meeting.

If your organization requires regular physical presence, I'm not the right person, and I'll tell you on the first call.

Who I am

Mounir Khebbaza

I'm head of hosting and development at a vendor that builds complete web platforms — sites, e-commerce, marketplaces, accommodation and transport booking — for municipalities and tourism boards, and for the past two years for companies.

I lead a team of 11 developers and 3 infrastructure engineers. I'm the architect on both the application and infrastructure sides, and I own all technical decisions: what we build, what we buy, what we host on, and what we refuse.

In this role, I've been technically responsible for platforms delivered to several major alpine resorts and mountain destinations: booking, stays, accommodation, transport, with the traffic spikes that come with a season. I can't name these destinations — they're my employer's clients, not mine — but it's terrain I know from the inside, and I can discuss it in detail on a call.

Before this, I spent two years in North America. At National Bank of Canada, on a fraud detection platform. Then at Turbulent in Montreal, on the e-commerce and community platforms for Star Citizen and high-traffic sites like Radio-Canada. I started at STMicroelectronics on tooling and data industrialization — that's where I developed a taste for systems that eliminate manual work.

My distinctive strength is the dual expertise in infrastructure and development. Most technical consultants come from a product or code background. Few can also size a cluster, read a cloud invoice, or say whether an architecture will handle the announced load — and that's often where the most costly decisions get made, for lack of someone to guide them.

My stack: TypeScript and Node.js with NestJS, Vue and Nuxt, React and Next, React Native, PostgreSQL and MongoDB, Docker, AWS and Kubernetes on EKS.

Computer science and networks engineer, CPE Lyon. Based in Savoie, one hour from Geneva.

I still hold this position. So I take on independent work on a limited and declared volume: one day per week of accompaniment, and one automation project at a time. I'd rather say it upfront than discover it along the way — that's what guarantees I'll deliver what I take on.

What a typical engagement looks like

These four situations are illustrations, not client references.

Example engagement — the Monday reconciliation

A logistics team exports three files from three tools, reconciles them in a spreadsheet, and manually fixes discrepancies. Four hours per week, and only one person knows how to do it. Automating this process takes about thirty hours and gives back half a day per week to someone with better things to do.

Example engagement — technical debt blocking hiring

A team of four developers can't ship anymore, and the leader thinks it's a headcount problem. It's almost always an architecture or deployment pipeline problem. A five-day diagnostic answers the question before you commit an annual salary.

Example engagement — vendor proposal review

A vendor proposes a heavy redesign, and nobody internally can judge whether the pricing is fair or the approach is right. One day of technical review is enough to decide — and it's often the first day of an engagement.

Example engagement — the approaching season

A tourism destination operates a booking platform, a stay site, and a lodging tool that don't share data. Each season start, someone manually re-enters availability. The project is to make these three systems talk to each other before peak season, not rebuild everything.

Let's start with thirty minutes

A thirty-minute call, no commitment and no sales pitch. You describe your situation, I tell you what I think and what I'd do — whether we work together afterward or not.

Or reach out directly at the contact address.

The information you send is used only to prepare our call. It is never sold, and never used for anything else. Privacy policy.