What does AI consulting actually cost in Ontario?

AI consulting in Ontario is priced in three parts, and the honest way to quote them is with published numbers. On this site, an AI business assessment for an Ontario business is $999, a single build under workflow automation in Ontario is $2,500 to $12,000, and a custom agent under AI agent development for Ontario businesses is $4,000 to $15,000 plus running costs. For comparison, one Canadian firm that publishes its pricing, ChatGPT.ca, puts AI automation consulting at $150 to $350 an hour, or $5,000 to $100,000 per project depending on scope. Ongoing operation, where you want somebody else watching the build, is a monthly fee on top.

There is a fourth band nobody advertises because it is small. A written use policy with a half day of staff training is $1,500 to $4,000 on this site, sold as an AI policy for a small Ontario business, and for a business whose staff are already using these tools it is the correct first purchase rather than the cheap one.

Those are the numbers. The rest of this note is about what moves you within them, because the range is wide and the reasons are not mysterious.

Why the assessment is priced separately at all

An assessment exists because the expensive mistake in this work is not paying too much for a build. It is paying the right amount for the wrong build.

Statistics Canada asked Canadian businesses about AI in the second quarter of 2026, and its analysis of the results is blunt. Two in five businesses, 40.0%, said the use of AI is not relevant to the business. Among the barriers that limit use, cybersecurity or privacy concerns led at 13.4% and cost came second at 10.6%. Cost is not what stops most businesses. The “not relevant” answer is usually a description of not knowing where to look rather than a considered judgement, and it is why the diagnosis and the build are separate purchases.

The assessment on this site is $999 for that reason, which is under the floor of the published Canadian band. The whole fee comes off any build that follows, so for anyone who proceeds it costs nothing. What it buys is ten business days of work, three named jobs with hours and dollars against each, and the ones I recommend against.

What actually moves a build price

Six things, in rough order of how much they matter.

Driver	Cheap end	Expensive end
Systems involved	Two, both with a modern API	Four or more, one a desktop application with no interface
Decision logic	One path, straight through	Branching by customer, value, region or approval level
Error handling	Retry, then email somebody	Reconciliation, audit trail, rollback
Personal information	None, or internal only	Client health, financial or identity data
Volume	Tens of runs a day	Thousands, where per-run model costs matter
Who operates it	You, on your own accounts	Me, with monitoring and a response time

The fourth row is the one people underestimate. A process that touches somebody else’s personal information cannot use whichever tool is cheapest. In May 2026 the Office of the Privacy Commissioner of Canada found that OpenAI’s initial training of ChatGPT did not comply with Canadian privacy law, and the guidance that followed treats prompts, retrieval corpora and model outputs as personal information handling like any other processing. The practical effect is a smaller list of eligible tools and a written data boundary in the scope and in the NDA, the clause set out in AI consultant NDA basics. The wider rules are covered properly in PIPEDA and AI compliance in Canada.

The first row is the one people overestimate. Two modern systems talking to each other is not hard and should not be priced as though it were.

What “AI” is doing in these projects

Frequently, very little, and that is the honest answer rather than a criticism.

A large share of what gets sold as AI in a small business is two systems that were never introduced to each other, with a person in the middle acting as the integration. Automating that involves no model at all. It is plumbing, it is well understood, and it is the cheapest thing on the list.

Where a model earns its place is in the messy middle: reading a document that arrives in eleven different layouts, drafting a reply that then gets approved, classifying an enquiry that does not fit a dropdown. Statistics Canada’s Q2 2026 figures put data analytics at 36.6% of Canadian AI use, text analytics at 34.5% and virtual agents or chatbots at 28.2%, which is roughly the order those jobs appear in real businesses.

The rule worth applying when you work out how to compare AI consultant quotes: if the proposal puts a model between a customer and a number that has to be correct, ask why. A model that composes an invoice total will eventually compose the wrong one.

Three worked examples at Ontario prices

A 14 person Hamilton fabrication shop. One estimator writes every quote from a drawing, a material price list and a memory of similar jobs. Quotes take days and work is lost to whoever answered faster. Automating the assembly around the estimator’s judgement sits in the upper half of the published workflow range, because it touches the price list, the historical job records and the document template. The judgement stays with the estimator. The assembly around the thinking is what goes away.

A five person Barrie trades business. The owner is on site all day and the phone rings anyway. An intake agent that answers, captures the address and the problem, and books the standard jobs starts around $4,000 and runs $80 to $200 a month. This is the highest return automation available to a small service business and the arithmetic is unusually simple, because it pays back on a small number of recovered jobs. The published range for that work is on the AI agents and intake page, and more detail on the trades case is in the note on AI automation for a trades business in Ontario.

A 40 person Mississauga head office. Data comes out of a global system, gets reshaped locally for a Canadian requirement the global system does not handle, and goes back in. Somebody owns that spreadsheet and thinks of it as their job rather than as a process. That is usually a small build at the bottom of the published workflow range, and finding it is the hard part, not building it.

What you should not pay for

A discovery call that produces a proposal instead of a number. The complexity of your business is the same whether or not a consultant has asked you questions first. A firm that will not publish a range is measuring what you will pay.

A strategy deck. If the deliverable is a slide about the AI landscape and a maturity curve, you have bought a summary of the news. What is useful is a list of your own processes with hours against them.

A quote that assumes compute stays cheap forever. Ask what the running cost is and what happens if model pricing moves. That is not a theoretical question: Ontario is now proposing to ration and separately price the grid connections that AI data centres need, which is covered in Ontario’s data centre playbook and what it means for your hydro bill.

A model subscription marked up. Model and platform costs should be on your own accounts, billed to your own card, in your own name. When they are on your supplier’s account, changing supplier means rebuilding. The platform bill itself is smaller and stranger than most people expect, and it is decided by how each vendor counts rather than by the advertised price: n8n vs Make vs Zapier, compared on the billing unit.

The comparison nobody runs. Before signing a build, price the same work as a hire. The salary plus employer CPP, EI and WSIB is the real benchmark a build is competing against, worked through in AI vs hiring another employee, with the 2026 numbers.

Anything that will not survive handover. Ask for the runbook before you agree: every credential, every trigger, every failure mode, written so a different supplier could take it over. If that request is awkward, you have learned something worth more than the answer.

The funding you may not have checked

Before paying for planning work at all, check whether a program will. Through its Digital Competence Centre, the Ontario Centre of Innovation offers a Digital Modernization and Adoption Plan grant of up to $15K toward a plan written with a Digital Adoption Consultant, open to Ontario-based for-profit SMEs with 1 to 499 employees, first come first served while funds last. A follow-on Technology Demonstration Program offers up to $50K toward implementing what the plan recommends, for SMEs with a completed DMAP and at least $750K of annual revenue in one of the last three tax years. On 2026-10-07 the OCI page listed that program as currently closed for applications.

Programs open, close and change their terms, so verify current status with the administrator rather than with a consultant who benefits from your application. The detail as published is in the note on the DMAP grant in Ontario.

The short version

Budget $999 for a diagnosis through the $999 assessment and $2,500 to $12,000 for the first workflow build in a business under 100 people. Expect the price to move on how many systems must agree and whether personal information is involved, not on how impressive the technology sounds. Knowing how to prepare for an AI consultant mostly means asking for every price before the call rather than after it, and asking what happens at handover before you ask what the model is.

One thing on this site is priced by the month rather than by the build, because the work repeats rather than ending: marketing automation, with its set-up fee and monthly range published on that page. Set that against what a Canadian agency quotes you for a small business program before you sign either. Where the money goes inside an agency, from the industry’s own accounts, is in the note on whether it is worth hiring a marketing agency for a small business.

If you already know exactly what you want built, skip the diagnosis and ask for a quote on workflow automation. If you do not, that is what the assessment is for, and it comes off the build.