Internal tools & dashboards
Clean interfaces for teams that live in their data: capture, track, verify, export. Faster than spreadsheets, sturdier than a generic SaaS, and tuned to how your operators actually work.
SR. SOFTWARE DEVELOPER · QUEBEC · BILINGUAL
Custom software development
I design and build internal tools, automations, desktop apps, and dashboards for businesses that want clean, documented, handover-ready code. No hidden debt, no lock-in, no agency overhead.
On the bench
The reality on the ground
These are the four patterns I see most often before a mandate starts. Each is a real cost, measured in slow days, missed launches, or quiet attrition.
Off-the-shelf SaaS bills monthly forever, takes work to fit your real process, and breaks when the vendor pivots.
A spreadsheet macro, a one-off Python script, a legacy Access form, running the business but unreadable to anyone but the original author.
Operators living inside the tool eight hours a day, fighting friction the original spec never accounted for.
No tests, no docs, no handover. The next engineer inherits archaeology.
Scope of work
Four kinds of mandates. All custom, all delivered with the same rigour. Each one directly answers one of the patterns above.
Clean interfaces for teams that live in their data: capture, track, verify, export. Faster than spreadsheets, sturdier than a generic SaaS, and tuned to how your operators actually work.
The repetitive tasks that drain hours each week, scripts, scheduled jobs, pipelines, turned into stable systems that run themselves and log when they don’t.
Windows .NET applications built for operators who spend their whole day inside them. Polished UI, real performance, a clear support cycle, and bilingual resource files where it matters.
Extract, transform, present. Reports you can read without decoding a legacy spreadsheet, and that the next analyst can extend without rewriting.
Tech stack
I favour technologies that have held up under real use, not the month's trend. The exact stack depends on the mandate; here is what I reach for most often, all production-tested in my own workflow tools.
How I work
Four stages. Every project follows the same sequence, regardless of mandate size, so the cost of being wrong is paid in the prototype, not in production.
We pin down the business problem, the end users, and the constraints. A short scoping document replaces vague estimates.
A first build validates the key assumption: the one that would cost the most if it were wrong. Adjustments happen early, not at the end.
The system is assembled in short, tested iterations. The code stays readable for whoever picks it up later.
Documented code, deployment notes, and maintenance procedures ship with the deliverable. No artificial dependency on my desk.
The hybrid edge
Sport coverage and live events are deadline labs: hundreds of frames, one chance to deliver, no second take. The same instinct, measure twice, ship clean, runs through every mandate I take on. The portfolio is proof of how I work, not just what I shoot.
See the photography portfolioMy own tools, in production
The clearest demonstration is the code I use myself every week: a set of internal tools that sort, edit, and deliver hundreds of images per mandate. The same standard of care a serious in-house team would demand, applied to a real business that depends on it.
Tell me what business problem needs solving and who the users are. You'll get a first response within 48 hours, in French or English.
Your message is sent only to me. No third-party CRM, no marketing list, no data resale. Read the privacy policy .