Language law
Bill 96 Compliance
French that matches the English in content, presentation and function — including the forms and checkout most sites leave in English.
Montreal, QC · Web Studio
Bill 96 · Law 25 · Real Québécois French
Four packages, delivered in 5 to 15 days on the date written in the contract. Your text written for you from a 20-minute call. Built in Montreal, in both languages, to meet Quebec law.
01 — What I Build
Six things Quebec businesses keep needing, and most agencies quietly hand to a translation plugin.
Language law
French that matches the English in content, presentation and function — including the forms and checkout most sites leave in English.
Privacy law
Consent at the point of collection, cookie handling, privacy and terms pages, and no third-party tracker firing before someone agrees.
Production web
Real /fr and /en routes with hreflang and localized metadata, on one design system so the two languages never drift apart.
Real FR-CA
Written in Quebec French — not France French, and not machine output. Your customers hear the difference immediately.
Documented
A documented review of where a site actually stands, ranked by severity, with the requirement cited for every finding.
Studio design
Studio-grade design, delivered in days rather than months.
02 — Packages
Choose by the number of pages and what the site must do. Every price is fixed and written in the quote; every date is written in the contract. Two rounds of revisions included. Hosting and upkeep optional, $45 a month. A page beyond the package: $250.
A business that needs a clean site in one language, fast.
Delivered in 5 days, fixed date in the contract
The bilingual path
A Quebec business that serves customers in both languages.
Delivered in 7 days, fixed date in the contract
A business that books appointments and collects personal information.
Delivered in 10 days, fixed date in the contract
A business that sells online or needs its tools connected.
Delivered in 15 days, fixed date in the contract
03 — Where Sites Fail
Most bilingual sites are a translated homepage sitting on top of an English application. The law looks at all of it.
04 — How I Build
The same four steps every time, which is why the delivery date is known before we start.
An automated pass over your live site: French parity, forms, checkout, consent, page speed. You get the findings whether or not you hire me.
Manual review of everything the scan flagged, ranked by severity with the law cited. What comes out is a fixed scope and a fixed date — not a range.
French and English are written side by side, never translated afterward. Forms, error states and transactional email included, because that is exactly where compliance fails.
Both languages checked route by route, privacy and consent pages live, security headers and performance confirmed. Then it ships.
05 — Proof
This page is bilingual, Law 25 compliant, tracker-free and audited before launch. It is the same build you would receive.
Enterprise support, retention and high-value queues — in French and English, every day.
Fonts self-hosted, nothing fires before consent. Check it yourself.
A fixed date written into the contract, not an estimate.



06 — Selected Work
Each one is framed the same way: the problem, what gets built, and what you end up holding.

Real /fr and /en routes on one design system, so the two languages cannot drift apart.
A site where the French exists on the homepage and disappears the moment someone tries to do anything.
Shared design system, hreflang and localized metadata, French written alongside the English rather than after it.
Every route, form and error state present and equivalent in both languages.
Handover package: route map, parity checklist, deployment rules.
days from signed scope to launch

A documented review of where a site stands, ranked by severity, with the requirement cited.
Owners are told their site is “probably fine” by the people who built it.
Automated scan first, then manual review of build integrity, parity, privacy, accessibility, performance and headers.
Severity-ranked findings with a prioritised fix list and a fixed price to resolve them.
Bilingual audit report, structured the same way every time.
review sections per audit

Quebec French written by someone who speaks it, with parity checks at the field level.
Machine translation and France French both get caught — by customers first, and by the regulator second.
FR/EN field mapping, parity rules, a QA pass in both languages, and review before launch.
Copy that holds its meaning and its tone across every page and component.
Handover package: field parity, component rules, review sign-off.
parity target across critical bilingual fields
Demonstration build — fictional brand, real production pipeline
A 70-second onboarding film rendered twice from one cut — Québec French and international French, same footage, same timing, switchable mid-sentence.
The international render says mutuelle, turns a REER into a generic savings plan and quotes the warehouse in metres. Fluent, professionally revised French describing benefits the employee does not have.
One cut, two subtitle tracks on an identical timeline, plus a full FR-CA dub. Every divergence logged per line with the reasoning attached, and corrections kept separate from register choices.
A player that switches between the two written French versions over the same footage, so the difference is read line by line rather than argued.
Delivered: source cut, EN and FR-CA audio, subs-fr-qc.vtt and subs-fr-intl.vtt, annotated comparison.
of the nine changed lines are factual errors, not matters of style
Demonstration build — fictional clinic, real production pipeline
A 58-second patient welcome for a Villeray clinic, where the international French sends a Montréal patient to their appointment with a health card that does not exist in this country.
Carte Vitale, tiers payant, mutuelles, médecin traitant and the RGPD — all correct French, none of it applicable here. A patient instruction with the wrong French is not embarrassing, it is unusable.
The same two-track pipeline plus a scope-of-practice check: a dental hygienist is a regulated profession in Québec with cleanings legally in scope, and France has no equivalent — so that line had to be restructured, not reworded.
A welcome film naming the RAMQ card, the right professional, and the vocabulary Québec privacy law actually uses.
Delivered: source cut, EN and FR-CA audio, both subtitle tracks, annotated comparison.
of the eight changed lines name an institution, profession or statute absent in Canada

Live demonstration — three fictional businesses, nothing is uploaded
The month’s bank statement and invoices go in. Out come a categorized ledger, the GST and QST to remit, who owes you what, and a list of what to fix before you close the month. Try it with a bakery, a plumber or a freelance studio.
Month-end is a pile: a bank statement, supplier invoices, customer invoices, a timesheet. Matching them by hand takes an evening, and what slips through — a deposit never invoiced, a receipt that never arrived — costs tax or cash.
Bank lines reconciled against the invoices, keyword rules for the rest, a GST/QST estimate, receivables ageing, payables, hours not yet billed, and checks for double payments, unknown deposits and purchases that look personal.
Every bank line categorized and marked with its proof — the matching invoice, a rule, or “to check”. Nothing is guessed.
Downloads: a one-page PDF report, the ledger as CSV, every invoice as PDF.
items flagged in one fictional plumber’s August: overdue invoices, a deposit with no invoice, missing receipts, an owner draw
07 — About
Seventeen years in telecom operations shaped how I build: clear systems that survive real-world pressure.
I spent those years switching between French and English all day, with real customers who noticed when the French was wrong. That is the part most web agencies cannot fake.
08 — Let’s Talk
Write what the site must do — or just send your current site address: I run the free scan and tell you what would fail, whether or not you hire me.