What it costs, before you even write to me.

Three things move it: the real scope, the timeline you want, and what you already have in place. A site built on a sound base costs less than one that starts by untangling what’s there.

What doesn’t move: you get a written estimate before anything is billed, and the final price is written into the contract — that’s what binds, not the ranges on this page.

A 30% deposit on signature, the balance on delivery. From $2,500, we agree on milestones set in advance instead — healthier for you and for me than two large blocks.

The deposit isn’t distrust: it commits both sides. Me to reserving time for you, you to that time being used.

A brochure site is measured in weeks. An AI integration or an automation depends on your systems more than mine: getting access and internal approvals often takes longer than the development itself.

The timeline is in the estimate. If something threatens it, you hear about it before the delay, not after.

No “satisfaction guaranteed or your money back”: that’s untenable for services, and nobody believes it.

What’s real: 30 days of corrections included after delivery. During that period, anything that doesn’t work as agreed gets fixed at no charge. A new request, on the other hand, is billed. The difference between the two is written into the agreement before the project starts, so it isn’t argued afterwards.

I’m not going to tell you I’m always available: that’s unverifiable, and it’s false. The real answer is elsewhere — you don’t depend on me.

You leave with the code and the documentation. It’s written so someone else can pick it up — not to tick a box. Your system’s access is in your name, on your own accounts, never mine.

If I disappear tomorrow, your system keeps running and any competent developer can take over. That’s a commitment, not a slogan.

What data goes out, to which provider, under which guarantees: all of it is decided in writing, project by project, in compliance with Quebec’s Law 25.

Depending on the case, there are setups where nothing leaves your servers. We choose knowingly. No AI is ever wired to your data without you knowing precisely what flows where.

Yes, and it’s the most common case. We first assess what deserves to be kept.

Starting from scratch only happens when it’s justified, never by reflex: rebuilding what already works is your money spent to end up in the same place.

What ships is documented, and the 30 days of corrections apply. Beyond that, we agree on a support arrangement that fits your real needs — no subscription imposed for support you don’t need.

Both. Remote for most of the work, on-site when it matters: team training, a project kickoff, a shop-floor reality you only understand by seeing it.

Based in Quebec, working in French and English.

Federal and provincial programs fund part of a small business’s digital transformation, and their criteria change often.

I’m not a grants consultant and I won’t pretend to be: we cover it on the first call, and I’ll point you to the right resources for your situation.

Because I don’t bill for expertise I can’t prove today. A security audit is an assessment you have to be able to defend if it’s challenged — not a report you generate.

What I do instead rests on real interventions: fixing vulnerabilities that have already been identified, cleaning up and restoring a compromised site, configuring and hardening your DNS and email. Corrective work on what’s already live, and nothing I can’t demonstrate.