We only sell in Ontario. Does French still matter?

Not today, and the question is whether it will. Retrofitting a second language into an application that assumed one is not a translation project - it reaches the URL structure, the routing, the metadata and every component that hardcoded a string. The cheap moment to make a single-language application bilingual-capable is before it exists.

Is machine translation acceptable for the French version?

Not where the requirement is legal. A translated interface that is visibly worse than the English one is both a compliance risk and a commercial one, and in Quebec it will be noticed. The engineering question we answer is making the second language structurally equal; the translations themselves need a human.

How does the time difference work?

Our end of day is your morning, which gives about an hour of overlap. A standing slot around 09:00 Eastern works. Everything else is written down, which is the habit that makes the arrangement work at all.

Do you invoice in Canadian dollars?

In US dollars, or euros if that suits your accounting better, from Codefacture Yazılım A.Ş. in Türkiye by bank transfer. Exported services carry no Turkish VAT.

Next.js in Toronto

Next.js development for Toronto companies

A Next.js development company working with Toronto teams. A bilingual requirement that is law rather than courtesy the moment you serve Quebec, and the routing decision that follows from it.

Updated November 4, 2026

Working day overlap: About one hour. Toronto is roughly eight hours behind Ankara, so our end of day is your morning
Who buys here: Fintech, SaaS and insurance, usually selling across the country rather than in Ontario alone
What that changes: Serving Quebec makes French a legal requirement, which is a routing decision rather than a content task
Local specifics: PIPEDA federally, and Quebec's own regime on top of it for anyone with customers there

Most Toronto companies sell across Canada rather than in Ontario alone. That single commercial fact produces the engineering decision that defines these projects: the moment a product has customers in Quebec, French stops being optional.

That is not a content task. It is an architecture decision, and it is made at the start or paid for later.

Bilingual is a routing decision

A second language that is a legal requirement rather than a courtesy has to be structurally equal to the first. That means the URL structure anticipates it, the routing is built around a locale segment, and no component contains a hardcoded string.

Doing that on day one costs very little. Doing it afterwards means touching every route, every metadata function, every form label, and auditing a codebase for strings that were never meant to move. The work is not difficult; there is simply a great deal of it, and it arrives at the worst time, which is when the Quebec launch already has a date.

Two things specifically go wrong when it is retrofitted. The URL structure gets a language parameter bolted on rather than a path segment, which makes hreflang awkward and the canonical ambiguous. And the second language becomes visibly second-class - a page that falls back to English for anything untranslated, which is exactly the outcome the requirement exists to prevent.

How internationalised routing is structured is the decision to get right, and it is one of the few in a web application that is genuinely expensive to reverse.

An hour of overlap, at the start of your day

Toronto is about eight hours behind us. Our day ends as yours begins, which gives roughly an hour of shared time.

A standing call at nine Eastern works and is late afternoon here. Everything else is written: proposals with a recommendation attached rather than open questions, pull request descriptions that answer the obvious follow-up before it is asked, and decisions recorded somewhere other than a chat thread.

This suits the buyers here reasonably well. Fintech and insurance teams tend already to document decisions because their own compliance obliges them to, so the habit exists.

What gets built

Financial product surfaces, insurance quote and claims flows, SaaS applications sold to Canadian enterprises.

These share a property worth naming: the interesting complexity is in rules rather than in rendering. Eligibility, pricing, what a user may see and do. The front end's job is to express those correctly and never to be the thing that enforces them - a route guard is a redirect, not a permission model, and the difference appears the first time an endpoint is called directly.

The regimes stack

Federally there is PIPEDA. Quebec has its own regime on top of it, and it reaches further - which is why the French question and the privacy question tend to arrive in the same conversation.

The detail belongs on the Canada market page rather than being repeated here. The city-level point is narrower: a Toronto company's product is usually national, so it inherits Quebec's requirements whether or not anyone planned for that.

Commercially

Invoiced by Codefacture Yazılım A.Ş. in Türkiye, in US dollars or euros, by bank transfer, with no Turkish VAT because exported services are exempt. Scope fixed in writing before work starts, priced per project rather than as a day rate.

The regulatory and commercial ground for this city is on the Canada market page.