Most ISVs think about ERP publishers the way they think about app stores: get listed, get certified, wait for distribution.

Then the marketplace listing goes live, nothing happens, and eighteen months later the ISV concludes the ecosystem "doesn't drive deals."

The listing was never the product. The publisher's field organization is the product: channel managers, territory reps, and solution engineers who talk to partners and customers every day and who decide, deal by deal, which ISVs get mentioned in the room. I spent years inside those conversations. Here is how they actually work.

What a publisher's field team cares about

A channel manager at a mid-market ERP publisher carries a number. Partner sourced revenue, platform seats, migrations, some mix. They mention your product when it helps that number, and not otherwise.

That gives you exactly three ways to matter:

  • You unstick their deals. A gap in the platform's story is losing deals in a vertical, and your product closes that gap. This is the strongest position in ecosystem life.
  • You bring deals to the platform. Your product's buyers sometimes arrive before an ERP decision is made, and you influence it. ISVs who send the publisher net-new logos become famous with field teams fast.
  • You make their partners richer. Your product adds services and margin to partner deals, and partners say so out loud where channel managers hear it.

Certification and marketplace fees buy you eligibility. Only those three buy you advocacy.

Relationships are territory-level, not corporate

ISVs love the top-down motion: get a meeting with the VP of channels, sign an alliance agreement, expect the field to follow. The field does not follow. Alliance agreements do not carry quota.

The motion that works is bottom-up. Individual channel managers, in individual territories, learning through repetition that deals go better when you are in them. That means showing up: their partner events, their QBRs when invited, the deals they ask for help on, even the unglamorous ones. Do this in two or three territories until the results speak, and the corporate conversation eventually comes to you.

This is slow, and it compounds. The reps rotate, get promoted, move to other publishers, and take their opinion of you along. A decade of that and you are getting introductions from people you first helped two ecosystems ago. There is no shortcut, which is precisely why it is defensible.

The reciprocity ledger

Every publisher relationship runs on an unwritten ledger. Introductions received, deals brought, favors done, events supported. ISVs who only withdraw, always asking for leads, intros, and stage time, get quietly deprioritized.

Cheap deposits that ISVs consistently skip:

  • Register and attribute deals honestly, even when you could take the direct path
  • Hand the publisher a win story they can use internally, written for them
  • Show up to the regional event that isn't worth it on paper
  • Flag competitive intel from the field to your channel manager first

None of this is complicated. It is just consistency, which is rarer than strategy.

When you have no relationships yet

A newer ISV without ecosystem history has to buy its first entries honestly: pick one publisher, one region, and go be physically present. Sponsor the partner roadshow. Work the room without pitching. Find the two channel managers whose territories fit your best-fit customer and offer help on a live deal with no strings.

One genuinely helpful deal is your first ledger entry. Everything builds from there.

What does not work is spreading thin across four ecosystems at once, attending nothing, and running "partnerships" from a CRM sequence. Publishers can tell tourists from residents, and they route their trust accordingly.