Publicité
ERP IMPLEMENTATION
🇫🇷 Lire en français →

ERP Vendor, Specialist Partner or Systems Integrator: Who Should Run Your ERP Project?

Vendor services, specialist partner or large systems integrator: three ERP implementation models compared, with a pick by company profile, 10 pitch questions and common mistakes.

ERP Vendor, Specialist Partner or Systems Integrator: Who Should Run Your ERP Project?

Once leadership has chosen an ERP, or even before, a second question comes up: who is going to implement it? Three families of partners are ready to answer. The software vendor with its own professional services, a specialist implementation partner, or a generalist systems integrator (SI), sometimes a Big Four-style consultancy. All three will promise “proven methodology” and “certified consultants”. They are not equivalent, and above all they do not serve the same interests.

This article compares partner types, not their scoring, their contracts or their geography. To score candidates, see our scoring framework for choosing an ERP integrator. For the contract mode, see our article on fixed price, time and materials and outcome-based commitments (in French). For team location, see our onshore, nearshore, offshore comparison (in French). Here the question comes earlier: which partner model suits which kind of company.

The honest verdict: there is no universal model. There is a model that fits your size, your product, your industry and your ability to steer a project.

Three Models, Three Economic Logics

Before comparing skills, look at who gets paid and how, because that shapes the advice you will receive.

ModelMain revenue sourceWhat the model rewards
Vendor directLicences or subscriptions, services on topProduct adoption, staying within standard, renewal
Specialist implementation partnerConsulting and configuration days, sometimes licence resale with a marginDepth on one product or industry, repeat clients
Generalist SI, large consultancyBillable days across large teams, often multi-technologyVolume, team size, ability to cover a broad scope

None of these logics is dishonest. But each creates a predictable bias. The vendor wants the project to stay inside the standard of its product, which is healthy until your business needs a deviation. The niche integrator wants to see you again: it looks after the relationship, but may depend on a single vendor and will therefore recommend that product. The SI, paid by time spent, has no natural reflex to reduce the number of days unless the contract pushes it to.

A useful point of vocabulary: at most large vendors, the bulk of projects are delivered by partners, not by the vendor. Vendor services typically step in on strategic accounts, new product launches, or very recent products. Always ask this explicitly rather than assume.

The Vendor-Direct Model (Professional Services)

What it offers

The vendor knows its product better than anyone: the roadmap, the undocumented limits, the fixes in preparation, the right contact in level 3 support. When a blocker comes from the software rather than from your configuration, the resolution loop is the shortest.

In practice the vendor is also the most aligned with best practice for its own product: predefined deployment templates, migration tooling, documented methodology. On standardised cloud offerings it often provides structured implementation paths.

Its limits

  • Industry knowledge is generally shallower than that of an integrator specialised in your sector. The vendor knows how the product works, not always how your shop floor or branch network works.
  • Staff availability is constrained. Vendor services teams are sized for priorities that are not yours. A mid-sized customer sometimes comes after a strategic account.
  • Dependency compounds. You already depend on the vendor for the licence, the roadmap and pricing. Giving it the implementation too concentrates everything in one counterpart, which weakens your negotiating leverage. Our article on vendor lock-in and reversibility details this mechanism.
  • Advice is not independent. A vendor will not tell you its product is unsuited to a given process, or will tell you late.

Typical cases

The vendor-direct model works well for a very standard deployment of a recent cloud product, for a first customer on a new release, or for a customer large enough to carry weight in the relationship. It works poorly when your project requires many industry-specific adaptations.

The Specialist Implementation Partner

What it offers

The implementation partner specialises either by vendor (a firm that only does Business Central, Odoo or SAP Business One), by industry (food processing, wholesale, distribution, services), or both. This is sometimes called an “ERP boutique”.

Its strength is depth of experience: it has already met your problems at customers close to you. It brings preconfigured templates, industry extensions, sometimes a vertical product built on the ERP. Teams are more stable and contacts more senior throughout the project than in large firms, which is an advantage, provided you get it written into the contract.

Its limits

  • Size and resilience. A small firm may depend on a few key people. If the project director leaves, the project wobbles. The integrator’s financial health matters as much as the vendor’s.
  • Limited geographic coverage. For a multi-country rollout, a niche integrator rarely has local teams everywhere and must subcontract or partner.
  • Vendor dependency. An integrator closely tied to one product may struggle to tell you another product would suit you better. Ask what share of its revenue comes from outside that vendor.
  • Partner status. Partnership tier and certifications should be checked with the vendor, not on the integrator’s website.

Typical cases

This is generally the best expertise-to-price ratio for an SME or mid-market company that has already chosen its product and whose business is fairly specific. It is also the natural model for vertical projects, where industry knowledge matters more than team size.

The Generalist SI and the Large Consultancy

What it offers

The generalist SI or large consultancy brings capacity: quickly mobilising many profiles, covering several countries, technologies and functions under one contract. For a group that must deploy in parallel across several subsidiaries, this coordination capacity is hard to reproduce any other way.

It also brings industrialised programme governance: PMO, risk management, standardised reporting, large-scale change management tooling. These arrangements reassure an executive committee and a board.

Its limits

  • Day rates are generally higher than at a niche integrator, and the team pyramid often includes more junior profiles than the commercial proposal suggests.
  • Product depth is uneven. An SI covers many technologies. On a specific product, the senior consultant in the proposal is not always the one who shows up at kick-off. Have people named, not profiles.
  • Team rotation can erode project memory.
  • The volume conflict of interest. The bigger the team and the longer the project, the higher the revenue. The contract must therefore align fees with your objectives.

Typical cases

Multi-country groups, programmes spanning ERP, infrastructure, integration and change management, customers whose procurement rules require a tier-1 provider. Conversely, for an SME the sizing is often disproportionate.

Comparison Table

This table is deliberately qualitative. Day rates vary widely by product, country and seniority, and we do not quote ranges we cannot source: ask for rate cards per profile in your own consultations.

CriterionVendor directSpecialist integratorGeneralist SI
Product expertiseMaximum on its own softwareStrong on one or two productsVariable, depends on assigned team
Industry knowledgeAverage, standard-orientedStrong if sector-specialisedBroad, sometimes superficial per sector
Day rateOften highGenerally the most competitiveOften high, pyramid effect
Staff availabilityConstrained by vendor prioritiesGood at small and mid size, limited at large volumeStrong ability to scale up
GovernanceAligned with vendor methodLight, direct, depends on individualsIndustrialised, formal PMO and reporting
Dependency riskHigh: licence and project with the same partyMedium: depends on a few people and one vendorMedium: depends on team volume, but replaceable
Multi-country projectsPossible on its own subsidiariesLimited unless partner networkCore strength

Quick read: the vendor wins on product, the niche integrator on industry fit and value, the SI on scale. Nobody wins on every criterion.

Recommendation by Profile

SME with 50 to 200 employees. Specialist integrator, almost always. An SME does not need a large-account PMO and lacks the weight to get the vendor’s attention. It needs a senior, stable team that knows its sector. Check the integrator’s solidity and write replacement of key people into the contract. In return, the SME must name an internal project manager who is genuinely available.

Industrial mid-market company. An integrator specialised in both the product and the industry, possibly with occasional vendor support on tricky technical topics. If the company has several plants in several countries, a niche integrator alone may show its limits, and a mixed model becomes relevant (see below).

Multi-country group. SI or large consultancy for programme coordination, with local or specialised integrators on specific work packages. The risk here is signing one giant contract that strips you of leverage. Split into lots and keep control of the architecture.

S/4HANA migration project. The topic combines very deep product expertise with programme governance. The SAP ecosystem has partners of every size, and the choice depends on migration strategy: greenfield, brownfield or selective data transition do not require the same skills. Our S/4HANA decision guide helps you decide before choosing the partner. As a rule, favour a partner that has run several migrations comparable to yours, whatever its size, and insist on references you can call.

Vertical project. Industry integrator, without hesitation, or the vendor if it is a vertical vendor. An industry ERP (wholesale, construction, healthcare, services) rests on practices that only players in that sector master. The generalist SI will be less relevant, except for a programme layer.

Mixed Models: Independent Owner’s Advisory and Integrator

By far the most protective model for the customer on large projects is the mixed model: an independent owner’s advisory (project assurance) firm that advises, challenges and controls, and an integrator that delivers.

The advisor provides what the integrator cannot honestly provide: an opinion on scope, deliverable quality, schedule and invoicing, with no interest in selling more delivery days. It helps you write the requirements, run acceptance testing and arbitrate at the steering committee. To structure this governance, see our weekly steering committee template (in French).

Conflicts of interest to guard against:

  • Advisory and delivery in the same group. If the firm advising you belongs to the same group as the integrator, or earns commissions from the vendor or the integrator, its independence is compromised. Ask in writing for the list of capital and commercial ties.
  • Selection advice paid by the chosen vendor. The firm helping you select an ERP must not be paid, directly or indirectly, by any of the candidates.
  • Integrator reselling licences. An integrator earning a margin on the licence has an incentive to sell more modules or users. Demand transparency on that margin.
  • Vendor imposing its partner. Some vendors steer you to “their” integrator. You have the right to compare.

The cost of an independent advisor is a real budget line and is not justified for every project. For an SME deploying a standard ERP, a strong internal project manager is often enough. For a multi-country programme or a critical initiative, it pays for itself through the overruns it avoids.

Ten Questions to Ask at the Pitch to Tell the Models Apart

  1. What share of your revenue comes from this vendor, and from which other products?
  2. What margin do you make on licence resale, and how do you disclose it to the customer?
  3. Who are the named people on my project, and what happens if one of them leaves?
  4. What is your partnership tier with the vendor, and can I verify it with them?
  5. Name two customers of comparable size and sector that I can call.
  6. For what type of specific need would you advise not using this product?
  7. Which deviations from standard do you advise against, and how do you limit them?
  8. How does your remuneration change if the project finishes earlier or later than planned?
  9. How much of the work is done by your own teams, and how much by subcontractors?
  10. How do you organise reversibility: documentation, knowledge transfer, access to configurations?

These questions reveal the real model behind the brochure. The vendor answers 4 well and 6 poorly. The niche integrator answers 5 and 7 well, and 9 poorly if it subcontracts. The SI answers 8 well if the contract is well worked, and 3 with more difficulty.

Five Common Mistakes and Countermeasures

1. Confusing the choice of vendor with the choice of partner. Many committees pick a software product and then take the first partner suggested. Countermeasure: run a separate selection for the partner, with at least three candidates, including two different models.

2. Choosing size for reassurance. A large firm reassures a committee, but the team assigned to your project is what counts. Countermeasure: assess the named team, not the brand, and require stability clauses for key profiles.

3. Picking the lowest day rate. A low rate with junior consultants and a high number of days costs more than a high rate with efficient seniors. Countermeasure: compare the total project cost and team composition, not the unit rate.

4. Delegating governance to the partner. Whatever the model, the customer remains responsible for scope decisions, data, business arbitration and change management. Countermeasure: an executive sponsor, a dedicated internal project manager, named process owners, a regular steering committee.

5. Ignoring conflicts of interest. Vendor commissions, licence margins, an advisory subsidiary of the same group: rarely visible at the start. Countermeasure: a clause requiring disclosure of ties and remuneration, and a genuinely independent advisor on sensitive projects.

Key Takeaways

The vendor offers product mastery, the specialist integrator industry knowledge at a fairer cost, the SI the ability to coordinate large programmes. For most SMEs and mid-market companies, the specialist integrator is the strongest starting point; for multi-country groups, a mixed model with an independent advisor best protects your interests. In every case, it is your governance that makes the project succeed, not the partner’s label.


To compare your candidates on objective criteria, download our 100-point integrator scoring grid and apply it to the three models side by side.