How to Choose an Odoo Implementation Partner

Quick answer: for an Odoo implementation, buy depth in the product. The decisions that cost money are configuration decisions inside one system, and no amount of project governance makes a wrong one right. Buy breadth instead when the platform is unchosen, when several systems move at once, or when the constraint is coordinating vendors rather than configuring software.

Local Context

Calgary’s shortlist for an ERP project usually contains two kinds of firm, and they are not competing on the same axis.

Calgary is also a specific market rather than a generic one, and two local facts should shape how a buyer weighs the shortlist. Statistics Canada’s business counts for the Calgary CMA (businesses with employees, July 2025) record 786 businesses in mining, quarrying and oil and gas extraction, which is 1.2% of the local base against 0.1% in Toronto. Professional, scientific and technical services account for 11,708 businesses, 17.8% of the base and the highest share of any major Canadian metro. Manufacturing is comparatively thin at 1,688 businesses, 2.6%.

So the Calgary ERP conversation is disproportionately about services delivered in the field and billed against a job, and comparatively less about a production line.

One argument that works elsewhere does not work here, and it is worth saying plainly. Alberta has no provincial sales tax, and Odoo’s Canadian localisation ships default fiscal positions per province including Alberta. Provincial tax configuration is a genuine differentiator for a British Columbia buyer. In Calgary it is close to a non-issue, and a firm making a lot of noise about it is selling you something you already have.

Why ERP Implementation Is a Depth Problem

An implementation is a few hundred configuration and data-mapping decisions, each with a correct answer that exists inside the product’s own semantics, and most with consequences that first surface at month-end, at year-end, or at the first upgrade.

Three properties follow from that, and they are the whole argument.

Governance can confirm a decision was made. It cannot make the decision correct. Stage gates, sign-offs and a steering committee produce a record that someone approved the inventory costing method. They contain no mechanism for knowing which method was right. That correctness sits entirely with whoever proposed it.

The failure mode is late and expensive to reverse. A coordination failure produces delay, which is costly, visible while it happens, and recoverable. A configuration failure produces a system computing wrong numbers, found after months of transactions have settled on top of it, and unwound at a cost proportional to how long it ran.

Depth is the one thing on the shortlist you cannot buy separately. Platform selection can be bought from a neutral advisor. Programme management can be bought from a prime contractor. Infrastructure and the service desk can stay with an MSP. Each is a distinct contract with a distinct deliverable. Product depth resists that split, because the person deciding and the person configuring are performing a single act.

The Customization Question, and Why It Is a Cost Question

Every implementation reaches a request the product does not answer natively. At that moment two firms can produce the identical output, a quoted custom module, out of opposite internal states. One knew the native mechanism and judged it insufficient. The other could not find it. The client cannot tell those apart in the room, and the invoice looks the same.

The consequence arrives years later and it is documented. Odoo’s upgrade documentation states that a database containing custom modules cannot be upgraded until a version of those modules is available for the target version. Odoo provides standard support for each major version for three years, after which extended support carries a mandatory additional fee.

Put those together and every custom module is a recurring bill on a three-year clock, paid for as long as the system lives. A configuration decision made in week six by someone who did not know the native path starts that annuity, and nobody in the room hears it start.

This is why the most useful question in the whole evaluation is about customizations a firm talked a client out of.

The Decisions That Hurt Look Operational and Are Financial

The expensive mistakes are settings that appear to be operational housekeeping while silently governing a financial outcome.

A concrete, checkable example. In Odoo 19, costing method sits on the product category, one level above the product itself. Odoo’s documentation states that to apply a landed cost to a vendor bill, products in the original purchase order must belong to a product category with a costing method of either AVCO or FIFO. Leave a category on standard cost and landed costs cannot be applied at all. An importer who discovers this after go-live has been valuing inventory wrong for however long the system ran, and the correction reaches into closed periods.

No methodology surfaces that. Product knowledge surfaces it in the discovery call, before anyone has spent money.

Where a Generalist Consultancy Is Genuinely the Right Call

These are real, and a buyer who ignores them will make a worse decision rather than a better one.

The platform is not chosen yet. A firm that implements one product should not run your selection. The conflict is structural and disclosure does not cure it, because the shortlist is shaped by what the firm can deliver. Pay a platform-neutral advisor separately for that.

Several systems are changing at once. When the ERP goes in alongside a WMS replacement, a CRM migration and a payroll switch, the binding constraint is sequencing across vendors who each want to go last. Nobody has product depth in all of them. A firm whose competence is running multi-vendor programmes should be the prime contractor, with the specialist underneath it.

There is no internal IT function. An MSP running endpoints, identity, network, backups and a staffed service desk, which also takes ERP tickets, gives you one contract and one number to call at 6am. That consolidation has real value for a company with nobody internal to own the seams.

The real problem is organisational. Three business units run three incompatible processes and nobody has the authority to pick one. Large consultancies are good at this and carry political weight a boutique cannot borrow. Configuring beautifully around an unresolved political dispute produces a system nobody adopts.

Procurement gates you cannot waive. Minimum insurance limits, SOC 2, audited financials, an approved vendor list. A small firm fails these on paper regardless of merit, and that is a legitimate win for the larger firm.

Continuity. A boutique is a concentration bet on specific people. If the person who configured your general ledger becomes unavailable, a large firm reassigns and a small one stops. Ask what the mitigation is and weigh it honestly.

Every case above has the same shape: the binding constraint sits outside the product. Breadth is the correct purchase whenever the constraint is the number of parties. Once the platform is chosen and configuration is the work, the constraint has moved inside the product.

A Note Specific to Calgary

The argument against a generalist in Calgary is not that they are far away. Several national consultancies maintain Calgary offices, and one of the largest lists two locations in the city on its own site.

The question is different here, and it is about which buyer the delivery bench is configured for. A practice built around a downtown head office with a corporate programme budget is a real capability, and it is calibrated for a scale of governance a 40-person energy services company operating between that head office and the field cannot absorb. Workstream leads, a PMO, stage gates and formal deliverable sign-off are proportionate on a large programme. Applied unchanged to a mid-size company, that governance layer is funded out of the same budget that would otherwise buy configuration and data hours.

That is a scale mismatch and not an accusation. Good firms scale the method down deliberately. The buyer’s job is to check whether this one did, by counting the named roles in the proposed team and asking what each produces that the client will actually use.

Seven Questions That Separate Depth From a Service Line

Run these on every firm on the shortlist. Each has an answer a firm with real depth gives immediately.

1. How many Odoo implementations have you completed, and how many are live and running a client’s business today? Two numbers, the second smaller, with the gap explained. A combined ERP count that does not split by product is answering a different question.

2. Name the person who will configure our chart of accounts and inventory valuation. What were their last three Odoo projects, and what else are they on during ours? A name, a percentage of their week, three projects. “We assign the right resource at kickoff” means the answer does not exist yet.

3. Tell me about the last three customizations you talked a client out of, and the native mechanism you used instead. Three specific stories naming fields, models or settings. This one cannot be answered without the underlying knowledge, which is why it is the most useful question on the list.

4. What in Odoo have you been burned by? A specific limitation, with a version number, that cost them something. Depth carries scar tissue and can describe it. Unbroken praise is the finding.

5. On your last five Odoo projects, what was the estimate at signing and what was the final invoice? A spread, and at least one overrun with a named cause. Five for five on budget means the numbers are either not kept or pre-padded.

6. For clients you implemented two or more years ago, how many are on a currently supported version today, and who paid for the upgrade? Odoo supports each major version for three years, so this tests whether their configuration choices survived contact with a release.

7. What would make you tell us Odoo is the wrong answer? A real disqualifying case they have walked away from. A firm that has never turned a deal away on fit has no fit criteria and will not apply one to you.

What This Guide Does Not Tell You

There is no reliable public dataset comparing specialist and generalist ERP outcomes, and the widely circulated ERP failure statistics do not survive a search for the study behind them. Nothing above rests on one. The argument is built from mechanism and from questions a buyer can ask directly, because that is what survives being repeated back to a competing firm.

Odoo’s Canadian partner directory lists partners nationally without exposing a city facet, so this guide does not state how many Odoo partners operate in Calgary. That number would require opening each partner record individually, and it is not published anywhere in aggregate.

About the publisher

Calgary Biztech is published by Solvync Inc., an Odoo implementation partner based in Calgary, Alberta.

That places the publisher inside one of the two categories this guide compares, so weigh it accordingly. The seven questions above are the ones to run on Solvync exactly as you would on any other firm on the shortlist, and a firm unwilling to answer them has told you something useful.

Related Reading

• Calgary Business Software Planning Guide covers sequencing a software decision before a partner is chosen.
• Field Service Software: A Calgary Buyer’s Guide covers the tool category itself.