Directory · how the market works

How the ERP partner channel actually works

Most mid-market ERP reaches customers through implementation partners rather than from the vendor, and that structure shapes the software, the pricing, and the outcome of your project. It is worth understanding before you evaluate anything.

Evaluating a partner-led product?

Send the proposal. We will tell you what the channel structure means for that specific quote.

1 / 3
We are not a partner for anyoneNo referral fees takenWe sell direct and compete

The economics

Six structural facts, none of which are secrets.

None of this is hidden and very little of it is discussed with buyers. It is simply how the channel is built, and knowing it changes what questions are worth asking.

Partners earn on services, not licence

Licence margin to a partner is typically 10–20% and recurs thinly. Implementation is billed at full rate. That ratio determines what a partner optimises for and it is not a criticism, it is arithmetic.

Configurability is a channel requirement

A product sold through partners must be adaptable to any customer, which pushes against opinionated defaults. That is a large part of why implementations take months rather than weeks.

Vendors do not control delivery

Acumatica, Business Central, and Sage Intacct sell nothing directly at this tier. Your experience of the product is largely your experience of one firm the vendor does not employ.

Certification measures the wrong thing

It tests product knowledge. Three quarters of the stalled projects we examined failed on requirements, data, or decision authority — none of which certification assesses.

Quality varies more than product does

Across the projects we have been called into, the spread between a strong and a weak partner exceeded the spread between the mid-market products they implement.

Referral fees are usually undisclosed

Most independent ERP selection consultancies take fees from vendors they recommend. It is legal, common, and rarely disclosed clearly enough to weight.

Why the channel exists at all

It is a rational structure, not a flaw. Mid-market ERP serves businesses that differ enormously from each other, and a vendor cannot maintain implementation capacity across every industry, region, and business shape. Partners provide that reach and carry local and vertical knowledge a vendor could not.

The good version of this is real: a partner who has deployed thirty times in your industry knows things no vendor documentation contains. The problem is not the model, it is that buyers evaluate the product carefully and the partner casually, when the second predicts the outcome better.

Buyers spend three months evaluating the product and three meetings evaluating the partner. The second choice predicts the outcome better than the first.

What the services-margin structure produces

When a partner earns most of its revenue from implementation hours, the incentive on scope runs one direction. That does not make partners dishonest — most are not — and it does mean that a shorter, simpler implementation is worse for them than a longer one, and nobody in the room has an interest in raising that.

The practical response is a fixed-scope contract with a written exclusions list, a discovery-failure allocation, and a phase gate you can exit at. Those terms shift the incentive without requiring anyone to be virtuous.

Referral fees and the independence problem

Most firms marketing themselves as independent ERP selection advisers take referral fees from the vendors they recommend. It is standard practice, it is legal, and it is disclosed rarely and vaguely.

The question to ask any adviser before the first meeting is simply how they are compensated and by whom. The answer is informative regardless of what it is; the unwillingness to answer plainly is more informative still.

Our own model, stated

We sell direct and implement our own product. There is no partner channel, no referral fee flowing in either direction, and no third party between us and a customer. That means one relationship rather than two and no ambiguity about who is responsible when something does not work.

It also means real limitations, and they are the mirror image of the channel’s strengths. We have no partner network, so we have no local presence, no vertical specialists in industries we have not worked in, and no capacity buffer when demand exceeds our team. A well-established Acumatica or Business Central partner in your city with thirty deployments in your industry is offering something we cannot.

We think the trade is right for the customers we serve, and it is a trade rather than a straightforward advantage. Anyone telling you their go-to-market model has no downside is describing marketing rather than economics.

Where our bias sits on this page

We compete with implementation partners — we implement our own product and we are paid to rescue projects theirs did not land. A page explaining why the partner channel has structural problems is a page that helps us. The check on it is that we state our own model’s weaknesses in the same detail, and that everything here is verifiable by asking any partner directly.

Questions

Common follow-ups.

Is the partner channel bad?
No. It is a rational structure that gives vendors reach and buyers access to vertical and local expertise. The problem is that buyers evaluate the product carefully and the partner casually.
Do you take referral fees?
None, from anyone, in either direction. We sell direct and implement ourselves, which has real disadvantages we state on this page.
What is the biggest weakness of your model?
No partner network. That means no local presence, no vertical specialists in industries we have not worked in, and no capacity buffer when demand spikes.
How do I check an adviser’s independence?
Ask how they are compensated and by whom, before the first meeting. The answer is informative whatever it is; reluctance to answer plainly is more informative.
Should we avoid partner-led products?
No. Acumatica, Business Central, and Sage Intacct are good products. Evaluate the partner with the same rigour as the software and negotiate the terms rather than the rate.

Evaluate the partner like the product.

For partner-led systems the firm delivering it predicts your outcome better than the software does.