How do you choose an operations consultant?
Choose an operations consultant who audits before recommending. The right one starts with a diagnostic of how work actually moves through your business, quantifies what each bottleneck costs, and hands you a prioritized roadmap you could execute without them. Anyone proposing a solution before measuring the problem is selling, not consulting.
That single test filters most of the market. Everything below is how to apply it in practice.
What does an operations consultant actually change?
An operations consultant works at the level where the work happens: the handoffs, approvals, data entry, and reporting that consume your team's week. This is different from management consulting, which operates on strategy, market position, and org design. Operations work is tactical, and its output is measurable in hours and error rates.
The gap it addresses looks much the same on both sides of the border. In Canada, the Canadian Federation of Independent Business found that while [92 percent of small businesses use digital tools, only 10 percent have fully integrated them across operations](https://www.lexpert.ca/news/technology-law/only-a-tenth-of-canadas-small-businesses-fully-integrate-digital-tools-in-operations-cfib-report/393488).
The American picture is the same shape. The U.S. Chamber of Commerce reports that [58 percent of small businesses now use generative AI, up from 40 percent in 2024](https://www.uschamber.com/technology/empowering-small-business-the-impact-of-technology-on-u-s-small-business). Yet the U.S. Chamber of Commerce Foundation's Main Street AI Monitor, an Ipsos survey of 1,070 workers at American small businesses, found that among those already using AI at work, [just 6 percent apply it to automate a workflow with minimal human involvement](https://www.uschamberfoundation.org/workforce/half-of-small-business-workers-use-ai-most-to-boost-productivity-not-automate-jobs). Most use it for individual productivity instead.
Adoption is close to universal in both countries. Integration is rare in both. Most businesses are not short of software. They are short of connective tissue between the software they already bought.
6% and 10%
is how far tool adoption actually reaches into operations
Just 6 percent of American small business workers using AI apply it to automate a workflow, and only 10 percent of Canadian small businesses have fully integrated their digital tools. Sources: U.S. Chamber of Commerce Foundation, 2026; CFIB, 2025.
That disconnect has a cost. Asana's [Anatomy of Work Index](https://asana.com/resources/anatomy-of-work) found that 62 percent of the workday is lost to repetitive, mundane tasks, with workers moving between an average of ten applications per day. A good operations consultant is hired to reclaim that percentage, not to add an eleventh application to the stack.
What should you ask before hiring an operations consultant?
Ask questions that force a consultant to reveal their method rather than their pitch. The answers to these six separate diagnostic practices from vendors who have already decided what to sell you.
Six questions worth asking
- Does the engagement begin with a diagnostic, and how long does it take?
- Will the roadmap be usable if we never hire you for implementation?
- Do you build around the tools we already run, or require us to migrate?
- How is the impact of each recommendation measured, and in what units?
- What happens after handoff if something you built stops working?
- Have you ever told a client that automation was the wrong answer?
The last question is the most revealing. A consultant who cannot recall an engagement where the honest recommendation was process change rather than new technology has probably never given one.
Pay attention to how precisely they answer the second question. A roadmap that only functions as an input to their own implementation work is not a deliverable. It is a quote. You should be able to hand it to your internal team or a different vendor and have it remain useful.
What are the warning signs of a poor fit?
The clearest warning sign is a recommendation that arrives before a measurement. If a consultant can describe your solution in the first meeting, they are pattern matching against their last client, not analysing yours.
Signals to take seriously
Forced migration deserves particular scrutiny. Replacing a functioning CRM or project management tool introduces retraining, data migration risk, and months of reduced throughput. Sometimes it is genuinely warranted. It should never be the opening move, and the reasoning should be explained and validated with the people who use the tool daily.
Be equally wary of deliverables described as activities. "Workshops with your team" and "process review sessions" describe how time gets spent, not what you receive. Ask what document lands on your desk at the end, and what decision it lets you make.
Do you actually need automation, or better process?
Often the answer is better process, and a consultant worth hiring will tell you so. Automating a workflow that is undocumented or performed inconsistently does not remove the inconsistency. It encodes it, at speed, and makes it harder to see.
This is why sequencing matters more than tooling. The businesses seeing returns are the ones that fixed the process first. CFIB found that Canadian small businesses average [$1.60 in return for every $1 invested in technology, while digital leaders see $2.40](https://www.lexpert.ca/news/technology-law/only-a-tenth-of-canadas-small-businesses-fully-integrate-digital-tools-in-operations-cfib-report/393488). The difference between those two numbers is not budget. It is integration and readiness.
The Business Development Bank of Canada reports a similar pattern: [only 30 percent of Canadian SMEs used AI in 2025, and those that did were 24 percent more productive](https://www.bdc.ca/en/about/mediaroom/news-releases/bdc-launches-lift-getting-canadian-smes-off-the-ai-sidelines) than those that did not. BDC also estimates overall SME productivity could rise by up to 38 percent at a very high level of digital maturity. Maturity is the operative word. The gains follow the groundwork.
American data points the same direction, and it should settle a common fear. The U.S. Chamber of Commerce found that [82 percent of small businesses using AI increased their workforce over the past year](https://www.uschamber.com/technology/empowering-small-business-the-impact-of-technology-on-u-s-small-business), and 84 percent plan to increase their use of technology platforms. Operations work of this kind tends to expand what a team can take on rather than shrink the team.
If you are unsure which side of that line you are on, our [Automation Readiness Quiz](/automation-readiness) is built for exactly this question, and our [Process Audit Checklist](/process-audit) scores where the structural gaps sit.
How should you evaluate the proposal?
A proposal should be legible before you sign it. You should be able to read it once and know what you receive, when you receive it, what it costs, and how you will judge whether it worked.
What a scoped proposal defines
| Vague | Scoped | |
|---|---|---|
| Named deliverables in a stated format | ||
| A timeline per stage, not open ended | ||
| A baseline measured before work begins | ||
| One success metric per initiative | ||
| A roadmap usable without the consultant | ||
| A defined end point |
A vague proposal describes activities: workshops, reviews, sessions. A scoped one describes what lands on your desk. You should finish reading it knowing what you receive, when, what it costs, and how you will judge whether it worked.
Insist on a baseline. If nobody measures how long invoicing takes today, no one can claim it improved later. The baseline is the single most skipped step in operations work, and its absence is what turns results into opinion.
This matters because sustaining improvement is genuinely hard. McKinsey's survey research on transformations has consistently found that [fewer than one third both improve performance and sustain that improvement over time](https://www.mckinsey.com/capabilities/transformation/our-insights/why-do-most-transformations-fail-a-conversation-with-harry-robinson). Ask directly what the consultant does to land in the third that holds.
How do you measure whether it worked?
Tie every initiative to one number, agreed before work starts. Hours recovered, error rate, cycle time, or throughput. Vague measures like "better visibility" cannot be disproven, which means they cannot be proven either.
Establish the baseline
measure the current cost of the workflow in hours, errors, or delay before anything changes
Define the target
state the expected improvement per initiative, with a number and a date
Measure after handoff
compare against the baseline at a set interval, not by impression
Review on a cadence
schedule the check so that drift gets caught while it is still cheap to correct
The follow-up interval matters as much as the initial build. Workflows drift as teams change, volumes grow, and tools update. An engagement that ends at deployment leaves you to discover the drift yourself, usually after it has cost something.
The short version
Where to go from here
If you are evaluating operations consultants now, the most useful preparation is knowing where your own gaps sit before anyone tells you. That way you can judge whether a consultant's diagnostic confirms what you already suspect or surfaces something you missed. Both are informative. Only one is worth paying for twice.
You can read how our own three stage process works on our [services page](/services), see the specific deliverables each engagement produces on our [results page](/results), and review engagement structure and timelines on our [what to expect page](/investment). For related reading, [What Does an Operations Consultant Actually Do?](/blog/what-does-operations-consultant-do) covers the role itself in more depth, and [5 Signs Your Business Operations Are Costing More Than They Should](/blog/signs-operations-costing-too-much) helps you decide whether the timing is right.
Norithm works with established businesses and growing teams across Canada and the United States. Every engagement begins with a conversation and a diagnostic, and the roadmap that follows stands on its own whether or not we build it. If that is the way you want to work, [get in touch](/contact).