In September 2025, someone in r/IAQuebec asked for advice as a beginner. Their boss had asked them to "incorporer l'IA à notre entreprise," and they felt the request overestimated what they could already do. The firm is in construction. The goal was specific: "pouvoir sortir toute l'information utile d'un devis rapidement," to pull the useful information out of a devis, quickly. They already use Office, so they wondered whether Microsoft Copilot would be better than the free version of ChatGPT, and whether it was worth building their own tool with an open-source model.
That post was not tagged to Quebec City. It was asked in a province-wide forum. The Quebec City subreddit has almost no getting-started thread of this kind; the only clear AI question there is a 2023 job-search post about moving from software work into machine learning. I am writing this here because the devis question is the strongest construction question in the province, and it applies in Quebec City as much as it does anywhere else in Quebec. Most local AI headlines are civic news that has nothing to do with reading a bid. This post is about the bid.
A devis, in this context, is a bid, a quote, or an estimate package: quantities, prices, exclusions, conditions, and the odd line that will hurt you later if you miss it. That is already a use case. It is a different situation from a mandate to "find some AI projects" with no task attached, which is the subject of What Do You Do When a Montreal Employer Asks You to Find AI Use Cases?.
Start with one devis, not with a new system
You do not need a custom tool to find out whether this helps. Pick one devis you already know well, or a redacted sample, and ask a tool to pull a short structured list: quantities, unusual conditions, exclusions, and anything that looks inconsistent. Then read the list against the original. The test is not whether the first pass looks tidy. The test is whether a careful person still has to hunt for misses, and whether those misses are the kind that would have changed a price or a promise.
Two weeks and one partner is enough. One person tries the first pass. The other reads it as if it were going to a client or a superintendent. If the review takes longer than the time you saved, stop. If a wrong quantity or a missed exclusion would have left the office, the tool is not ready to run unattended, and may never be.
Do this on a document that does not identify a client, or on a file that stays inside a system your firm already controls, until you know where the data goes. A devis is not a blog post. It has prices, scopes and sometimes personal information. That is the first reason not to paste it into a consumer window just because the window is free. If the only copy you have is a live bid, wait. Make a version with names, addresses and prices removed, and run the test on that.
Copilot, free ChatGPT, or a custom model
The original post asked the right product question, in the right order: we already use Office, so is Copilot better than free ChatGPT, and should we build our own?
I am not going to claim that one vendor is safer than another without looking at your licence and your settings. What can be said, without a sales pitch, is this. A free consumer chatbot is the easiest thing to try and the wrong place for a live devis. You do not control where that text goes, or how it might be used. If the firm already lives in Microsoft 365 and already has Copilot, that is a closer fit for an Office-based workflow, but only if you know how your tenant is configured, who can see the files, and what the licence actually covers. "We use Office" is not the same as "Copilot is already approved for bid documents." Check that before you put a real estimate through it.
Building your own system on an open-source model is the last of the three questions, and it should stay last. It can make sense later if you have a task that already works, a reason to keep data on a machine you control, and someone who can maintain the setup. For a first trial, it is almost always the long way around: you still have to write the instructions, you still have to review the output, and you now also have a system to keep running. The September 2025 writer already had a clear job: pull useful information from a devis. That job can be tested with a tool you already have, or with a carefully limited trial, before anyone books a custom build.
What "useful information" should mean, in writing
Agree, before the first pass, what you want out of the devis. A wall of summary prose is not useful. A short list is: every quantity and unit, every exclusion, every condition that shifts risk, and any obvious mismatch between sections. If your bids have a standard checklist, use that checklist as the shape of the output. Then decide who is allowed to treat the list as a starting point, and who still has to open the original document before a number is reused.
If the devis is in French, or mixed, keep the extract in the same language as the source unless you have a separate, reviewed reason to translate. A bilingual office in Quebec City will already know how often a small shift in wording changes a condition. Do not let a tool quietly translate as it summarizes.
The tool will miss things, and it will sometimes invent a tidy line that was not in the source. That is why the review step is the work, not an optional polish. If you cannot spare a second person for two weeks, you do not yet have a process. You have a shortcut with no brakes.
Quebec's rules still apply
This is a Quebec question, even though it was not asked in the city forum, so the same legal context that hangs over a Montreal office hangs over this trial too. Quebec's Law 25 is the province's privacy statute. You do not need a legal memo to take the practical point: client files, employee information, pricing and drawings do not belong in a third-party window until you know where the data goes. The Charter of the French Language, as amended by Bill 96, is a separate issue. Commercial communications aimed at Quebec, and many contracts, generally need to be in French. An English-only extract of a French devis, or an English-only process note, is not finished work in this market. This post is not legal advice on either statute.
Construction labour in Quebec is also its own system, through the Commission de la construction du Québec. Figures from other provinces, or Canada-wide adoption numbers, do not tell you how a Quebec City contractor has to hire, and I am not going to borrow them here to make the market sound busier. They are useful only as a reminder that construction, nationally, is still near the bottom of the adoption table. A clear task, like reading a devis, is a better place to start than a mandate with no job attached.
The limits of these sources
The r/IAQuebec post is one person's account, dated September 12, 2025. It tells you what one construction employee was asked to do, and what they were considering. It does not tell you how many Quebec firms extract bids this way, or whether Copilot, ChatGPT or a local model worked for that team. I have not seen the replies treated as a survey, and I am not using them as one.
The r/quebeccity job-search post is from 2023 and is about machine-learning roles, not about reading a devis. It is mentioned only to be honest about how little the city forum itself has on this topic.
Nothing here is a review of Microsoft Copilot, OpenAI, or any open-source model. Licence terms, tenant settings and data-use policies change, and they have to be checked inside your own firm. Law 25, Bill 96 and CCQ rules are named as real context, not as a ruling on a specific tool.
What to do with this
If you have been asked to "bring AI in" and you already have a devis problem, you are further ahead than a firm that only has a mandate. Write down the list you want out of one document. Try that list on a redacted or well-controlled file. Have a second person check it against the original. Decide, in writing, whether the review time is shorter than the time you saved, and whether anything unsafe would have left the office.
Do not start by pasting a live bid into a free consumer chatbot. Do not start by building your own model. If you already have Copilot in a configured Office environment, that is a reasonable place to test, after you have confirmed what the licence and the settings actually allow. If the trial helps, then you can talk about a better tool or outside help. If it does not, say so. The useful question from September 2025 was not "how do we look like a modern construction firm?" It was "how do we get the useful information out of a devis without getting in over our heads?"
