Choosing an AI Automation Agency in Quebec: A Buyer’s Guide

Two years ago, searching for an AI automation agency in Quebec returned almost nothing built specifically for the province. That has changed. A real competitive set now exists: firms selling workflow automation, AI agents, and process diagnostics to Quebec SMBs, several of them verticalized by industry, most of them leading with a free discovery call. Telos Machina is one of them. This piece is not the pitch. It is the evaluation framework we would want a founder to use before signing with any of us, including us.

The category looks similar from the outside. Diagnostic call, proposal, build, handoff. Where these firms actually differ shows up after the contract is signed, not during the sales call, which is exactly why it is hard to compare from a landing page. The five questions below are where the real differences live.

Who owns the automation when the relationship ends

Ask this before anything else, because the answer determines whether a bad breakup costs you a rebuild. Some automation vendors build inside their own account structure: their API keys, their workspace, their n8n or Make instance with your data flowing through it. Cancel the relationship and the workflow stops, sometimes overnight, because you never actually held the keys.

The alternative is a build that lives in infrastructure you own or control from day one: your own automation platform account, your own credentials, your own hosting if the tool is self-hosted. A vendor who builds this way can walk away and you keep running. A vendor who builds inside their own stack has, intentionally or not, built a lock-in.

This is not a hypothetical concern. Ask directly: “If I stop paying tomorrow, what happens to the workflow at midnight?” A vendor with nothing to hide answers in one sentence.

Look past the account structure question to the individual pieces. Who holds the API keys for the tools the automation touches, your CRM, your invoicing software, your email provider? If the answer is “we do, in our own vault,” ask what the handoff process looks like on exit, in writing, before you sign anything. A custom AI agent is worse in this respect than a simple workflow, because the prompt engineering, the tool definitions, and the guardrails around it are often treated as the vendor’s proprietary asset rather than something you are buying outright. Settle in the contract, not in a future email thread, whether the agent’s configuration belongs to you the day it ships.

How to read the free diagnostic itself

Nearly every firm in this category, ourselves included, opens with a free discovery call or a short diagnostic. That is not a red flag on its own; it is now table stakes for the category. What separates a genuine diagnostic from a sales call wearing a diagnostic’s clothes is whether it ends with something specific to your business or something that could have been written before the call started.

A real diagnostic names your actual tools by name, points at a specific process, and gives you a rough shape of what a build would look like, even without pricing attached. A sales call disguised as a diagnostic ends with generic language about “streamlining your operations” and a push straight to a proposal. Fifteen minutes is enough time for an experienced team to tell whether your problem is a good fit for automation at all; if a fifteen-minute call ends with unconditional enthusiasm for every idea you raised, that enthusiasm is doing the selling, not the diagnosis.

Whether the documentation would let someone else pick it up

A workflow diagram is not documentation. Documentation is the thing that lets a person who was not in the room understand what triggers the automation, what each step does, what happens when a step fails, and how to change it without breaking something two steps downstream.

Ask to see a redacted example from a past engagement, not a description of the vendor’s documentation philosophy. The honest test: if your bookkeeper, your ops hire, or a different vendor entirely had to take over this workflow next month with zero handoff call, could they, from the documentation alone? If the answer requires a call to the original builder, the documentation is decorative.

This matters more in Quebec than the marketing suggests, because the market is young enough that vendors churn. A firm that folds, pivots, or gets acquired leaves its clients holding whatever documentation it left behind. Weak documentation is a bet that the vendor relationship never ends badly. That is not a bet worth making on a system that touches customer data or revenue.

Good documentation for a workflow answers five things without a phone call: what triggers it, what each step does in plain language, where the decision points are and what determines which branch runs, what happens when a step fails partway through, and who to contact if it needs to change. Good documentation for an AI agent adds a sixth: what the agent is instructed to do, in the actual prompt or system instructions, not a paraphrase of it. If a vendor treats the underlying prompt as a trade secret they will not show you after you have paid for the build, that is a lock-in disguised as a documentation gap.

Where your data lives, and whether they can answer the Loi 25 question

Every automation touching a customer’s name, email, phone number, or order history is subject to Quebec’s Law 25, and article 17 specifically governs what happens when that information crosses the province’s border. The rule is stricter than most Quebec SMB owners expect: before communicating personal information outside Quebec, or entrusting someone outside Quebec to hold, use, or communicate it, the business must first assess whether the information will receive protection consistent with what Quebec law would provide, and refuse the transfer if it will not. The full text of article 17 is public on Legis Quebec, and it is worth reading once rather than trusting a summary, including this one.

Ask a prospective vendor two direct questions. Where is the data these workflows will touch actually hosted, and can you name the province or country. And has this firm ever run a privacy assessment before connecting a new tool to a client’s data, or is that something they assume someone else handles. A vendor that hedges on either question has not thought about this seriously, and the exposure lands on you, not them, if it goes wrong. A vendor whose answer is “everything stays in Canada” has answered a real question, but not the whole one: Canada is not Quebec, and article 17 does not stop at the national border.

Subscription versus one-off project

Some firms sell automation as a fixed-price, one-time build. Others sell it as an ongoing subscription. Neither model is inherently better, and the marketing around each tends to oversell its own case.

A one-off project makes sense when the process you are automating is genuinely stable: the same steps, the same tools, month after month, with no reason to expect that to change. You pay once, you own the result, and if nothing shifts, nothing breaks.

A subscription earns its cost when your stack changes often enough that an unmaintained automation quietly breaks and nobody notices until a customer complains. Vendor APIs deprecate. Fields get renamed in your CRM. A form provider changes its webhook payload. An automation with nobody watching it does not fail loudly, it fails silently, and silent failure on a customer-facing workflow is worse than the process it replaced. If your business changes tools or volume more than a couple of times a year, ask what happens when something upstream breaks: is that included, or is it a separate invoice every time?

Ask both models the same question before you compare price: what is the actual response time when something breaks at 4pm on a Friday? A one-off vendor’s answer is often “email us and we’ll fit you in,” which is a fair answer for a fixed-price engagement with no ongoing obligation, but a poor answer if your business genuinely cannot tolerate a broken invoicing workflow over a weekend. A subscription is, functionally, a service-level commitment dressed up as a monthly fee. Read what the vendor actually commits to in writing, not what the sales page implies.

Whether they show you the artifact before you pay

The friendliest version of this test: does the vendor show you the actual workflow, the actual agent, the actual thing that will run in your business, before you pay for it, or only after? A diagnostic call and a proposal document are not the artifact. A working prototype, even a rough one, on a real (or realistic sample) piece of your own data is.

This is not a demand for free work. It is a filter for vendors who can build fast versus vendors who are selling a process. If every vendor in your shortlist requires a signed contract before you see anything functional, that is normal for a complex, multi-month build. If a vendor cannot show you a working example of similar past work, redacted for client confidentiality, that is a gap worth asking about directly.

Pay attention to what the artifact is built with, not just whether it exists. A screen recording of a workflow running in a demo environment is weaker proof than a live link you can click through yourself. A chatbot transcript the vendor selected is weaker than a live conversation you can have with the agent, on a topic you choose, right now. The artifact’s job is to let you test the vendor’s claim, not to illustrate it.

What Telos Machina does, and does not, do

We build workflow automation, custom AI agents, and process audits for Quebec SMBs, and we sell it as a subscription, not one-off projects, because we would rather stay accountable to a workflow after it ships than hand it off and hope. We are two technical co-founders who implement the work ourselves, based in Sherbrooke, and we build on infrastructure the client can hold, including self-hosted n8n where that fits, specifically so the lock-in question above has a clean answer.

We also do not do several things a buyer might assume an AI automation firm covers. We do not train or fine-tune AI models; we use the strongest existing ones. We do not do data science or statistical analytics. We do not build mobile apps. We do not manage a client’s social media accounts day to day, though we will build and automate the publishing pipeline. We do not do graphic design or recruitment. If your shortlist includes a firm claiming to do all of the above under one roof, ask how many of those are genuinely staffed versus subcontracted without disclosure.

None of this makes us the right fit for every Quebec SMB evaluating this category, and it should not. Wondercloud, Agentique Quebec, and AgentQC are each building a real practice in this space, and each is worth evaluating against the five questions above, the same way we would want to be evaluated. The right vendor is the one whose answers to those five questions you would still trust a year in, not the one with the best landing page. If you want a working example of what a process audit looks like before you commit to anything, that is a reasonable first ask of any firm on your list, including ours.

FAQ

What is the single most important question to ask an AI automation vendor in Quebec?

Who owns the automation once the engagement ends, and can you show me the underlying workflow. If the vendor cannot answer both without hedging, keep looking.

Does Loi 25 actually apply to a small automation project?

Yes, if the workflow touches any personal information: a customer’s name, email, phone number, or order history. Size does not exempt a business from Loi 25. What changes with size is the depth of documentation the CAI expects, not whether the law applies.

Is a subscription model better than a one-off project for automation?

Neither is universally better. A one-off project is right when the workflow is stable and rarely changes. A subscription earns its cost when your tools, volume, or processes shift often enough that someone needs to be watching the automation, not just the ones who built it.

Can I check whether an AI automation vendor is actually registered in Quebec?

Yes. The Registraire des entreprises maintains a free public registry searchable by company name or Quebec Enterprise Number (NEQ). A vendor claiming to be Quebec-based should show up there with an active registration.