This article is also published in French.

In late February 2026, someone in r/montreal described a familiar kind of workplace pressure. They work in an office that is "pas vraiment lié à la technologie," not really a technology field. For months, the company had been running internal and external sessions on artificial intelligence, "nous expliquant ce que c'est mais aussi à quel point c'est super." Then management asked staff to think of projects that could be improved or helped with AI.

The question they put to the city was direct: "Vivez vous ça avec votre employeur aussi? On vous demande de trouver des cas où l'IA pourrait être utilisée sans qu'il y ait actuellement un vrai besoin?" Are you being asked to find AI use cases even though there is no real need right now? They also had a bad feeling about what the request might mean for their job later.

That post is not a construction thread, and the answers under it are not a survey of Montreal contractors. It is still the most useful public question about getting started with AI in this city, because it names the thing many offices are actually doing: starting from a mandate, not from a problem. It is easy, in a city with so many AI companies, to feel that every office should already have a project. If the research labs and vendors are here, surely a firm across town should be "doing AI" too. That is a different question from "what is costing us time this week?"

Start from a task, not from a mandate

If your employer, or you, has asked the team to "find AI use cases," do not begin with a brainstorming session about the future of the firm. Begin with one recurring piece of work that already hurts. A weekly update, a first pass on a routine email, a meeting summary, or a checklist you rewrite every time a job starts is enough. If you cannot name a task like that, you may not have a use case yet. That is an acceptable finding. It is more useful than a list of ideas that no one will try, and it is more honest than inventing a project so the mandate can be checked off.

A construction or trades office can use the same test. The request may arrive from a head office, a client, or a well-meaning owner who has been to a conference. None of that creates a need on its own. If the painful work is in the field, start with the office task that supports it, not with a promise to run the site from a chatbot. A newsy post in the same city forum about using AI to manage construction sites is a reminder that big claims travel faster than a two-week trial.

Write down, before you open a tool, what "better" would mean. Shorter drafting time is not enough if the review takes longer than the time you saved, or if a wrong date or a wrong name leaves the office. Agree who will read the output as if it were going to a client or a superintendent. If no one is willing to do that, you do not have a use case. You have a demo.

What the comments add, and what they do not

People who replied to the February 2026 thread described very different workplaces. One person said AI use was already part of their annual review. Another described required training and a minimum monthly use of a company system. A programmer said their team treats tools mainly as a way to learn new technical concepts, and raised Quebec's Law 25 as a reason not to send sensitive data "somewhere" into a model. Those are individual comments. They are not evidence that every Montreal employer now scores people on AI use, and they are not legal advice.

They are useful as a warning about how a vague mandate can harden. "Find some use cases" can become "you must use the tool a certain number of times," including on work that did not need it. If you run a firm, do not build your first experiment that way. Pick a task, set a short window, and decide in writing whether to keep it, change it, or stop. If you are the employee being asked to invent a project, you can still bring back a narrow trial and a clear no, rather than a slide deck of ideas.

Hiring a consultant, or booking a vendor meeting, can wait until you have that result. A consultant can help you design a trial. They cannot tell you, in advance, that your office has a need you have not felt.

Keep Quebec's rules in the room, without pretending this is legal advice

Two legal contexts hang over this conversation, and both are easy to skip in a rush to show that the team is "doing AI."

Quebec's Law 25, which a commenter in the same thread already flagged, 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 and who is allowed to see it. If you cannot answer that, use a made-up example or a tool that stays inside a system your firm already controls.

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. This post is in English because a large part of Montreal works in English, but it will reach a narrower audience than the French version, published the same week. It is not a substitute for advice on how your firm should write to clients or employees. It is a reason not to treat an English-only tool, or an English-only policy, as finished work in this market.

Construction labour in Quebec is also its own system, run through the Commission de la construction du Québec. Figures from other provinces, or Canada-wide adoption surveys, do not tell you how a Montreal or Quebec contractor has to hire. I am not going to borrow those numbers here just to make the market sound busier.

A two-week way to answer the boss

Give the mandate a boundary. Two people, one task, ten working days. One person tries a first draft. The other reads it. At the end, you should be able to say whether the review time was shorter than the drafting time you saved, and whether anything unsafe would have left the office if the review had been skipped.

If the trial helps, you have a use case you can describe in plain language. That is the moment to ask whether a better tool, a short course, or outside help would make the same task safer or faster. If it does not help, report that. A negative result is how you avoid spending the next quarter on a project that existed only to show that the firm is modern. It is also how you avoid training people to invent work so they can look busy with a new tool.

Nationally, construction still sits near the bottom of Canada's AI adoption numbers. Being in a city with a large AI sector does not automatically change that inside a contracting firm. The capital's version of the getting-started question was about finding someone to learn with, which is the subject of Want to Learn AI With Other People in Ottawa?. Montreal's public question is different: what to do when the pressure arrives before the need.

If you cannot name the task that already hurts, you do not have a use case yet. That is an answer, not a failure to be modern.

The limits of these sources

The r/montreal post is one person's account of one workplace, dated February 26, 2026. It does not tell you how many Montreal firms have issued the same request, or what happened after the thread. The comments under it are anecdotes. The construction-site post is a news share about a public proposal, not a question from a contractor about their own jobs.

Law 25 and Bill 96 are named here only as real legal contexts that belong in the conversation. This post is not legal advice, and it does not tell you how either statute applies to a specific tool or contract. CCQ hiring rules are noted only so that labour figures from elsewhere are not dropped onto Montreal by habit.

This post also does not treat a directory of AI firms as proof that your office should hire one, or that a particular company is the right help.

What to do with this

If you have been asked to find use cases, come back with one real task or with a clear no. Do not come back with a list. If you run the firm, ask for a two-week trial and a written decision, not for a catalogue of ideas. Keep client and employee data out of the trial until you know where it goes.

If the trial works, then it is worth talking about the next step, including whether you need help from outside the firm. If it does not, stop. The point of the February 2026 question was not "how do we look like we use AI?" It was "what do we do when we are asked to use it without a need?" The honest answer is to test one piece of work, or to say that the need is not there yet.

Explore the assessment →