Your partners are winning deals. But who's tracking adoption?

A few years ago, I sat in on a quarterly business review for a mid-market software vendor that sold almost entirely through resellers. Sales walked the room through pipeline and bookings.

Then someone from customer success asked a simple question: "Do we actually know if these customers are using the product?" Nobody had a good answer.

The partners owned the relationship; the vendor owned the roadmap, and whether the product was actually landing lived somewhere between the two, unclaimed by either.

That gap is more expensive than most vendors realize, and it is only getting bigger. A 2026 survey of more than 150 B2B software leaders found that channel and partnership revenue climbed from 21% to 31% of all B2B software revenue in a single year, while direct sales fell from 73% to 57%.  

More of your revenue is moving through partners every year. Adoption, the thing that determines whether that revenue renews, is the part you have the least visibility into.

This is not a partner problem. It’s a vendor problem in disguise. If you don't address it, partners will naturally prioritize the products that make customer success easier, whether those products are yours or a competitor's. 

The adoption challenge hiding inside your channel strategy

Vendors who sell directly can see engagement trends, training participation, and health indicators as they happen. Once a partner owns the relationship, that visibility mostly disappears. I call this the adoption gap, and it is not a sign that partners do not care. It is a sign that adoption does not scale the way certification does.

Every partner runs its own processes and level of expertise. Some deliver exceptional onboarding. Others stop at implementation and call it done. Two customers can buy the identical product and land in completely different places, depending only on which partner closed the deal, which leaves vendors unable to forecast retention or expansion with any confidence. 

Why traditional partner enablement falls short

Most partner programs are built around partner readiness: certifications, product knowledge, sales training. All of it matters, and none of it covers what happens after go-live, when customers keep hiring, products keep shipping features, and the need for enablement never really ends.

Most organizations still treat customer education as a single event instead of an ongoing one. That mismatch creates a predictable cycle: an intensive onboarding push, a plateau a few months later, another round of retraining.

I have watched vendors pour enormous effort into onboarding only to see adoption flatten by month six, simply because nothing existed to sustain it after the launch celebration ended. 

Consistency and personalization are two sides of the same problem

Partners naturally adapt vendor content to fit their own business, which is often a good thing. It also means a customer's understanding of the product depends heavily on which partner they work with. Use cases get skipped, features go unmentioned, and best practices get lost between the vendor's deck and the partner's version of it.

At the same time, a finance leader does not need the same content as a customer success manager, and a power user does not need what a first-time user needs. Most partner programs still hand every audience the same one-size-fits-all library.

Customers do not adopt a product because they sat through training. They adopt it because they understand how it helps them succeed in their specific role, and that has to be built consistently and personally, at scale, no matter which partner is doing the building. 

The best channel programs think like ecosystems

The organizations winning the channel game right now are not trying to control every customer interaction. They are building shared infrastructure that partners plug into, instead of handing over assets once and leaving partners to interpret them. In practice, that means:

• Co-branded, not just handed off. Give partners enablement content they can put their own name on but build it on a shared foundation, so the core product story stays intact no matter who is delivering it.

• Journeys, not events. Replace one-time onboarding decks with structured learning paths that keep reaching customers at 30, 90, and 180 days, tied to the moments they are most likely to stall, not just the week they went live.

• Shared visibility. Give both the vendor and the partner a common view into who has adopted what, so a stalling account gets caught by whoever notices first instead of falling into the space between two teams.

• Built-in feedback loops. Have partners flag where customers get stuck so that feedback improves the next version of the enablement content, instead of every partner rediscovering the same gaps on their own. 

Underneath all four is the same balancing act: consistency for the vendor, flexibility for the partner. Force rigid delivery and you lose partner buy-in. Hand off content with no shared framework and you lose consistency. The programs that work hold both at once, and that is a deliberate design choice, not something that happens by accident. 

Scaling adoption without scaling headcount

Better adoption does not require a bigger customer success or education team. The real opportunity is building systems that scale expertise instead of headcount: adaptive learning paths, in-workflow nudges, and behavior-based interventions that reach a customer the moment they are stuck, not three weeks later in a scheduled session. 

The goal was never more training. It is more customers who actually get value, and when that happens, retention, expansion, satisfaction, partner success, and revenue growth all move together.

Final thoughts

If your growth strategy depends on partners, your adoption strategy has to depend on partners too. Too many organizations pour investment into scaling sales through the channel while leaving adoption to whichever partner happens to care most.  

The vendors that stand out treat customer education as a shared growth engine between vendor and partner, not a support function that gets bolted on after the deal closes. Build the shared infrastructure, and partners differentiate, customers succeed, and adoption ends up scaling exactly as reliably as revenue does.

Keep exploring

Where this plays out first is usually the structure of the partner relationship itself, whether that runs through channel resellers, service providers, or systems integrators.  

From there, it becomes a question of what a shared education framework actually looks like day to day, which is where our thinking on customer education and product adoption picks up. 

Connect with the author on LinkedIn: Casey Trujillo | LinkedIn