Ask an ISV about partner enablement and you will hear about the portal: the deck library, the certification path, the battle cards, the LMS nobody has logged into since onboarding week.

Ask a VAR seller what they know about that same ISV and you get one sentence. Sometimes it is even accurate.

That sentence is your real enablement. Everything else is shelf inventory.

The one-sentence test

Here is the exercise I run in every enablement audit. Call three sellers at your most active partner and ask each one: when do you bring us into a deal?

If the answers match and they are right, your enablement works, whatever it looks like. If you get three different answers, or worse, three variations of "when the customer asks for it," no portal refresh will save you.

The goal of enablement is not knowledge transfer. It is a trigger installed in a busy seller's head: when I see X in a deal, I call these folks. One trigger, correctly installed across a partner's sales floor, outperforms a forty-slide certification.

Why the portal model fails

VAR sellers carry the core ERP plus a dozen add-on products from vendors who all built portals. Do the math on attention. Your product gets minutes of their year, not hours.

The portal model assumes the seller will invest study time before the deal shows up. Real sellers work the other way: the deal shows up, and they grab whoever can help them win it. Enablement that works is built for that moment, not for the imaginary study session.

The asset stack that earns its keep

If I could only build four things for a new ISV channel, in order:

  1. The trigger sheet. One page. The three deal signals that mean "call us," the one-sentence pitch, and a cell phone number that answers. Not a form. A number.
  2. The ten-minute demo. Recorded, current, and watchable the night before a meeting. Sellers prep in the car and the hotel room. Meet them there.
  3. A deal-support promise. "Bring us in and we run the product conversation; you keep the relationship." VAR sellers fear two things: looking dumb in front of their customer, and losing the account to a vendor. Kill both fears explicitly and repeatedly.
  4. A win story from their world. Not a logo slide. A two-paragraph narrative: the customer looked like this, the deal was stuck on that, here is what closed it and what the partner earned. Sellers retell stories. They do not retell feature grids.

Everything else, the certifications, the tiers, the co-branded decks, comes later, if ever, and only when partners are asking for it.

Enablement is a rhythm, not a launch

The pattern I see everywhere: enablement happens once, at signing, delivered to whoever attended the kickoff. Eighteen months later that person has changed jobs and the partner "knows nothing about us."

Partner sales floors turn over constantly. Enablement has to be a standing rhythm: a short quarterly touch with each active partner's sales team, run around live and recent deals, not curriculum. Fifteen minutes on a Monday sales call beats a scheduled training webinar every time, because attendance is real and the context is money.

This is also, quietly, the best qualification tool you have. A partner who will not give you fifteen minutes a quarter with their sellers has told you exactly where you stand on their priority list. Spend your energy on the ones who say yes.

Measure the only thing that matters

Portal logins, certification completions, and content downloads are activity metrics. They measure your effort, not your channel.

The number that matters is partner-sourced pipeline: deals that exist because a partner seller pulled you in. If that number is zero, your enablement has not worked yet, no matter what the dashboard says. If it is growing, whatever scrappy, unscalable thing you are doing is the right thing. Keep doing it and resist the urge to replace it with a portal.